serial config handbook: /boot.conf or /boot.config
I'm trying to get the dell bmc +sol serial thing working, kin dof getting there, but noticed this inconsistency in the handbook: Is it boot.conf or boot.config? Create boot.config in the root directory of the a partition on the boot drive. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html#SERIALCONSOLE-HOWTO 7.2 Create the /boot.conf file http://www.freebsd.org/doc/en_US.ISO8859-1/articles/console-server/freebsd.html Paul. -- - Paul Macdonald IFDNRG Ltd Web and video hosting - t: 0131 5548070 m: 07534206249 e: p...@ifdnrg.com w: http://www.ifdnrg.com - IFDNRG 40 Maritime Street Edinburgh EH6 6SA - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: serial config handbook: /boot.conf or /boot.config
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Paul Macdonald Sent: Tuesday, February 01, 2011 7:24 AM To: freebsd-questions@freebsd.org Subject: serial config handbook: /boot.conf or /boot.config I'm trying to get the dell bmc +sol serial thing working, kin dof getting there, but noticed this inconsistency in the handbook: Is it boot.conf or boot.config? Create boot.config in the root directory of the a partition on the boot drive. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole- setup.html#SERIALCONSOLE-HOWTO 7.2 Create the /boot.conf file http://www.freebsd.org/doc/en_US.ISO8859-1/articles/console- server/freebsd.html Here on my HP Proliant 350's I use - /boot.conf This is with FreeBSD 8.0. Patrick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: serial config handbook: /boot.conf or /boot.config
In the last episode (Feb 01), Patrick Mahan said: From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Paul Macdonald I'm trying to get the dell bmc +sol serial thing working, kin dof getting there, but noticed this inconsistency in the handbook: Is it boot.conf or boot.config? Create boot.config in the root directory of the a partition on the boot drive. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html#SERIALCONSOLE-HOWTO 7.2 Create the /boot.conf file http://www.freebsd.org/doc/en_US.ISO8859-1/articles/console-server/freebsd.html Here on my HP Proliant 350's I use - /boot.conf This is with FreeBSD 8.0. I don't see anything in /usr/src/sys/boot that reads a /boot.conf. boot2 reads /boot.config, and the loader will read /boot/boot.conf but that path is deprecated. I have -D in /boot.config on my SOL-enabled Dell 1950, which allows for both serial and keyboard input during the boot process. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: serial config handbook: /boot.conf or /boot.config
It's at the root - # echo /boot.conf -P Patrick Patrick Mahan Lead Technical Kernel Engineer Adara Networks Disclaimer: The opinions expressed here are solely the responsibility of the author and are not to be construed as an official opinion of Adara Networks. -Original Message- From: Dan Nelson [mailto:dnel...@allantgroup.com] Sent: Tuesday, February 01, 2011 11:52 AM To: Patrick Mahan Cc: Paul Macdonald; freebsd-questions@freebsd.org Subject: Re: serial config handbook: /boot.conf or /boot.config In the last episode (Feb 01), Patrick Mahan said: From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Paul Macdonald I'm trying to get the dell bmc +sol serial thing working, kin dof getting there, but noticed this inconsistency in the handbook: Is it boot.conf or boot.config? Create boot.config in the root directory of the a partition on the boot drive. http://www.freebsd.org/doc/en_US.ISO8859- 1/books/handbook/serialconsole-setup.html#SERIALCONSOLE-HOWTO 7.2 Create the /boot.conf file http://www.freebsd.org/doc/en_US.ISO8859-1/articles/console- server/freebsd.html Here on my HP Proliant 350's I use - /boot.conf This is with FreeBSD 8.0. I don't see anything in /usr/src/sys/boot that reads a /boot.conf. boot2 reads /boot.config, and the loader will read /boot/boot.conf but that path is deprecated. I have -D in /boot.config on my SOL-enabled Dell 1950, which allows for both serial and keyboard input during the boot process. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: serial config handbook: /boot.conf or /boot.config
On Tue, 1 Feb 2011, Patrick Mahan wrote: It's at the root - # echo /boot.conf -P Line 78 of sys/boot/i386/boot2/boot2.c says: #define PATH_CONFIG /boot.config Also, there's boot.config(5). If boot.conf also works, maybe it's only looking for a match on the first 8 or 9 characters. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: serial config handbook: /boot.conf or /boot.config
On Tue, 1 Feb 2011, Warren Block wrote: On Tue, 1 Feb 2011, Patrick Mahan wrote: It's at the root - # echo /boot.conf -P Line 78 of sys/boot/i386/boot2/boot2.c says: #define PATH_CONFIG /boot.config Also, there's boot.config(5). If boot.conf also works, maybe it's only looking for a match on the first 8 or 9 characters. Just tested this on an 8.1-stable VM, with a file containing only a -s (no quotes): /boot.conf - no effect /boot.config - boots into single-user mode ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /boot.config
On 31 March 2010 04:53, Fbsd1 fb...@a1poweruser.com wrote: Dan Nelson wrote: In the last episode (Mar 30), Fbsd1 said: During the boot process I want to change the device used to boot from. From the default 0:ad(0,a)/boot/loader to 0:da(0,a)/boot/loader forcing the boot to continue from usb stick. Here is the problem, the bios have no option to boot from USB device. So thinking let the bios point to first drive to start the boot process and have a /boot.config file to redirect to booting from the USB stick. I am assuming the '0' zero will mean the first USB device. Is there any command i can use to verify the single USB stick is the 0 device? If you boot DOS from a floppy, can you see the USB stick as B: or C: ? If not, then the BIOS probably has no USB support at all, and you'll need to put a small boot partition somewhere on your hard drive to pull the kernel from. 128MB is large enough for a /boot directory, and you can set vfs.root.mountfrom=ufs:/dev/da0s1a in loader.conf to make it mount its root filesystem from the USB stick (since at that point the kernel has loaded its own USB drivers). If you do see the USB drive from a DOS boot floppy, try entering 1:da(0,a)? at the boot block prompt and see if it lists the files in your USB filesystem. If it does, then 1:da(0,a)/boot/loader should let you boot FreeBSD. The USB stick is plugged in before booting. During boot I select option 6 from Freebsd menu to go direct to the loader prompt. I have ok on command line. I enter vfs.root.mountfrom=ufs:/dev/da0s1a and get not found after hitting enter key. At the ok prompt I enter ? for list of available boot devices and only have ad0 listed. It seems the da0 device USB stick is not recognized yet. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org try legacy usb in the bios, it may help ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /boot.config
krad wrote: On 31 March 2010 04:53, Fbsd1 fb...@a1poweruser.com wrote: Dan Nelson wrote: In the last episode (Mar 30), Fbsd1 said: During the boot process I want to change the device used to boot from. From the default 0:ad(0,a)/boot/loader to 0:da(0,a)/boot/loader forcing the boot to continue from usb stick. Here is the problem, the bios have no option to boot from USB device. So thinking let the bios point to first drive to start the boot process and have a /boot.config file to redirect to booting from the USB stick. I am assuming the '0' zero will mean the first USB device. Is there any command i can use to verify the single USB stick is the 0 device? If you boot DOS from a floppy, can you see the USB stick as B: or C: ? If not, then the BIOS probably has no USB support at all, and you'll need to put a small boot partition somewhere on your hard drive to pull the kernel from. 128MB is large enough for a /boot directory, and you can set vfs.root.mountfrom=ufs:/dev/da0s1a in loader.conf to make it mount its root filesystem from the USB stick (since at that point the kernel has loaded its own USB drivers). If you do see the USB drive from a DOS boot floppy, try entering 1:da(0,a)? at the boot block prompt and see if it lists the files in your USB filesystem. If it does, then 1:da(0,a)/boot/loader should let you boot FreeBSD. The USB stick is plugged in before booting. During boot I select option 6 from Freebsd menu to go direct to the loader prompt. I have ok on command line. I enter vfs.root.mountfrom=ufs:/dev/da0s1a and get not found after hitting enter key. At the ok prompt I enter ? for list of available boot devices and only have ad0 listed. It seems the da0 device USB stick is not recognized yet. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org try legacy usb in the bios, it may help My bios have no reference to USB at all. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
/boot.config
During the boot process I want to change the device used to boot from. From the default 0:ad(0,a)/boot/loader to 0:da(0,a)/boot/loader forcing the boot to continue from usb stick. Here is the problem, the bios have no option to boot from USB device. So thinking let the bios point to first drive to start the boot process and have a /boot.config file to redirect to booting from the USB stick. I am assuming the '0' zero will mean the first USB device. Is there any command i can use to verify the single USB stick is the 0 device? Is this concept valid? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /boot.config
In the last episode (Mar 30), Fbsd1 said: During the boot process I want to change the device used to boot from. From the default 0:ad(0,a)/boot/loader to 0:da(0,a)/boot/loader forcing the boot to continue from usb stick. Here is the problem, the bios have no option to boot from USB device. So thinking let the bios point to first drive to start the boot process and have a /boot.config file to redirect to booting from the USB stick. I am assuming the '0' zero will mean the first USB device. Is there any command i can use to verify the single USB stick is the 0 device? If you boot DOS from a floppy, can you see the USB stick as B: or C: ? If not, then the BIOS probably has no USB support at all, and you'll need to put a small boot partition somewhere on your hard drive to pull the kernel from. 128MB is large enough for a /boot directory, and you can set vfs.root.mountfrom=ufs:/dev/da0s1a in loader.conf to make it mount its root filesystem from the USB stick (since at that point the kernel has loaded its own USB drivers). If you do see the USB drive from a DOS boot floppy, try entering 1:da(0,a)? at the boot block prompt and see if it lists the files in your USB filesystem. If it does, then 1:da(0,a)/boot/loader should let you boot FreeBSD. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: /boot.config
Dan Nelson wrote: In the last episode (Mar 30), Fbsd1 said: During the boot process I want to change the device used to boot from. From the default 0:ad(0,a)/boot/loader to 0:da(0,a)/boot/loader forcing the boot to continue from usb stick. Here is the problem, the bios have no option to boot from USB device. So thinking let the bios point to first drive to start the boot process and have a /boot.config file to redirect to booting from the USB stick. I am assuming the '0' zero will mean the first USB device. Is there any command i can use to verify the single USB stick is the 0 device? If you boot DOS from a floppy, can you see the USB stick as B: or C: ? If not, then the BIOS probably has no USB support at all, and you'll need to put a small boot partition somewhere on your hard drive to pull the kernel from. 128MB is large enough for a /boot directory, and you can set vfs.root.mountfrom=ufs:/dev/da0s1a in loader.conf to make it mount its root filesystem from the USB stick (since at that point the kernel has loaded its own USB drivers). If you do see the USB drive from a DOS boot floppy, try entering 1:da(0,a)? at the boot block prompt and see if it lists the files in your USB filesystem. If it does, then 1:da(0,a)/boot/loader should let you boot FreeBSD. The USB stick is plugged in before booting. During boot I select option 6 from Freebsd menu to go direct to the loader prompt. I have ok on command line. I enter vfs.root.mountfrom=ufs:/dev/da0s1a and get not found after hitting enter key. At the ok prompt I enter ? for list of available boot devices and only have ad0 listed. It seems the da0 device USB stick is not recognized yet. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: What is correct syntax in boot.config fo GPT partitions?
I've used the syntax 1:ad(1,a)/boot/loader in boot.config to specify the boot device. This doesn't work with GPT partitions. What's the correct syntax in boot.config for GPT partitions? I looked at the source code to boot.c and there doesn't seem to be anything specifically related to GPT partitioning. So I'm puzzled: If I have a two drive system with BSD loaded on both drives and the drives are configured with GPT partitions, how can I force the system to boot from the second drive using boot.config? I've done with this MBR partitioning using either 0:ad(0,a)/boot/loader 1:ad(1,a)/boot/loader to specify either the first disk or the second disk. I've tried various incarnations of this to select with drive to boot from in my GPT based system but nothing works. My impression is that it isn't supported, except for MBR partitioning. Is this true? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
What is correct syntax in boot.config fo GPT partitions?
I've used the syntax 1:ad(1,a)/boot/loader in boot.config to specify the boot device. This doesn't work with GPT partitions. What's the correct syntax in boot.config for GPT partitions? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
boot process failure (/boot.config, boot2, loader)
Booting problem... I have installed FreeBSD 6.0 on my little Pentium III box. My problem started when I was trying to have it boot ACPI enabled by default (now, of course, I know about the loader.conf control file). Anyway, I read another post stating that all I needed to do was put the boot option into /boot.config, so I make a /boot.config file with the number 2 in it (for the second boot option which has ACPI enabled) and reboot. Now during boot it stops in (apparently) boot2 with: Free BSD/i386 boot Default: 0:ad(0,a)2 boot: If I type ? to see what commands may be allowed I get: ?. .. .snap dev tmp usr var home etc cdrom dist bin boot lib libexec mnt proc rescue root sbin sys .cshrc .profile COPYRIGHT compat entropy boot.config No matter which of these commands I type it just puts it in place of the 2 above: enter: root comes back with: Default: 0:ad(0,a)root So I have apparently broke the boot process with my 2 in /boot.config, but according to the manual I should be able to find files on my system, etc (maybe even delete /boot.config for example). But no matter what I type in for a command it just eats it making a new Default: line. Any ideas on how to use the boot2 system to find/edit/remove the /boot.config file? Or maybe to just tell the boot2 process to ignore /boot.config? Thanks! Garrett -- ___ Search for businesses by name, location, or phone number. -Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: boot process failure (/boot.config, boot2, loader)
J oberweith schrieb: [...] Now during boot it stops in (apparently) boot2 with: Free BSD/i386 boot Default: 0:ad(0,a)2 boot: [...] Any ideas on how to use the boot2 system to find/edit/remove the /boot.config file? You can't. Or maybe to just tell the boot2 process to ignore /boot.config? As far as I know you can't either. But try /boot/loader instead of 2 or root ;-) Björn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
5.4-RELEASE reset with /boot.config -m
I wonder if someone can help me. I want to run my 5.4-RELEASE system with a serial console and muted cons. My /boot.config is: -h -m The system loads the kernel but during startup the PC resets. No messages, just a reset. If I use -h by itself it is fine. If I use -m by itself it similarly resets. I must be doing something dumb. If you have any insights please let me know. Thanks, Paul. __ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
boot.config problem, can't boot
Hi, I was doing some work on my gateway and decided to tighten up the security a bit... In essence, I had -h in /boot.config, but I commented it out (because I thought that somehow comments would be understood). So, now I have #-h in /boot.config, which by the way I set the immutable flag on according to one unofficial HOWTO I was reading. BTW, the comment in the /boot.config was not part of that HOWTO. It was my own lack of understanding about how that file is parsed during boot. Yes, I feel stupid, but I'm also wondering why the file can't include a comment. I think that this a bug. And then I rebooted for some other reason. And now, I can't get past the boot: prompt. The #-h is not understood and I can't override it. There are some changes to files which are on that box that I'd like to keep, which have been made since the last backup. Is there any way to recover from this situation, or is it re-install time? Thanks, -- Mike Jackson ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: boot.config problem, can't boot
On Sun, Feb 01, 2004 at 01:06:04PM +0200, Mike Jackson wrote: I was doing some work on my gateway and decided to tighten up the security a bit... In essence, I had -h in /boot.config, but I commented it out (because I thought that somehow comments would be understood). So, now I have #-h in /boot.config, which by the way I set the immutable flag on according to one unofficial HOWTO I was reading. BTW, the comment in the /boot.config was not part of that HOWTO. It was my own lack of understanding about how that file is parsed during boot. Yes, I feel stupid, but I'm also wondering why the file can't include a comment. I think that this a bug. And then I rebooted for some other reason. And now, I can't get past the boot: prompt. The #-h is not understood and I can't override it. There are some changes to files which are on that box that I'd like to keep, which have been made since the last backup. Is there any way to recover from this situation, or is it re-install time? If you've got disk two from the install set, you should be able to boot the repair system from that, mount your hard drive on it and edit your boot.config file. Then just reboot as usual. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: boot.config problem, can't boot
Hi, if you have a bootebel CD-Rom installed you can get a live CD from http://www.freesbie.org/ and boot with it. then you can mount your root-FS and edit the boot.config file. Sebastian On Sun, 1 Feb 2004 13:06:04 +0200 Mike Jackson [EMAIL PROTECTED] wrote: Hi, I was doing some work on my gateway and decided to tighten up the security a bit... In essence, I had -h in /boot.config, but I commented it out (because I thought that somehow comments would be understood). So, now I have #-h in /boot.config, which by the way I set the immutable flag on according to one unofficial HOWTO I was reading. BTW, the comment in the/boot.config was not part of that HOWTO. It was my own lack of understanding about how that file is parsed during boot. Yes, I feel stupid, but I'm also wondering why the file can't include a comment. I think that this a bug. And then I rebooted for some other reason. And now, I can't get past the boot: prompt. The #-h is not understood and I can't override it. There are some changes to files which are on that box that I'd like to keep, which have been made since the last backup. Is there any way to recover from this situation, or is it re-install time? Thanks, ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: boot.config problem, can't boot
ext Sebastian Kutsch ([EMAIL PROTECTED]) wrote: Hi, if you have a bootebel CD-Rom installed you can get a live CD from http://www.freesbie.org/ and boot with it. then you can mount your root-FS and edit the boot.config file. Hey, I looked at that page and that sounds cool. Sort of like the Knoppix linux project. Anyhow, the download site for the iso is not visible in DNS, at least from my perspective: $ host www.willystudios.com Host www.willystudios.com not found: 3(NXDOMAIN) BR, Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: boot.config problem, can't boot
Hi, On Sun, 1 Feb 2004 14:00:50 +0200 Mike Jackson [EMAIL PROTECTED] wrote: ext Sebastian Kutsch ([EMAIL PROTECTED]) wrote: Hi, if you have a bootebel CD-Rom installed you can get a live CD from http://www.freesbie.org/ and boot with it. then you can mount your root-FS and edit the boot.config file. Hey, I looked at that page and that sounds cool. Sort of like the Knoppix linux project. Anyhow, the download site for the iso is not visible in DNS, at least from my perspective: $ host www.willystudios.com Host www.willystudios.com not found: 3(NXDOMAIN) I got the same problem. If you just net a 4.x FreeBSD you can also get a livecd from http://livecd.sourceforge.net/. BR, Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Sebastian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
