Did something supercede Socialism in Russia around the years 1988 to 1991?
Did something supercede Socialism in Russia around the years 1988 to 1991?
This might be relevant:
https://youtu.be/J_fZ9o6P0-A?si=-fl7rLryYZBDVgTN&t=194
Conditions here were deplorable by any objective measure. And if you’ll recall, one of the hallmarks of early Russian industrialization was: the workforce was often transient. People moved back and forth between their home villages and jobs in the cities, and this flux meant that the places people lived and where they ate and bathed and got medical attention were only ever temporary expedients. It was a bit like you were going off to some particularly crappy summer camp. It was only meant to be temporarily endured, not lived in full time, and so conditions just never got better. People were not just renting rooms; they were renting corners of rooms. You could rent not just a bed, but part of a bed. Sanitation was, of course, practically non-existent, and the food was disgusting. The work itself, meanwhile, was long and grueling. There were no safety standards in the factories. There were hardly any rights for anybody at all. And pay was literally inadequate. The ministry of finance itself surveyed conditions and concluded that a family of four needed about fifty rubles a month to purchase basic necessities (that is, food and shelter and heat) and then they found that 75% of the workers were making less than 30 rubles a month. The economic and moral math was just not adding up.
https://youtu.be/J_fZ9o6P0-A?si=FtaiY47HVyXXBeAP&t=340
The lower skilled, less educated, and still mentally “peasant” workers tended to remain culturally conservative. They were orthodox christian and believed strongly in the divine benevolence of the czar. And indeed one of the things reported by both social democrats and SRs back to their respective central committees was that they struggled to recruit among these workers because they were out there pitching “overthrowing the czar” and everyone was like “What? We… we love the czar, and he loves us too!”
To them, the czar was not a villain, but a hero. Not the devil, but their savior. It understandably made recruiting for a political revolution to overthrow their “hero and savior” very difficult.
https://thehistoryofrome.typepad.com/revolutions_podcast/2020/02/1033-bloody-sunday.html
Note that many versions of macOS adhere to these standards: https://www.opengroup.org/openbrand/register/ https://www.opengroup.org/openbrand/register/brand3700.htm https://www.opengroup.org/openbrand/register/brand3705.htm
If people were more resistant to “grandfathered” features I think we would not have as much software as we do today: https://www.jwz.org/doc/worse-is-better.html https://en.wikipedia.org/wiki/Worse_is_better
provide about 50%–80% of what you want from an operating system
one expects that if the 50% functionality Unix and C support is satisfactory, they will start to appear everywhere.
Unix and C are the ultimate computer viruses.
users have already been conditioned to accept worse than the right thing.
It’s probably possible to make several programs with “50% functionality” in the time it takes to make one program with 100% functionality. Having more programs that are suitable for a majority of relevant applications is probably better than having one program that is suitable for all relevant applications, since having more programs will probably enable a larger variety of problems to be solved, and people often have to solve many different types of problems in their life.
https://refspecs.linuxfoundation.org/fhs.shtml https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04.html
Some operating systems may handle long path or file names in a surprising way, so having short paths and names is useful: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_13
If any pathname component is longer than {NAME_MAX}, the implementation shall consider this an error.
if the combined length exceeds {PATH_MAX}, and the implementation considers this to be an error, pathname resolution shall fail
{NAME_MAX}
and {PATH_MAX}
are described in more detail at https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/limits.h.html#tag_13_23_03_02 and used in the context of https://pubs.opengroup.org/onlinepubs/9699919799/utilities/pathchk.html
The resources I linked are descriptive and not prescriptive, but in my experience they are suitable to depend upon as a reliable baseline, which makes meeting client requirements with software engineering easier.
You surely need to explicitly cause systemd
to process changes after writing to a file. I would be very surprised if it reacted to file system changes automatically.
For example, I recall that I need to execute a command like systemctl daemon-reload
after editing a service
file: https://unix.stackexchange.com/questions/364782/what-does-systemctl-daemon-reload-do
You might get more useful information from resources like https://www.man7.org/linux/man-pages/man1/systemctl.1.html
Typo:
s/FOUR\/FOR\/s/s\/FOUR\/FOR\//
To “substitute”, the editing command is
s/RE/replacement/
which has as
character before any<slash>
(/
) character: https://pubs.opengroup.org/onlinepubs/9799919799/utilities/sed.html#tag_20_109_13_03