----- Original Message -----
From: "Ken Schneider"
Greg Freemyer pecked at the keyboard and wrote:
On Thu, Jun 19, 2008 at 2:19 PM, Larry Stotler
wrote: I use it as well, but if it is missing from 11.0 we can always use an older distro DVD to do that right? Actually, I don't believe so. Since the kernel is already loaded, you can probably boot the system, but none of the modules will load
On Thu, Jun 19, 2008 at 1:25 PM, Greg Freemyer
wrote: properly because you are using the wrong kernel. That can cause a problem if you need stuff like networking and stuff. I'm pretty sure it is a grub menu item on the DVD and that it is pre-initrd, so that there is not a kernel loaded.
If someone has 11.0 installed (or one of the RCs, etc.) it should be an easy test to boot off of the 10.3 DVD and select boot from hard disk.
Greg
"Boot from hard disk" is not the same as "boot installed system". The later uses a kernel from the CD/DVD not the one installed on the hard drive.
Welp I've already run into a wish for that option. I did a basic text-only minimal install onto a Dell Poweredge 1550. During install it recoognized the nics and hard drives (and thus the scsi cntroller) seemingly perfectly. I used the installer to do a basic 3-drive, 3 partitions per drive, software raid install. md0 = 128Mx3 raid1 on sd{a,b,c}1 /boot md1 = 1Gx3 raid0 on sd{a,b,c}2 swap md2 = 33Gx3 raid5 on sd{a,b,c}3 / All done from within the gui installer. I didn't do any manual package selecting/deselecting to mess up the install base, just selected "minimal text" from the early screen where you select gnome/kde/xcfe/etc. No errors or warnings or anything funny at all during install. It finishes without fuss and and reboots and hangs at the end of the bios/post. ...time passes... feh... mess. now I'm trying to use the repair system option and it gets to the point near the end where is discovers it can neither find nor create a working grub. So, I magically happen to know exactly what grub config will work. So I use the handy dandy expert option to dirctly edit the config files, and the damned thing doesn't keep what I wrote into grub.conf, and of course, that doesn't work. It would work if it would just do what I tell it.... I don't have time to futz with it more right now but next I'll try doing it completely manually from the shell.. Now here's the kicker. This actually worked FINE, WITHOUT manual intervention or any grub know-how back somewhere between 10.0 to 10.2. It was exactly the same way broken in 10.3, but 10.3 had the nice boot-installed option, and it was easy to proceed with the install that way and fix up grub manually afterwards using a nice full featured system instead of the mini.iso environment so it wasn't too much of a hardship that it stopped working completely automagically. When I get it I'll post detailed recipe to make it work and what exactly it's doing wrong. Loosely though, it's like this, It's putting paths like /boot/vmlinuz into menu.lst, meanwhile the files are on their own seperate boot filesystem, and from the point of view of grub looking at that filesystem, the path to the files are just (hd0,0)/vmlinuz It also writes resume=/dev/md1 which not only doesn't work (it's a raid0 that isn't assembled at that point) but it interferes with the later stages assembling and mounting swap somehow. So what I need in menu.lst is: ------- title openSUSE root (hd0,0) kernel /vmlinuz root=/dev/md2 showopts noresume initrd /initrd ------- But I can manually edit that and those changes stick, so, annoying but not a show stopper. The real problem is in grub.conf. It's initially creating entries in there that are like... gone now, have to capture them later sorry When what I need , exactly, is: ------- setup (hd0) (hd0,0) setup (hd1) (hd1,0) setup (hd2) (hd2,0) quit ------- And even though I magically know that, and actually type it into the expert edit files editor, it tosses out my entries and writes it's own, borked ones, and differently from the original entries too. I'm pretty sure there will be a way to get the job done completely from within the installer but it's looking like it will take some significant trial & error and tedious rebooting to work it out and it sure is a drag. At some point back in 10.1 this worked well all by itself, all automatic, no editing, no need to boot-install-system etc, it "just worked", way back then. In fact, I'll test that just for the heck of it. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org