So you think it is faster to write a block if we first have to check all the other blocks on the disk to see if one of them is the same as the block I want to write? And when I change one byte in a file we would have to do it again?
If you use 4096=2^12 Byte=2^15 Bit Blocks this would mean to search at most 2^15 other Blocks to see if they are the same.
The difference between aliases and symlinks is simple. A symlink is just another name for a file. An alias is basically a short form for a command line which means it can contain builtin commands, multiple commands, parameters,... which does not work for symlinks because those are not even commands at all, you can just as easily symlink a config file as you can an executable.
That isn't really a Unix Problem but the problem that the lowest common denominator for inter-language calls is still C. You have to replace that before you can seriously talk about removing C from the equation.
So how do you copy them easily (and selectively) to other systems. In Linux I did all my configuration for the programs I use on several computers exactly once and I do not plan to do it again should I have to reinstall, use another distro, buy another/additional PC,...
I just copy them (and back them up) in the easiest way imaginable.
1. You know there are actually reasons why people don't want to reboot their production servers (or their workstations with 5 open apps).
2. I haven't quite figured out what your system and the/etc directory have to do with each other
3. Rebooting everytime you want to execute something from a removable media is definitely too much
The real problem here is they "solve" the dependency problem by duplicating shared libs for every app which means:
1. Your libs will be n times in memory if you use n apps that use them instead of just 1 time
2. You can not be sure you updated all the vulnerable versions of a given library because instead of one in a known place they are all over the place
Even better designed software uses autoconf/automake or something similar so the package manager can configure where to install which part (config files, bins, libs,docs,...) of the software.
Games in Linux are perfectly possible. Linux just can not run (all) Windows Games as Windows can not run any Games from other OSs. You have to start using Linux to get a bigger Userbase to convince Game Companies to produce Linux ports of their Games.
So which do you prefer? Unix Man Pages that contain all there is to know about a certain app in a not quite end user refined form or Windows Assistants ("Did you plug in the Cable?" - "Yes" - "Then I can't help you - call your vendor") and cryptic error codes?
I think Unix is a lot better in this aspect then all other OSs I know. Global Configuration is stored in/etc (or in case of multiple config file apps in a subdir of/etc) and user configuration is stored in the user directory in a hidden directory called like the app.
Slashdot Mirror
install/uninstall is if anything more difficult in Windows than in modern Linux distros today.
I remember this text (the one in your comment0 being (part of) an Aprils Joke a few years ago but I can't quite remember by whom.
So you think it is faster to write a block if we first have to check all the other blocks on the disk to see if one of them is the same as the block I want to write? And when I change one byte in a file we would have to do it again?
If you use 4096=2^12 Byte=2^15 Bit Blocks this would mean to search at most 2^15 other Blocks to see if they are the same.
The difference between aliases and symlinks is simple. A symlink is just another name for a file. An alias is basically a short form for a command line which means it can contain builtin commands, multiple commands, parameters,... which does not work for symlinks because those are not even commands at all, you can just as easily symlink a config file as you can an executable.
You should try Docbook or Tex (seriously try, not just a few minutes or hours) before you assert a GUI is a better tool for word processing.
So we need a better system for signal handlers (or signals) not the removal of a very useful system call.
That isn't really a Unix Problem but the problem that the lowest common denominator for inter-language calls is still C. You have to replace that before you can seriously talk about removing C from the equation.
There are even lots of distros out there that consider rpm obsolete.
So how do you copy them easily (and selectively) to other systems. In Linux I did all my configuration for the programs I use on several computers exactly once and I do not plan to do it again should I have to reinstall, use another distro, buy another/additional PC,...
I just copy them (and back them up) in the easiest way imaginable.
How does OS X replace vulnerable versions of libraries in all those app dirs?
1. You know there are actually reasons why people don't want to reboot their production servers (or their workstations with 5 open apps). /etc directory have to do with each other
3. Rebooting everytime you want to execute something from a removable media is definitely too much
2. I haven't quite figured out what your system and the
The real problem here is they "solve" the dependency problem by duplicating shared libs for every app which means:
1. Your libs will be n times in memory if you use n apps that use them instead of just 1 time
2. You can not be sure you updated all the vulnerable versions of a given library because instead of one in a known place they are all over the place
Even better designed software uses autoconf/automake or something similar so the package manager can configure where to install which part (config files, bins, libs,docs,...) of the software.
Shared libs are more about RAM than about disk space.
LSB would have a better chance if it wouldn't used the braindamaged RPM format.
Ideally one should add a dependency list into the bundle so each apps can tell the OS which shared libraries in which versions it uses.
Does OS X do that? How does it handle shared libs?
Games in Linux are perfectly possible. Linux just can not run (all) Windows Games as Windows can not run any Games from other OSs. You have to start using Linux to get a bigger Userbase to convince Game Companies to produce Linux ports of their Games.
And since there are no versioning filesystems for Unix (none that I know of, might be a useful addition) your delete attribute is useless (for now).
You have too many files in one directory
Not to mention that "ease of administrator-use"!="ease of newbie-use"
If Humans don't distinguish case why is it there in the first place? After all if that were the case we could just get rid of capital letters.
Where exactly is the difference between write and delete? If you can write to a file you can do all the damage you can with delete.
Guess you missed the "without the bloat" part.
I think Unix is a lot better in this aspect then all other OSs I know. Global Configuration is stored in /etc (or in case of multiple config file apps in a subdir of /etc) and user configuration is stored in the user directory in a hidden directory called like the app.