[PATCH] command line options for hald-addon-acpi

[Richard Hughes]

On Tue, 2005-08-02 at 21:44 +0200, Timo Hoenig wrote:
> Aren't you frightened by the amount of reboots you'd have to accept
> while developing HAL?

No, I seem to manage fine with a boot in the morning and a shutdown in
the evening on my laptop.

> > > Wait, just let me check my uptime... ;-)
> > 
> > I just don't know about statements like that. Uptime is really just a
> > geek-factor, what we want is a robust, secure and predictable system.

[hughsie at localhost ~]$ uptime
 20:57:38 up  4:07,  5 users,  load average: 2.01, 1.06, 0.68

l33t.

> I was not taking this as geek factor.  I am just enjoying my hundreds of
> suspend cycles and the software updates in between without the need of
> rebooting.  Maybe rebooting doesn't take long, but restoring the
> workspace like it was before takes very long.

Depends how you define "long".

> If you take reboot as 
> 
>         BIOS + kernel boot + X + restoring workplace
> 
> you will be bored by every single reboot it takes.

I'm pleased of the coffee break to be honest. And my girlfriend is
pleased with the attention. :-)

> > You mention "Other" operating systems - well, I don't think the
> > mainstream Linux-based systems are doing better, in fact I think Windows
> > XP SP2 is pretty darn good in terms of both user experience and making
> > sure security patches get applied. But that is of course my personal
> > somewhat uninformed opinion (I'm not a security expert by any means).
> 
> I am always looking left and right -- Windows still reboots all too
> often and even though it boots up quick, the amounts of reboots are
> killing too much time.

I'm agreed on this. I installed a W2K PC for my sis, and probably
rebooted it about 8 or 9 times before I was finished.

I've only ever had to reboot once using "yum update" tho.

> > > There are drivers (IBM ACPI, Panasonic ACPI, Sony ACPI just to name a
> > > few) generating ACPI events which are not handled by HAL and thus get
> > > lost if HAL claims /proc/acpi/event.  Yes, there is a generic hotkey
> > > driver on its way to make the specific drivers obsolete but it does not
> > > yet provide the wide range of functionality the specific ones do.
> > 
> > Just start acpid before hald and everything will be fine. Btw, we will
> > add support for vendor-specific drivers at some point in HAL (as well as
> > the new generic hotkey driver).
> 
> That is fine.

Will be, when we write the backend!

> Back to the real problem, what is you're opinion about HAL on server
> systems (high availability)?

Err, high-availability servers? I wouldn't be running X on a
high-availability server, let alone HAL. Plus you never have 1
high-availability server - you have a cluster in a round-robin fallback,
where you can take each one down without effecting the main services.

Thanks, 
Richard.

_______________________________________________
hal mailing list
hal at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/hal