meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 8 months |
| seen | May 8 at 0:14 | |
| stats | profile views | 8 |
|
Apr 20 |
comment |
How to determine whether a linux filesystem belongs to a running system or not I’m glad I could help. |
|
Apr 19 |
comment |
How to determine whether a linux filesystem belongs to a running system or not @psusi: On Jan 14 at 18:23 JLledo issued this comment: «the first option, "the filesystem is the root of the current system –– the one that your program is running on".» |
|
Apr 19 |
answered | How to determine whether a linux filesystem belongs to a running system or not |
|
Apr 18 |
answered | How to find out out WHEN an user account was locked |
|
Apr 2 |
answered | vi backspace problem |
|
Mar 12 |
comment |
Reorder folders on FAT32 drive I suggest (1) adding a -type d to the find command (after the -o) to avoid getting mv: ./Beatles/Hey_Jude.mp3/*: Not a directory, mv: ./Beatles/Yesterday.mp3/*: Not a directory, etc., and (2) changing "$0/*" to "$0"/* (in the first mv command) so it will work and not throw mv: ./Beatles/*: No such file or directory errors. |
|
Mar 12 |
revised |
Reorder folders on FAT32 drive Corrected a typo (omitted “–exec”) and changed the language to conform better to the question (which asked about the order of _folders_ (presumably within the root directory) rather than the order of files). |
|
Mar 12 |
answered | PATH work with relative directories |
|
Mar 12 |
awarded | Custodian |
|
Mar 12 |
reviewed | Reviewed PATH work with relative directories |
|
Mar 12 |
suggested | suggested edit on Reorder folders on FAT32 drive |
|
Mar 5 |
awarded | Citizen Patrol |
|
Feb 28 |
revised |
redirect and log script output Fixed formatting, spelling, and punctuation. |
|
Feb 28 |
revised |
Is there some sort of “no newline at eof” rules for bash scripts? Fixed a typo and a formatting problem; added a case to the answer. |
|
Feb 28 |
suggested | suggested edit on redirect and log script output |
|
Feb 28 |
suggested | suggested edit on Is there some sort of “no newline at eof” rules for bash scripts? |
|
Feb 26 |
awarded | Informed |
|
Feb 14 |
awarded | Commentator |
|
Feb 14 |
comment |
file descriptor problem with looping bash script I’m still not 100% sure what you mean. (A car stops when the driver steps on the brake, and it stops when it runs out of fuel –– do you see the difference?) More importantly, does my correction fix the problem? If not, what have you done to debug it? (Other suggestions: put $LOGFILE and $LOGERR into quotes; i.e., "$LOGFILE" and "$LOGERR". And if you intend to capture all the output from the function in the $LOG files (as opposed to just the last call), the second (third) command should be “exec >> "$LOGFILE"” and the fifth (sixth) one should be “exec 2>> "$LOGERR"”.) |
|
Feb 8 |
answered | file descriptor problem with looping bash script |
