AntonioK's questions

I have some script with STDOUT and STDERR output. By default, both STDOUT and STDERR goes to console:

./script.sh

I can redirect STDOUT to file, leaving STDERR output in console:

./script.sh > log.txt

I can redirect both STDOUT + STDERR to same file with no output in console:

./script.sh > log.txt 2>&1

I can have both STDOUT and STDERR in console and logfile simultaneously:

./script.sh 2>&1 | tee -a log.txt

I don't want to see STDOUT, but I want to see STDERR, and I have to save everything in logfile. How could I have STDERR in console + logfile, while STDOUT in logfile only? Something like (pseudo-code, doesn't work):

./script.sh > log.txt 2 > /dev/tty | tee -a log.txt

Everyone who deal with PC and servers assembling knows how does the screw to connect HDD with chassis (tray) looks like.

But how to name it correctly? Is it M3.5 screw or what?

I'm trying to add the second administrator to IPMI:

$ ipmitool -I lanplus -H $ip -U ADMIN -P $passw user list
ID  Name             Callin  Link Auth  IPMI Msg   Channel Priv Limit
2   ADMIN            false   false      true       ADMINISTRATOR
6   TESTUSR          true    false      false      ADMINISTRATOR

I could login into web-ui and act as administrator using TESTUSR, but when I'm trying to use it with ipmitool - it don't work as planned:

$ ipmitool -I lanplus -H $ip -U ADMIN -P $passw chassis status
System Power         : on
Power Overload       : false
Power Interlock      : inactive
Main Power Fault     : false
Power Control Fault  : false
Power Restore Policy : previous
Last Power Event     : 
Chassis Intrusion    : inactive
Front-Panel Lockout  : inactive
Drive Fault          : false
Cooling/Fan Fault    : false

$ ipmitool -v -I lanplus -H $ip -U TESTUSR -P $passw chassis status
Get Device ID command failed: 0xd4 Insufficient privilege level
Get HPM.x Capabilities request failed, compcode = d4

Running Get PICMG Properties my_addr 0x20, transit 0, target 0x20
Error Response 0xd4 from Get PICMG Properities
No PICMG Extenstion discovered
Error sending Chassis Status command: Insufficient privilege level

Adding -L ADMINISTRATOR don't changes anything.

Any ideas why one administrator is "better" then the other one?

Let's say I have linux-vm-image.raw with size of 10GB. Inside there is one primary ("classical" MS-DOS-like partition table used, not GPT) etx4 partition (no LVM used), extending to the entire volume. And real data allocated on that partition is, for example, 3GB.

This image is prepared to use for some virtualization environment (kvm+OpenStack in my case), and any VM created from this image would resize itself to target virtual disk size, depending on user's choice. So there are no reasons to keep any free diskspace inside of that disk image.

How could I shrink size of this raw disk image to minimal (from 10GB to ~3GB)?

There are some instructions for qcow2 disk images, but I have to use raw images only - not qcow, not OVF and not others.

My guess is somethink like

• mount this image somewhere as a block device
• do some maintenance to have all files inside of ext4 partition moved to "beginning" of it, another words - do a freespace defragmentation
• unmount image
• minify size of filesystem into image (to match the size of data inside of it)
• minify size of image (to match the size of filesystem inside of it)
• update partition table into image to match new partition size

But don't I try to invent a bicycle? Is there some one-line command or special software to do what I want?

I have a box with SuperMicro X9DRW-iF mainboard. It has built-in BMC module, which provides IPMI interface and web-GUI for it.

After upgrading BMC firmware from R 2.35 to R 2.59 under web-GUI ("Network" and "IPMI" options was checked in "BMC Preserve Configuration" screen, "Preserve all Configuration" option was unchecked) BMC module restarted, accessible via both HTTP and SSH, but rejects my login attempts with default login and password (ADMIN/ADMIN) via both HTTP and SSH.

Before firmware upgrade there was only one user in IPMI - the default one (ADMIN/ADMIN).

Where did I go wrong? What should I do to restore access now? I only guess to re-flash firmware with some Linux stuff on local system on this box, without preserving any BMC config, to bring it generally to factory defaults.

Usually I deal with Linux and other Unix-like OS, but now I have to set up Windows server to run some specific software.

I can't have physical box for it, so I decide to buy and deploy Windows Server 2012 R2 on KVM virtual machine.

Reading licensing documents on Microsoft website I cannot understand, what is the difference between "installation on physical server" and "installation on virtual machine" in WinServer terminology. I phoned Microsoft store support, but they also can't answer me, course they don't know what KVM is =)

So my first question is: when running under KVM, would Windows Server 2012 R2 "think" that it running under virtual, or physical environment?

The second is related - which type of licence ("for physical server installation" or "for VM installation") do I need?

When you deal with Supermicro IPMI/BMC, you could access it via:

• HTTP(S) in your browser - seeing web pages with sensors/configs and java applet to run redirection console
• IPMI protocol (using ipmitool-like CLI or IPMIView-like GUI apps)

Once I discovered I could just ssh [email protected] and get into the BMC - there is Linux-like shell, ifconfig (not with server's, but with BMC's network settings), and - the greatest thing! - ability to tape reboot to reset BMC when IPMI starts glitching.

But now, having access to numerous Supermicro boxes with IPMI, I discover that SSH access works differently: about a half of boxes runs "normal" shell on IPMI's 22 port, other runs the "ATEN SMASH-CLP System Management Shell". It is not Linux-like, not supports standard commands like ls, and I can't reset BMC with it.

Google mainly says of SMASH-CLP in source-of-security-breaches way. Is there any user documentation for it? Or could I make my IPMI/BMC run "normal" shell via SSH, not SMASH-CLP?

I deal with X9DRW-iF, X9DRi-F and X9SCL-F motherboards.

I have numerous D-Link DGS-1500-28 switches with firmware 1.00.013, 1.10.005 and 2.10.002 on it, and there are no visible option to set up date/time via web- or telnet-interface.

Device uses date/time in logs, but there is no idea, where it obtains it from: now it is different days in 2009 for 1.00.013, in 2011 for 1.10.005 and in 2012 for 2.001.006. The date showing is even not 01/01/YYYY + system uptime, as it could seems to be.