On 25.03.2010 13:17:48, Tom Hacohen wrote: > On Thu, Mar 25, 2010 at 8:58 AM, Benjamin Schieder wrote: > > On 24.03.2010 20:40:45, Jakob wrote: > > > A proper implementation would stop the daemons to be > > updated BEFORE the update, run the update, and then restart the daemons > > again. > > > No, that would just kill network connectivity before/after, that's also > annoying. > I don't think we should inerfere with phone's work without user confiramion.
I would take the "opkg install <newversion>" or "opkg upgrade" as
implicit user confirmation.
> > Think about it: start and stop might depend on config files, like the
> > inherently broken network configuration found in SLES.
> SLES?
SuSE Linux Enterprise Server. I've had nothing but problems with its
/etc/sysconfig/network/ifcfg-* files when using mildly advanced
configurations like bonding and vlan.
> > There, if you change your network configuration and then RESTART the
> > network services,
> > you will end up with a broken running network configuration. The correct
> > solution here is to stop the network script, change the config and start
> > it again.
> >
> But this will still stop your network connection unwanted.
Then don't update the network stuff.
Kind regards,
Benjamin
--
_ _ _ _ _
| \| |___| |_| |_ __ _ __| |__
| .` / -_) _| ' \/ _` / _| / /
|_|\_\___|\__|_||_\__,_\__|_\_\
| | (_)_ _ _ ___ __
| |__| | ' \ || \ \ /
|____|_|_||_\_,_/_\_\
Play Nethack anywhere with an x86 computer:
http://www.crash-override.net/nethacklinux.html
signature.asc
Description: Digital signature
_______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
