tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: makesyscalls (moving forward)



On 2020-06-15 12:25, Kamil Rytarowski wrote:
On 15.06.2020 00:57, Johnny Billquist wrote:
On 2020-06-15 00:52, Kamil Rytarowski wrote:
On 15.06.2020 00:26, Johnny Billquist wrote:
But that's just me. I'll leave the deciding to you guys...


This is only me, but /sbin and /usr/sbin are for users with root
privileges, while /bin and /usr/bin for everybody. makesyscalls(1)
intends to be an end-user program that aids building software and this
is just another specialized program similar to flex(1) or yacc(1), just
a more domain specific code generator.

Is ping only for people with root privileges???


ping needs setuid so yes.

What kind of silly argument is that?
I don't at all understand how people first of all can think that stuff under /sbin is for root only. Second, setuid exists for exactly the reason that non-root people should be able to run some things that requires root provileges.

It seems we are starting to do the distinction on where programs should go based on whether you need to be root to run them or not, which for me is a totally crazy idea.

Should passwd then move to /sbin?

Just look around, there are plenty of programs under /bin and /usr/bin which are setuid root. They should *not* move into /sbin because of that.

/sbin and /usr/sbin holds tools that are generally not used by others that system administrators. Tools that are often needed to bring up a system at boot time. Tools that commonly are not in normal users path.

We should not clutter the directories that are in the normal users path with things that a normal user would never care about.

If we basically place any kind of tool in /bin or /sbin just because it don't require people to be root, then you will have all kind of stuff there are is totally meaningless for most users, while a lot of meaningful things will be in /sbin and /usr/sbin, at which point everyone will need to have all directories in their paths, at which point there is no point in even having a separate /bin and /sbin.

There has to be a reason to split binaries into different directories. A reason that have some practical meaning. Or else it's not actually useful, and instead becomes just some obscure inner circle "thing" of obscurity.

  Johnny

--
Johnny Billquist                  || "I'm on a bus
                                  ||  on a psychedelic trip
email: bqt%softjar.se@localhost             ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol


Home | Main Index | Thread Index | Old Index