Jump to content

More Partitions . . More Distro's to boot


longgone

Recommended Posts

This is the full planned setup Dale:

hda1 ... 1.9   Drake10.1 beta 1 ( /home )hda3 ... 34    XPhda5 ...       SWAPhda6 ... 3.8   Drake 10.1 Beta 1 ( / )hda7 ... 9.7   Backup- - - - - - - - - - - - - - - hda8 ... 6.8   Slackwarehda9 ... 6.8   Knoppixhda10 .. 6.8   SUSE= = = = = = = = = = = = = = = hdb1 ... 1.9   Drake10hdb5 ... 3.9   Drake10hdb6 ... 9.7   Drake10 - - - - - - - - - - - - - - hdb7 ... 7.0   Fedorahdb8 ... 7.0   Debianhdb9 ... Keep empty for future new things
But for today . . . . it is getting late and my day is done :DSee you tomorrow !:w00t: Bruno
Link to comment
Share on other sites

  • Replies 845
  • Created
  • Last Reply

Top Posters In This Topic

  • longgone

    415

  • Bruno

    377

  • SonicDragon

    22

  • teacher

    14

Top Posters In This Topic

:wacko: :"> :thumbsup: Welllll ...... darn the bad luck ... booted into SuSE today and the mouse/cursor is froze solid won't move at all ... last thing I did was download updates last night (that was a mistake). Just way to many to have done that at that late hour... also noticed on the display during the boot up that there were five "fatal error" notifications, one on emu (sound) and the rest on mod/libs, so I would make a guess that the libraries have a slight problem ... ??????
Link to comment
Share on other sites

;( . . looks like you are in for a re-install . . . . ;(This time please select lilo as bootloader . . . ( there is an option to do that during install ! )The lilo-section in Mandrake can stay the same :DB) Bruno

Link to comment
Share on other sites

:D :D :) Bruno,,,.....I just knew that without a doubt you was a gonna say that ...... well ... guess I add that onto my weekend list of what to do things
Link to comment
Share on other sites

Hi DaleIf after that install you do the updates again . . . : Check if there is a new kernel or updated kernel-modules and what extra notes or directions are available on the updates . . . . I suspect that there was a kernel update and that there would have been instructions like: "run lilo after the updates" . . . ( Just a guess :) )Anyway post any info you get on the updates on the forum so we can both read them and discuss what to do ( and what not :D )Anyway the advantage of a reinstall is that we will have lilo . . . so any future kernel upgrade will be easiuer to manage ( and we can get the info from the SUSE lilo to incorporate in the Drake lilo :D )B) Bruno

Link to comment
Share on other sites

Bruno....reinstall is done ... I paid closer attention this time found that option to change the boot loader ... it is now Lilo ... only error encounter was with the boot loader but I do not see any errors at the reboot and the only errors that were encounter in the boot listing were with eth0 and since I am not on broadband I can understand what they are (no cable hooked up) now onto the updates,,, slowly this time ... :) :D

Link to comment
Share on other sites

Bruno....reinstall is done ... I paid closer attention this time found that option to change the boot loader ... it is now  Lilo  ...  only error encounter was with the boot loader but I do not see any errors at the reboot  and the only errors that were encounter in the boot listing were with  eth0 and since I am not on broadband I can understand what they are (no cable hooked up)  now onto the updates,,, slowly  this time ... :)  :D
Dale you don't need to worry about eth0 error it happens because by default Suse tries to load eth0 and of course if you're on dial up it fails. :D Happens to me all the time.There is a way to disable it through network devices in YAST but not in Suse right now so you can leave it as it is for now no worries.As soon as I boot into Suse I'll be able to tell you how to disable it. B)
Link to comment
Share on other sites

now onto the updates,,, slowly  this time ...
Good plan Dale . . :thumbsdown: . . . . . slowly . . . and post all notes you get during the update ;):'( Bruno
Link to comment
Share on other sites

