Hot answers tagged

3

You are confusing filesystem (organization) semantics with partition (storage) semantics. Linux filesystem hierarchy is like a single giant tree with a stem (/) , branches ( /boot, /home, /bin, /usr, /var ) and sub-branches ( /usr/bin, /var/log ...). This metaphor is equivalent of the parents, children and grandchildren. All these symbols/names ...


2

It means that the RAM sticks are driven by a clock signal — as opposed to (older) asynchronous DRAMs. See the Wikipedia page on SDRAMs. To find out whether your RAM is dual-channel, look for “Interleaved Data Depth” in dmidecode output. It should say 1 for single and 2 for dual channel RAM.


2

It's quite a job for sed: $ printf 'foo\nbar\n' | sed -n '$!N;/\nbar$/P;D' foo


2

In the case of MBR (and 1/2 KiB blocks) the information are stored in the first block (first 512 bytes) and for historical reasons and out of compatibility with various OSes the first really useful block would be the 63th. The space in-between is often used by boot-loaders for the program code for one of their levels. In the case of GPT you have the ...


1

There are of course two possibilities: decrease the permissions of the files to a level the user can access increase the permissions the modifying app is having regarding 1) You can try to add additional rights via ACLs (I would heavily discourage changing the UNIX permissions, lots of programs have expectations and they will be changed with the next ...


1

Solution is to run the program itself as root, thereby having permission to files in /etc.



Only top voted, non community-wiki answers of a minimum length are eligible