bkil vs. programming

One day, I was playing with a chroot jail. This whole incident has taken place some months ago. I wanted to test if I could install software from user mode because my apt-get was doing a system update. Well, building from source via "apt-get -b source" would have also solved the issue, though dependency handling in this case is not automatic if I understand correctly. In order for this process to take as little overhead as possible, I wanted to simulate a manual copy-on-write filesystem by creating links to the parts that are common with my root system, and recreating directories which are partially different. I first tried to use symbolic links, but I had to realize that relative links that point outside the sandbox were dysfunctional. Hence I made a hardlink for my root in the chroot. Well, it was a read-only bind-mount to be more exact. Note that I did succeed previously with a different system and kernel (Gentoo 2005.x) by using symbolic links, that's why I gave it a...

Most users up until now had only a single partition on their single rotating media disk in their personal computers. Common operating systems did not (and some still not) encourage their end users to organize their data into partitions in a different way. Naturally, this would be both an overkill and a mental overload for most users. However, an advanced user should not turn away from the possible benefits of restricted fragmentation and lowered seek times. Also consider the ease of backing up only the partitions that contain truly precious data. A few words about fragmentation. Most random access file systems today use block-sizes of discreet steps (sometimes only a single block size). External fragmentation is the physical discontinuity of logically continuous stored entities (files). Internal fragmentation is the overhead of this block scheme. Naturally if a file is composed of many identically sized, relatively large buckets, then most files will have some buckets that are not com...

The first OS I have installed was probably some DOS for a friend or classmate in primary school, I can't remember which. You understand if normal people can't install and configure that properly, as it is considered pretty difficult. I then did winblows a few times, though that's a harder treat. How do you expect a normal user to feel at home with his computer if he can't even install it for himself? It's supposed to be user friendly or so. Also note, that after removing the installer disk and placing it on the shelf does not end your responsibilities. If you install new hardware, software, or just simply switch some setting that change a major part of the system, you will need to get used to handling setup dialogs and wizards. And by the way, if the installation process is usually done by a semi-professional anyway - either in the shop before you buy, or if you ask help from a friend - then that voids the major part of the very common argument against using any unu...