Bruno / jodef ........Ahhh.... another day in the valley ... jodef .... the error about the etc0 is not a big issue... I would imagine that if and when someday .... I get broadband that will go away .. until then I can live with it .. I don't think it is going to cause a crash or malfunction of any sort .. thanks again though ..Bruno .... during the install of the updates as far as I went (there are still about 12-16 to do, 1 is security related, 2 are recommended and the last group are optional) the following two extra screens opened:Patch: kernelsummary: the linux kernel on x86 architectureThis update can be used to install a new kernel if you decide to use the kernel update, we recommend that you reboot your system upon completion of the YaST online update as additional kernel modules may be needed which can only be loaded after the system is rebootedif you are in the course of performing a new installation, you should delelect this kernel update in order to avoid problems with the hardware detection during the installationthis is what the second one had to sayPatch: mkinitrdsummary: creates an initial RamDisk image for preloading modulesThe initrd has to be re=created and lilo must be executed if configured upon update of the mkinitrd package. the choices for the first one were A. continue B. abort C. skip package ..... my choice was Cthe second one was either :see details" or "ok" I chose "ok"I have not yet tried to boot into SuSE today to see if all is well or not .. that is a bit later on , but that is an update to date ....

Link to comment
Share on other sites

Hi DaleGreat !! . . . But not really clear what you did with the kernel upgrade . . . ( hoping you skipped that one too ;) )We can do the kernel upgrade seperately . . . but after that you have to reboot to get the modules AND do the "mkinitrd" after . . . because the mkinitrd makes a new initrd.img we need to copy over to Mandrake ( /boot/suse ) together with the new kernel . . then we have to adapt the Mandrake Lilo to point to the new kernel and initrd.imgBecause the forum will go offline in the next 24 hrs, I am not really sure if we should wait till the down-time is over . . or we should do it before the down-time and hope we manage to finish it . . . B) Bruno

>>  Important Notice Posted at 11:30AM ET, Sat. July 10, 2004: Scot's Newsletter Forums will go offline within the next 36 hours for planned maintenance. It could be offline for up to three days. Please take a moment now to bookmark this status page link for information while the board is offline. >>
Link to comment
Share on other sites

Bruno,,,,,I skipped the update for the kernel, I had a hunch that that was what caused the freeze up of the cursor .... I did go ahead and okay the mkinitrd patch/update and I saw no noticeable opppssss there ... I did boot into SuSE today and all seems good to go there, if we are in agreement lets wait until the forum gets all well and good and stable again before continuing on ... I need lots of help as we both can see ... B) :D ;) :lol:

Link to comment
Share on other sites

I just did my Suse install this morning. It did say to skip the kernel patch if doing an initial install!Julia ;)

Link to comment
Share on other sites

Bruno,,,,,I skipped the update for the  kernel, I had a hunch that that was what caused the freeze up of the  cursor  ....  I did go ahead and okay the  mkinitrd patch/update and I saw no noticeable opppssss  there  ...  I did boot into SuSE  today and all seems good to go there, if we are in agreement lets wait until the forum gets all well and good and stable again before continuing on ...  I  need lots of help as we both  can see ...  B)  :D  ;)  :lol:
Good thinking Dale !! We will do the kernel + modules + mkinitrd when the forum is on the new server !B) Bruno
>>  Important Notice Posted at 11:30AM ET, Sat. July 10, 2004: Scot's Newsletter Forums will go offline within the next 36 hours for planned maintenance. It could be offline for up to three days. Please take a moment now to bookmark this status page link for information while the board is offline. >>
Link to comment
Share on other sites

Here is what Suse does for the Lilo with the 9.1 after the basic updates:

image=/boot/vmlinuzlabel=Suseinitrd=/boot/intrdoptionalroot=/dev/hda5vga=0x31aappend="splash=silent desktop resume=/dev/hdb7 showopts"

This is with the / being on hda5 and the swap at hdb7.....This surprised me. I had the vmlinuz as the speciif 2.6 one ...... and the intrd as the specific one as well. I just let it write to the hda5 and then copied the files over and added it to my Mandrake Lilo.Julia ;)

Link to comment
Share on other sites

teacher....my SuSE install is fully contained on hda10 (/, and anything else too)... that is the partition that was allocated for it to use. I noticed while doing the updates that I did do, that it appears that security updates are listed in red, recommended updates in blue, and optional are in black, at least that is the way they appear on the DVD from Novell ... I still have two "blue" to do ... (no pun there) and all of the optionals but I think i shall wait until after this kernel update for them. Things could change in mid-stream on me ....

