[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: bin/37415: sysinst should be available after installation
The following reply was made to PR bin/37415; it has been noted by GNATS.
From: Marc Balmer <mbalmer%NetBSD.org@localhost>
Cc: David Holland <dholland-bugs%NetBSD.org@localhost>,
Subject: Re: bin/37415: sysinst should be available after installation
Date: Sun, 04 Mar 2012 10:19:10 +0100
Am 03.03.12 19:45, schrieb David Holland:
> The following reply was made to PR bin/37415; it has been noted by GNATS.
> From: David Holland <dholland-bugs%netbsd.org@localhost>
> To: gnats-bugs%NetBSD.org@localhost
> Subject: Re: bin/37415: sysinst should be available after installation
> Date: Sat, 3 Mar 2012 18:41:03 +0000
> On Sat, Mar 03, 2012 at 09:40:04AM +0000, Marc Balmer wrote:
> > If sysinst can be used for something useful _after_ system installation,
> > then we can move it to /usr/sbin or /sbin.
> There are a number of possible things, such as configuring the
> network, or installing sets that one didn't the first time.
> Or, even, doing a system update, but that is probably not safe the way
> things are currently organized.
What would be a good way to detect whether sysinst is run at
installation time or after installation? The difference between the two
modes should be the menus. It would behave differently and offer
Maybe sysinst can detect whether it's part of a crunched binary (install
time) or a selfstanding binary (after installation)?
Main Index |
Thread Index |