Re: Updating to FreeBSD-current, can't mount -uw / : update: seemingly solved

> In both cases, the entry is INcorrect. Juraj is correct. The swap entry is > missing sw > IOW the line MUST read as: > /dev/gpt/Sea1-18noneswapsw 0 0 > or > /dev/gpt/Sea1-18noneswapsw,trimonce 0 0 > as appropriate for the media referenced.

Re: kernel panic while copying files

On Mon, Jun 07, 2021 at 11:01:09AM +0200, Gary Jennejohn wrote: > I've seen this panic three times in the last two days: > > [first panic] > Unread portion of the kernel message buffer: > > > Fatal trap 12: page fault while in kernel mode > cpuid = 3; apic id = 03 > fault virtual address =

Re: What happen to mailing list archives?

On Mon, Jun 07, 2021 at 12:30:46AM -0700, Mark Millard wrote: > On 2021-Jun-6, at 13:25, Mark Millard wrote: > > > Baptiste Daroussin wrote on > > Date: Sun, 6 Jun 2021 10:53:49 +0200 : > > > >> What has happended: > >> plan A: we migrated everything off mailman/pipermail seamlessly with > >>

Re: Files in /etc containing empty VCSId header

On Mon, 2021-06-07 at 13:53 -0600, Warner Losh wrote: > On Mon, Jun 7, 2021 at 12:26 PM John Baldwin wrote: > > > On 5/20/21 9:37 AM, Michael Gmelin wrote: > > > Hi, > > > > > > After a binary update using freebsd-update, all files in /etc > > > contain > > > "empty" VCS Id headers, e.g., > > >

Re: Files in /etc containing empty VCSId header

On Mon, Jun 7, 2021 at 12:26 PM John Baldwin wrote: > On 5/20/21 9:37 AM, Michael Gmelin wrote: > > Hi, > > > > After a binary update using freebsd-update, all files in /etc contain > > "empty" VCS Id headers, e.g., > > > > $ head /etc/nsswitch.conf > > # > > # nsswitch.conf(5) -

Re: Files in /etc containing empty VCSId header

On 5/20/21 9:37 AM, Michael Gmelin wrote: Hi, After a binary update using freebsd-update, all files in /etc contain "empty" VCS Id headers, e.g., $ head /etc/nsswitch.conf # # nsswitch.conf(5) - name service switch configuration file # $FreeBSD$ # group: compat

Re: Updating to FreeBSD-current, can't mount -uw / : update: seemingly solved

On 2021-06-06 23:49, Graham Perrin wrote: On 07/06/2021 07:10, Juraj Lutter wrote: Bacause swap entry is in inapropriate format. The line should read: /dev/gpt/Sea1-18noneswapsw 0 0 Very well spotted, Juraj, but maybe a typo in your correction. A clearer view of

kernel panic while copying files

I've seen this panic three times in the last two days: [first panic] Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03 fault virtual address = 0x801118000 fault code = supervisor write data, page not present

Re: What happen to mailing list archives?

On 2021-Jun-6, at 13:25, Mark Millard wrote: > Baptiste Daroussin wrote on > Date: Sun, 6 Jun 2021 10:53:49 +0200 : > >> What has happended: >> plan A: we migrated everything off mailman/pipermail seamlessly with >> redirection >> and so on. We patched the new archiver to produce the same

Re: Updating to FreeBSD-current, can't mount -uw / : update: seemingly solved

On 07/06/2021 07:10, Juraj Lutter wrote: Bacause swap entry is in inapropriate format. The line should read: /dev/gpt/Sea1-18noneswapsw 0 0 Very well spotted, Juraj, but maybe a typo in your correction. A clearer view of the original

Re: Updating to FreeBSD-current, can't mount -uw / : update: seemingly solved

> On 7 Jun 2021, at 02:15, Thomas Mueller wrote: > > I updated a FreeBSD-current to the newest FreeBSD-current/14, buildworld took > 11:15 (hours:minutes), buildkernel was also successful, I even appeared to be > successful with "dhclient re0". > > UPDATING file says to boot single-user