TEMPO RUN 4.48 KM IN 29M:33S
Ran 5.46 KM in 28:49
A pretty miserable start to 2014. Wind, rain, and a boiler which keeps cutting out because of the wind….
Current weather: 6degC, showers, wind @ 22mph. Tomorrow: 8degC, mostly sunny, wind @ 12mpg.
Some information I found off the web:
First type:
cat /sys/power/state
If the result line contains “mem”, you can use this to suspend to RAM:
sudo pm-suspend
If the result line contains “disk”, you can also use this to suspend to disk (hibernate):
sudo pm-hibernate
If you have both results, you can use this to suspend with a hibernate backup. In other words, your system will prepare for hibernation, but only suspend, not turn off. This will use a bit of power, but means that it’s faster to resume, and if your battery runs out, it’ll use the hibernate image as backup.
sudo pm-suspend-hybrid
You can pipe the hibernation into a timed job using the at command. This will hibernate in one hour from now
echo 'pm-hibernate' | sudo at now + 60 minutes
And you can confirm the job is present:
sudo at -l
10 Wed Jan 1 12:38:00 2014 a root
Suspend/Hibernate requires root access, hence the reason I did sudo before the at command
Happy New 2014 everyone :)
Life’s not always going to be easy, and there will be days when you feel like giving up, but just keep your head up. Remember that tomorrow is another day and it can always get better.
Just because you have a “Baby on Board” stuck to your rear windscreen does NOT mean you can get away with doing stupid driving manoeuvres. Remember, it’s “mirror-signal-manoeuvre”, and NOT “manoeuvre-signal-mirror”
Had my first encounter of Linux, or specifically, a linux-like environment in a corporate environment. The IT peops were trying to setup an environment on Xenserver, and they had setup a storage space to copy a virtual machine image onto. But they kept running out of space. It took me a while to figure out what they were doing (wrong), though.
They were trying to copy onto the PV partition, and Xenserver had setup its environment to use LVM, so the PV partition was already allocated to the LVM system, and therefore had no space to copy onto.
After figuring out which LV was the one they wanted to use, I had problems mounting, with mount saying I had to specify the filesystem. After trying various switches with mount and specifying a filesystem (only NFS, ext, ext2 and ext3 were supported by Xenserver. No vfat, ntfs or btrfs. Admittedly, however, the Xenserver version the IT people were using was an older version), I soon found out that the IT people had created the storage space, but not done anything else. Therefore, that would explain why I couldn’t mount it — it hadn’t been formatted. So a simple mkfs.ext3 (remember ext4 wasn’t supported) on the block device in /dev/mapper/ meant I could mount it without specifying filesystem. scp’ing into the server and copying into the path proved it worked.
You must be logged in to post a comment.