Link to comment
Share on other sites

Here is what Suse does for the Lilo with the 9.1 after the basic updates:
image=/boot/vmlinuzlabel=Suseinitrd=/boot/intrdoptionalroot=/dev/hda5vga=0x31aappend="splash=silent desktop resume=/dev/hdb7 showopts"

This is with the / being on hda5 and the swap at hdb7.....This surprised me.  I had the vmlinuz as the speciif 2.6 one ...... and the intrd as the specific one as well.  I just let it write to the hda5 and then copied the files over and added it to my Mandrake Lilo.Julia B)

This is because if you do:
ls -al /boot

You will see that the vmlinuz and initrd are only sym links that now point to the new kernel and initrd.img, they used to point to the "old" ones (vmlinuz-2.6.4-52) ;) Bruno

>>  Important Notice Posted at 11:30AM ET, Sat. July 10, 2004: Scot's Newsletter Forums will go offline within the next 36 hours for planned maintenance. It could be offline for up to three days. Please take a moment now to bookmark this status page link for information while the board is offline. >>
Link to comment
Share on other sites

Okay . . this is the drill ( No need to do it today . . I just wanted to write/post the How-To ;) )The old kernel 2.6.4-52 will be replaced by 2.6.5-7.95 . . . . The best thing to do to stay on the safe side is:First write the SUSE lilo to the MBR ( so do this command in SUSE ):

# /sbin/lilo -b /dev/hda

Then do the updates and after the updates reboot ( using the SUSE lilo ) it will then boot from the new kernel and modules. ( Check if all is well B) )Now, after that use the Mandrake boot-cd to boot Mandrake and first copy over the new kernel and initrd over to /boot/suse . . . or even better remove the old /boot/suse first and then copy the new one over:

$ su< password ># rm -rf /boot/suse# mount /dev/hda10 /mnt/hda10# cp -r /mnt/hda10/boot /boot/suse# ls -l /boot/suse# umount  /mnt/hda10

The change the /etc/lilo.conf to the new vmlinuz and initrd

image=/boot/suse/vmlinuz-2.6.5-7.95-default        label="SUSE"        initrd=/boot/suse/initrd-2.6.5-7.95-default        optional        root=/dev/hda10        vga=0x317        append="splash=silent desktop resume=/dev/hda5 showopts"
Then save the file and write the new Lilo to the MBR with:
#  /sbin/lilo -b /dev/hda

That is all :DB) Bruno

>>  Important Notice Posted at 11:30AM ET, Sat. July 10, 2004: Scot's Newsletter Forums will go offline within the next 36 hours for planned maintenance. It could be offline for up to three days. Please take a moment now to bookmark this status page link for information while the board is offline. >>
Link to comment
Share on other sites

Bruno,,,Haven't we already done the /sbin/lilo once already after the SuSE was written to Mndrk 10.0 boot menu .... I recall doing a /sbin/lilo not so very long ago .. (2 days) or is this a completely different critter hereAlso if I understand correctly you are saying go ahead and do the d/l for the kernel change update ... now if so when I reboot how do I know it will be using the SuSE lilo and not the Mndrk boot menu ... ????

Link to comment
Share on other sites

No DaleThis time I want you to boot in SUSE and temporary write SUSE's lilo to the MBR ( only to get the updates and after that has been settled we go back to Drake for the usual lilo )Then you reboot and see if you get the SUSE lilo to boot from ( you will only be able to boot SUSE from it ) . . . Then you do the updates . . . . Reboot into SUSE again after and see if all is done 100%Only after that you boot ( with the boot-cd ) back into Drake and restore the Drake lilo back to the original.The only thing left to do then is to change the entry for SUSE in the Drake lilo so it uses the new SUSE kernel to boot SUSE . . ;):D Bruno

>>  Important Notice Posted 11:00AM Eastern Time, Sun. July 11, 2004:Scot's Newsletter Forums will go offline today starting late afternoon/early evening ET for planned maintenance. It will be offline for at least 18 hours and as much as three days.  Please take a moment now to bookmark this status page link for information while the board is offline. >>
Link to comment
Share on other sites

