Hi folks,
I haven't see man page for boot0cfg(8) for FreeBSD 9-Current on
FreeBSD website, but it exists for 8.x and earlier versions. Is it
website bug or this utility will be removed in the future?
___
freebsd-current@freebsd.org mailing list
http
http://svn.freebsd.org/base/head/usr.sbin/boot0cfg/
It is still connected to the build in the previous directory ../ by the
Makefile.* foreach arch.
Even if, gpart(8) used along with the corresponding files in /boot you
can still achieve the same results for a selection menu at boot time
); cloned
that slice to slice 1; booted from slice 1.
* In a head src working directory, I issued
svn diff -c209469
and saw that r209469 merely added 2 lines to usr.sbin/boot0cfg/boot0cfg.c.
* On the build machine's src working directory, I edited
usr.sbin/boot0cfg/boot0cfg.c
On Sat, Jun 26, 2010 at 12:10:57PM +0300, Daniel Braniss wrote:
...
what do you see when you type boot0cfg -v ...?
gpart show?
then try
gpart set -a active -i n aacd0
n will probably be 5.
bottom line, the MBR is NOT being updated by boot0cfg
OK; here's what I see -- note
--qZLFzaLf2KECwqmh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Jun 26, 2010 at 12:10:57PM +0300, Daniel Braniss wrote:
...
what do you see when you type boot0cfg -v ...?
gpart show?
then try=20
the effect, as after I finished building
smoke-checking head on the build machine, I power it off, via:
sudo boot0cfg -s 2 aacd0 sudo shutdown -p now || sudo shutdown -r now
(as leaving it on generates too much noise and heat).
And when I powered it up last night (in preparation for the nightly
On Friday 25 June 2010 7:40:11 am David Wolfskill wrote:
Well, one one of my machines -- I realize that there are some
machines for which it's been problematic for a while. And all of
the machines I'm using run FreeBSD/i386.
209469 perhaps?
--
John Baldwin
added 2 lines to usr.sbin/boot0cfg/boot0cfg.c.
* On the build machine's src working directory, I edited
usr.sbin/boot0cfg/boot0cfg.c to remove the lines in question.
* Then (as root), I made /usr/src/usr.sbin/boot0cfg/ my current working
directory and issued:
make make install
* I
managers like GRUB, but it is another
beer.
You need to turn on 'packet' mode by hand.
# boot0cfg -o packet ad0
should do the trick.
Do you think this should be the default?
ie would it fix more things than it breaks?
My feeling is yes...
Or is sysinstall supposed to set
On 05-Mar-2003 [EMAIL PROTECTED] wrote:
Last weekend I had to reinstall Windows XP on my PC and certainly I lost
boot manager. After booting from CD and mounting as root ad0 device, I
replaced boot0 record
using the following command line :
# boot0cfg -Bv -s 1 -t 91 ad0
On my PC I have
:
# boot0cfg -Bv -s 1 -t 91 ad0
On my PC I have 14G Windows XP partition(primary partition), 7G Linux (2
extended partitions) and 7G FreeBSD 5.0 - Current (primary partition). On
second disk I have Windows 98.
After installing I see something like this :
F1 - ???
F3 - FreeBSD
F5
Kevin Oberman [EMAIL PROTECTED] wrote:
For any system less than about 4 year old and may older systems, you
really want to use this option.
The other possibility, if both FreeBSD and XP are installed on the
same disk, is to just use XP's boot selector to select which one to
boot. It can
beer.
You need to turn on 'packet' mode by hand.
# boot0cfg -o packet ad0
should do the trick.
Do you think this should be the default?
ie would it fix more things than it breaks?
My feeling is yes...
Or is sysinstall supposed to set the flags based on where you install
stuff?
(I had
Last weekend I had to reinstall Windows XP on my PC and certainly I lost
boot manager. After booting from CD and mounting as root ad0 device, I
replaced boot0 record
using the following command line :
# boot0cfg -Bv -s 1 -t 91 ad0
On my PC I have 14G Windows XP partition(primary partition), 7G
David Wolfskill writes:
| 0:ad(0,1,a)/boot/loader
... or put that in /boot.config on the / that boot0 defaults to boot.
a21p% cat /boot.config
0:ad(0,2,a)/boot/loader
a21p% ls -l /boot.co*
Then just change it. It does mean that in my setup if I'm running -current
I have
Hi
I'm using both -current and -stable on the same machine, very
common. Boot0cfg has -s [12345] flag to set the slice to boot on and
it has been working so far. Beginning from Dec 1, I'm unable to set
the slice:
root:vallo# boot0cfg -v ad0
# flag start chs type end chs
Date: Wed, 4 Dec 2002 15:17:39 +0200
From: Vallo Kallaste [EMAIL PROTECTED]
I'm using both -current and -stable on the same machine, very
common. Boot0cfg has -s [12345] flag to set the slice to boot on and
it has been working so far. Beginning from Dec 1, I'm unable to set
the slice:
root:vallo
[EMAIL PROTECTED] wrote, On 11/18/02 07:52:
Any reason why this doesn't work ?
sheelsudo boot0cfg -B ad0
boot0cfg: /dev/ad0: Operation not permitted
securelevel too high ?
Dan
--
Dan Lukes tel: +420 2 21914205, fax: +420 2 21914206
root of FIONet, KolejNET, webmaster
Howdy crew,
Any reason why this doesn't work ?
sheelsudo boot0cfg -B ad0
boot0cfg: /dev/ad0: Operation not permitted
running: FreeBSD 5.0-CURRENT #0: Fri Nov 8 15:07:18 CST 2002
Thanks
- aW
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
On Mon, Nov 18, 2002 at 05:07:08PM +1030, Wilkinson,Alex wrote:
Howdy crew,
Any reason why this doesn't work ?
sheelsudo boot0cfg -B ad0
boot0cfg: /dev/ad0: Operation not permitted
running: FreeBSD 5.0-CURRENT #0: Fri Nov 8 15:07:18 CST 2002
GEOM, I presume?
When file systems
20 matches
Mail list logo
