Linked by Thom Holwerda on Wed 25th Jul 2012 22:18 UTC
OSNews, Generic OSes The article I'm about to link to, by Oliver Reichenstein, is pretty terrible, but it's a good way for me to bring up something I've been meaning to talk about. First, the article: "Apple has been working on its file system and with iOS it had almost killed the concept of folders - before reintroducing them with a peculiar restriction: only one level! With Mountain Lion it brings its one folder level logic to OSX. What could be the reason for such a restrictive measure?" So, where does this crusade against directory structures (not file systems, as the article aggravatingly keeps stating) come from?
Thread beginning with comment 528522
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: Oliver has lost it.
by UltraZelda64 on Fri 27th Jul 2012 16:18 UTC in reply to "RE[5]: Oliver has lost it."
Member since:

Honestly, I don't know the last time I had to set up system files. Configuring SSH or MPD maybe? I doubt that a typical person coming from Windows would even know what a daemon is as I mentioned, and I wish them luck on somehow managing to download some kind of malware to destroy things like /boot as I mentioned to truly wreck a system, Windows-style. UNIX doesn't make it easy.

For those people who *are* likely to play around by experimenting heavily and screw up OS installations, well, chances are they're intermediate to advanced users, and at least have an understanding on the Linux filesystem to get things back up again if needed. For those users who do hear of some interesting daemons that they'd like to learn to use, well, a couple commands for start/restart/stop and editing a file or two under /etc is really not that difficult, and by the time they learn of it they'll probably already feel at home in the OS.

I don't recall ever having to modify a program's configuration that placed its config files in /bin or /usr/bin. If the configuration is not within a configuration window of the program itself, it's somewhere under /home/user. If it's a daemon, it's somewhere under /etc, or for some web-based daemons it can be accessed as a GUI by logging into a web page on the machine running it. Simple as that.

Reply Parent Score: 2