:D :D :D (Ohhhhh....)I see now .... okay it will give me something to do while the forum is out to lunch and I am trying to fix a computer or two .... just a regular day in the country ..
Link to comment
Share on other sites

Just for the new part in the Drake Lilo I advise you to wait till the forum is back UP . . . . . the rest you can do while we are off-line:1). Boot SUSE2). Write SUSE lilo to MBR3). Get all the updates4). Reboot into SUSE to check5). Reboot into Drake ( boot-CD ) and restore the Drake Lilo to MBRThe only thing you will not be able after that list is to boot into SUSE. To do that we first have to do a few tweaks and that will be done after the "down-time" . . . .:D( All your other distros will boot as usual from the Drake lilo ) :D Bruno

>>  Important Notice Posted 11:00AM Eastern Time, Sun. July 11, 2004:Scot's Newsletter Forums will go offline today starting late afternoon/early evening ET for planned maintenance. It will be offline for at least 18 hours and as much as three days.  Please take a moment now to bookmark this status page link for information while the board is offline. >>
Link to comment
Share on other sites

:hmm: :hmm: :hmm: Welllllll ..... I guess that the forum is back ... on somewhat shakey legs albeit (I think) but if I can post here ... it must be ready ;) :'(
Link to comment
Share on other sites

Let's go for it Dale . . .Boot into SUSE and do

$ su< password ># /sbin/lilo

And let me see what it says . . . ;);) Bruno

Link to comment
Share on other sites

;)  :'(  :hmm: And ... away I goooo.......................
Hey . . no . . don't go away . . . . let's go for it and do the tweak ! :lol::hmm: Bruno
Link to comment
Share on other sites

;) :hmm: :'( Bruno,,,...And away I goooooooooooooo .... from Mndrk 10.0 into SuSE 9.1 ........ and here is the results of the /sbin/lilo ... entryPassword:linux:/home/dale # /sbin/liloWarning: LBA32 addressing assumedFatal: Image name, label, or alias contains a blank character: 'Linux other 1'linux:/home/dale #this is in Suse BTW
Link to comment
Share on other sites

;) Ask and ye shall receive ...# Modified by YaST2. Last modification on Sat Jul 10 00:07:08 2004message = /boot/messagetimeout = 80promptdefault = Linuxboot = /dev/hdaother = /dev/hda1 label = "Linux other 1"other = /dev/hda3 label = "Linux other 2"other = /dev/hdb1 label = "Linux other 3"image = /boot/memtest.bin label = "Memory Test" optional append = ""image = /boot/vmlinuz label = Linux initrd = /boot/initrd optional root = /dev/hda10 vga = 0x31a append = "splash=silent desktop resume=/dev/hda5 showopts"other = /dev/hda1 label = "Linux other 1"other = /dev/hda3 label = "Linux other 2"other = /dev/hdb1 label = "Linux other 3"image = /boot/vmlinuz label = Failsafe initrd = /boot/initrd optional root = /dev/hda10 vga = normal append = "showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 3"image = /boot/memtest.bin label = "Memory Test" optional append = ""linux:/home/dale #.... sort of ...
Link to comment
Share on other sites

Dale . . remove the RED parts . . ;)

# Modified by YaST2. Last modification on Sat Jul 10 00:07:08 2004message = /boot/messagetimeout = 80promptdefault = Linuxboot = /dev/hdaother = /dev/hda1 label = "Linux other 1"other = /dev/hda3 label = "Linux other 2"other = /dev/hdb1 label = "Linux other 3"image = /boot/memtest.bin label = "Memory Test" optional append = ""image = /boot/vmlinuz label = Linux initrd = /boot/initrd optional root = /dev/hda10 vga = 0x31a append = "splash=silent desktop resume=/dev/hda5 showopts"other = /dev/hda1 label = "Linux other 1"other = /dev/hda3 label = "Linux other 2"other = /dev/hdb1 label = "Linux other 3"image = /boot/vmlinuz label = Failsafe initrd = /boot/initrd optional root = /dev/hda10 vga = normal append = "showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 3"image = /boot/memtest.bin label = "Memory Test" optional append = ""
And let me see:
# /sbin/lilo

again . . :'( Bruno

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...