« first day (1533 days earlier)   

5:45 AM
What happens on boot if a device referenced by UUID in fstab can't be found?
I assumed that it just failed and life moved on.
Once my Pi comes up, I'll take a look at the log, but I think that it's taking a lot longer to boot because something is wrong with finding the USB drive.
 
6:24 AM
@derobert I was the last reviewer on that and IIRC there were so many different reasons to close this one that it caught my eye and I had another ( asking for learning materials). I briefly considered editing the "Thanks" out of the question (in another window). Could it be that because of 5 different reasons not giving majority consensus the orginal close reasons was taken?
Not 100% sure if that is true, but I will keep that in mind that that might happen if I notice multiple close reasons.
 
 
6 hours later…
12:46 PM
what is so bad about my answer to deserve a downvote? unix.stackexchange.com/a/175142/17433
 
1:06 PM
@Janos - it's really not bad. I'm sorry man. It's just a kneejerk thing when I read no you can't or similar. I can't reverse it now though wihtout an edit being made,
 
1:24 PM
@mikeserv You could make an edit.
 
Yes I can!
 
@mikeserv That's the spirit!
Never Say Die!
 
ok. so maybe it's kinda bad. I downvoted it before because of the no you cant thing - I didn't really notice the whole find | xargs deal til now.
Oh well.
 
and the whole find | xargs thing is bad because.....?
 
There are many reasons it is bad - in the first place it needlessly complex - why do you need so many processes? Also you dont quote $dir123, and you don't even know the filenames can be read like head -n1
What's the point of doing print -0 at all in that case?
Why do you not find ... -exec ...?
 

« first day (1533 days earlier)