odification. I'm unclear
on the situation with other architectures.
hth,
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
t; in /usr/src to no avail, is there something else
to try, or should I just wait for a source update?
Thanks for reading,
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
On Sat, Jun 09, 2018 at 04:13:08PM -0400, Mark Johnston wrote:
> On Sat, Jun 09, 2018 at 01:07:24PM -0700, bob prohaska wrote:
> > I'm seeing persistent
> > --- dwarf.o ---
> > /usr/src/cddl/contrib/opensolaris/tools/ctf/cvt/dwarf.c:1980:8: error: use
> > of undecla
/clang/libllvm
*** [all_subdir_lib/clang/libllvm] Error code 2
make[5]: stopped in /usr/src/lib/clang
I'll try again, this time with USB swap turned off.
Thanks for reading!
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://li
On Thu, Jun 07, 2018 at 05:13:45PM -0700, bob prohaska wrote:
>
> I'll try again, this time with USB swap turned off.
The circle closed, back to the original panic in the subject line.
Console, top and buildworld.log files are at
http://www.zefox.net/~fbsd/rpi3/crashes/20180607
essions, doing an explict "make clean" or
"rm -rf /usr/obj/usr" when necessary. In a few cases it
seemed helpful to start with "make kernel-toolchain" then
follow with make -DNO_CLEAN buildworld" but I didn't keep
good enough records to be
rld logs in
http://www.zefox.net/~fbsd/rpi3/swaptests/
The more recent experiments are sorted by revision first, then swap config
and then other modifications.
If I can do anything to make the records more useful please let me know.
hth,
bob prohaska
_
ll-informed, but if there's any hope of success I'd like to try
it.
>From time to time there seem to be traffic jams among flash devices on the
>RPI3, it
would a pleasant surprise if this feature helps.
Thanks for reading!
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
blocks the TRIM service
the behavior of the device doesn't matter.
As an aside, Sandisk now says:
"Please be informed that we have not tested running TRIM commands on USB flash
drive
and microSD cards therefore we would not be able to comment on it explicitly."
Thanks f
On Mon, Jul 23, 2018 at 08:25:59PM -0600, Ian Lepore wrote:
> On Mon, 2018-07-23 at 18:54 -0700, bob prohaska wrote:
> > at sdiff, the learning curve proved very steep. Too steep, in fact.
> >
> > I'm going to try a more incremental approach.?
> >
> > Thank you _
t.
I'm going to try a more incremental approach.
Thank you _very_ much!
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Mon, Jul 23, 2018 at 09:28:41PM -0700, Kevin Oberman wrote:
> On Mon, Jul 23, 2018 at 7:25 PM, Ian Lepore wrote:
>
> > On Mon, 2018-07-23 at 18:54 -0700, bob prohaska wrote:
> > > On Mon, Jul 23, 2018 at 09:34:26PM +0200, Herbert J. Skuhra wrote:
> > > >
>
les.
There's minimal customization on the machine, basically /etc/fstab,
/etc/rc.conf and /etc/passwd. Nothing else of real value, so if I kill
it in the attempt it won't be a disaster.
Thanks for waking me to my blunder...
bob prohaska
___
freebsd-curr
yond locking) to secure the ntpd
account please warn me.
Thanks for reading,
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Sun, Jul 22, 2018 at 01:49:41AM +0200, Herbert J. Skuhra wrote:
> On Sat, Jul 21, 2018 at 03:09:26PM -0700, bob prohaska wrote:
> > The failure is a little surprising, is ntpd a reserved name?
>
> Why? You obviously entered the string "ntpd" instead of an integer
over 4 RPi2's and 2 RPi3's, has been good.
> I can't tell, however, if they are better in case of power loss
> related data corruption.
>
Never done a systematic test, but accidental unplugs and power cycles
after a crash have never caused problems fsck -f won't fix.
hth,
bob prohaska
On Mon, Apr 09, 2018 at 06:04:24AM -0700, Mark Millard wrote:
> On 2018-Apr-8, at 10:08 PM, bob prohaska wrote:
> >> . . .
> > On my RPi3
> > root@www:/usr/src # ls -l /usr/lib/clang/6.0.0/include/stdint.h
> > -rw-r--r-- 1 root wheel 23387 Feb 16 07:37
&g
e included from /usr/lib/clang/6.0.0/include/arm_neon.h:31:
There's a "-I/usr/src/sys" in the fourth line, which in my case makes sense,
but where does the reference to /usr/lib/clang/ come from, and is it
appropriate?
> > If the two problems are related, should the subject li
ory UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
> Revision: 332293
> Last Changed Rev: 332293
>
>
> I do not have an arm64 system that is anywhere near up to
> date at this time so the above evidence is not from a
> self-hosted build: My context is not a full-match.
>
Loo
ost system's (already-stale) software?
If the two problems are related, should the subject line on the bug
report be changed?
Thanks for reading,
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/fre
gs like make -j8 buildworld and running of stress2's
default test suite. It doesn't seem to be a serial issue in that case.
Hard to believe you're seeing something related, but my $.02 anyway.
bob prohaska
___
freebsd-current@freebsd.org mailing list
https:
On Wed, Mar 21, 2018 at 09:49:34PM -0700, bob prohaska wrote:
> On Wed, Mar 21, 2018 at 12:07:18PM +0100, Hartmann, O. wrote:
> >
> > not the ZFS. I can plugin the USB and then unplug it and after two or
> > three times doing this, the box goes down.
> >
> &
od continued).
The console flood came back after a quick power disconnect/reconnect, but
finally stopped when the power was left off for a minute or so. Then all
returned to normal.
Thanks for reading!
bob prohaska
___
freebsd-current@freebsd.org mailin
On Sun, Mar 18, 2018 at 08:50:33PM -0700, bob prohaska wrote:
> On Sun, Mar 18, 2018 at 05:54:30PM -0700, Mark Millard wrote:
> > bob prohaska fbsd at www.zefox.net wrote on
> > Sun Mar 18 21:09:42 UTC 2018 :
> >
> > > On Sun, Mar 11, 2018 at 10:43:5
orting c++ killed, apparently for want of swap,
even though swap usage never exceeded about 30% accoring to top.
The machine employs UFS filesystems, the kernel config can be seen at
http://www.zefox.net/~fbsd/rpi3/kernel_config/ZEFOX
Thanks for reading, I hope it's useful.
bob pr
s1 target 0 lun 0
da1: Removable Direct Access SPC-4 SCSI device
da1: Serial Number AA010428162242131598
da1: 40.000MB/s transfers
da1: 59836MB (122544516 512 byte sectors)
da1: quirks=0x2
Thanks for reading, I hope it's useful.
bob prohaska
___
freebs
On Sun, Mar 18, 2018 at 05:54:30PM -0700, Mark Millard wrote:
> bob prohaska fbsd at www.zefox.net wrote on
> Sun Mar 18 21:09:42 UTC 2018 :
>
> > On Sun, Mar 11, 2018 at 10:43:58AM -1000, Jeff Roberson wrote:
> >
> > > Also, if you could try going back to r328
/Target/X86/X86ISelDAGToDAG.cpp:3072:3: error: use of
undeclared identifier 'SelectCode'
SelectCode(Node);
Should I wait for an update, or run cleandir? This is on a Pi3.
Thanks for reading,
bob prohaska
___
freebsd-current@freebsd.org mailing list
https
: 344113
Any idea what's going on?
Thanks for reading
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
, a firstboot script that
asked the user for some configuration information would be a great help
to both new and experienced foot-shooters. I'm thinking of Raspberry Pi,
but perhaps it applies to non-embedded platforms also.
The original FreeBSD install program (the one by Jordan Hubbard) did a
very servic
On Fri, May 03, 2019 at 07:39:00PM -0700, Rodney W. Grimes wrote:
> > On Fri, May 3, 2019, 7:42 PM bob prohaska wrote:
> >
> > > On Fri, May 03, 2019 at 11:06:15AM -0700, Rodney W. Grimes wrote:
> > > > -- Start of PGP signed section.
> > > > >
fixed asking a new user to start
by using gpart is unlikely to encourage further exploration.
Thanks for your attention!
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, s
isn't freeing swap in a timely manner?
Thanks for reading,
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Fri, Sep 13, 2019 at 10:59:58PM -0700, Mark Millard wrote:
> bob prohaska fbsd at www.zefox.net wrote on
> Fri Sep 13 16:24:57 UTC 2019 :
>
> > Not sure this is relevant, but in compiling chromium on a Pi3 with 6 GB
> > of swap the job completed successfully some month
exiting the shell
brought multi-user operation. Still, It appears that recognition
of an FTDI FT232 usb-serial adapter is impaired as well. It had to
be unplugged and replugged after booting to be recognized.
Also FWIW, an RPI3 running r355422 seems not to share
On Wed, Nov 20, 2019 at 11:18:41AM -0700, Warner Losh wrote:
> On Wed, Nov 20, 2019 at 10:39 AM bob prohaska wrote:
>
> > From time to time it would be handy to revert freebsd-current to
> > an older, well-behaved revision.
> >
> > Is there a mechanism fo
t's hardware, maybe something else. Is
there a way to pick a revision number to revert to, that's
better than merely guessing?
Thanks for reading,
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-curr
achine was heavily loaded, but storage didn't appear to be
swamped.
I hope the foregoing has been of some interest, thanks for reading!
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-c
On Sat, Nov 30, 2019 at 05:16:15PM -0800, bob prohaska wrote:
> A Pi3 running r355024 reported a panic while doing a -j3 make of
> www/chromium:
>
Ok, another panic, looks like a dying storage device. This time there
was a preamble on the console:
(da0:umass-sim0:0:0:0): READ(10). CDB:
e
unreasonable. Sad but not surprising. At least now I know.
Thanks to everyone for enlightening me,
bob prohaska
> >>
> >> . . .
> >
>
> ===
> Mark Millard
> marklmi at yahoo.com
> ( dsl-only.net went
> away in early 2018-Mar)
>
>
u to
> download, as well, if you'd accept that.
>
If I understand correctly there's no need, if I'm mistaken please let me
know.
Thanks for your attention!
bob prohaska
> Thanks,
>
> Kyle Evans
___
freebsd-current@freebsd.org mailing list
htt
increase kern.maxswzone or reduce amount of swap.
Starting file system checks:
At this point things returned to normal.
Thanks for reading, I hope it's useful.
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
, on a Pi3 without WiFi nor bluetooth, to add
enable_uart=1
to config.txt?
At this point config.txt contains
arm_control=0x200
dtparam=audio=on,i2c_arm=on,spi=on
dtoverlay=mmc
dtoverlay=pwm
dtoverlay=pi3-disable-bt
device_tree_address=0x4000
kernel=u-boot.bin
and is, I think, default.
Thanks
ing
Thanks for reading!
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Tue, Jan 28, 2020 at 11:28:14AM -0800, Mark Millard wrote:
>
>
> On 2020-Jan-28, at 11:02, bob prohaska wrote:
>
> > On Tue, Jan 28, 2020 at 09:42:17AM -0800, Mark Millard wrote:
> >>
> >>
> >>
> > The (partly)modified kernel compiled
On Thu, Aug 27, 2020 at 10:02:21AM -0700, bob prohaska wrote:
> On Tue, Aug 25, 2020 at 11:29:16AM -0700, bob prohaska wrote:
>
> > With a _different_ FT232 plugged in it also came up normally.
> >
> > Both are thought to be genuine, but they are of different age
&
= 0x5d96c980
handle_el0_sync() at 0x40421150
pc = 0x0072c224 lr = 0x40421150
sp = 0x5d96c990 fp = 0xd830
KDB: enter: panic
[ thread pid 2429 tid 100951 ]
Stopped at 0x403fa408
db>
Thanks for reading,
bob proha
rals. They've
caused no obvious trouble, if you anticipate conflicts let me know
and I'll remove them
I've never seen either a vmcore file or debug symbols on this machine.
A sequence of instructions to generate the data needed would be helpful.
Thanks for r
tdi0 on uhub1
uftdi0: on usbus1
The one that seems to work is newer and reports
ugen1.4: at usbus1
uftdi0 on uhub1
uftdi0: on usbus1
On balance I think the new kernel is better-behaved. Beyond that
I'm at a loss. If you can suggest other things to try please do.
Thanks for all your help,
On Tue, Aug 25, 2020 at 12:46:01AM +0200, Hans Petter Selasky wrote:
> On 2020-08-24 18:37, bob prohaska wrote:
> > After updating to
> > FreeBSD 13.0-CURRENT (GENERIC) #5 r364475: Mon Aug 24 06:47:29 PDT 2020
> > on a Pi3 it was necessary to disconnect the mouse, keyboard an
On Tue, Aug 25, 2020 at 11:29:16AM -0700, bob prohaska wrote:
> With a _different_ FT232 plugged in it also came up normally.
>
> Both are thought to be genuine, but they are of different age
> and produce different recognition messages:
>
> The FT232 that causes trouble
with FT232 obstructing disk detection
in some cases and self-disconnecting in others on a Pi3B.
Thanks for reading,
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send a
, but
the "giving up port reset" _is_ new at least to me.
Are there any experiments which might narrow down what's wrong?
Thanks for reading,
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freeb
On Mon, Aug 24, 2020 at 05:26:27PM +, Bjoern A. Zeeb wrote:
> On 24 Aug 2020, at 16:37, bob prohaska wrote:
>
> >
> > uhub_reattach_port: giving up port reset - device vanished
> > uhub_reattach_port: giving up port reset - device vanished
> > uhub_reattach_port:
eem to find core
dumps when coming up after a crash. It does routinely issue "no core dumps
found" during reboot, so it's looking. It it necessary to issue a dump
command from inside the debugger?
Thanks for writing!
bob prohaska
___
Is there any error checking on swap traffic, along the lines of
a checksum or parity test?
Just curious what happens if a page written out is corrupted when
it comes back.
Thanks for reading,
bob prohaska
___
freebsd-current@freebsd.org mailing
On Sun, Jul 12, 2020 at 12:29:12AM -0700, John-Mark Gurney wrote:
> bob prohaska wrote this message on Sat, Jul 11, 2020 at 20:33 -0700:
> > Is there any error checking on swap traffic, along the lines of
> > a checksum or parity test?
> >
> > Just curious what ha
hits.
Good luck,
bob prohaska
On Sun, Jun 07, 2020 at 04:27:24PM +, Filippo Moretti wrote:
> Good evening, FreeBSD sting
> 13.0-CURRENT FreeBSD 13.0-CURRENT #2 r361787: Sun Jun?? 7 15:02:09 CEST
> 2020 root@sting:/usr/obj/usr/
ing
the repository solved the problem.
Thanks for reading,
bob prohaska
>
>
> Regards,
> Ronald.
>
>
> Van: bob prohaska
> Datum: 4 juni 2020 21:24
> Aan: freebsd-current@freebsd.org
> CC: bob prohaska
> Onderwerp: Recovering after a crash during installwor
i-user without problems, but attempts to update
or simply rebuild the system run afoul of the svnlite errors.
Is there a practical way to recover?
Thanks for reading,
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freeb
seems to work fine on the Pi3.
Thanks for replying!
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
iming issues.
>
Is there some way to obtain git on a Pi2B running
13.0-CURRENT FreeBSD 13.0-CURRENT #2 r365692
without installing the ports tree? I expected
to find git in base, but it isn't there.
Can it be found under another package name?
Thanks for reading, and any guidance
t, but if I've
made other mistakes please point them out.
Thanks for your help!
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
DIAGNOSTIC
> >> nooptions BUF_TRACKING
> >> nooptions FULL_BUF_TRACKING
> >> nooptions USB_DEBUG
> >> nooptions USB_REQ_DEBUG
> >> nooptions USB_VERBOSE
> >>
> >> The /boot/loader.conf file and the /et
a new kernel was compiled to fix the "won't boot with HDMI connected"
problem on Raspberry Pi.
Thanks for explaining!
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
or two newer.
Nothing is obviously wrong; swap usage is small, no warnings or errors on the
console.
In past occurrences, an old kernel (pre-git) worked through the problem.
If a restart of make buildworld doesn't get past the stoppage I'll check again.
Thanks for reading,
bob prohaska
On Fri, Jan 15, 2021 at 09:25:00PM -0800, Mark Millard wrote:
>
> On 2021-Jan-15, at 20:37, bob prohaska wrote:
>
> > While playing with -current on armv7 using a raspberry pi 2 v1.1
> > an error crops up with recent kernels while building world:
> >
> >
On Sat, Jan 16, 2021 at 11:17:52AM -0800, Mark Millard wrote:
>
>
> On 2021-Jan-16, at 07:55, bob prohaska wrote:
>
> > On Fri, Jan 15, 2021 at 09:25:00PM -0800, Mark Millard wrote:
> >>
> >> On 2021-Jan-15, at 20:37, bob prohaska wrote:
> >>
>
On Sun, Jan 17, 2021 at 12:30:51PM -0800, Mark Millard wrote:
>
>
> On 2021-Jan-17, at 09:40, bob prohaska wrote:
>
> > On Sat, Jan 16, 2021 at 03:04:04PM -0800, Mark Millard wrote:
> >>
> >> Other than -j1 style builds (or equivalent), one pretty much
&g
are computed, and roughly what they mean?
I've noticed that different sources sometimes produce the
same values, so the level of detail is less, but might suffice
for initial reports to the mailing lists.
Thanks for reading,
bob prohaska
___
freebsd-current
ages?
Thanks for reading!
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
nnot create
'refs/remotes/freebsd/vendor/openzfs/zfs-2.1-release'
! [new branch] vendor/openzfs/zfs-2.1-release ->
freebsd/vendor/openzfs/zfs-2.1-release (unable to update local ref)
Is this a problem at my end, or the server's end?
Thanks for reading,
bob prohaska
On Tue, Mar 02, 2021 at 09:46:11AM -0700, Warner Losh wrote:
> On Tue, Mar 2, 2021 at 9:18 AM bob prohaska wrote:
>
> > A while back I obtained a buildable source tree for stable/13
> > but it hasn't been updated in the last few days. Running
>
> It would help
.
This is used for self-hosting on a Raspberry Pi, if it matters.
bob prohaska
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
at sys___sysctl+0x68
do_el0_sync() at do_el0_sync+0x520
handle_el0_sync() at handle_el0_sync+0x40
--- exception, esr 0x5600
KDB: enter: panic
[ thread pid 869 tid 100091 ]
Stopped at kdb_enter+0x44: undefined f902011f
I tried typing bt at the debugger prompt but got no more output.
I've put the buildworld log file at
http://www.zefox.net/~fbsd/rpi3/crashes/20220307/
Hope this is of some use
bob prohaska
d.log
Thanks for reading,
bob prohaska
one, you can locally
> copy the tree over to the armv7 media. But that is
> not the point of my suggestion above.
Under the circumstances it seems like the path of
least resistance. Can I do something simple like
sftp, using get -r ? Any trick to updating the copy?
Many thanks!
bob prohaska
On Fri, Aug 25, 2023 at 02:21:33AM -0700, Mark Millard wrote:
>
> That will not help avoid the R_AARCH64_ABS64 abuse,
> unfortunately.
>
>
Thank you for the analysis. I've posted a bug,id=273349.
Sounds like I shouldn't hold my breath 8-(
bob prohaska
>
*** Error code 1
No messages on the console at all, no indication of any swap use at all.
If somebody can tell me how to invoke MAKE_JOBS_UNSAFE=yes, either
locally or globally, I'll give it a try. But, if it's a system problem
I'd expect at least a peep on the console....
Thanks for reading,
bob prohaska
On Thu, Aug 24, 2023 at 03:20:50PM -0700, Mark Millard wrote:
> bob prohaska wrote on
> Date: Thu, 24 Aug 2023 19:44:17 UTC :
>
> > On Fri, Aug 18, 2023 at 08:05:41AM +0200, Matthias Apitz wrote:
> > >
> > > sysctl vfs.read_max=128
> > > sy
It looks as if daily email reporting login failures and system status
are no longer being sent out on -current. Is there a switch for
/etc/rc.conf that will turn them back on?
Thanks for reading,
bob prohaska
e and
mergemaster is simply overwhelming. And, I suspect, largely
unnecessary.
Thanks for reading!
bob prohaska
is-set clocks in buildworld. Is this
new behavior?
Thanks to both Mark and Ronald!
bob prohaska
On Sat, Feb 25, 2023 at 10:33:23AM -0600, Mike Karels wrote:
> On 25 Feb 2023, at 10:16, bob prohaska wrote:
>
> > On Sat, Feb 25, 2023 at 12:21:09AM +0100, Ronald Klop wrote:
> >>
> >> UFS stores the current timestamp in the superblock of the FS on clean
> >
no trouble sending to -stable.
On a fresh reboot I don't see any reference to dma in the
dmesg output, and ps -aux reports only busdma.
Thanks for reading,
bob prohaska
, as that is what
> "connection refused" implies.)
>
Indeed, that's the case. It looks as if dma isn't intended
to replace sendmail, so I'll take the hint in UPDATING and
turn sendmail back on.
Thank you!
bob prohaska
o hardware clock,
how does it set time when booted without a reference?
Thanks for reading,
bob prohaska
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:
> >
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
s
odd if that can null a root password.
Still, it does seem an outside possibility. I could see it adding
system users, but messing with root's existing password seems a
bit unexpected.
Thanks very much for raising the point!
bob prohaska
ular and root account.
AFAIK, /etc/master.passwd is _the_ password repository,
but clearly I'm wrong.
If somebody can tell me what's going on and what to
check for before placing the machine back on line
it would be much appreciated.
Thanks for reading,
bob prohaska
ith the first case,
passwords seem to work normally (null rejected, normal accepted).
Any advice appreciated!
bob prohaska
> 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
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 configuratio
ng injected via part of the
network
login process. Reboot pauses have been an ongoing phenomenon for months, this
is the
first time I've noticed the "invalid characters" message from ssh on the
console.
Thanks for reading, apologies if I'm being a worrywart.
bob prohaska
<<<<< The shell prompt on the 2nd Pi3's serial
console.
Clearly nothing to do with sshd, might it simply be a misdirected echo of
console
output generated by a (dead or broken) tip connection? The first example looked
possibly malicious, this does not
Thanks for reading,
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,
sible versions,
delimited by <<<<<<<<<<<<<, ||| and >>>>>>>>>
characters. Once edited, that will become the new local
version of the file. If this is mistaken please say so.
bob prohaska
..
..
ping
..
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.
If there's a relevant man section please point it out.
Thanks for reading,
bob prohaska
eebsd-current to the cc list 8-(
Thanks for writing!
bob prohaska
nicky about booting, sometimes requiring
intervention at the serial console to prod u-boot to find the
usb disk. This particular Pi is booting without a microSD, it's
possible the usb-sata adapter contributes to the problem. It
might be worth trying the "bootcode.bin-only" method to see
if that hel
1 - 100 of 110 matches
Mail list logo
