On Thu 29 Mar 2007 06:41:00 NZST +1200, Chris wrote: > I think it's fair to assume that something in either grub or suses install > fails to process the more obscure (?) debian based systems menu.lst entry's.
Grub only does what it's told by its config files, so yast's grub config assembler doesn't quiet do what you want in what is a complex system configuration. > although deleting the mepis one for me went down like a cup of cold stuff. If yast deleted a file which wasn't on a system yast was installing file a bug report. You will need to provide the yast logs (run save_y2logs /tmp/yastlogs.tar.bz2 while booted into suse) . In general it is not so difficult to edit together some menu.lst changes. > I booted with a live CD to do this tweaking, as suse had no obvious way of > looking at the content of an unmounted partition Uhm well *no* Linux will let you look at files on a filesystem which isn't mounted. Alternatively feel free to do block access to the media the filesystem is stored on and interpret the data either yourself or with some aid of some program. Mounting it read-only is far easier. You can use any live disk for any Linux, there are ones from suse, knoppix, you name it. You can also boot any suse install disk and select rescue system, which gives you a minimal Linux system which totally runs out of RAM (and *not* off CD, like all the others) so you can remove the boot disk from your drive should you need to. Once there you can do anything you can do with a text mode Linux. Personally I'd mount the to-be-doctored root filesystem read-write, mount --bind /proc and /dev, and chroot. Reverse order before reboot (the normal Linux shutdown sequence won't untangle this automatically). Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
