On Sun, 26 May 2013 04:02:56 +0200 Peter Stuge <pe...@stuge.se> wrote:
> By take effect I mean that the filesystem should be modified in such > a way that the next boot will use what I selected. No further action > which could fail should be required beyond the eselect command. > > Unless the eselect command has successfully modified the filesystem I > can't really know that my system will boot with what I have selected, > ie. eselect does not provide any useful feedback, because it can not. That's exactly what I've described in another mail in another subthread. http://thread.gmane.org/gmane.linux.gentoo.devel/85778/focus=85789 Snippet of what I said: > Sounds like we would have two files like 'current_init' and > 'boot_init' and `eselect init ...` would update 'boot_init'. Then, > the first `init` invocation on boot would update 'current_init' with > the value of 'boot_init'; latter `init` invocations can then read out > 'current_init', which is not to be touched by `eselect init ...`. This assumes that you would be working with a wrapper, not a symlink. -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : tom...@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
signature.asc
Description: PGP signature
