Because you're not necessarily installing the same API.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
On Tue, 18 Dec 2018 23:33:30 +0100 (CET)
k...@aspodata.se wrote:
> With all this discussion about installing procedures, why do we need
> to reboot during reboot ?
>
> Couldn't one boot the install media like an initram thing and then
> pivot_root (or what is used today) the real system and
With all this discussion about installing procedures, why do we need
to reboot during reboot ?
Couldn't one boot the install media like an initram thing and then
pivot_root (or what is used today) the real system and continuing
from there...
I did some experiments some ten years ago, but run out
On Tue, Dec 18, 2018 at 06:28:06PM +, g4sra via Dng wrote:
> >
> > I still fail understanding what you mean by "Program 2". It's called,
> > maybe, just "apt-get" or "synaptic".
> >
>
> OK, um..
> take tasksel, clone it into two.
>
> In tasksel one [1], keep everything that is NOT optional
On Tue, Dec 18, 2018 at 06:36:30PM +0100, Adam Borowski wrote:
>
> Yeah but all the partitioner questions can be asked before the action is
> committed. Not that mkfs takes a noticeable amount of time anyway...
Can be ... at present I don't think you can start defining partitions
in a RAID or
>
> I still fail understanding what you mean by "Program 2". It's called,
> maybe, just "apt-get" or "synaptic".
>
OK, um..
take tasksel, clone it into two.
In tasksel one [1], keep everything that is NOT optional (and is stateful).
Partitioning, formatting, kernel, bootloader, package manager
On Tue, Dec 18, 2018 at 05:30:47PM +, g4sra via Dng wrote:
> [snip]
> >
> > You are confusing a simple config file that is read once and for all
> > during boot time (the config file on raspberry pis) with the complete
> > installation of a new system. They are not even comparable. There is
>
On Tue, Dec 18, 2018 at 05:24:10PM +, g4sra via Dng wrote:
> I often have difficulty with correct terminology despite having a very
> definite
> idea.
>
> The term 'Installer' applies to the first stage actions taken outside of the
> package manager such as partitioning, formatting,
On Tue, Dec 18, 2018 at 06:19:39PM +0100, KatolaZ wrote:
> > It is my view that the configuration program should be capable of being
> > run at any time after installation, even multiple times on separate
> > occasions as required.
>
> I am not sure what you exactly mean here. The installer
[snip]
>
> You are confusing a simple config file that is read once and for all
> during boot time (the config file on raspberry pis) with the complete
> installation of a new system. They are not even comparable. There is
> no thing like "oh I re-run the installer configuration to change the
>
I often have difficulty with correct terminology despite having a very definite
idea.
The term 'Installer' applies to the first stage actions taken outside of the
package manager such as partitioning, formatting, bootloader and kernel...
which actually make the build host bootable. There 'may' be
On Tue, Dec 18, 2018 at 04:58:00PM +, g4sra via Dng wrote:
> On 18/12/2018 03:48, Steve Litt wrote:
> > [snip]
> > Perhaps reframing it would make a difference. Perhaps renaming the
> > second program "Install Software" (install_software), and having it
> > boot into install_software, would
On Tue, Dec 18, 2018 at 04:58:00PM +, g4sra via Dng wrote:
[cut]
>
> To clarify further...
> It is my view that the configuration program should be capable of being
> run at any time after installation, even multiple times on separate
> occasions as required.
>
I am not sure what you
On 18/12/2018 03:48, Steve Litt wrote:
> [snip]
> Perhaps reframing it would make a difference. Perhaps renaming the
> second program "Install Software" (install_software), and having it
> boot into install_software, would satisfy all but the most
> windows-phobic that the sum of the two programs
On Tue, Dec 18, 2018 at 04:29:25PM +, g4sra via Dng wrote:
> On 18/12/2018 13:19, Hendrik Boom wrote:
> > On Mon, Dec 17, 2018 at 10:51:53PM -0500, Steve Litt wrote:
> >> On Sun, 16 Dec 2018 13:28:43 +0100
> >> KatolaZ wrote:
> >
> >> Also, Hendrik is right: If the bootable installer
> >>
On 18/12/2018 13:19, Hendrik Boom wrote:
> On Mon, Dec 17, 2018 at 10:51:53PM -0500, Steve Litt wrote:
>> On Sun, 16 Dec 2018 13:28:43 +0100
>> KatolaZ wrote:
>
>> Also, Hendrik is right: If the bootable installer
>> finds information, it should be saved for the secondary installer to
>> use.
>
On Mon, Dec 17, 2018 at 10:51:53PM -0500, Steve Litt wrote:
> On Sun, 16 Dec 2018 13:28:43 +0100
> KatolaZ wrote:
> Also, Hendrik is right: If the bootable installer
> finds information, it should be saved for the secondary installer to
> use.
It would be enough if the software the bootable
!Ola outra vez!
and: sorry for delay ...
(to be ill)
Am 10.12.18 um 16:26 schrieb Didier Kryn:
> don't ask me why, I don't know, but it works.
OK, *Big Thanks* for Help and the Script.
*Yes! it work's for me*
Happy Hollyday's @all (whatever you celebrate)
Michael
--
GnuPG Fingerprint: CF03
18 matches
Mail list logo
