Re:Systemd, ten years later: a historical and technical retr...
by tomatocracy on Monday May 04, 2020 @06:01AM
(#23066232)
I noticed the ConsoleKit->logind change at the time being largely justified by support for multiseat but had forgotten about it. It seems like a rather extreme case of the tail wagging the dog but perhaps I'm missing something. How many people use multi-seat in large deployments? Where and why?
[ Parent
| on HN ]
Re:Systemd, ten years later: a historical and technical retr...
by michaelmrose on Monday May 04, 2020 @12:23PM
(#23069955)
Virtually nobody is using multi-seat and none should.
For most cases you would get better results by networking n cheap boxes rather than trying to buy a single beefy box to support n users on every dimension including perhaps even power usage if you used low power devices.
Contention for io is a problem. Everyone wanting to say decode video simultaneously is a problem. Browsers high ram usage is a problem.
Re:Systemd, ten years later: a historical and technical retr...
by Koshkin on Monday May 04, 2020 @12:54PM
(#23070393)
> rather than trying to buy a single beefy box to support n users
This sentiment has always felt weird to me, as I have always seen UNIX as an OS that has been designed - from the ground up (in late 1960s) to support multiple concurrent users - whether it is via a serial terminal, and now multi-seat, VNC or an X terminal. By today's standards it's not even such a "beefy box" that can easily do that.
Re:Systemd, ten years later: a historical and technical retr...
by michaelmrose on Tuesday May 05, 2020 @12:07AM
(#23076378)
Blame browsers as soon as 3 users wanted to use facebook youtube on your 1200 box each user will probably have a worse experience than 3 users running 400 boxes plus hardware failure would reduce capacity to 0% instead of 1 box failing at a time.
Re:Systemd, ten years later: a historical and technical retr...
by AsyncAwait on Monday May 04, 2020 @08:56AM
(#23067414)
Except you seem to have forgotten the other big reason was that basically nobody was actually maintaining ConsoleKit at the time at it was a horrible, insecure mess when logind replaced it.