I want to thank Patrick, Dmitry and Mark for providing
orientation sufficient to make some headway. The Handbook
simply says
"If etcupdate(8) is not able to merge a file automatically,
the merge conflicts can be resolved with manual interaction
by issuing:
# etcupdate resolve
While not wrong,
[Note: In this 2nd try, I've indented everything by a tab
to help avoid reinterpretation/reformatting of some of the
text.]
I'm going to comment about the notations mean, not
about that the specific type of file is not one
you would be likely to have other than sn
o
On 15 Jun 2023, at 19:26, bob prohaska wrote:
>
> Here's an example of the puzzles faced when using etcupdate
> that have so far proved baffling:
>
> On running etcupdate resolve, the system reports
>
> Resolving conflict in '/etc/mtree/BSD.tests.dist':
> Select: (p) postpone, (df) diff-full, (
Hi,
> Am 15.06.2023 um 19:26 schrieb bob prohaska :
> The puzzle at this point is what to do. It's looks like the
> points of interest are the lines marked "yours" and "new",
> but I'll admit to bafflement which to modify and whether
> the modifications needed include the and > characters
Here's an example of the puzzles faced when using etcupdate
that have so far proved baffling:
On running etcupdate resolve, the system reports
Resolving conflict in '/etc/mtree/BSD.tests.dist':
Select: (p) postpone, (df) diff-full, (e) edit,
(h) help for more options: df
--- /etc/mtree/BS
On 30/05/2023 20:11, Dag-Erling Smørgrav wrote:
David Chisnall writes:
There was a very nasty POLA violation a release or two ago. OpenSSH
defaults to disallowing empty passwords and so having a null password
was a convenient way of allowing people to su or locally log into that
user but disal
Quoting bob prohaska (from Tue, 30 May 2023
08:36:21 -0700):
I suggest to review changes ("df" instead of "tf" in etcupdate) to at least
those files which you know you have modified, including the password/group
stuff. After that you can decide if the diff which is shown with "df" can be
appl
On May 30, 2023, at 18:39, bob prohaska wrote:
> On Tue, May 30, 2023 at 11:02:13AM -0700, Mark Millard wrote:
>> bob prohaska wrote on
>> Date: Tue, 30 May 2023 15:36:21 UTC :
>>
>>> On Tue, May 30, 2023 at 08:41:33AM +0200, Alexander Leidinger wrote:
Quoting bob prohaska (from Fri
On Tue, May 30, 2023 at 11:02:13AM -0700, Mark Millard wrote:
> bob prohaska wrote on
> Date: Tue, 30 May 2023 15:36:21 UTC :
>
> > On Tue, May 30, 2023 at 08:41:33AM +0200, Alexander Leidinger wrote:
> > >
> > > Quoting bob prohaska (from Fri, 26 May 2023 16:26:06
> > > -0700):
> > >
> > > >
W dniu 26.05.2023 o 19:35, bob prohaska pisze:
While going through normal security email from a Pi2
running -current I was disturbed to find:
Checking for passwordless accounts:
root::0:0::0:0:Charlie &:/root:/bin/sh
This thread reminded me of another issue with passwords I encountered a
few
David Chisnall writes:
> There was a very nasty POLA violation a release or two ago. OpenSSH
> defaults to disallowing empty passwords and so having a null password
> was a convenient way of allowing people to su or locally log into that
> user but disallowing ssh. This option does not work in r
bob prohaska wrote on
Date: Tue, 30 May 2023 15:36:21 UTC :
> On Tue, May 30, 2023 at 08:41:33AM +0200, Alexander Leidinger wrote:
> >
> > Quoting bob prohaska (from Fri, 26 May 2023 16:26:06
> > -0700):
> >
> > > On Fri, May 26, 2023 at 10:55:49PM +0200, Yuri wrote:
> > > >
> > > > The quest
On Tue, May 30, 2023 at 8:36 AM bob prohaska wrote:
>
> On Tue, May 30, 2023 at 08:41:33AM +0200, Alexander Leidinger wrote:
> >
> > Quoting bob prohaska (from Fri, 26 May 2023 16:26:06
> > -0700):
> >
> > > On Fri, May 26, 2023 at 10:55:49PM +0200, Yuri wrote:
> > > >
> > > > The question is how
On Tue, May 30, 2023 at 08:41:33AM +0200, Alexander Leidinger wrote:
>
> Quoting bob prohaska (from Fri, 26 May 2023 16:26:06
> -0700):
>
> > On Fri, May 26, 2023 at 10:55:49PM +0200, Yuri wrote:
> > >
> > > The question is how you update the configuration files,
> > > mergemaster/etcupdate/som
Quoting bob prohaska (from Fri, 26 May 2023
16:26:06 -0700):
On Fri, May 26, 2023 at 10:55:49PM +0200, Yuri wrote:
The question is how you update the configuration files,
mergemaster/etcupdate/something else?
Via etcupdate after installworld. In the event the system
requests manual int
> It turns out all seven hosts in my cluster report
> a null password for root in /usr/src/etc/master.passwd:
> root::0:0::0:0:Charlie &:/root:/bin/sh
>
> Is that intentional?
No, but I suspect your build/update procedures are infact telling
the system to do this. Someone else pointed out etcupd
> On 26 May 2023, at 12:35, bob prohaska wrote:
>
> > While going through normal security email from a Pi2
> > running -current I was disturbed to find:
> >
> > Checking for passwordless accounts:
> > root::0:0::0:0:Charlie &:/root:/bin/sh
> >
> > The machine had locked up on a -j4 buildworld sinc
On 27 May 2023, at 03:52, Mike Karels wrote:
>
> On 26 May 2023, at 21:28, bob prohaska wrote:
>
>> It turns out all seven hosts in my cluster report
>> a null password for root in /usr/src/etc/master.passwd:
>> root::0:0::0:0:Charlie &:/root:/bin/sh
>>
>> Is that intentional?
>
> Well, it has
On 26 May 2023, at 21:28, bob prohaska wrote:
> It turns out all seven hosts in my cluster report
> a null password for root in /usr/src/etc/master.passwd:
> root::0:0::0:0:Charlie &:/root:/bin/sh
>
> Is that intentional?
Well, it has been that way in FreeBSD since 1993, and in BSD since
1980 (4.
It turns out all seven hosts in my cluster report
a null password for root in /usr/src/etc/master.passwd:
root::0:0::0:0:Charlie &:/root:/bin/sh
Is that intentional?
Thanks for reading,
bob prohaska
On Fri, 26 May 2023 16:26:06 -0700
bob prohaska wrote:
> On Fri, May 26, 2023 at 10:55:49PM +0200, Yuri wrote:
> >
> > The question is how you update the configuration files,
> > mergemaster/etcupdate/something else?
> >
>
> Via etcupdate after installworld. In the event the system
> requests
On Fri, May 26, 2023 at 10:55:49PM +0200, Yuri wrote:
>
> The question is how you update the configuration files,
> mergemaster/etcupdate/something else?
>
Via etcupdate after installworld. In the event the system
requests manual intervention I accept "theirs all". It seems
odd if that can null
bob prohaska wrote:
> On Fri, May 26, 2023 at 07:48:04PM +0100, Ben Laurie wrote:
>> -T on ls will give you full time resolution...
>>
> More's the wonder:
> root@www:/usr/src # ls -lT /etc/*p*wd*
> -rw--- 1 root wheel 2099 May 10 17:20:33 2023 /etc/master.passwd
> -rw-r--r-- 1 root wheel
On Fri, May 26, 2023 at 07:48:04PM +0100, Ben Laurie wrote:
> -T on ls will give you full time resolution...
>
More's the wonder:
root@www:/usr/src # ls -lT /etc/*p*wd*
-rw--- 1 root wheel 2099 May 10 17:20:33 2023 /etc/master.passwd
-rw-r--r-- 1 root wheel 1831 May 10 17:20:33 2023 /e
-T on ls will give you full time resolution...
On Fri, 26 May 2023 at 19:45, bob prohaska wrote:
> On Fri, May 26, 2023 at 01:03:19PM -0500, Mike Karels wrote:
> > On 26 May 2023, at 12:35, bob prohaska wrote:
> >
> > > While going through normal security email from a Pi2
> > > running -current
On Fri, May 26, 2023 at 01:03:19PM -0500, Mike Karels wrote:
> On 26 May 2023, at 12:35, bob prohaska wrote:
>
> > While going through normal security email from a Pi2
> > running -current I was disturbed to find:
> >
> > Checking for passwordless accounts:
> > root::0:0::0:0:Charlie &:/root:/bin/
On 26 May 2023, at 12:35, bob prohaska wrote:
> While going through normal security email from a Pi2
> running -current I was disturbed to find:
>
> Checking for passwordless accounts:
> root::0:0::0:0:Charlie &:/root:/bin/sh
>
> The machine had locked up on a -j4 buildworld since
> sending the ma
While going through normal security email from a Pi2
running -current I was disturbed to find:
Checking for passwordless accounts:
root::0:0::0:0:Charlie &:/root:/bin/sh
The machine had locked up on a -j4 buildworld since
sending the mail, so it was taken off the net, power
cycled and started sin
28 matches
Mail list logo
