The *.mov files are records from hibernation/suspend attempt. They have polish names, ignore that. You can see that it reboots again right at the end of resume, then boots into log-in screen
I think it is related to my hardware: dual Xeon E5-2687Wv2, 64 GB of RAM, motherboard SUPERMICRO MBD-X9DRI, GPU nvidia GTX 780 (only debian approved nonfree drivers, no blobs from nvidia.com)
Here's my SLEEP script, in which I am testing various kernels:
logger "========== touch forcefsck ==========="
# if resume failed, then I want fsck (SSD disks, so it's just few seconds)
# it says there to try hibernating using various different methods
### method: 1 kernel 3,13,0 - fail, (2/6 success rate)
### method: 2 kernel 3,13,0 - fail, (3/6 success rate)
### method: 3 kernel 3.13.0 - fail, (2/6 success rate)
#echo platform >
#echo disk >
### method: 4 kernel 3.13.0 - (3/6 success rate)
### kernel 3.2.0 - 80% sukcesów 20% fail (over 80/100 success rate - currently in use)
### kernel 3.12-bpo - (0/1) success rate)
echo shutdown >
echo disk >
logger "restart network"
## something screws networking after resume
## also UPS connection is screwed (sometimes I need to disconnect and reconnect the USB cable)
# don't mess with clock
logger "resume complete"
Besides, this is old news. Our new and better site beat slashdot: https://soylentnews.org/articl... . The only working kernel was 2.6.29 with tuxonice
1.) Run sudoedit and uncomment the line that says "%wheel ALL=(ALL) ALL".
2.) Make sure you're in the wheel group.
If you're a sysadmin, you need to stop people from shooting themselves in the foot. There should be some way of restricting use, right? Just gotta check out the man page.... And that's where I stopped, every time. I've yet to truly understand Extended Backus-Naur Form, and my eyes would glaze over. And so I'd go back to putting some small number of people in the 'wheel' group, and letting them run sudo, and cleaning up the occasional mess afterward. Fortunately, Michael W. Lucas has written Sudo Mastery: User Access Control for Real People." Keep reading for the rest of Saint Aardvark's review.
If you were paying attention you would know that from 10 to 17 february there is slashdot boycott (slashcott) in which people log off and can only browse anonymously to give dice holdings fewer requests from logged in users.
PS: doesn't that posting a new story exactly once per hour doesn't ring you a bell?
So if we can get this thread out of the Firehose, I was thinking that, as the 10th arrives for us in our respective locations, we could leave here what may be our final farewells to Slashdot.
Until Midnight, this is our meeting place, our City Hall, our town square.
(and yes, our playground)
After that I'm not sure where we can congregate to discuss how the Slashcott's going and whether it's time to move on.
I'm going to jump the gun and lay claim to "So long and thanks for all the Karma", and perhaps someone could do a Bob Hope and re-write the lyrics to "Thanks for the Memories".
In the meantime, a bit of housekeeping.
An AC beat me to the week-long boycott idea by a couple of hours, and suggested the date range of the 10th through the 17th.
As part of a group of people familiar with the concept of beginning a count with 0 instead of 1, I really should have spotted the mistake of putting 8 days into that particular week.
So, should Slashcott Week end as the 17th begins, or do we give Dice a bonus day?"
I hope it will have UTF-8 support as well as mathjax - the math rendering engine used on stackexchange. Imagine how wonderful comments and posts could look like, if people could embed formulas easily!
Our wiki now collects all the most important ideas: http://www.altslashdot.org/wik...
Also you are welcome on IRC ##altslashdot on freenode
BTW, I haven't changed my sig since 2002, and it will be the same on new slashdot, whatever name we pick: http://www.altslashdot.org/wik...
Link to Original Source