SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
All my partitions are primary so as far as I understod I should only add
append=" resume=/dev/sda1"
to my lilo.conf file.
My /etc/lilo.conf look like this after modification:
Quote:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255
# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt
# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# VESA framebuffer console @ 1024x768x64k
#vga=791
# VESA framebuffer console @ 1024x768x32k
#vga=790
# VESA framebuffer console @ 1024x768x256
#vga=773
# VESA framebuffer console @ 800x600x64k
#vga=788
# VESA framebuffer console @ 800x600x32k
#vga=787
# VESA framebuffer console @ 800x600x256
#vga=771
# VESA framebuffer console @ 640x480x64k
#vga=785
# VESA framebuffer console @ 640x480x32k
#vga=784
# VESA framebuffer console @ 640x480x256
#vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda2
label = Slack
append=" resume=/dev/sda1"
read-only
# Linux bootable partition config ends
I use KDE and turn on hibernation by clicking "HIBERNATE" in menu.
After I want to resume i click power on button, LILO starts I choose my linux system and click enter, slackware boots up and its like new session - not resuming my old one.
What do you mean by "run 'lilo' after any changes" ? Do you mean to restart linux first to let lilo gain new configuration and then do hibernate ?
Thank you and @zasavage for anwsering my question.
Sorry, I should have been a bit clearer. What I mean is that you need to run the command lilo as root so that lilo accepts the changes that you've made in lilo.conf.
What do you mean by "run 'lilo' after any changes" ? Do you mean to restart linux first to let lilo gain new configuration and then do hibernate ?
Any time you make a change to /etc/lilo.conf you have to run the command
Code:
lilo
as root afterwards to make the bootloader aware of the changes. After you have done that hibernate the system and wake it up again, it should work now, since I assume that not running lilo was the problem here.
Thanks for noticing. I wrote that article on SlackDocs, but never tried 'simple' hibernating (I use full disk encryption with LVM) and I wasn't sure if the resume line is correct. Updating article right now.
Thanks for noticing. I wrote that article on SlackDocs, but never tried 'simple' hibernating (I use full disk encryption with LVM) and I wasn't sure if the resume line is correct. Updating article right now.
Is disk encryption and LVM connected ? By LVM you mean that you use extended partition, not primary, right ?
I want to use true crypt encryption too, how about LILO in this case ?
Is disk encryption and LVM connected ? By LVM you mean that you use extended partition, not primary, right ?
No, they are independent.
Linux LVM stands for Logical Volume Manager, don't confuse it with disk partitions. In LVM you use physical partition, it doesn't matter if primary or logical, as container in which you can create as many Logical Volumes (LV) as you want (and partition can store). Think of them as dynamic partitions, which can be created, resized, deleted, moved from one LVM container to another on the fly without touching partition table.
For example: If you are running out of space on home LV, just expand it and you can continue working in virtually no time. In case of physical partitions, you would have to shutdown OS, recreate/modify entire partition table and hope that nothing broke, data remained intact, etc.
Of course you can just encrypt you physical partitions, but basic idea behind full disk encryption is to hide as many information as possible. If you have several encrypted partitions, anyone can guest your system layout (and therefore it's purpose) just by looking at partition table and sizes of these partitions. With LVM only visible information is that you have one small partition (for /boot) and rest of disk encrypted on second partition.
Sure, one would guess that since there is linux kernel on first partition, you probably have linux OS on the second partition, but who really knows? There could be anything.
If you are interested in this setup, read README_CRYPT.TXT - especially part Combining LUKS and LVM.
Quote:
Originally Posted by daf1kpp
I want to use true crypt encryption too, how about LILO in this case ?
Do you mean TrueCrypt, disk encryption software, or full disk encryption with linux tools? If the first I can't help you, because I never tried TrueCrypt and I suggest to start another thread. If the second, I would point you to SlackDocs http://docs.slackware.com/howtos:sla...in:hibernation. If anything is not clear or something is missing, feel free to ask.
Last edited by yenn; 03-01-2013 at 06:52 AM.
Reason: typo
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.