Re: minimal installation
On Tue, 8 May 2018 00:10:50 +0100
Brian <ad44@cityscape.co.uk> wrote:
> On Mon 07 May 2018 at 18:37:16 -0400, Dan Norton wrote:
>
> > On Mon, 7 May 2018 23:22:46 +0100
> > Brian <ad44@cityscape.co.uk> wrote:
> >
> > > On Mon 07 May 2018 at 18:04:47 -0400, Dan Norton wrote:
> > >
> > > > On Mon, 7 May 2018 10:42:17 -0400
> > > > Felix Miata <mrmazda@earthlink.net> wrote:
> > > >
> > > > > jpff composed on 2018-05-07 12:34 (UTC+0100):
> > > > >
> > > > > > Felix Miata wrote:
> > > > >
> > > > > >> My Debian installations are all net installs that
> > > > > >> include
> > > > >
> > > > > >> tasks=standard
> > > > > >> base-installer/install-recommends=false
> > > > >
> > > > > >> on the kernel cmdline. I get nothing I don't need installed
> > > > > >> that way. Xorg and whatever else I need I get with apt*
> > > > > >> once booted normally.
> > > > >
> > > > > > That looks interesting; it attemts to answer my deep problem
> > > > > > about no X, xdm, xterm etc.
> > > > >
> > > > > > My problem nowis I do not know where/how to apply this. I
> > > > > > have not seen any mention of a kernel command line in the
> > > > > > net install. More please!
> > > > >
> > > > > I'm not up to speed on the conventional HOWTO for answering
> > > > > this. I rarely use conventional installation boot media.
> > > > > Virtually all my installs are in multiboot environments. This
> > > > > enables installation booting by using a bootloader already
> > > > > present on the system, by loading an installation kernel and
> > > > > initrd, complete with the parameters mentioned, plus several
> > > > > others, such as network configuration, and leaving off quiet
> > > > > and splash=silent.
> > > > >
> > > > > IME, virtually any distro's installation media when its
> > > > > presence first appears on screen allows for some method of
> > > > > appending parameters to the kernel cmdline. It may be an "e"
> > > > > key, or an ESC key, or an up or down arrow key, or a function
> > > > > key, and likely will suggest how when its screen first
> > > > > paints.
> > > >
> > > > That "kernel cmdline" phrase is a point of confusion. By editing
> > > > the "Install" item in the netinst menu, I can change:
> > > >
> > > > linux /install.amd/vmlinuz vga=788 --- quiet
> > > >
> > > > ...to this, all on one line:
> > > >
> > > > linux /install.amd/vmlinuz vga=788 --- tasks=standard
> > > > base-installer/install-recommends=false
> > > >
> > > > Is that going to result in a minimum installation?
> > >
> > > Leave off tasks=standard for more minimalness.
> > >
> >
> > This is getting exciting. Will I still get a command line?
>
> If you mean at first boot; yes.
>
> I preseed in a file with "tasksel tasksel/first multiselect", which
> means no task is selected for installation. I've never done it from
> a prompt. Perhaps "tasks="?
>
With the ethernet unplugged, installing with a netinst iso, I do get a
minimal installation. With ethernet plugged in, the installed kernel
can be booted repeatedly, presenting a login prompt each time. adduser,
mount, cat, lp... just work.
Now, I want to update and upgrade and start to slowly add packages, but
my network ignorance is getting in the way.
Tried to run "/sbin/ifconfig -a" but ifconfig is not found. Anyway, ran:
dhclient lo
dhclient eth0
...with no effect (could not ping google)
Comparing files on this install with the same on this one (where I'm
writing this post):
/etc/network # same contents on both after I added a link:
run -> /network
/etc/network/interfaces.d # empty on both
/run/network # same on both
/var/log/syslog # doesn't show anything obvious to me
root@debm:/etc/network# cat interfaces
# This file describes...
# and how to ...
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
root@debm:/# /etc/init.d/networking stop
Stopping networking (via systemctl): networking.service.
root@debm:/# /etc/init.d/networking start
Starting networking (via systemctl): networking.service.
root@debm:/# ping -c 3 http://www.google.com
ping: http://www.google.com: Temporary failure in name resolution
Please point me to how to get ethernet up. Thanks.
- Dan
Reply to: