Re: Freebsd, Suse Linux dual booting
On 17 Sep Ahmad Arafat Abdullah wrote: For me, booting BSDa and other OS is easier with grub: mine: FreeBSD 6.1 rootnoverify (hd0,0) chainloader +1 Is this chainloader thing still valid? To my knowledge grub knows about ufs2 nowadays. -- dick -- http://nagual.nl/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 6.1 +++ Solaris 10 6/06 ++ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd, Suse Linux dual booting
On Sat, Sep 16, 2006 at 04:49:17PM -0700, Dan Bikle wrote: FreeBSD and Linux people, I have a PC which I want to boot as windows, FreeBSD, and Suse 10.1 Linux. Currently, FreeBSD boot0 menu shows both Windows and FreeBSD as boot-able. The FreeBSD boot0 menu does not show the Linux OS (which I just installed). So, I did some reading of the FreeBSD handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html It suggests that I have 2 ways to solve this problem: 1. Configure the FreeBSD boot0 menu so that it can boot Windows, FreeBSD, and Linux Or, 2. Replace The FreeBSD boot0 menu with LILO Boot Manager I like option 1. Q1: How do I add Suse 10.1 Linux to the FreeBSD boot0 menu? As for option 2, if I want to try LILO, I'll need to toss my FreeBSD boot0 menu in the trash. Q2: If I cannot get LILO to boot FreeBSD, how do I boot get FreeBSD to boot and then how do I restore my old FreeBSD boot0 menu? Well, LILO should be able to do it. But it should work anyway with the FreeBSD MBR. Did you install FreeBSD last? Did you tell it to put in the FreeBSD MBR? You must have if it sees Win and FreeBSD. Did you install Susie in a primary partition (slice) and not some logical partition within a slice? Did you define the Susie slice as bootable? It must have a boot sector on it too. The boot manager just checks all the primary slices to see if they have boot sectors and then puts them in a menu for booting. If it recognizes it as a bootable sector, but does not find any identifying information, it puts it in the menu but with ??? as the system identifyer. Since the FreeBSD boot manager (MBR) follows the official standard and uses only one sector, it doesn't have a lot of room to store tables of different systems and recognition information. So, it is pretty much FreeBSD, MS-Dos except NTFS and generic Linux as far as I can see. The rest are identified as ???, but they will boot just fine, because all the MBR has to do is load the boot sector and hand off control. The two advantages of Grub or some other third party MBR is that they cheat and generally use a whole track instead of only one sector because most systems don't do anything with the rest of the track anyway. That gives them more room for nice looking menus and other things and to muck with logical partitions or whatever. This works fine for most cases, but could cause problems if some system tries to also assume the rest of the track will not be used and tries to do something with it. Some instant recovery systems do that. Then those more fancy MBRs will not work or the other system will not work and you will need something that follows the official rules like the FreeBSD MBR. - I have used the FreeBSD MBR to rescue systems that had one of those instant recovery utilities trashed itself, even though that was on XP. So, I think it is good to keep the FreeBSD MBR handy. jerry Thanks, -Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd, Suse Linux dual booting
On 2006 Sep 18 , at 06:26, dick hoogendijk wrote: On 17 Sep Ahmad Arafat Abdullah wrote: For me, booting BSDa and other OS is easier with grub: mine: FreeBSD 6.1 rootnoverify (hd0,0) chainloader +1 Is this chainloader thing still valid? To my knowledge grub knows about ufs2 nowadays. Chainloader is still valid. However, it hands off control to the UFS boot blocks. (The spinning /|\- thing. If you press space during this, you get a simple interactive boot-loader, which lets you pick the next stage boot-loader.) The danger with chainloader on UFS systems (or other filesystems) with grub, is if you try to chainload the boot blocks of a filesystem that has GRUB embedded on it. In that case... you either recursively boot into grub... or worse, you get weirdnesses... and have to track down a boot disk. If you wish to chainload the boot-blocks, from grub, you're better off doing: root( hd0,0,a ) chainloader /boot/boot2 # I think it's boot2 -- boot1 is a first stage, and needs boot2 in fixed location. Also, doing the bootloading from the filesystem with GRUB still passes off control to the FreeBSD loader, anyhow, so GRUB isn't the last step in the process. There's a whole host of other fun tricks to use with the FreeBSD bootloader, grub, and more. I'd be happy to talk more about it, but I don't want to bore you. -- ADAM David Alan Martin -- Adam David Alan Martin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd, Suse Linux dual booting
Well, I rolled the dice and tried grub. Moral: grub is good. Details: I decided to re-install Suse 10.1 so I could interact with the mechanism which installs Grub. Then... I found this in /boot/grub/menu.lst suse:/boot/grub # cat menu.lst # Modified by YaST2. Last modification on Sun Sep 17 05:08:44 UTC 2006 color white/blue black/light-gray default 0 timeout 8 ###Don't change this comment - YaST2 identifier: Original name: linux### title SUSE Linux 10.1 root (hd0,5) kernel /boot/vmlinuz root=/dev/sda6apm=off acpi=off mce=off barrier=off ide=nodma idewait=50 i8042.nomux psmouse.proto=bare irqpoll pci=nommconf resume=/dev/sda5 splash=silent showopts initrd /boot/initrd ###Don't change this comment - YaST2 identifier: Original name: windows 1### title windows 1 chainloader (hd0,0)+1 ###Don't change this comment - YaST2 identifier: Original name: windows 2### title windows 2 chainloader (hd0,1)+1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- SUSE Linux 10.1 root (hd0,5) kernel /boot/vmlinuz root=/dev/sda6 showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3 initrd /boot/initrd It looks like Suse thinks the disk is named hd0 rather than hd8. So, I added this entry: ###Don't change this comment - YaST2 identifier: Original name: FreeBSD 5.5### title FreeBSD 5.5 root (hd0,2,a) kernel /boot/loader This is a direct pattern off of the discussion here: http://www.lemis.com/grog/diary-apr2006.html#21 And the grub file in front of my face. Then I rebooted and saw a nice Grub menu with FreeBSD 5.5 listed on the bottom. I picked it. It sent me to the Beastie boot menu I'm so familiar with. And I used that to boot my FreeBSD box. I'm jazzed. I wish golf were this easy. Thanks gentlemen. -Dan On 9/16/06, Jeff Rollin [EMAIL PROTECTED] wrote: On 17/09/06, Dan Bikle [EMAIL PROTECTED] wrote: People, this is great info; thanks for taking time to type it up. I'm now convinced that Grub is good. On my FreeBSD box I see this: bash moibsd maco /usr/home/maco 3 $ bash moibsd maco /usr/home/maco 3 $ bash moibsd maco /usr/home/maco 3 $ bash moibsd maco /usr/home/maco 3 $ bash moibsd maco /usr/home/maco 3 $ cat /etc/fstab # DeviceMountpoint FStype Options Dump Pass# /dev/ad8s3b noneswapsw 0 0 /dev/ad8s3a / ufs rw 1 1 ##/dev/ad8s4a /u1 ufs rw 1 1 /dev/acd0 /dvd1 cd9660 ro,noauto 0 0 /dev/acd1 /dvd2 cd9660 ro,noauto 0 0 linprocfs /compat/linux/proc linprocfs rw 0 0 bash moibsd maco /usr/home/maco 4 $ bash moibsd maco /usr/home/maco 4 $ bash moibsd maco /usr/home/maco 4 $ bash moibsd maco /usr/home/maco 4 $ bash moibsd maco /usr/home/maco 4 $ df bash moibsd maco /usr/home/maco 4 $ df bash moibsd maco /usr/home/maco 4 $ df bash moibsd maco /usr/home/maco 4 $ df Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad8s3a 91913630 37443012 4711752844%/ devfs 110 100%/dev linprocfs 440 100%/usr/compat/linux/proc bash moibsd maco /usr/home/maco 5 $ bash moibsd maco /usr/home/maco 5 $ Comparing that with the information in the mail list and this page: http://www.lemis.com/grog/diary-apr2006.html#21 suggests to me, that this Grub entry would be appropriate: title FreeBSD 5.5 root (hd8,2,a) kernel /boot/loader Dang, I always mix up XP and FBSD syntax. Yes, that looks fine. Good luck! Jeff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd, Suse Linux dual booting
- Original Message - From: Jeff Rollin [EMAIL PROTECTED] To: Dan Bikle [EMAIL PROTECTED] Subject: Re: Freebsd, Suse Linux dual booting Date: Sun, 17 Sep 2006 01:59:36 +0100 On 17/09/06, Dan Bikle [EMAIL PROTECTED] wrote: People, this is great info; thanks for taking time to type it up. I'm now convinced that Grub is good. On my FreeBSD box I see this: bash moibsd maco /usr/home/maco 3 $ bash moibsd maco /usr/home/maco 3 $ bash moibsd maco /usr/home/maco 3 $ bash moibsd maco /usr/home/maco 3 $ bash moibsd maco /usr/home/maco 3 $ cat /etc/fstab # DeviceMountpoint FStype Options Dump Pass# /dev/ad8s3b noneswapsw 0 0 /dev/ad8s3a / ufs rw 1 1 ##/dev/ad8s4a /u1 ufs rw 1 1 /dev/acd0 /dvd1 cd9660 ro,noauto 0 0 /dev/acd1 /dvd2 cd9660 ro,noauto 0 0 linprocfs /compat/linux/proc linprocfs rw 0 0 bash moibsd maco /usr/home/maco 4 $ bash moibsd maco /usr/home/maco 4 $ bash moibsd maco /usr/home/maco 4 $ bash moibsd maco /usr/home/maco 4 $ bash moibsd maco /usr/home/maco 4 $ df bash moibsd maco /usr/home/maco 4 $ df bash moibsd maco /usr/home/maco 4 $ df bash moibsd maco /usr/home/maco 4 $ df Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad8s3a 91913630 37443012 4711752844%/ devfs 110 100%/dev linprocfs 440 100%/usr/compat/linux/proc bash moibsd maco /usr/home/maco 5 $ bash moibsd maco /usr/home/maco 5 $ Comparing that with the information in the mail list and this page: http://www.lemis.com/grog/diary-apr2006.html#21 suggests to me, that this Grub entry would be appropriate: title FreeBSD 5.5 root (hd8,2,a) kernel /boot/loader Dang, I always mix up XP and FBSD syntax. Yes, that looks fine. Good luck! Jeff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] For me, booting BSDa and other OS is easier with grub: mine: FreeBSD 6.1 rootnoverify (hd0,0) chainloader +1 NetBSD 3.0.1 rootnoverify (hd0,2) chainloader +1 gud luck! -- ___ Play 100s of games for FREE! http://games.mail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd, Suse Linux dual booting
On Saturday, 16 September 2006 at 16:49:17 -0700, Dan Bikle wrote: FreeBSD and Linux people, I have a PC which I want to boot as windows, FreeBSD, and Suse 10.1 Linux. Currently, FreeBSD boot0 menu shows both Windows and FreeBSD as boot-able. The FreeBSD boot0 menu does not show the Linux OS (which I just installed). So, I did some reading of the FreeBSD handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html It suggests that I have 2 ways to solve this problem: 1. Configure the FreeBSD boot0 menu so that it can boot Windows, FreeBSD, and Linux Or, 2. Replace The FreeBSD boot0 menu with LILO Boot Manager I like option 1. Q1: How do I add Suse 10.1 Linux to the FreeBSD boot0 menu? That depends on how you have laid out your Linux partition. Given that you have three systems on the disk, you have almost certainly put Linux in a BIOS extended partition. If that's the case, you can't use the FreeBSD boot manager, because it doesn't handle extended partitions. As for option 2, if I want to try LILO, I'll need to toss my FreeBSD boot0 menu in the trash. You also have the option of GRUB, which is what I used in this situation. See http://www.lemis.com/grog/diary-apr2006.html#21 for further details. Q2: If I cannot get LILO to boot FreeBSD, how do I boot get FreeBSD to boot and then how do I restore my old FreeBSD boot0 menu? Save the very first sector of the disk somewhere: # dd if=/dev/ad0 of=bootsector count=1 To restore it, you'll need to somehow boot, of course (I'd recommend FreesBIE (http://www.freesbie.org/), and copy it back: # dd if=bootsector of=/dev/ad0 count=1 Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers. pgpz34x19QJOY.pgp Description: PGP signature
Re: Freebsd, Suse Linux dual booting
On 17/09/06, Dan Bikle [EMAIL PROTECTED] wrote:
FreeBSD and Linux people,
I have a PC which I want to boot as windows, FreeBSD, and Suse 10.1 Linux.
Currently, FreeBSD boot0 menu shows both Windows and FreeBSD as boot-able.
The FreeBSD boot0 menu does not show the Linux OS (which I just
installed).
So, I did some reading of the FreeBSD handbook:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html
It suggests that I have 2 ways to solve this problem:
1. Configure the FreeBSD boot0 menu so that it can boot
Windows, FreeBSD, and Linux
Or,
2. Replace The FreeBSD boot0 menu with LILO Boot Manager
I like option 1.
Q1: How do I add Suse 10.1 Linux to the FreeBSD boot0 menu?
As for option 2,
if I want to try LILO, I'll need to toss my FreeBSD boot0 menu in the
trash.
Q2: If I cannot get LILO to boot FreeBSD, how do I boot get
FreeBSD to boot and then how do I restore my old FreeBSD boot0 menu?
AFAIK, FreeBSD's boot loader cannot be configured, but merely loads the OSes
detected when it is run. If it does not detect something, you're out of
luck.
A better option than LILO is GRUB, which is installed by default by SUSE
10.x. XP will probably be detected by the installlation program, but if not,
here's how to add both XP and FreeBSD to the menu:
Edit the file /boot/grub/menu.1st. Create new entries as follows.
# The following entries assume that Windows XP is on drive 0, partition 0
(/dev/hda1 in Linux, /dev/ad0s1 in FBSD), with SuSE Linux on drive 0,
partition 1 (/dev/hda2 or /dev/ad0s2), and FreeBSD on drive 1, partition 0
(/dev/hdb1, /dev/ad1s0a)
title=WindowsXP
root (hd0,0)
chainloader +1
title=SuSE Linux 10.1
root (hd0,1)
kernel={the correct parameters should already be here}
title=FreeBSD 6.1
root (hd1,0,a)
chainloader +1
# menu.1st ends here
HTH,
Jeff.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd, Suse Linux dual booting
People,
this is great info; thanks for taking time to type it up.
I'm now convinced that Grub is good.
On my FreeBSD box I see this:
bash moibsd maco /usr/home/maco 3 $
bash moibsd maco /usr/home/maco 3 $
bash moibsd maco /usr/home/maco 3 $
bash moibsd maco /usr/home/maco 3 $
bash moibsd maco /usr/home/maco 3 $ cat /etc/fstab
# DeviceMountpoint FStype Options Dump
Pass#
/dev/ad8s3b noneswapsw 0 0
/dev/ad8s3a / ufs rw 1 1
##/dev/ad8s4a /u1 ufs rw 1 1
/dev/acd0 /dvd1 cd9660 ro,noauto 0 0
/dev/acd1 /dvd2 cd9660 ro,noauto 0 0
linprocfs /compat/linux/proc linprocfs rw 0 0
bash moibsd maco /usr/home/maco 4 $
bash moibsd maco /usr/home/maco 4 $
bash moibsd maco /usr/home/maco 4 $
bash moibsd maco /usr/home/maco 4 $
bash moibsd maco /usr/home/maco 4 $ df
bash moibsd maco /usr/home/maco 4 $ df
bash moibsd maco /usr/home/maco 4 $ df
bash moibsd maco /usr/home/maco 4 $ df
Filesystem 1K-blocks UsedAvail Capacity Mounted on
/dev/ad8s3a 91913630 37443012 4711752844%/
devfs 110 100%/dev
linprocfs 440 100%/usr/compat/linux/proc
bash moibsd maco /usr/home/maco 5 $
bash moibsd maco /usr/home/maco 5 $
Comparing that with the information in the mail list
and this page:
http://www.lemis.com/grog/diary-apr2006.html#21
suggests to me,
that this Grub entry would be appropriate:
title FreeBSD 5.5
root (hd8,2,a)
kernel /boot/loader
Anyone care to confirm before I pull the plug on my FreeBSD boot0 menu?
-Dan
On 9/16/06, Jeff Rollin [EMAIL PROTECTED] wrote:
On 17/09/06, Dan Bikle [EMAIL PROTECTED] wrote:
FreeBSD and Linux people,
I have a PC which I want to boot as windows, FreeBSD, and Suse 10.1Linux.
Currently, FreeBSD boot0 menu shows both Windows and FreeBSD as
boot-able.
The FreeBSD boot0 menu does not show the Linux OS (which I just
installed).
So, I did some reading of the FreeBSD handbook:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html
It suggests that I have 2 ways to solve this problem:
1. Configure the FreeBSD boot0 menu so that it can boot
Windows, FreeBSD, and Linux
Or,
2. Replace The FreeBSD boot0 menu with LILO Boot Manager
I like option 1.
Q1: How do I add Suse 10.1 Linux to the FreeBSD boot0 menu?
As for option 2,
if I want to try LILO, I'll need to toss my FreeBSD boot0 menu in the
trash.
Q2: If I cannot get LILO to boot FreeBSD, how do I boot get
FreeBSD to boot and then how do I restore my old FreeBSD boot0 menu?
AFAIK, FreeBSD's boot loader cannot be configured, but merely loads the
OSes detected when it is run. If it does not detect something, you're out of
luck.
A better option than LILO is GRUB, which is installed by default by SUSE
10.x. XP will probably be detected by the installlation program, but if
not, here's how to add both XP and FreeBSD to the menu:
Edit the file /boot/grub/menu.1st. Create new entries as follows.
# The following entries assume that Windows XP is on drive 0, partition 0
(/dev/hda1 in Linux, /dev/ad0s1 in FBSD), with SuSE Linux on drive 0,
partition 1 (/dev/hda2 or /dev/ad0s2), and FreeBSD on drive 1, partition 0
(/dev/hdb1, /dev/ad1s0a)
title=WindowsXP
root (hd0,0)
chainloader +1
title=SuSE Linux 10.1
root (hd0,1)
kernel={the correct parameters should already be here}
title=FreeBSD 6.1
root (hd1,0,a)
chainloader +1
# menu.1st ends here
HTH,
Jeff.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd, Suse Linux dual booting
On 17/09/06, Dan Bikle [EMAIL PROTECTED] wrote: People, this is great info; thanks for taking time to type it up. I'm now convinced that Grub is good. On my FreeBSD box I see this: bash moibsd maco /usr/home/maco 3 $ bash moibsd maco /usr/home/maco 3 $ bash moibsd maco /usr/home/maco 3 $ bash moibsd maco /usr/home/maco 3 $ bash moibsd maco /usr/home/maco 3 $ cat /etc/fstab # DeviceMountpoint FStype Options Dump Pass# /dev/ad8s3b noneswapsw 0 0 /dev/ad8s3a / ufs rw 1 1 ##/dev/ad8s4a /u1 ufs rw 1 1 /dev/acd0 /dvd1 cd9660 ro,noauto 0 0 /dev/acd1 /dvd2 cd9660 ro,noauto 0 0 linprocfs /compat/linux/proc linprocfs rw 0 0 bash moibsd maco /usr/home/maco 4 $ bash moibsd maco /usr/home/maco 4 $ bash moibsd maco /usr/home/maco 4 $ bash moibsd maco /usr/home/maco 4 $ bash moibsd maco /usr/home/maco 4 $ df bash moibsd maco /usr/home/maco 4 $ df bash moibsd maco /usr/home/maco 4 $ df bash moibsd maco /usr/home/maco 4 $ df Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad8s3a 91913630 37443012 4711752844%/ devfs 110 100%/dev linprocfs 440 100%/usr/compat/linux/proc bash moibsd maco /usr/home/maco 5 $ bash moibsd maco /usr/home/maco 5 $ Comparing that with the information in the mail list and this page: http://www.lemis.com/grog/diary-apr2006.html#21 suggests to me, that this Grub entry would be appropriate: title FreeBSD 5.5 root (hd8,2,a) kernel /boot/loader Dang, I always mix up XP and FBSD syntax. Yes, that looks fine. Good luck! Jeff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
