Re: suspend to disk unreliable?
On Thu, Jul 01, 2010 at 07:10:58PM +0000, Camaleón wrote:
>
> So... when something goes wrong, you need to debug it, whatever it is
> (hibernation or something else). And debugging usually requires some
> "sacrifices" >:-) (meaning, trial and error tests).
Insofar such testing involves eventually losing data, doing such
testing isn't really an option.
> > Hibernating isn't worth taking a risk.
>
> Ah, that is a personal choice (not the one I would choose, BTW).
>
> But by following a "do-nothing" path you are losing some nice features
> that hibernation provides and the worst here is that the problem your are
> facing most sure could be easily bypassed by following a little steps and
> requesting further info. BTS (Debian bug tracking system) is your
> friend :-).
Losing features like corrupting your filesystems? Filing bug reports
doesn't seem to achieve anything these days.
> > There's the dealers selling the hardware and warranty on the hardware.
>
> No, sir. You maybe meesed Windows with Debian ;-)
No, you're doing that. It's just hardware, and if it doesn't work, I
return it. It's that simple.
> > Do you expect to behave a car as described above just because you buy it
> > as is? Do you buy cars certified by the manufacturer to work reliably
> > and to play nice with your specific using conditions?
>
> Sure, and if not, I will make some debug on the car ;-)
No manufacturer or dealer is going to give you a certificate that the
car in question will perform as desired under your particular
driving/using conditions. And who would buy a car that comes with a
certificate that only the ppl named in the certificate are allowed to
use it and that otherwise the car might break down and any warranty is
forfeited?
> I wish I had the same flexibility with a car than I currently have with
> my computer systems... A car is a "turn-key" piece of hardware: as long
> as you make any change you void the guarantee.
The difference is that I bought my "car" in parts and put them
together myself. When a part doesn't work, I return it under
warranty. You could do the same with cars --- it might involve some
more trial and error testing, but I'm sure you won't mind that, all
the less since it would give you all the flexibility you desire ;)
> >> What "required tools" are you referring to?
> >
> > the tools needed for graphics cards
>
> There no such tools. What you usually have to do when the graphics card
> driver (or any other driver) has problems to resume from hibernating is
> creating a hook to load/unload the required driver, that should be all.
The documentation says that there are. Perhaps what you're describing
is what these tools do ...
> For instance, it's quite normal to lose the network connection after
> resuming, so a hook for restarting networkmanager is sometimes required.
I have disabled starting networkmanager. It doesn't seem to have any
use but rather seemed to mess around with network settings, or it
spawned lots of processes, I don't remember. Obviously, it's not
needed.
Reply to: