Topic: Lenovo Laptops and bsdinstall zfsboot with MBR layout...
Should we do the quick patch to change the default
from /boot/boot0 to /boot/mbr:
Index: zfsboot
===
--- zfsboot (revision 258016)
+++ zfsboot (working copy)
@@
in making sure Allan and I design
a worthy bootcode selection menu.
These seems like the best approach for now, based on the feedback I have
gotten from people with BIOSs that won't boot GPT and often choke on the
boot0 boot manager.
--
Allan Jude
signature.asc
Description: OpenPGP digital signature
FreeBSD boot manager or something), which also
means it works for UFS systems.
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr
for tradition. #3 is probably best done as a
post-install config step (Install FreeBSD boot manager or
something), which also means it works for UFS systems.
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
except for tradition. #3 is probably best done as a
post-install config step (Install FreeBSD boot manager or
something), which also means it works for UFS systems.
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
except for tradition. #3 is probably best done as a post-install config step
(Install FreeBSD boot manager or something), which also means it works for
UFS systems.
Well, I'm sensitive to the fact that sysinstall offered none and
even explained why in an F1 dialog that brought up drives.hlp
Unifying 1 and 2 would help a lot -- I don't know of any reason we
need both except for tradition. #3 is probably best done as a
post-install config step (Install FreeBSD boot manager or
something), which also means it works for UFS systems.
-Nathan
of any reason we need both
except for tradition. #3 is probably best done as a post-install config step
(Install FreeBSD boot manager or something), which also means it works for
UFS systems.
Well, I'm sensitive to the fact that sysinstall offered none and
even explained why in an F1 dialog
both except for
tradition. #3 is probably best done as a post-install config step (Install FreeBSD
boot manager or something), which also means it works for UFS systems.
Well, I'm sensitive to the fact that sysinstall offered none and
even explained why in an F1 dialog that brought up drives.hlp
3. boot0
Unifying 1 and 2 would help a lot -- I don't know of any reason we need
both except for tradition. #3 is probably best done as a post-install
config step (Install FreeBSD boot manager or something), which also means
it works for UFS systems.
Well, I'm sensitive to the fact
. UFS boot code
3. boot0
Unifying 1 and 2 would help a lot -- I don't know of any reason we need both except for
tradition. #3 is probably best done as a post-install config step (Install FreeBSD
boot manager or something), which also means it works for UFS systems.
Well, I'm sensitive to the fact
manager or something), which also
means it works for UFS systems.
Well, I'm sensitive to the fact that sysinstall offered none and
even explained why in an F1 dialog that brought up drives.hlp
to explain that you might want to keep whatever (alternate) boot
manager you may be using already
except for tradition. #3 is probably best done as a
post-install config step (Install FreeBSD boot manager or
something), which also means it works for UFS systems.
-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman
-- I don't know of any reason we
need both except for tradition. #3 is probably best done as a
post-install config step (Install FreeBSD boot manager or
something), which also means it works for UFS systems.
-Nathan
___
freebsd-current@freebsd.org mailing
On 11/11/13 18:22, Julian Elischer wrote:
On 11/11/13, 1:32 PM, Nathan Whitehorn wrote:
On 11/11/13 15:19, Teske, Devin wrote:
Topic: Lenovo Laptops and bsdinstall zfsboot with MBR layout...
Should we do the quick patch to change the default
from /boot/boot0 to /boot/mbr:
Index: zfsboot
On Fri, 9 Jun 2000, John Hengstler wrote:
Greetings,
What is the quick way to restore the boot manager (dual os). Lost it when I
reloaded Win98.
man boot0cfg
Doug White| FreeBSD: The Power to Serve
[EMAIL PROTECTED] | www.FreeBSD.org
To Unsubscribe: send mail
Greetings,
What is the quick way to restore the boot manager (dual os). Lost it when I
reloaded Win98.
Have 4.0 CD, machine running 5.0-current.
John Hengstler
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ÓÒ , 30 ÉÀÎ 1999, Thomas Dean ÎÁÐÉÓÁÌ:
I installed -current on a notebook with WINNT on the disk. The
notebook has the ide disk limitation. So, I chopped the disk do get
around it. Maybe I should buy a new notebook, but, this one works.
Everything worked OK, except the boot manager. I
I installed -current on a notebook with WINNT on the disk. The
notebook has the ide disk limitation. So, I chopped the disk do get
around it. Maybe I should buy a new notebook, but, this one works.
Everything worked OK, except the boot manager. I get:
F1 ??
F2 FreeBSD
F3 ??
F4
On 30-Jun-99 Thomas Dean wrote:
I installed -current on a notebook with WINNT on the disk. The
notebook has the ide disk limitation. So, I chopped the disk do get
around it. Maybe I should buy a new notebook, but, this one works.
Everything worked OK, except the boot manager. I get
In the last episode (Jun 29), Thomas Dean said:
I installed -current on a notebook with WINNT on the disk. The
notebook has the ide disk limitation. So, I chopped the disk do get
around it. Maybe I should buy a new notebook, but, this one works.
Everything worked OK, except the boot
21 matches
Mail list logo
