TRUTH TIME! How many of you have actually read a user manual of an operating system completely?
[Mention your Sex if you are comfortable, I want to see the breakdown between the sexes here]
I just tried to skim through Linux User Manual and it was really quite informative and made me think of reading it someday, but I kinda know for a fact that that someday might never come, but it's truly a shame though.
Now, you, yes you! Have you read the user manual of your Operating system!
[I am wasting a lot of time on here, so I won't be engaging or enraging y'all, but this is a good convo topic, isn't it? (try that on a girl), I just wanted to know how many or how few people read UMs]___
I got a manual (or just a general book about DOS?) with my first MSDOS PC, which I read. Otherwise no. I have read books about Linux or specific parts of Windows/Linux, but no “official” manual.
Looks like they're coming over from reddit. Obligatory "women, not girls you incel. Go outside and touch grass".
Reading an OS manual cover to cover is a collosal waste of time. There are more efficient ways to level up skills. But what do I know with my gIrLy LoGiC.
I read most of the DOS 6.0 manual around 1994. This was the era of memory management. Computers had 640k of conventional memory despite my PC having 4M of total ram. Every TSR you could extract out to high or extended memory would have a massive impact on the performance of high demand applications (like all my important applications from Lucas Arts...). I managed to get mouse, soundcard, video, and other drivers loaded and still have 580+K of free conventional memory.
Now I design web scale server architectures capable of handling hundreds of requests per second with five 9's of uptime (for a few years anyway), and that memory management, from back when I was a tween, is still one of my proudest technological achievements. Thanks DOS manual!
I've read the Gentoo handbook and Sakaki's old guide, if that counts.
Reading the entire user manual doesn't seem relevant. IMO it is a reference work; like reading all of Wikipedia or a dictionary. A manual is not a tutorial, and neither are a wiki reference article database. Most users likely expect a more intuitive design where the proper reference materials either make themselves available when needed or are never needed at all.
It's not too difficult, in fact many websites reuse the same terms and conditions, which means you can skim it over. I read it for the citations among other reasons, which I do by doing the CTRL + F trick.
I forgot what website it was, but there was a website that put in a large cash prize designed to be claimable by whoever read the terms of service. It took six months before there was ever a winner.
Not completely, but back in like 2011 there was an official iOS user guide available as a PDF, and having just gotten an iPad I did go through a decent chunk of it learning about what I could (and couldn't) do with it.
I mean, my time came around long after the age of hundred-page software manuals. But I've spent a good portion of my life knee-deep in man pages and Google searches, which kinda counts?
[Male] Twice+. I have read both the manual of the TI99/4A and the manual of the C64 several times over, and on top of that, also the Data Becker books on the C64 and the C1541 that include the OS' (well-)commented sources. I actually had to purchase both Data Becker books twice, as the first books started to fall apart.
I have also read nearly all the manuals of the Amiga 1000, including the application manuals and the programming documentation.
Yeah, but not for anything Unix-like or Windows. More like small operating systems for some piece of specific hardware. One that comes to mind is some custom OS for a small robot that maps rooms.
Probably the longest technical document I know very well is the datasheet for AVR microcontrollers (the full one, not the summary). Those are 170-300 pages long, depending on the exact chip. They detail how every feature of the chip operates and is accessed. It's pretty normal in my occupation to know one or two chips really well.
Male. My first computer was an iMac 333. It came with a book, that I read from start to finish, then proceeded to use it for nothing but Soundjam (iTunes) and Hoyle Cards
I read the entire set of Amiga manuals, and the one for the Spectrum +3 (we're stretching the definition of Operating System here, but +3DOS is still an operating system)
I remember reading some old technical manuals for windows 95 way back in the day. Taught me heaps about PnP, bus arbiters and so on.
To be fair, I probably didn't use that knowledge all that much as PnP and ACPI actually worked really well (I was fortunate enough to only have to deal with DOS as far as himem and whatnot...)
The old GUI style guidelines were fantastic back in the day too - completely unlike the anything-goes approach to modern software development (very different pros and cons, basically), especially in windows-land.
We have a lot of machines that run on HP unix at work. I read a lot of those manuals as I didn't want to break anything. It's very annoying to use coming from modern Linux.
I read some of the 9front documentation and a lot of the Debian administrator's handbook. I'm weird and just like operating systems though.