On 7/18/21 2:21 PM, Graham Perrin wrote:
> On 16/07/2021 18:35, Warner Losh wrote:
>> # newfs_msdos -F 32 /dev/ada0p4
>> # mount -t msdos /dev/ada0p4 /boot/efi
>
>
> Typo: msdosfs, not msdos.
>
> Alternatively, mount_msdosfs(8).
>
> Alternatively (I agree, even better), incorporate things such
On 16/07/2021 18:35, Warner Losh wrote:
# newfs_msdos -F 32 /dev/ada0p4
# mount -t msdos /dev/ada0p4 /boot/efi
Typo: msdosfs, not msdos.
Alternatively, mount_msdosfs(8).
Alternatively (I agree, even better), incorporate things such as this in
the Handbook :-)
Then have the (ahem) book of
My deep apologies for the top post.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
On my laptop, which comes with W10 installed, I wanted to shrink W10 to
256G and put FreeBSD on a new 680G partition and make FreeBSD the default
boot.
This was all easy except setting up boot and making it default. I just
created a EFI/FreeBSD folder in the existing EFI partition (ada0p1) and
> On 16. Jul 2021, at 19:38, Warner Losh wrote:
>
> On Fri, Jul 16, 2021 at 6:14 AM Thomas Laus wrote:
>
>> Group:
>>
>> This is an issue for more than just CURRENT. The 'usr/src/UPDATING'
>> file has the instructions for updating the ZFS bootblocks but not the
>> EFI partition. I
On 7/16/21 1:35 PM, Warner Losh wrote:
>
> There should be. Yes. Last time I went hunting for a place to shoe-horn it
> in, I got distracted by something else.
>
> The instructions are relatively straight forward. I'm writing them here for
> your benefit, and also in case someone wants to send
On Fri, Jul 16, 2021 at 6:14 AM Thomas Laus wrote:
> Group:
>
> This is an issue for more than just CURRENT. The 'usr/src/UPDATING'
> file has the instructions for updating the ZFS bootblocks but not the
> EFI partition. I recently upgraded a RELEASE-12.2 to RELEASE-13.0. The
> freebsd-update
On Fri, Jul 16, 2021 at 3:15 PM Thomas Laus wrote:
>
> Since CURRENT receives more updates to the EFI boot loader than the
> release versions, there should be instructions in the CURRENT
> 'usr/src/UPDATING' file on how to update the EFI bootcode.
>
Old systems have little efi part 800K or
Group:
This is an issue for more than just CURRENT. The 'usr/src/UPDATING'
file has the instructions for updating the ZFS bootblocks but not the
EFI partition. I recently upgraded a RELEASE-12.2 to RELEASE-13.0. The
freebsd-update procedure did not upgrade the ZFS bootblocks. I forgot
that
e just too many booting variations for it to know what
is the right thing to do. And even if it could figure this out,
the boot partition may be too small :-)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/
On 2/11/21 9:34 PM, Bakul Shah wrote:
On Feb 11, 2021, at 7:13 PM, Russell L. Carter wrote:
root@terpsichore> gpart show
=> 34 625142381 da0 GPT (298G)
341281 freebsd-boot (64K)
16283886082 freebsd-swap (4.0G)
8388770 6167536453
On Feb 11, 2021, at 7:13 PM, Russell L. Carter wrote:
>
> root@terpsichore> gpart show
> => 34 625142381 da0 GPT (298G)
> 341281 freebsd-boot (64K)
>16283886082 freebsd-swap (4.0G)
>8388770 6167536453 freebsd-zfs (294G)
You can do
Carter
> > wrote:
> >
> >> Greetings,
> >>
> >> I really want to jump from stable/12 to stable/13 but one thing is
> >> causing a hesitancy. And that is, my main raidz2 system has
> >> a system boot zfs mirror pair that has boot partition size
> >&
raidz2 system has
a system boot zfs mirror pair that has boot partition size
(Mediasize) of 64K, and when I tried to zpool upgrade that pool a
year or 2 ago I got some scary message something like "boot
partition size is not large enough". I asked about this on the
lists but never received
gt; a system boot zfs mirror pair that has boot partition size
>> (Mediasize) of 64K, and when I tried to zpool upgrade that pool a
>> year or 2 ago I got some scary message something like "boot
>> partition size is not large enough". I asked about this on the
>> lists b
On Thu, Feb 11, 2021 at 05:34:40PM -0700, Russell L. Carter wrote:
> Greetings,
>
> I really want to jump from stable/12 to stable/13 but one thing is
> causing a hesitancy. And that is, my main raidz2 system has
> a system boot zfs mirror pair that has boot partition size
>
On Thu, Feb 11, 2021 at 04:43:57PM -0800 I heard the voice of
Freddie Cash, and lo! it spake thus:
>
> Sorry, meant 256 KB or 512 KB, not MB!
Worth remembering: at least in the past, there was also an _upper_
limit to the size based on the lower-level bootblocks that read the
freebs
. And that is, my main raidz2 system has
a system boot zfs mirror pair that has boot partition size
(Mediasize) of 64K, and when I tried to zpool upgrade that pool a
year or 2 ago I got some scary message something like "boot
partition size is not large enough". I asked about this on
ncy. And that is, my main raidz2 system has
>> a system boot zfs mirror pair that has boot partition size
>> (Mediasize) of 64K, and when I tried to zpool upgrade that pool a
>> year or 2 ago I got some scary message something like "boot
>> partition size is not large e
On Thu, Feb 11, 2021 at 4:35 PM Russell L. Carter
wrote:
> Greetings,
>
> I really want to jump from stable/12 to stable/13 but one thing is
> causing a hesitancy. And that is, my main raidz2 system has
> a system boot zfs mirror pair that has boot partition size
> (Mediasize
Greetings,
I really want to jump from stable/12 to stable/13 but one thing is
causing a hesitancy. And that is, my main raidz2 system has
a system boot zfs mirror pair that has boot partition size
(Mediasize) of 64K, and when I tried to zpool upgrade that pool a
year or 2 ago I got some scary
Trying to boot a kernel r249381 fails and I see on the console the
loader prompt at mountroot. Obviously, the bootloader doesn't find the
root/boot partition. On all FreeBSD 10 boxes I have this phenomenon is
the same, all boxes have GPT (UFS) partitions to boot from and set GPT
labels to address
On Sat, Apr 13, 2013 at 09:14:10AM +0200, O. Hartmann wrote:
Trying to boot a kernel r249381 fails and I see on the console the
loader prompt at mountroot. Obviously, the bootloader doesn't find
the root/boot partition.
Same problem observed here. r249435, gpt zfs root. Entering
zfs:zroot
On 13.04.2013 12:07 (UTC+2), Marcus Reid wrote:
On Sat, Apr 13, 2013 at 09:14:10AM +0200, O. Hartmann wrote:
Trying to boot a kernel r249381 fails and I see on the console the
loader prompt at mountroot. Obviously, the bootloader doesn't find
the root/boot partition.
Same problem observed
On Sat, 13 Apr 2013, Marcus Reid wrote:
On Sat, Apr 13, 2013 at 09:14:10AM +0200, O. Hartmann wrote:
Trying to boot a kernel r249381 fails and I see on the console the
loader prompt at mountroot. Obviously, the bootloader doesn't find
the root/boot partition.
Same problem observed here
On Sat, 2013-04-13 at 10:07 +, Marcus Reid wrote:
On Sat, Apr 13, 2013 at 09:14:10AM +0200, O. Hartmann wrote:
Trying to boot a kernel r249381 fails and I see on the console the
loader prompt at mountroot. Obviously, the bootloader doesn't find
the root/boot partition.
Same problem
On Tue, 26 Nov 2002, Robert Watson wrote:
tunefs changes the flag for the next mount, so doesn't take immediate
effect. Once you've tunefs'd a read-only file system, you need to unmount
and remount it -- for the file system root, this generally means
rebooting. Just to confirm: you're
at 23:34, [EMAIL PROTECTED] wrote...
How do I enable ACLs on the boot partition? tunefs -a enable /dev/ad0s1a
indicates it got set (in single user mode with / mounted readonly). But I
still can't set anything with setfacl(1). I tried booting to the fixit
floppy, hoping
On Wed, 27 Nov 2002, Bruce Evans wrote:
On Tue, 26 Nov 2002, Robert Watson wrote:
tunefs changes the flag for the next mount, so doesn't take immediate
effect. Once you've tunefs'd a read-only file system, you need to unmount
and remount it -- for the file system root, this generally
On Wed, 27 Nov 2002, Robert Watson wrote:
On Wed, 27 Nov 2002, Bruce Evans wrote:
On Tue, 26 Nov 2002, Robert Watson wrote:
tunefs changes the flag for the next mount, so doesn't take immediate
effect. Once you've tunefs'd a read-only file system, you need to unmount
and remount
On Thu, 28 Nov 2002, Bruce Evans wrote:
On Wed, 27 Nov 2002, Robert Watson wrote:
On Wed, 27 Nov 2002, Bruce Evans wrote:
On Tue, 26 Nov 2002, Robert Watson wrote:
tunefs changes the flag for the next mount, so doesn't take immediate
effect. Once you've tunefs'd a read-only
On Wed, 27 Nov 2002, Robert Watson wrote:
On Thu, 28 Nov 2002, Bruce Evans wrote:
On Tue, 26 Nov 2002, Robert Watson wrote:
Er, what is the mount(..., MNT_RELOAD ...) in tunefs for then?
The problem is that some flags can't be changed via MNT_RELOAD and require
a
On 25 Nov 2002 at 23:34, [EMAIL PROTECTED] wrote...
How do I enable ACLs on the boot partition? tunefs -a enable /dev/ad0s1a
indicates it got set (in single user mode with / mounted readonly). But I
still can't set anything with setfacl(1). I tried booting to the fixit
floppy, hoping to set
On Tue, 26 Nov 2002, Bruno Miguel wrote:
On 25 Nov 2002 at 23:34, [EMAIL PROTECTED] wrote...
How do I enable ACLs on the boot partition? tunefs -a enable /dev/ad0s1a
indicates it got set (in single user mode with / mounted readonly). But I
still can't set anything with setfacl(1). I tried
On Tue, Nov 26, 2002 at 11:21:28AM -0700, [EMAIL PROTECTED] wrote the words in effect
of:
On Tue, 26 Nov 2002, Bruno Miguel wrote:
On 25 Nov 2002 at 23:34, [EMAIL PROTECTED] wrote...
How do I enable ACLs on the boot partition? tunefs -a enable /dev/ad0s1a
indicates it got set
On Tue, 26 Nov 2002, Hiten Pandya wrote:
On Tue, Nov 26, 2002 at 11:21:28AM -0700, [EMAIL PROTECTED] wrote the words in
effect of:
On Tue, 26 Nov 2002, Bruno Miguel wrote:
On 25 Nov 2002 at 23:34, [EMAIL PROTECTED] wrote...
How do I enable ACLs on the boot partition? tunefs
do I enable ACLs on the boot partition? tunefs -a enable /dev/ad0s1a
indicates it got set (in single user mode with / mounted readonly). But I
still can't set anything with setfacl(1). I tried booting to the fixit
floppy, hoping to set acls flag from there to my partition
How do I enable ACLs on the boot partition? tunefs -a enable /dev/ad0s1a
indicates it got set (in single user mode with / mounted readonly). But I
still can't set anything with setfacl(1). I tried booting to the fixit
floppy, hoping to set acls flag from there to my partition, but it doesn't
have
On Fri, Oct 13, 2000 at 07:22:20AM -0500, Mike Meyer scribbled:
| Just curious - now that the kernel has moved into /boot/kernel/kernel,
| does anyone know how well would it work to put /boot in it's own
| partition (possibly in it's own slice)?
I do not think loader can see stuff in
On Tue, 17 Oct 2000, Terry Lambert wrote:
I could have a 40G /, and not worry about the cylinder spanning
problem, if my /boot were in a seperate (low) partition.
I could have a / that was of an FS type not understood by the
kernel, until after a module defining the FS type had been
loaded.
I
On Fri, Oct 13, 2000 at 07:18:05PM +0300, Maxim Sobolev wrote:
Nope, the loader can load stuff from other partitions, even from some strange
ones like msdos ;), so theoretically it should be possible to have /boot, or
even /boot/kernel, on another partition (it may require to tweak loader
David O'Brien writes:
On Fri, Oct 13, 2000 at 07:18:05PM +0300, Maxim Sobolev wrote:
Nope, the loader can load stuff from other partitions, even from some strange
ones like msdos ;), so theoretically it should be possible to have /boot, or
even /boot/kernel, on another partition (it may
Maxim Sobolev writes:
"Michael C . Wu" wrote:
On Fri, Oct 13, 2000 at 07:22:20AM -0500, Mike Meyer scribbled:
| Just curious - now that the kernel has moved into /boot/kernel/kernel,
| does anyone know how well would it work to put /boot in it's own
| partition (possibly in it's own
On Fri, Oct 13, 2000 at 12:39 -0500, Mike Meyer wrote:
[ ... separate /boot partition ... ]
Since you implied a question...
This is a standard setup for Linux, so Linux people dealing with
problems with the root file system try and make it work in -stable
(with no luck). The best
Just curious - now that the kernel has moved into /boot/kernel/kernel,
does anyone know how well would it work to put /boot in it's own
partition (possibly in it's own slice)?
Thanx,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the
On Fri, Oct 13, 2000 at 07:22:20AM -0500, Mike Meyer scribbled:
| Just curious - now that the kernel has moved into /boot/kernel/kernel,
| does anyone know how well would it work to put /boot in it's own
| partition (possibly in it's own slice)?
I do not think loader can see stuff in other
"Michael C . Wu" wrote:
On Fri, Oct 13, 2000 at 07:22:20AM -0500, Mike Meyer scribbled:
| Just curious - now that the kernel has moved into /boot/kernel/kernel,
| does anyone know how well would it work to put /boot in it's own
| partition (possibly in it's own slice)?
I do not think
"Michael C . Wu" wrote:
On Fri, Oct 13, 2000 at 07:22:20AM -0500, Mike Meyer scribbled:
| Just curious - now that the kernel has moved into /boot/kernel/kernel,
| does anyone know how well would it work to put /boot in it's own
| partition (possibly in it's own slice)?
I do not
48 matches
Mail list logo
