Debian 9 Net Installer Iso

0 views
Skip to first unread message

Boone Southern

unread,
Jun 30, 2024, 8:45:33 AM6/30/24
to nesstusdypa

This is a list of known problems in the installer shipped withDebian 12.5. If you have experienced a probleminstalling Debian and do not see your problem listed here, please send us aninstallation reportdescribing the problem orcheck the wikifor other known problems.

For extra convenience, these images may also be written directly to a USB stick. So long as your computer will boot directly from that USB stick, it should start the Debian installer that way.

In most cases it is not necessary to download and use all of these images to be able to install Debian on your computer. Debian comes with a massive set of software packages, hence why it takes so many disks for a complete set. Most typical users only need a small subset of those software packages.

The netinst CD here is a small CD image that contains just the core Debian installer code and a small core set of text-mode programs (known as "standard" in Debian). To install a desktop or other common software, you'll also need either an Internet connection or some other Debian CD/DVD images.

For more information about how to do these steps, read the verification guide. Only the first few images are available! Where are the rest? We don't store/serve the full set of ISO images for all architectures, to reduce the amount of space taken up on the mirrors. You can use the jigdo tool to recreate the missing ISO images instead.

This Debian image build only includes Free Software where possible. However, many systems include hardware which depends on non-free firmware to function properly so this build also includes those firmware files for those cases. See the Debian Wiki non-free firmware page for more information.Other questions?See the Debian CD FAQfor lots more information about Debian CDs and installation.

Limit to suite:[buster][buster-updates][buster-backports][bullseye][bullseye-updates][bullseye-backports][bookworm][bookworm-updates][bookworm-backports][trixie][sid][experimental]Limit to a architecture: [alpha] [amd64] [arm] [arm64] [armel] [armhf] [avr32] [hppa] [hurd-i386] [i386] [ia64] [kfreebsd-amd64] [kfreebsd-i386] [m68k] [mips] [mips64el] [mipsel] [powerpc] [powerpcspe] [ppc64] [ppc64el] [riscv64] [s390] [s390x] [sh4] [sparc] [sparc64] [x32] You have searched for packages that names contain debian-installer in all suites, all sections, and all architectures.Found 34 matching packages.

Debian Installer network install console (over ssh) in Stretch differs from that of Jessie and earlier. It has additional black "menu" line above the screen, which shows four "tabs" and a clock. These "tabs" are "(1*installer)", "2 shell", "3 shell", "4- log".

I remember them from "local" installer, where installer is on tty1, shells are on tty2 and tty3 and log is on tty4. It seems the Debian team added similar functionality to the ssh network install console.

Strangely I couldn't find any reference about this feature, but the whole remote ssh installer menu is actually running inside a screen, as this line can confirm (later, once the solution is already found):

The Debian Installer is a collection of packages maintained by theinstaller development team in GIT (level1) and other packages that show up during the installation process. These "other" packages are in level 2 and 3.

Ubuntu Server ISO images with debian-installer continue to be available, including for 18.04.3 LTS. There is no need to use media for an earlier point release. You most likely want ubuntu-18.04.3-server-amd64.iso, though other architectures are available.

On the main download page, the Use the traditional installer link takes you to a section for the "Alternative Ubuntu Server installer." These are the non-live ISO images for Ubuntu Server that use debian-installer (as Ubuntu Server has used exclusively for most of its history). This is in contrast to the more recently introduced live server images, which use curtin.

The link there for 18.04.3 LTS takes you to . The alternative server ISOs have names like ubuntu-18.04.3-server-arm64.iso; this indicates they use debian-installer. This is in contrast to the server ISOs offered at , which have names like ubuntu-18.04.3-live-server-amd64.iso and use curtin.

Debian-Installer is a system installer designed for the Debian Linux distribution. It originally appeared in the Debian release 3.1 (Sarge),[2] released on June 6, 2005,[3] although the first release of a Linux distribution that used it was Skolelinux (Debian-Edu) 1.0, released in June 2004.[4]

Originally, it was only supported under text-mode and ncurses. A graphical front-end (using GTK-DirectFB) was first introduced in Debian 4.0 (Etch). Since Debian 6.0 (Squeeze), it is used over Xorg instead of DirectFB.

