News for hackers. Stuff that matters.
Re:I wish systemd logged information about the source of “tr... by lathiat on Wednesday November 24, 2021 @05:44AM (#29328714)
I can do one better for exit. The Solaris kernel debugger KDB can be used at runtime for inspecting some stats and also to change some global configurable variables.

For whatever reason if you type a variable/symbol it assigns it the value 0. If you type exit nothing happens immediately but as soon as the next process exits usually a few seconds to 10s of seconds later the entire system kernel panics on a null pointer de-reference.

Kernel paniced our production ZFS filer twice before I cottoned on. Newer releases special cased “exit” not to do that.

Re:I wish systemd logged information about the source of “tr... by heavenlyblue on Wednesday November 24, 2021 @05:49AM (#29328742)
That sounds like the most amazing UX I have ever encountered :)

For those familiar with Solaris, is there any reason they did it this way?

How can you possibly set the default behaviour of assigning any symbol a value of 0 by default?

Re:I wish systemd logged information about the source of “tr... by zaarn on Wednesday November 24, 2021 @12:58PM (#29332932)
Solaris is built on some idiosyncrasies (Speaking as someone who, as a Linux person, has to sysadmin Solaris systems).

For example, on our Solaris machines, after install, "reboot" does not do a clean reboot, it's a hard reset. If you want a clean reboot you need "init 6". Same story for "shutdown" and "init 5".

"killall" also kills all processes. Not the one you specified. Or more specifically it SIGKILLs all processes that have open files (ssh session and server go byebye). If you type "reboot" or "shutdown", this is in fact the binary that gets called do that.

Sadly, Solaris is also one of the few systems that support the NFSv4 ACLs (Linux supports NFSv4 but not the ACL Extension, TrueNAS has a patch for that).

Re:I wish systemd logged information about the source of “tr... by ibotty on Friday November 26, 2021 @02:21AM (#29348119)
Doesn't Ganesha support NFSv4 ACLs?
Re:I wish systemd logged information about the source of “tr... by zaarn on Friday November 26, 2021 @03:29AM (#29348389)
On Linux only for non-Filesystem backends (Ceph, Gluster, etc.)

The only fork of Ganesha that supports it on a proper filesystem is the TrueNAS fork and that only on their ZFS Fork that brings NFSv4 ACLs to Linux.

So really, no. You can't use NFSv4 ACLs with Ganesha on Linux outside of Forks or using scale-out data stores.

Re:I wish systemd logged information about the source of “tr... by gpderetta on Wednesday November 24, 2021 @06:59AM (#29329119)
That's of course due to the principle of maximal astonishment, a time honoured software design law.
Re:I wish systemd logged information about the source of “tr... by saagarjha on Wednesday November 24, 2021 @08:39AM (#29329845)
Hey, it’s better than what C does for its variables ;)
Re:I wish systemd logged information about the source of “tr... by ChuckMcM on Wednesday November 24, 2021 @11:47AM (#29331964)
because adb(1) did it that way.
Re:I wish systemd logged information about the source of “tr... by cyberpunk on Wednesday November 24, 2021 @12:26PM (#29332523)
Remember how on sparc machines if you turned off your laptop with the console cable connected it powers the servers down too?

That was a fun lesson…