Re: Problems installing from flash drive.
Hi Richard, Here's what I would probably do: - create directories on your USB or partition for each of the DVDs - extract each ISO, and place the contents in the directories - if using a separate partition, mount it in your fstab at a location such as /mnt/deb, or if using a USB, just make sure to always mount it at the same location when you want to install something Then you can add a line such as this to your APT sources: deb [trusted=yes] file:///mnt/deb/DVD1/ buster main deb [trusted=yes] file:///mnt/deb/DVD2/ buster main deb [trusted=yes] file:///mnt/deb/DVD3/ buster main Now whenever you want to install something, you shouldn't have to worry about which DVD it was on, APT should just automatically find it. Jeremy On Fri, 5 Feb 2021 at 09:55, Richard Owlett wrote: > I wish to do custom Debian install on a machine *WITHOUT*: >1. functional mechanical CD/DVD drive. >2. without internet access. > > One can purchase a flash drive containing ISO images of all installation > DVDs of the desired architecture. It is straight forward to do a default > install after copying dvd1.iso to a flash drive. > > Resulting problems include: >1. undesired programs clutter machine (e.g. LibreOffice). >2. project critical software cannot be installed as Synaptic > asks for a non-existent DVD be inserted in a non-existent drive. > > One vendor has a shell program which loop mounts the ISO files in such a > way that *IF* you have the purchased flash drive installed you can use > Synaptic. > > The Debian documentation does not appear to describe how apt &/or > Synaptic can access ISO files on dedicated partition. > > Are the instructions to create a "local repository" composed of > appropriate ISO files? > > TIA > > >
Re: "Run fsck manually"..?
You might have to boot from a recovery CD image, such as a Debian live install image, or GParted Live. You can't actually run fsck on a drive while said drive is mounted. On Tue, 2 Feb 2021 at 19:24, Stefan Monnier wrote: > >> My brother's Debian system suddenly says on attempt to boot, "/dev/sda1: > >> UNEXPECTED INCONSISTENCY:Runfsck manually", and, "inodes that were part > of > >> a corrupted orphan linked list found." > >> > >> He enters "fsck" or "fsck /dev/sda1", and in a short while gets fsck > >> identifying it's version, and nothing else. Tha appears to take place > >> from (initramfs) and Busybox. An attempt to reboot just starts the > >> problem all over again. > >> > >> We'd be grateful for help with this. Thanks. > >> > > hello, > > > > fsck -fy /dev/sda1 is probably what you want > > Then again, after the "UNEXPECTED INCONSISTENCY", the `-f` flag to > `fsck` shouldn't be needed. This is weird. > > > Stefan > >
Re: debian stable kernel not updating on one machine
Possibly a dependency conflict of some kind. Maybe try updating from the terminal to see if it works or at least gives a useful error message sudo apt update && sudo apt upgrade && sudo apt full-upgrade You could also check the contents of the /boot directory to see if the kernel is actually there. If the kernel is there on the drive but not being used to boot, then you could try running "sudo update-grub" and then rebooting. On Tue, 2 Feb 2021 at 18:14, D. R. Evans wrote: > I went to update one of my machines running debian stable today, using (as > usual) synaptic [which I think is basically a wrapper for various apt > functions]. The machine is running: > > > > [Z:~] uname -a > Linux zserver 4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28) x86_64 > GNU/Linux > [Z:~] > > > > But I see that synaptic lists 4.19.0-14-amd64 as being available in the > repository; and, indeed, on another machine I updated earlier in the day > the > kernel was updated from -13 to -14. > > How might I be able to diagnose why the files relating to the -14 kernel > are > not selected when I hit synaptic's "Mark All Upgrades" button? > >Doc > > -- > Web: http://enginehousebooks.com/drevans > >
