Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
In SuSE 9.3 Pro, during a system turn off process
at the logout, I always get "turning off swap - missing"
How can I correct this? That is, how can I make sure
I have my swap partition on automatically to begin with
during the boot up process so that I do not get this missing
message at the swap turn off process during system off stage.
I thing the message comes from the attempt to use both available swap partitions the same time. Are you using the same /etc/fstab for both OS's? Otherwise try to delete the FC3 swap from SUSE's fstab.
EDIT: I don't know if it is possible to use two swap partitions on one system, but the error comes most probably from the FC3 device-node (/dev/mapper/VolGroup00-LogVol01) that does not exist on SUSE (or has another identifier).
Linux can handle multiple swaps, and they can be in an extended partition.
Can't advise about LVM, as I haven't, as yet, bothered with it.
I did a quick check of the source tree (2.6.11), and couldn't find any obvious candidate for your message - I wonder if it's being issued by a Suse shutdown script.
I don't do Suse, so I don't know what they use, or where you could look.
If Suse only uses the /dev/hdd1 as swap it shouldn't even attempt to use the swap of FC3. It's either in the fstab file or a startup script. Unfortunately, I'm also not familiar with the quirks of Suse.
In the /etc/init.d/boot.d, I found two script files:
K17boot.lvm and S07boot.lvm. These files appear
to turn on logical partitions, and FC3's swap partition
happens to be a logical partition.
Not knowing the difference in K-something and S-something
scripts, I looked at the contents of these files, and they look alike.
Just out of curiosity, I executed some command lines out of K17boot.lvm file,
and they indeed turn on FC3's swap partition, I think. So, could this be
the reason why FC3's swap partition is turned on automatically even though
I do not reference it in the /etc/fstab? But then, how come turning it off doesn't
work if the FC3's swap is turned on automatically during boot?
Also, when the resume kernel option for FC3's swap partition is included
during boot, how come SuSE reports it as not found and ignore it eventually?
I'm a bit perplexed now ...
Anyway, I hope someone could pinpoint where and what to look in startup/
shutdown scripts and correct any anomalies to correct this "turning off swap -
If Linux allows multiple swap partitions even if they're logical partitions under
extended volumes, I'd like to leave them untouched as SuSE had found them
during the boot process.