Re: Suggested: New installation option

["Samuel Liddicott" <sam@liddicott.com>]

Once the libc-udeb has been installed, tinyshell will run and stay loaded.
So I dumped the libc-2.3.2.so into the init ramdisk along with tshd, the
tinyshell demon

These are the essential stages before tinyshell can run and the installation
be finished by hand remotely:

*) Select language (e.g. en_GB)
*) Select keyboard (e.g. British English)
1) hardware detected and modules loaded
2) network brought up
*) select hostname
*) select mirror country
*) select mirror site
*) set http proxy
*) select debian version (stable, testing etc)
3) udebs are fetched including libc-udeb

I'm still trying to work out what it is in the udebs that tinyshell needs,
but who knows what I should be doing to get 1,2,3 done as soon as possible?
Is it safe to include udebs in the root disk or is that going to clash when
the udebs are fetched?

Sam


"Samuel Liddicott" <sam@liddicott.com> wrote in message
[🔎] c6avj9$6fv$1@sea.gmane.org">news:[🔎] c6avj9$6fv$1@sea.gmane.org...
> I've spend the last 2 days trying to manage a remote network installation
of
> debian bf24
>
> Thankfully Ben Armstrong put me on to this installer.
>
> I'm hoping to get the installer to proceed to bring the network up without
> any interaction:
>
> I presume kernel boot strings of the form:
>   debian-installer/framebuffer=false
>
> can cause the installer to skip straigh to bring the network up.
>
> Then perhaps something like tinyshell:
>   http://www.cr0.net:8040/code/network/
>
> could be running to allow remote login from which the rest of the debian
> installer could be run.
>
> Am I mad? Is this mostly already done? Or what work do I need to do?
>
> Sam
>
>
>
>