Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #244589
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Bullseye - who and users return nothing |
| Date | 2022-01-25 14:20 +0100 |
| Message-ID | <DJtTQ-2FU-7@gated-at.bofh.it> (permalink) |
| References | <DJ4iK-3DD-5@gated-at.bofh.it> <DJ6Xh-5h8-31@gated-at.bofh.it> <DJiYq-48P-11@gated-at.bofh.it> <DJtK9-2BU-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Jan 25, 2022 at 01:06:42PM +0000, Gareth Evans wrote: > Just realised I gave contradicting info earlier - I said both that I upgraded from Buster (which is literally true) and that > > "But for root on ZFS per > > https://openzfs.github.io/openzfs-docs/Getting%20Started/Debian/Debian%20Buster%20Root%20on%20ZFS.html (adjusted for Bullseye) <<<<<< > > ..." > > which isn't, because Bullseye arrived via dist-upgrade, rather than a fresh installation. > > My mistake may have prompted Andrei's suggestion which I then explained away partly in relation to having upgraded - sorry. I don't know anything about ZFS. That said, it's *conceivable* that your / ownership has been broken this entire time, and you never noticed until now. Either because you never ran "who", or because systemd in buster didn't check the parent directory ownerships, but the one in bullseye does. Food for thought. (It's not clear to me how setting up ZFS on / would involve your unprivileged username, though. Sounds more like a "boot from rescue media and do everything in a root shell" sort of job. So I'm more inclined to think the damage was done by some sort of backup/recovery gone wrong, as previously speculated.)
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bullseye - who and users return nothing "Gareth Evans" <donotspam@fastmail.fm> - 2022-01-24 11:00 +0100
Re: Bullseye - who and users return nothing Greg Wooledge <greg@wooledge.org> - 2022-01-24 13:50 +0100
Re: Bullseye - who and users return nothing "Gareth Evans" <donotspam@fastmail.fm> - 2022-01-25 02:40 +0100
Re: Bullseye - who and users return nothing "Gareth Evans" <donotspam@fastmail.fm> - 2022-01-25 02:40 +0100
Re: Bullseye - who and users return nothing Greg Wooledge <greg@wooledge.org> - 2022-01-25 04:00 +0100
Re: Bullseye - who and users return nothing "Gareth Evans" <donotspam@fastmail.fm> - 2022-01-25 04:10 +0100
Re: Bullseye - who and users return nothing "Gareth Evans" <donotspam@fastmail.fm> - 2022-01-25 04:10 +0100
Re: Bullseye - who and users return nothing Greg Wooledge <greg@wooledge.org> - 2022-01-25 04:30 +0100
Re: Bullseye - who and users return nothing "Gareth Evans" <donotspam@fastmail.fm> - 2022-01-25 05:10 +0100
Re: Bullseye - who and users return nothing Polyna-Maude Racicot-Summerside <debian@polynamaude.com> - 2022-01-25 05:20 +0100
Re: Bullseye - who and users return nothing "Gareth Evans" <donotspam@fastmail.fm> - 2022-01-25 05:30 +0100
Re: Bullseye - who and users return nothing David Wright <deblis@lionunicorn.co.uk> - 2022-01-25 06:00 +0100
Re: Bullseye - who and users return nothing "Gareth Evans" <donotspam@fastmail.fm> - 2022-01-25 06:40 +0100
Re: Bullseye - who and users return nothing Andrei POPESCU <andreimpopescu@gmail.com> - 2022-01-25 11:50 +0100
Re: Bullseye - who and users return nothing "Gareth Evans" <donotspam@fastmail.fm> - 2022-01-25 13:20 +0100
Re: Bullseye - who and users return nothing "Gareth Evans" <donotspam@fastmail.fm> - 2022-01-25 14:10 +0100
Re: Bullseye - who and users return nothing local10 <local10@tutanota.com> - 2022-01-25 14:20 +0100
Re: Bullseye - who and users return nothing Greg Wooledge <greg@wooledge.org> - 2022-01-25 14:20 +0100
Re: Bullseye - who and users return nothing "Gareth Evans" <donotspam@fastmail.fm> - 2022-01-25 16:00 +0100
csiph-web