On Mon, Aug 22, 2022 at 12:29 PM Bjoern A. Zeeb <
bzeeb-li...@lists.zabbadoz.net> wrote:
> On Mon, 22 Aug 2022, Warner Losh wrote:
>
> Hi,
>
> > On Mon, Aug 22, 2022 at 9:17 AM Konstantin Belousov >
> > wrote:
> >
> >> On Mon, Aug 22, 2022 at 02:56:47PM +, Bjoern A. Zeeb wrote:
> >>> Hi,
>
On Mon, 22 Aug 2022, Warner Losh wrote:
Hi,
On Mon, Aug 22, 2022 at 9:17 AM Konstantin Belousov
wrote:
On Mon, Aug 22, 2022 at 02:56:47PM +, Bjoern A. Zeeb wrote:
Hi,
I am trying to get some arm64 up and running a bit but cannot use
loader. I have an MD_ROOT embedded in the kernel
On 2022-08-22 12:29, Peter Jeremy wrote:
On 2022-Aug-22 10:56:51 +0200, "Patrick M. Hausen" wrote:
Am 22.08.2022 um 10:45 schrieb Peter Jeremy :
On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" wrote:
Isn't beadm retired in favour of bectl?
2) "bectl activate" doesn't update
On Mon, Aug 22, 2022 at 9:17 AM Konstantin Belousov
wrote:
> On Mon, Aug 22, 2022 at 02:56:47PM +, Bjoern A. Zeeb wrote:
> > Hi,
> >
> > I am trying to get some arm64 up and running a bit but cannot use
> > loader. I have an MD_ROOT embedded in the kernel with /rescue on it.
> > I set
On Mon, Aug 22, 2022 at 02:56:47PM +, Bjoern A. Zeeb wrote:
> Hi,
>
> I am trying to get some arm64 up and running a bit but cannot use
> loader. I have an MD_ROOT embedded in the kernel with /rescue on it.
> I set INIT_PATH=/rescue/sh .
>
> However that doesn't seem to work:
>
>
On Mon, Aug 22, 2022 at 5:10 AM Ronald Klop wrote:
>
>
>
> Van: Peter Jeremy
> Datum: maandag, 22 augustus 2022 10:45
> Aan: "Patrick M. Hausen"
> CC: Ryan Moeller , freebsd-current@freebsd.org
> Onderwerp: Re: Beadm can't create snapshot
>
> On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen"
Hi,
I am trying to get some arm64 up and running a bit but cannot use
loader. I have an MD_ROOT embedded in the kernel with /rescue on it.
I set INIT_PATH=/rescue/sh .
However that doesn't seem to work:
start_init: trying /rescue/sh
init died (signal 0, exit 0)
panic: Going nowhere without my
Van: Peter Jeremy
Datum: maandag, 22 augustus 2022 10:45
Aan: "Patrick M. Hausen"
CC: Ryan Moeller , freebsd-current@freebsd.org
Onderwerp: Re: Beadm can't create snapshot
On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" wrote:
>Isn't beadm retired in favour of bectl?
bectl still has a
hi All
I know this is not the ports list , but the problem only happens in CURRENT
anyway
BitchX from ports (at least for me and i've installed freebsd current several
times here with the same result) uses CC to compile and in freebsd CURRENT its
getting segfault as soon as BitchX connects
Still the same with current.(from today).
Opening a PR for it..
Santi
On 8/22/22 10:43, Santiago Martinez wrote:
Thanks Toommas,
I compiling current right now and will give it a try, hopefully, will
be able to mount and recover the machine.
Will also open a PR as even if the is any
On 2022-Aug-22 10:56:51 +0200, "Patrick M. Hausen" wrote:
>> Am 22.08.2022 um 10:45 schrieb Peter Jeremy :
>> On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" wrote:
>>> Isn't beadm retired in favour of bectl?
>>
>> 2) "bectl activate" doesn't update /boot/loader.conf so the wrong
>> root
Hi,
> Am 22.08.2022 um 10:45 schrieb Peter Jeremy :
>
> On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" wrote:
>> Isn't beadm retired in favour of bectl?
>
> bectl still has a number of bugs:
> 1) The output from "bectl list" is in filesystem/bename order rather
> than creation date
On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" wrote:
>Isn't beadm retired in favour of bectl?
bectl still has a number of bugs:
1) The output from "bectl list" is in filesystem/bename order rather
than creation date order. This is an issue if you use (eg) git
commit hashes as the
Thanks Toommas,
I compiling current right now and will give it a try, hopefully, will be
able to mount and recover the machine.
Will also open a PR as even if the is any corruption/pool damage it
should not panic the machine.
Santi
On 8/18/22 21:45, Toomas Soome wrote:
On 18. Aug 2022,
14 matches
Mail list logo
