On Tue, 9 Jun 2026 19:44:19 -0000 (UTC), John McCue wrote:
There is one use for ed(1), when I boot NetBSD into single user
mode, ed(1) is the only one available without jumping through hoops.
Why is that? Is it because NetBSD still has the legacy root-versus-usr separation of executables and libraries?
Lawrence D?Oliveiro <ldo@nz.invalid> wrote:
On Tue, 9 Jun 2026 19:44:19 -0000 (UTC), John McCue wrote:
There is one use for ed(1), when I boot NetBSD into single user
mode, ed(1) is the only one available without jumping through hoops.
Why is that? Is it because NetBSD still has the legacy root-versus-usr
separation of executables and libraries?
From what I have seen, seems Linux does not have a real single
user mode. But I think that is OK for Linux.
NetBSD and the other BSDs have real single user mode where no
file systems are mounted, no daemons are started and root is
mounted RO. NetBSD boots into /bin/sh or a shell of your
choice and you work from that, no login needed. Also I think
only static executables are available for use.
I do not know what "legacy root-versus-usr" means, I would
never want a system that does not have a clear separation
between root and users.
Lawrence D?Oliveiro <ldo@nz.invalid> wrote:
On Tue, 9 Jun 2026 19:44:19 -0000 (UTC), John McCue wrote:
There is one use for ed(1), when I boot NetBSD into single user
mode, ed(1) is the only one available without jumping through hoops.
Why is that? Is it because NetBSD still has the legacy root-versus-usr
separation of executables and libraries?
From what I have seen, seems Linux does not have a real single
user mode. But I think that is OK for Linux.
NetBSD and the other BSDs have real single user mode where no
file systems are mounted, no daemons are started and root is
mounted RO. NetBSD boots into /bin/sh or a shell of your
choice and you work from that, no login needed. Also I think
only static executables are available for use.
I do not know what "legacy root-versus-usr" means, I would
never want a system that does not have a clear separation
between root and users.
John McCue <jmclnx@gmail.com.invalid> writes:[...]
I do not know what "legacy root-versus-usr" means, I would
never want a system that does not have a clear separation
between root and users.
That's not what it means.
John McCue <jmclnx@gmail.com.invalid> writes:
Lawrence D?Oliveiro <ldo@nz.invalid> wrote:
On Tue, 9 Jun 2026 19:44:19 -0000 (UTC), John McCue wrote:
There is one use for ed(1), when I boot NetBSD into single user
mode, ed(1) is the only one available without jumping through hoops.
Why is that? Is it because NetBSD still has the legacy root-versus-usr
separation of executables and libraries?
From what I have seen, seems Linux does not have a real single
user mode. But I think that is OK for Linux.
NetBSD and the other BSDs have real single user mode where no
file systems are mounted, no daemons are started and root is
mounted RO. NetBSD boots into /bin/sh or a shell of your
choice and you work from that, no login needed. Also I think
only static executables are available for use.
I do not know what "legacy root-versus-usr" means, I would
never want a system that does not have a clear separation
between root and users.
That's not what it means.
Historically, /bin and /usr/bin were two different directories,
with /bin containing only executables that are needed during
system startup. /usr/bin can be on a separate filesystem that isn't >initially mounted. I think /usr was also where home directories were >located; for example, Dennis Ritchie's home directory was /usr/dmr.
I think the origin of that is an early PDP-11 or PDP-7 system at
Bell Labs that had limited space on its main hard drive a larger
secondary drive.
NetBSD 10.1, the latest release, retains that distinction. I have
it running in a VM, and it has 39 files in /bin and 515 in /usr/bin.
All the executables are dynamically linked, but I think they
depend on on libraries in /lib, not /usr/lib. /bin and /usr/bin
are on the same filesystem (though I think it can be configured
with /usr in its own filesystem).
Many other Unix-like systems have transitioned to making /bin a
symbolic link to /usr/bin. But remnants of the old layout still
exist; for example /usr/bin and /bin are typically both in $PATH
even if they're the same directory.
Similar things apply to /lib and /usr/bin, and to /sbin and
/usr/sbin.
Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
Historically, /bin and /usr/bin were two different directories,Yup. I usually just make one big filesystem on most machines.
with /bin containing only executables that are needed during
system startup. /usr/bin can be on a separate filesystem that isn't
initially mounted. I think /usr was also where home directories were
located; for example, Dennis Ritchie's home directory was /usr/dmr.
There isn't much reason to split them up anymore.
Lawrence D?Oliveiro <ldo@nz.invalid> wrote:
On Tue, 9 Jun 2026 19:44:19 -0000 (UTC), John McCue wrote:
There is one use for ed(1), when I boot NetBSD into single user
mode, ed(1) is the only one available without jumping through hoops.
Why is that? Is it because NetBSD still has the legacy root-versus-usr
separation of executables and libraries?
From what I have seen, seems Linux does not have a real single
user mode. But I think that is OK for Linux.
NetBSD and the other BSDs have real single user mode where no
file systems are mounted, no daemons are started and root is
mounted RO. NetBSD boots into /bin/sh or a shell of your
choice and you work from that, no login needed. Also I think
only static executables are available for use.
I do not know what "legacy root-versus-usr" means, I would
never want a system that does not have a clear separation
between root and users.
On Wed, 10 Jun 2026 00:38:51 -0000 (UTC), Lawrence DrCOOliveiro wrote:
On Tue, 9 Jun 2026 19:44:19 -0000 (UTC), John McCue wrote:
There is one use for ed(1), when I boot NetBSD into single user
mode, ed(1) is the only one available without jumping through
hoops.
Why is that? Is it because NetBSD still has the legacy
root-versus-usr separation of executables and libraries?
From what I have seen, seems Linux does not have a real single user
mode.
NetBSD and the other BSDs have real single user mode where no file
systems are mounted, no daemons are started and root is mounted RO.
NetBSD boots into /bin/sh or a shell of your choice and you work
from that, no login needed. Also I think only static executables are available for use.
I do not know what "legacy root-versus-usr" means, I would never
want a system that does not have a clear separation between root and
users.
Another factor for those old space limited systems was you probably
wanted everything in /bin to be statically linked ...
In comp.unix.shell, Dan Cross <cross@spitfire.i.gajendra.net> wrote:
Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
Historically, /bin and /usr/bin were two different directories,Yup. I usually just make one big filesystem on most machines.
with /bin containing only executables that are needed during
system startup. /usr/bin can be on a separate filesystem that isn't
initially mounted. I think /usr was also where home directories were
located; for example, Dennis Ritchie's home directory was /usr/dmr.
There isn't much reason to split them up anymore.
I've worked with systems where /usr was a NFS filesystem.
You had to get
the system booted and on the network before you got /usr/bin. Another
factor for those old space limited systems was you probably wanted
everything in /bin to be statically linked while the /usb/bin stuff
could afford to rely on dynamic libraries, again possibly existing on >filesystems not mounted at boot or even not available until networking
is up.
These days you probably turn to busybox or the like when you need all >statically linked utilities.
In article <eli$2606102012@qaz.wtf>,[...]
When Solaris 2 came along, essentially everything was
dynamically linked; statically linked binaries went into /sbin,
and my sense at the time was that 's' stood for 'static' (or
possibly 'standalone'). Nowadays, that is mostly system
utilities, whether statically linked or not, and so the meaning
has shifted again.
Oh, do you mean initlevel "S" or "s"? As in:
si:S:sysinit:/etc/rc.d/rc.S
su:1S:wait:/etc/rc.d/rc.K
20:21:14 $ head /etc/rc.d/rc.S<snip>
#!/bin/sh
#
# /etc/rc.d/rc.S: System initialization script.
#
# Mostly written by: Patrick J. Volkerding, <volkerdi@slackware.com>
Like Slackware??
I do not know what "legacy root-versus-usr" means, I would
never want a system that does not have a clear separation
between root and users.
Agreed.
Although the OP might have meant the current (IMHO aberrant) trend
of dispensing with the /bin vs /usr/bin (etc) dichotomy.
John McCue <jmclnx@gmail.com.invalid> writes:<snip>
I do not know what "legacy root-versus-usr" means, I would
never want a system that does not have a clear separation
between root and users.
That's not what it means.
Historically, /bin and /usr/bin were two different directories,
NetBSD 10.1, the latest release, retains that distinction. I have
it running in a VM, and it has 39 files in /bin and 515 in /usr/bin.
All the executables are dynamically linked, but I think they
depend on on libraries in /lib, not /usr/lib. /bin and /usr/bin
are on the same filesystem (though I think it can be configured
with /usr in its own filesystem).
Many other Unix-like systems have transitioned to making /bin a
symbolic link to /usr/bin. But remnants of the old layout still
exist; for example /usr/bin and /bin are typically both in $PATH
even if they're the same directory.
Similar things apply to /lib and /usr/bin, and to /sbin and
/usr/sbin.
I believe that the name "sbin" long predates Solaris 2.
When I boot Slackware single user, an extremely rare occurrence, I
can see whit I think are many kernel items executing in background
plus files systems are mounted. On NetBSD, nothing is running in
background and only / is mounted RO. But for Linux that is not a
major deal, just different. That is why said "BSD has a real single
user mode".
M-q is the 'fill-paragraph' function.
On Fri, 03 Jul 2026 00:55:34 +0100, Daniel Cerqueira wrote:
M-q is the 'fill-paragraph' function.
And a very versatile one it is, too. It copes with indented text,
preserves quoting or comment prefixes, and also helpfully removes
redundant spaces. ;)
A little warning about M-q. In GNU Emacs 30+, the scratch buffer's
M-q is redefined to something else.
FWIW, I tend to use 'fill-paragraph' a lot in scratch.
On Fri, 3 Jul 2026 01:32:46 -0000 (UTC), John McCue wrote:
A little warning about M-q. In GNU Emacs 30+, the scratch buffer's
M-q is redefined to something else.
I didnrCOt notice this (running Emacs 30.2, since thatrCOs what was in
Debian Unstable on my last upgrade), because I run with EmacsrCO entire
mode system disabled.
FWIW, I tend to use 'fill-paragraph' a lot in scratch.
So do I.
Oh, and I also added a buffer-protection mechanism, because I have a
shortcut (super-W) for closing the current buffer, and I was losing
the scratch buffer too often from this. ;)
[...]
The point being that I use the initial buffer more for quick
note-keeping that ought to be transitory until saved in a more
appropriate fashion, but I kept getting bitten by bugs of the following species - not saying it happened often enough, but still it happening
once an year or so would pose an issue:
* Drosophila Segmentationum Faltum
* Aedes Blackoutitis
Now more seriously, [...]
[...] I usually just make one big filesystem on most machines.
There isn't much reason to split them up anymore. [...]
On Wed, 10 Jun 2026 22:01:23 -0000 (UTC), John McCue wrote:
From what I have seen, seems Linux does not have a real single user
mode.
There is no rCLreal single user moderCY in any *nix. The concept of single/multi-user mode is irrelevant to the kernel.
[...]
In article <eli$2606102012@qaz.wtf>,[...]
When Solaris 2 came along, essentially everything was
dynamically linked; statically linked binaries went into /sbin,
and my sense at the time was that 's' stood for 'static' (or
possibly 'standalone'). Nowadays, that is mostly system
utilities, whether statically linked or not, and so the meaning
has shifted again.
My recollection is that the 's' in sbin (/sbin and/or /usr/sbin), has
always stood for "system". Typically an ordinary non-administrative
user would not have /sbin or /usr/sbin in their $PATH, but both
would be in the default $PATH for the root account.
Wikipedia (which is not a primary source) says it's "system" or
"superuser". >https://en.wikipedia.org/wiki/Unix_filesystem#Conventional_directory_layout
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:01:42 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,448 |