so i thought maybe something wasn’t installed but after running cnf swapon I get
~> cnf swapon
Program ‘swapon’ is present in package ‘util-linux’, which is installed on your system.
Absolute path to ‘swapon’ is ‘/sbin/swapon’, so running it may require superuser privileges (eg. root).
I’m guessing theres a problem with gparted?
I mostly just wanted to test swapon in gparted and I know it doesnt really matter so I’ll probably just find a real way to enable swap, and maybe open a bug report.
The reason swap isn’t already enabled is because I deleted it when I did a new install, and I’ve been running without it for a couple months now, I don’t particularly need it but I want to compare the results of hibernating vs suspend, which is faster etc.
Should the menu entry for gparted be defaulted to run as pkexec or gnomesu then, perhaps? Thus indicating that the problem is with the gparted install script or just the part where the menu entry is created, or is it supposed to be this way, sort of like unetbootin is? Maybe it should create 2 entries like Catalyst does?
With that said my next question is, it seems when the swap was deleted fstab and the ‘kernel command’ still have the old swap set at boot time. So I changed it in fstab but how do I update it everywhere else? I found out to edit the kernel command line I can use Yast>Boot Loader, the question is
For example in dmesg I would have seen something like this pointing to the old swap: 0.000000] Kernel command line: root=/dev/disk/by-id/ata-ST95005620AS_5YX0A613-part1 resume=/dev/disk/by-id/ata-ST95005620AS_5YX0A613-part5 splash=silent quiet vga=0x3f0
Is there anywhere else I need to change ‘part5’ besides the kernel command and fstab?
The DEFAULT_APPEND and XEN_KERNEL_APPEND keys in /etc/sysconfig/bootloader. If you use UUIDs instead of disk/by-id symlinks, you don’t have this problem. openSUSE’s default is not optimal. If you partitionate in expert mode, you can change this default during setup by clicking on fstab options for each partition and selecting “mount by UUID”. It is better IMO.
It would seem as though it has updated /etc/sysconfig/bootloader automatically, as the entries there are correct. So that part was simple, but it was nice looking over it. I’ll look over the boot logs again after this.
Can’t the UUID’s change somehow or am I mistaken and it’s the ‘part ids’ that can change? Is there no way to switch over to the uuid method after already having chose the default. I did probably use expert mode, but I saw no reason to choose uuid instead. Thanks
The UUID is written in the filesystem superblock. It won’t change unless you reformat the partition. You can change the UUID with tune2fs but it is only needed if you clone a hard disk and want to mount both on the same machine.
You can edit /etc/fstab. Be careful though. Make a copy first. Here’s an example:
Is it at all possible to comment something out in menu.lst that way I can always re-edit it later. If not, I can always make a copy, I was just wondering if the whole menu.lst get overwritten when running mkinitrd?
Excellent. Than you for being oh, so, very informative. The only remaining question I can think of is: Just for clarifications sakes, Perl BootLoader=Yast>Bootloader? Meaning, that is probably what did the ‘automagical’ updates earlier when I used it to change the kernel command line initially?
Now I can start switching over to uuids, Thanks again!