meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 4 months |
| seen | yesterday | |
| stats | profile views | 24 |
|
1d |
comment |
Query an overlayfs Oh! I didn't realize there was a filesystem actualy called "overlayfs". I'm only familiar with aufs and unionfs. The latter two do provide an easy way to query what their underlying branches are, but I wouldn't know about overlayfs. |
|
May 15 |
comment |
Query an overlayfs Which type of "overlay" filesystem are you using? |
|
May 12 |
answered | Finding all the hard-links of a file without traversing the file system |
|
May 8 |
comment |
Which home directory should 'nobody' have? I think that generally each operating system or operating system distribution has its own pesudo-standard for what the home directories of various system users are. For example, on Debian it's /nonexistent. What is the home directory of the nobody user on a fresh install of the operating system you are using? |
|
May 5 |
comment |
Standard I/O File Descriptors stdin, stdout, and stderr are file descriptors, not files. They may refer to files (or pipes, or sockets, etc...). In this case you made the stdout file descriptor (which is 1) refer to your file stdout.txt in the current directory. It doesn't matter what type of filesystem stdout.txt lives on. |
|
May 5 |
comment |
Standard I/O File Descriptors It doesn't matter what kind of filesystem is in use. If you use 1> stdout.txt (or, more commonly, just > stdout.txt), you should get a file called stdout.txt in the current directory. If the file can't be opened in the current directory (permission problem or some other error), you should get an error message informing you of this. |
|
Apr 29 |
comment |
Why is resolv.conf spelled without the 'e'? The easy answer is because it's a configuration file for libresolv, but of course that just leads to the question of why libresolv is called libresolv. To me it sounds like one of those legacy 6-character limits — the same reason why strcmp & co. are all named with 6 characters. |
|
Apr 17 |
comment |
Fixing ssd card filesystem I have no idea what a sansa is, but error -110 is ETIMEDOUT, so that looks like a USB communication problem more than a problem with the block device or its contents. Writing to the device with dd or by creating a new filesystem on it (with mkfs) should definitely work if the hardware is healthy... |
|
Apr 13 |
revised |
Having the 'id_rsa.pub' file in my dotfiles public repo securely additional information about sharing; see comments |
|
Apr 13 |
comment |
Having the 'id_rsa.pub' file in my dotfiles public repo securely Correct, but I wouldn't tempt fate by doing that. See edits. |
|
Apr 13 |
answered | Having the 'id_rsa.pub' file in my dotfiles public repo securely |
|
Mar 24 |
comment |
Creation of a WORM file Permission bits of 4000 make no sense. Did you mean 0400? If so, that's a read-only file, not a WORM file. Also, what's the "retention"? I do not believe that any such thing as "retention time" actually exists. Most importantly, what are you actually trying to do? |
|
Mar 18 |
comment |
find in /sys/class does not show everything, why?hwmon0, hwmon1, and hwmon2 are probably symlinks. The actual location of those directories is elsewhere in the /sys hierarchy. |
|
Mar 6 |
comment |
How to make a path world-readable?chmod o=+x doesn't make sense. In the chmod syntax, -, =, and + are mutually exclusive operations. They mean, respestively, remove permissions, set exact permissions, and add permissions. |
|
Mar 6 |
comment |
Horrible situation - file systems mounted simultaneously by multiple independent OS instances @Johan I didn't know about SCSI-level reservations managed by the target itself. Thanks for that information. |
|
Mar 5 |
comment |
Horrible situation - file systems mounted simultaneously by multiple independent OS instances Regarding your post script: if the devices are visible through multiple paths then the kernel probably doesn't even know that they are all the same device, so how could it "reserve" it? As for exporting a device from dom0 to multiple domUs, it lets you do that because you might actually want to do it on purpose (e.g. with a filesystem that supports it, or mounted read-only everywhere). |
|
Mar 1 |
comment |
what happens when a window manager is put to background Re: "explain why when a parent bash script exits it causes child background processes to terminate". It does not have this effect at all. |
|
Mar 1 |
comment |
what happens when a window manager is put to background 2. the shell script (which is not a bash script here but a general shell script) does not send any signal to less to cause it to terminate. After the shell script exists, less loses its parent, is inherited by init, and is on its own. It can continue if it wants to, or not. In this particular case, less is an interactive process and it cannot interact with the controlling terminal if it is not the foreground process, so it won't accomplish much. However in the case of .xsession and a window manager, there is no controlling terminal and no interactive process. Any process can run. |
|
Mar 1 |
comment |
what happens when a window manager is put to background 1. The X server does not run in the "foreground" or "background" as those terms are defined with reference to controlling terminals and job control (See Gilles' answer for details on that). |
|
Feb 28 |
answered | what happens when a window manager is put to background |
