On 03/21/2013 05:42 PM, Peter Krempa wrote:
The man page states that with --config the next boot is affected. This
can be understood as if _only_ the next bood was affected. This isn't
s/bood/boot/
true if the machine is running.
This patch adds the full --live, --config, --current
On 03/21/2013 12:42 PM, Peter Krempa wrote:
The man page states that with --config the next boot is affected. This
can be understood as if _only_ the next bood was affected. This isn't
true if the machine is running.
Are you certain of that? My understanding was that when --config was
On 03/27/13 16:22, Laine Stump wrote:
On 03/21/2013 12:42 PM, Peter Krempa wrote:
The man page states that with --config the next boot is affected. This
can be understood as if _only_ the next bood was affected. This isn't
true if the machine is running.
Are you certain of that? My
On 03/27/2013 11:39 AM, Peter Krempa wrote:
On 03/27/13 16:22, Laine Stump wrote:
On 03/21/2013 12:42 PM, Peter Krempa wrote:
The man page states that with --config the next boot is affected. This
can be understood as if _only_ the next bood was affected. This isn't
true if the machine is
On 03/27/13 17:25, Laine Stump wrote:
On 03/27/2013 11:39 AM, Peter Krempa wrote:
On 03/27/13 16:22, Laine Stump wrote:
On 03/21/2013 12:42 PM, Peter Krempa wrote:
The man page states that with --config the next boot is affected. This
can be understood as if _only_ the next bood was affected.
The man page states that with --config the next boot is affected. This
can be understood as if _only_ the next bood was affected. This isn't
true if the machine is running.
This patch adds the full --live, --config, --current infrastructure and
tweaks stuff to correctly support the obsolete