debootstrap can be used to install Debian in a system without using an installation disk but can also be used to run a different Debian flavor in a chroot environment.[7] This way it is possible to create a full (minimal) Debian installation which can be used for testing purposes, or for building packages in a "clean" environment (e.g., as pbuilder does).[7]

win32-loader (officially Debian-Installer Loader)[8] is a component of the Debian Linux distribution that runs on Windows and has the ability to load the actual Debian installer either from the network (as in the version in an official website) or from CD-ROM media (as in the version included in Jessie CD images).

win32-loader was born as an independent project, for which only the network version was available. Later the code went through a long review and polishing process to become part of the official Debian distribution.

win32-loader strongly relies on projects such as NSIS, GRUB 2, loadlin and Debian-Installer to perform its task. Additionally, it has drawn inspiration and ideas from similar projects such as Wubi and Instlux.

I'm having problems installing OMV 0.4 from the ISO CD-Rom to a hard drive. It gets to the point where it is "Installing the System", then goes to the "Debian installer main menu", with "Install the System" highlighted. Selecting "Install the System" brings me to a screen that says
"The target files system contains files from a past installation. These files... Proceed with installation to unclean target?"
Then brings me right back to the same spot.

Almost any other selection from this menu presents me with the screen
"This installation step depends on one or more steps that have not yet been performed. Choose an installation step: "Install the System"

I booted a live linux CD after it failed, and used gparted to have a looksee at the partitions. OMV has is creating a 1.5gb linux-swap partition and the rest is a bootable ext4 partition with what looks like a complete file system. It does not however boot. It just hangs with a flashing cursor after post, with no error messages.

I can't find anything that resembles dmesg or messages. There is not /var/log directory either.
Is there an easy way to get logging in another terminal while the installation is happening, like a file that I can tail -f during the install to try and sort this out?

I'm trying to write a preseed.cfg which should be used for a full automated installation of Debian wheezy. For some reasons the installer is still asking to select a lanugage even if I set this in my preseed.cfg.

For a Debian installer script, if there is an error within the postinst script or the user uses Ctrl+C to kill the process, is it possible to have the entire install be rolled back? It looks like even if I return a non zero exit code, it still leaves the program installed.

Well, it's probably possible, because the postinst runs as root and can do all sorts of tricky stuff to subvert the system. But dpkg tries to protect against this as much as possible using locks, because maintainer scripts should not ever change the "desired" status of packages.

I haven't verified this, but I would guess that if you cancel a postinst script with Ctrl+C, it counts as a postinst failure, and the package is marked as being in the half-configured state. So, it's not left fully-installed, exactly, but yeah, it might be hard for the user to tell the difference.

If your package provides a service, you could have a flag (e.g., a file in some place like /var/lib/$yourpackage) which is set only when the package is fully installed (at the end of the postinst). The service would check for this flag on startup, and if it's not present, the service would not start, and might even print a warning message about not being fully installed. This solution would be similar in some respects to having the package totally uninstalled. Remember to unset the flag or remove the file at in the prerm and at the beginning of the postinst (in case a Ctrl+C occurs during an upgrade instead of on the first install).

You could catch the Ctrl+C (SIGINT) in the postinst, and print a message saying something like "This package will be left in the Failed-Config state. To remove it entirely, run (dpkg -P/apt purge/whatever). To attempt to complete installation, run dpkg --configure -a." (Then exit the postinst with a nonzero exit code, so that dpkg knows about the failure.)

You could take whatever thing in your postinst is most likely to be Ctrl+C'd, and move it to the preinst. If the preinst fails, then dpkg will call the postrm with the abort-install action. The postrm is expected to clean up anything that the preinst already did. If the postrm succeeds, then the package is left cleanly and entirely uninstalled. Of course, if this step of the postinst needs the files from your package to be unpacked and present, this isn't really an option.

Edit 9/1 - @fzinken, nfs install on pi3 installed ok, but permissions issues resulted in frown face. I suspect this is down to the export on my NAS. I suspect it should work correctly, for anyway one who knows how to correctly set up the nfs share on their server.

This is not about maintaining the package versions, I plan to make the 3 versions available via my github for the life of the current osmc-installer. Its more about aesthetics, do we need to add more to official site and wiki (and possible add bloat) if less will meet the users needs.

d3342ee215
Reply all
Reply to author
Forward
0 new messages