Re: Problem with Macbook 2,1 Installation Instructions
Sorry, just realised that i forgot to CC Carl on my response. In case he's not reading the list: Andy Cater wrote: >On Sat, Apr 17, 2021 at 06:20:19AM -0400, Carl N wrote: >> Can anyone please help me with this installation? >> >> https://wiki.debian.org/InstallingDebianOn/Apple/MacBook/2-1 >> >> the line: >> grub-install --target=i386-efi --efi-directory=/mnt/usb >> --boot-directory=/mnt/usb/boot --bootloader-id=boot --removable >> >> I try this and it says 'doesn't look like an EFI file system" >> >> I'm really stuck here. >> >> This macbook supports 64 bit operating system but the UEFI requires 32 bit >> >> that line I entered in the terminal (From the install guide) doesn't work. >> any help is appreciated > >Ignore most of the above: > >There is a CD image that will work here: > >https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-mac-10.9.0-amd64-netinst.iso Sorry, no. That's a good answer for solving awkward problems for *even older* Mac machines, but not this one. The machine that Carl has is similar to the Bay Trail netbooks - it's 64-bit but with crappy firmware that's limited to 32-bit only. Carl: please try the multi-arch netinst from https://cdimage.debian.org/debian-cd/current/multi-arch/iso-cd/debian-10.9.0-amd64-i386-netinst.iso instead. That will start in 32-bit UEFI, then install a 64-bit system with a 32-bit version of Grub etc. You should not need to do anything special for this to work. -- Steve McIntyre, Cambridge, UK.st...@einval.com Into the distance, a ribbon of black Stretched to the point of no turning back
Re: Problem with Macbook 2,1 Installation Instructions
Andy Cater wrote: >On Sat, Apr 17, 2021 at 06:20:19AM -0400, Carl N wrote: >> Can anyone please help me with this installation? >> >> https://wiki.debian.org/InstallingDebianOn/Apple/MacBook/2-1 >> >> the line: >> grub-install --target=i386-efi --efi-directory=/mnt/usb >> --boot-directory=/mnt/usb/boot --bootloader-id=boot --removable >> >> I try this and it says 'doesn't look like an EFI file system" >> >> I'm really stuck here. >> >> This macbook supports 64 bit operating system but the UEFI requires 32 bit >> >> that line I entered in the terminal (From the install guide) doesn't work. >> any help is appreciated > >Ignore most of the above: > >There is a CD image that will work here: > >https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-mac-10.9.0-amd64-netinst.iso Sorry, no. That's a good answer for solving awkward problems for *even older* Mac machines, but not this one. The machine that Carl has is similar to the Bay Trail netbooks - it's 64-bit but with crappy firmware that's limited to 32-bit only. Carl: please try the multi-arch netinst from https://cdimage.debian.org/debian-cd/current/multi-arch/iso-cd/debian-10.9.0-amd64-i386-netinst.iso instead. That will start in 32-bit UEFI, then install a 64-bit system with a 32-bit version of Grub etc. You should not need to do anything special for this to work. -- Steve McIntyre, Cambridge, UK.st...@einval.com "We're the technical experts. We were hired so that management could ignore our recommendations and tell us how to do our jobs." -- Mike Andrews
Re: Problem with Macbook 2,1 Installation Instructions
On Sat, Apr 17, 2021 at 06:20:19AM -0400, Carl N wrote: > Can anyone please help me with this installation? > > https://wiki.debian.org/InstallingDebianOn/Apple/MacBook/2-1 > > the line: > grub-install --target=i386-efi --efi-directory=/mnt/usb > --boot-directory=/mnt/usb/boot --bootloader-id=boot --removable > > I try this and it says 'doesn't look like an EFI file system" > > I'm really stuck here. > > This macbook supports 64 bit operating system but the UEFI requires 32 bit > > that line I entered in the terminal (From the install guide) doesn't work. > any help is appreciated Ignore most of the above: There is a CD image that will work here: https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-mac-10.9.0-amd64-netinst.iso Note: none of the images team has your hardware. Somebody somewhere may have similarly old Mac hardware and had reported successful installs a while ago. There were discussions either here / debian-cd as to whether it was appropriate to continue making this Mac media. All the very best, as ever, Andy C
Problem with Macbook 2,1 Installation Instructions
Can anyone please help me with this installation? https://wiki.debian.org/InstallingDebianOn/Apple/MacBook/2-1 the line: grub-install --target=i386-efi --efi-directory=/mnt/usb --boot-directory=/mnt/usb/boot --bootloader-id=boot --removable I try this and it says 'doesn't look like an EFI file system" I'm really stuck here. This macbook supports 64 bit operating system but the UEFI requires 32 bit that line I entered in the terminal (From the install guide) doesn't work. any help is appreciated
Re: Installation instructions.
From: David Date: Sun, 6 Dec 2020 11:39:20 +1100 > so if he writes "the iso file simply wasn't present" then that > would explain the complaint, case closed. Perhaps. David, the problem is not resolved. Only delayed until a spare HDD is available so that risk of damage to the extant system is avoided. A drive can be obtained when travel restrictions are lifted. Greetings for the New Year,... P. E. -- Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: Installation instructions.
On Sun 06 Dec 2020 at 07:20:38 (-0800), pe...@easthope.ca wrote: > From: David Wright > Date: Fri, 4 Dec 2020 15:12:16 -0600 > > With such a small disk, I'd try modifying that suggestion: dispense > > with /home, but only during the installation, making partition 3 the > > one used for the iso ( and marked "do not use"): > > > > Part 1 labeled ROOT. 7 GB. Format ext4. > > Part 2 labeled SWAP. 1 GB. Format swap or linux-swap. > > Part 3 labeled HOME. 4 GB. Format ext4. (The LABEL doesn't affect > > things.) > > > > When the installation has completed, you can now, as root, > > > > . mount Part 3 as /mnt > > . clear any installation files off it > > . cp -a /home/ /mnt/ (which should be user 1000's ~, > > containing just the files that were copied from /etc/skel) > > . edit /etc/fstab to mount LABEL=HOME on /home > > . umount /mnt/ > > . mount -a (to mount /home) > > . login ordinarily, as sysadmin. > > > > That increases your space on /home by 14%. > > That's similar to the proceedure described in this message. > https://lists.debian.org/debian-user/2020/12/msg00197.html Yes, that's because I based the partitioning on your own https://lists.debian.org/debian-user/2020/12/msg00045.html to which I was going to thread it until David's comment came in. But I posted my reply merely to place this method (using future /home) on record. You'd rather modify the partition table instead, which I've always avoided. Your new partition layout is not one I'd personally use, but then, I don't know what your first two (unused) partitions are going to be used for. (I presume they're not reserved for BIOS Boot and ESP, like the two I always put on my GPT disks.) I haven't created an extended partition since 1997, and eliminated those I'd created or inherited by 1999. Cheers, David.
Re: Installation instructions.
On Sat 05 Dec 2020 at 20:50:44 -0800, pe...@easthope.ca wrote: > The installer then gives the option to search for USB devices. It > gives no evidence of a hdd although it's running from one. (?) In the > snapshot of console 4, the last line reports "devices found: ''". > Meaning "no devices found". > http://easthope.ca/FailedBootVrtConsole4.jpg Please give what you get in an installer console for list-devices disk list-devices partition -- Brian.
Re: Installation instructions.
From: David Wright Date: Fri, 4 Dec 2020 15:12:16 -0600 > With such a small disk, I'd try modifying that suggestion: dispense > with /home, but only during the installation, making partition 3 the > one used for the iso ( and marked "do not use"): > > Part 1 labeled ROOT. 7 GB. Format ext4. > Part 2 labeled SWAP. 1 GB. Format swap or linux-swap. > Part 3 labeled HOME. 4 GB. Format ext4. (The LABEL doesn't affect things.) > > When the installation has completed, you can now, as root, > > . mount Part 3 as /mnt > . clear any installation files off it > . cp -a /home/ /mnt/ (which should be user 1000's ~, > containing just the files that were copied from /etc/skel) > . edit /etc/fstab to mount LABEL=HOME on /home > . umount /mnt/ > . mount -a (to mount /home) > . login ordinarily, as sysadmin. > > That increases your space on /home by 14%. That's similar to the proceedure described in this message. https://lists.debian.org/debian-user/2020/12/msg00197.html Thanks,... P. -- Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: Installation instructions.
From: David Date: Fri, 4 Dec 2020 22:56:41 +1100 > 1) grub needs a partition table on the target device so it can do > embedding, so the target device can't be an entire block device (eg > sdx) it must be a partition[*] (eg sdxN where N is some natural number) > > 2) And you probably need at least N=2 on an older machine. > If there is sufficient RAM, the installer offers to load itself > into RAM which frees up the partition where the iso is, so that it can > be overwritten by the new install. My first step was to plan the partition layout and create it with gparted. ROOT, HOME & INSTLLR were formatted ext4. (hd0,mdos1) unused (hd0,mdos2) unused (hd0,mdos3) ROOT / (hd0,mdos4) extended (hd0,mdos5) SWAP swap (hd0,mdos6) HOME /home (hd0,mdos7) INSTLLR (iso, initrd, vmlinuz) are in INSTLLR. There is no need to overwrite INSTLLR during the installation. INSTLLR can be joined onto /home later. From: David Date: Sun, 6 Dec 2020 07:29:37 +1100 > > Thanks. Well, the iso file simply wasn't present. > > I don't understand this sentence. Do you mean you made a > human error? Or something else? Yes, my human error. I omitted putting the iso in the folder before the last trial run yesterday. > I suggest the use of priority=medium which allows you to > choose which [*]partitions are searched for the iso, which might help. That definitely helps. The installer then gives the option to search for USB devices. It gives no evidence of a hdd although it's running from one. (?) In the snapshot of console 4, the last line reports "devices found: ''". Meaning "no devices found". http://easthope.ca/FailedBootVrtConsole4.jpg Then I put the iso on a SD card in a USB adapter. The installer finds that iso. Ie. boot from (iso, initrd, vmlinuz) in INSTLLR and let the installer search USB devices. The iso in a USB connected device is found. Preliminary conclusion. The installer can be started from (hd0,msdos7) but the iso search fails to acknowledge existence of (hd0) and fails to find the iso in (hd0,msdos7). Does the installer search algorithm work in the msdos extension? Not always. Does it ever work on the extension? Don't know yet. Regards, ... P. -- Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: Installation instructions.
On Sun, 6 Dec 2020 at 11:18, Brian wrote: > On Sun 06 Dec 2020 at 08:07:30 +1100, David wrote: > > On Sun, 6 Dec 2020 at 07:54, Brian wrote: > > > On Sun 06 Dec 2020 at 07:29:37 +1100, David wrote: > > > > On Sun, 6 Dec 2020 at 06:57, wrote: > > > > > > I give their md5sums below so you can check we are using the same > > > > > > files. > > > > > Thanks. Well, the iso file simply wasn't present. > > > > I don't understand this sentence. Do you mean you made a > > > > human error? Or something else? > > > The OP is using an i386 version. We expect you are on amd64. > > Err sorry, I'm still baffled by what is being said here. > Inconsequential, and probably better left unsaid. I hope so :) I'm not arguing with you, just expressing wry amusement at the random hints of information being supplied ... Peter is complaining that he sees ["Failed to find an installer image"] so if he writes "the iso file simply wasn't present" then that would explain the complaint, case closed. Perhaps.
Re: Installation instructions.
On Sun 06 Dec 2020 at 08:07:30 +1100, David wrote: > On Sun, 6 Dec 2020 at 07:54, Brian wrote: > > On Sun 06 Dec 2020 at 07:29:37 +1100, David wrote: > > > On Sun, 6 Dec 2020 at 06:57, wrote: > > > > > > I give their md5sums below so you can check we are using the same > > > > > files. > > > > > Thanks. Well, the iso file simply wasn't present. > > > > I don't understand this sentence. Do you mean you made a > > > human error? Or something else? > > > The OP is using an i386 version. We expect you are on amd64. > > Err sorry, I'm still baffled by what is being said here. It was a data point for those following this thread. I noted the md5sum of the ISO file: As I said: > That's not the problem, of course. Inconsequential, and probably better left unsaid. -- Brian.
Re: Installation instructions.
On Sun, 6 Dec 2020 at 08:35, John Boxall wrote: > On 2020-12-05 4:07 p.m., David wrote: > > I have both i386 and amd64 machines available to test, and I'm > > using i386 when trying to assist Peter. > In your testing have you been able to cleanly boot and run the installer > through to completion, whether i386 or amd64? I have some results from a > buster amd64 VirtualBox guest, but it isn't clean (kernel mismatch), but > the install does progress. I will be testing on bare metal soon-ish. Hi John, Yes these days stable always works for me on actual hardware i386 and amd64. Due to lack of playtime I haven't done much with testing/unstable releases or the testing versions of debian-installer, but that's where I'm headed (if I wasn't too busy with too many projects). With those development suites I guess mismatches between installer/vmlinuz/initrd might be more likely. But stable should work unless there are occasional bugs, it can happen when kernels change. When I first tried this years ago I experienced the same problem as Peter. Which was irritating, because on old hardware, removable media installs can be very slow. I like fast installs, so I wanted to find a better way. My approach now is to create a very flexible setup on each machine, disks these days are so huge that there's plenty of space. I use 4 primary partitions with an msdos partition table. Three of them are 12 GB and the fourth is much bigger consuming the rest of the drive using LUKS and LVM. The 12GB boot partition is big enough to hold the boot files of many different installs regardless if outside or inside the LUKS/LVM, plus however many different installation iso images that I want to play with. I do each install without a separate boot, and then move the boot images to the boot partition and symlink to them. This keeps all the kernels and initrds and installation ISOs on their own partition. Sometimes an initrd from one install can be helpful to use to fix another. Another benefit of this is that the grub of every install can do whatever stupid things it wants to its grub.cfg without corrupting my actual grub.cfg that boots the system, which I manage manually and keep simple without all the overcomplicated default stuff makes the default grub.cfg hard to read. The other two 12GB primary partitions are just throwaway play spaces which are sometimes helpful if convincing the installer to install into LUKS/LVM gets tricky, I can just do it outside and then move it inside afterward if I want to keep it. I also use 'approx' on another machine on my LAN as a repo cache which speeds things up too. All this gives me the ability to easily test these things on actual hardware. I'm not claiming my way is "best" just sharing how I do it and why. So these days I expect hd-media install to work every time. And when it doesn't then I'm curious to understand why. So my interest here is purely academic curiosity to better understand something that I didn't know how to troubleshoot when it was happening to me years ago. I haven't tried VM's for a while but if I did I would use kvm not VirtualBox.
Re: Installation instructions.
On 2020-12-05 4:07 p.m., David wrote: I have both i386 and amd64 machines available to test, and I'm using i386 when trying to assist Peter. David, In your testing have you been able to cleanly boot and run the installer through to completion, whether i386 or amd64? I have some results from a buster amd64 VirtualBox guest, but it isn't clean (kernel mismatch), but the install does progress. I will be testing on bare metal soon-ish. -- Regards, John Boxall
Re: Installation instructions.
On Sun, 6 Dec 2020 at 08:09, wrote:
> Added DebianInstaller FAQ 29.
> https://wiki.debian.org/DebianInstaller/FAQ#Q:_Running_the_installer_from_an_iso_file_on_a_hdd_...
> If someone improves it or a maintainer incorporates the point into the
> official instructions, I won't object.
Thanks for your contribution but one nitpick: I think that linking to
an i386 specific directory ("hd-media"directory) is a bad idea. Most
people aren't using i386. So you might want to reconsider how you've
presented that information, or not be surprised when that link gets
removed by someone.
Re: Installation instructions.
On Sun, 6 Dec 2020 at 06:41, Brian wrote: > On Fri 04 Dec 2020 at 22:56:41 +1100, David wrote: > > 2) And you probably need at least N=2 on an older machine. > > If there is sufficient RAM, the installer offers to load itself > > into RAM which frees up the partition where the iso is, so that it can > > be overwritten by the new install. If the RAM is insufficient this is > > not possible, so the partition where the iso is must be specified > > "do not use" because it is mounted and in use by the installer, so > > the new install must be done into another partition. I would > > deal with this by converting our installer boot partition to a /boot > > partition manually after the install is complete and rebooted > > into the new partition. > I have been using the hd-media installation method with preseeding > at priority-high for many years and never encountered this. It turns > out it was introduced as a consequence of #868900: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868900 > The default for iso-scan/copy_iso_to_ram is false, which is why I > never saw it. Thanks for drawing the option to our attention. > Choosing "true" doesn't suit me because hd-media is then unmounted. > All the files I use during an installation, including the critical > preseed.cfg, then become unavailable. Thanks again for sharing interesting info about different work methods.
Re: Installation instructions.
From: David Date: Fri, 4 Dec 2020 07:20:19 +1100 > The instructions can be modified ... Added DebianInstaller FAQ 29. https://wiki.debian.org/DebianInstaller/FAQ#Q:_Running_the_installer_from_an_iso_file_on_a_hdd_... If someone improves it or a maintainer incorporates the point into the official instructions, I won't object. > ... submit a patch to their maintainer. Editing first hand seems to work better. A few examples. https://en.wikibooks.org/wiki/X86_Assembly https://en.wikibooks.org/wiki/X86_Disassembly https://en.wikibooks.org/wiki/Shelf:Computer_software Regards,... P. -- Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: Installation instructions.
On Sun, 6 Dec 2020 at 07:54, Brian wrote: > On Sun 06 Dec 2020 at 07:29:37 +1100, David wrote: > > On Sun, 6 Dec 2020 at 06:57, wrote: > > > > I give their md5sums below so you can check we are using the same > > > > files. > > > Thanks. Well, the iso file simply wasn't present. > > I don't understand this sentence. Do you mean you made a > > human error? Or something else? > The OP is using an i386 version. We expect you are on amd64. Err sorry, I'm still baffled by what is being said here. I have both i386 and amd64 machines available to test, and I'm using i386 when trying to assist Peter. On Fri, 4 Dec 2020 at 20:00, David wrote: > I give their md5sums below so you can check we are using the same > files. > $ md5sum *iso > f327723426dc90a4daaf1609595d8306 debian-10.6.0-i386-netinst.iso It's the md5sum of an i386 iso file. What's that got to do with "you are on amd64"? Sorry if I'm being dense, it's early morning is my excuse for today :)
Re: Installation instructions.
On Sun 06 Dec 2020 at 07:29:37 +1100, David wrote: > On Sun, 6 Dec 2020 at 06:57, wrote: > > > > I give their md5sums below so you can check we are using the same > > > files. > > > > Thanks. Well, the iso file simply wasn't present. > > I don't understand this sentence. Do you mean you made a > human error? Or something else? The OP is using an i386 version. We expect you are on amd64. That's not the problem, of course. -- Brian.
Re: Installation instructions.
On Sun, 6 Dec 2020 at 06:57, wrote: > > I give their md5sums below so you can check we are using the same > > files. > > Thanks. Well, the iso file simply wasn't present. I don't understand this sentence. Do you mean you made a human error? Or something else? > Files match but the search still failed. Please report the results of a manual search in the installer as I suggested previously here: On Fri, 4 Dec 2020 at 22:56, David wrote: > I suggest the use of priority=medium which allows you to > choose which [*]partitions are searched for the iso, which might help. See the rest of that message for more details. Please report what *partitions* you see offered in the menu, and what happens when you try them, and the logfile after doing all of that.
Re: Installation instructions.
On Sat 05 Dec 2020 at 11:19:17 -0800, pe...@easthope.ca wrote: > http://easthope.ca/FailedBootVrtConsole4.jpg > > Apologies for the snapshot but it serves the purpose. It doesn't serve any purpose. It is completely useless. -- Brian.
Re: Installation instructions.
> I give their md5sums below so you can check we are using the same
> files.
Thanks. Well, the iso file simply wasn't present. Now I have this.
root@joule:/mnt# md5sum !$
md5sum {d*,i*,v*}
f327723426dc90a4daaf1609595d8306 debian-10.6.0-i386-netinst.iso
d3f41e1b683fa87cca189f8595b80a7c initrd.gz
b30966bc534a606bb8dafab40e106ca9 vmlinuz
> $ md5sum *iso
> f327723426dc90a4daaf1609595d8306 debian-10.6.0-i386-netinst.iso
> $ md5sum *
> d3f41e1b683fa87cca189f8595b80a7c initrd.gz
> b30966bc534a606bb8dafab40e106ca9 vmlinuz
Files match but the search still failed.
> I suggest to check the installer log just after the search fails.
> The method of doing that is here:
> https://www.debian.org/releases/stable/i386/ch06s03.en.html#di-miscellaneous
http://easthope.ca/FailedBootVrtConsole4.jpg
Apologies for the snapshot but it serves the purpose.
To me, the most relevant notes are "missing firmware" and "devices found: ''".
An old magnetic HDD should be detected by a driver without fancy firmware.
That leaves "devices found: ''" while files are in (hd0,msdos7). Does
the search algorithm work for an extended part? Ref.
https://en.wikipedia.org/wiki/Disk_partitioning#Extended_partition
Depending on replies, I might try the files in (hd1,1).
Thx, ... P.
--
Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: Installation instructions.
On Fri 04 Dec 2020 at 22:56:41 +1100, David wrote:
> 2) And you probably need at least N=2 on an older machine.
> If there is sufficient RAM, the installer offers to load itself
> into RAM which frees up the partition where the iso is, so that it can
> be overwritten by the new install. If the RAM is insufficient this is
> not possible, so the partition where the iso is must be specified
> "do not use" because it is mounted and in use by the installer, so
> the new install must be done into another partition. I would
> deal with this by converting our installer boot partition to a /boot
> partition manually after the install is complete and rebooted
> into the new partition.
I have been using the hd-media installation method with preseeding
at priority-high for many years and never encountered this. It turns
out it was introduced as a consequence of #868900:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868900
The default for iso-scan/copy_iso_to_ram is false, which is why I
never saw it. Thanks for drawing the option to our attention.
Choosing "true" doesn't suit me because hd-media is then unmounted.
All the files I use during an installation, including the critical
preseed.cfg, then become unavailable.
> 3) The grub.cfg I used was
>
> menuentry 'Debian Installer' {
> insmod part_msdos
> insmod ext4
> set root='(hd0,msdos1)'
> linux /vmlinuz priority=medium
> initrd /initrd.gz
> }
My grub.cfg is
menuentry 'Debian Installer' {
linux /boot/vmlinuz priority=medium
initrd /boot/initrd.gz
}
I think this would make "set root='(hd0,msdos1)'" superfluous. I wonder
whether the other two directives are defaults for GRUB?
--
Brian.
Re: Installation instructions.
On Fri 04 Dec 2020 at 22:56:41 +1100, David wrote:
> On Fri, 4 Dec 2020 at 20:00, David wrote:
>
> > Looking now, I can confirm that I did a Debian installation here on 20
> > Oct 2020 using these files. There is no doubt because they are still
> > on the hard drive.
>
> Actually it was 14 Oct, just for the record :)
>
> I have just now done another fresh install, this time using the same 3 files
> on a blank hard drive, it worked to completion without your complaint
> occurring.
>
> Due to actually going through the entire procedure on a blank drive
> so as to catch any unanticipated hiccups due to the process being
> different to my usual one, I can add some more thoughts about that:
>
> 1) grub needs a partition table on the target device so it can do
> embedding, so the target device can't be an entire block device (eg
> sdx) it must be a partition[*] (eg sdxN where N is some natural number)
Indeed.
> 2) And you probably need at least N=2 on an older machine.
> If there is sufficient RAM, the installer offers to load itself
> into RAM which frees up the partition where the iso is, so that it can
> be overwritten by the new install. If the RAM is insufficient this is
> not possible, so the partition where the iso is must be specified
> "do not use" because it is mounted and in use by the installer, so
> the new install must be done into another partition. I would
> deal with this by converting our installer boot partition to a /boot
> partition manually after the install is complete and rebooted
> into the new partition.
Suppose vmlinuz, initrd.gz, grub.cfg and the ISO are on a USB stick. The
stick can be booted and the installation done to a hard drive, which I
would guess is common place to put it. This avoids having to consider
the memory situation or mess with the installation afterwards.
Those users who cannot boot from a USB stick can have vmlinuz, initrd.gz
and grub.cfg on the hard disk and the ISO on a USB stick, where it should
found.
--
Brian.
>
> 3) The grub.cfg I used was
>
> menuentry 'Debian Installer' {
> insmod part_msdos
> insmod ext4
> set root='(hd0,msdos1)'
> linux /vmlinuz priority=medium
> initrd /initrd.gz
> }
>
> I suggest the use of priority=medium which allows you to
> choose which [*]partitions are searched for the iso, which might help.
> Once the problem is resolved you can remove that or
> change it to what you prefer: low or high (which eg specifies
> that only a few high priority questions are asked during install).
>
Re: Installation instructions.
On Sat 05 Dec 2020 at 09:34:14 (+1100), David wrote: > On Sat, 5 Dec 2020 at 08:12, David Wright wrote: > > > With such a small disk, I'd try modifying that suggestion: > > Thanks for adding that, my attention was focussed on just > getting the installer working in a minimal way and I completely > forgot to adapt my instructions to fit Peter's desired partition layout. No, you followed Peter all right. I was going to make my suggestion to one of his posts, but was still checking my notes from when I played around with this type of installation process. That was with jessie (for which I never burnt a CD) on my Pentium III, which doesn't know how to boot from a stick. I was also reviewing his posts to see whether he'd earlier expressed a need for a separate /boot partition (I believe not). I always leave my (encrypted) /home partition out of any new installation, because any interference with the LUKS header could be terminal. So all my systems have an occluded home directory of three files, hidden under the /home mountpoint. Cheers, David.
Re: Installation instructions.
On Sat, 5 Dec 2020 at 08:12, David Wright wrote: > With such a small disk, I'd try modifying that suggestion: Thanks for adding that, my attention was focussed on just getting the installer working in a minimal way and I completely forgot to adapt my instructions to fit Peter's desired partition layout.
Re: Installation instructions.
On Fri 04 Dec 2020 at 22:56:41 (+1100), David wrote:
> On Fri, 4 Dec 2020 at 20:00, David wrote:
> > On Fri, 4 Dec 2020 at 03:39, wrote:
>
> > > > David, the current procedure is simple enough. Have you or anyone you
> > > > trust run the procedure with the specific three (iso, vmlinuz,
> > > > initrd.gz) files you cited?
>
> > > Yes ...
>
> > Looking now, I can confirm that I did a Debian installation here on 20
> > Oct 2020 using these files. There is no doubt because they are still
> > on the hard drive.
>
> Actually it was 14 Oct, just for the record :)
>
> I have just now done another fresh install, this time using the same 3 files
> on a blank hard drive, it worked to completion without your complaint
> occurring.
>
> Due to actually going through the entire procedure on a blank drive
> so as to catch any unanticipated hiccups due to the process being
> different to my usual one, I can add some more thoughts about that:
>
> 1) grub needs a partition table on the target device so it can do
> embedding, so the target device can't be an entire block device (eg
> sdx) it must be a partition[*] (eg sdxN where N is some natural number)
>
> 2) And you probably need at least N=2 on an older machine.
> If there is sufficient RAM, the installer offers to load itself
> into RAM which frees up the partition where the iso is, so that it can
> be overwritten by the new install. If the RAM is insufficient this is
> not possible, so the partition where the iso is must be specified
> "do not use" because it is mounted and in use by the installer, so
> the new install must be done into another partition. I would
> deal with this by converting our installer boot partition to a /boot
> partition manually after the install is complete and rebooted
> into the new partition.
With such a small disk, I'd try modifying that suggestion: dispense
with /home, but only during the installation, making partition 3 the
one used for the iso ( and marked "do not use"):
Part 1 labeled ROOT. 7 GB. Format ext4.
Part 2 labeled SWAP. 1 GB. Format swap or linux-swap.
Part 3 labeled HOME. 4 GB. Format ext4. (The LABEL doesn't affect things.)
When the installation has completed, you can now, as root,
. mount Part 3 as /mnt
. clear any installation files off it
. cp -a /home/ /mnt/ (which should be user 1000's ~,
containing just the files that were copied from /etc/skel)
. edit /etc/fstab to mount LABEL=HOME on /home
. umount /mnt/
. mount -a (to mount /home)
. login ordinarily, as sysadmin.
That increases your space on /home by 14%.
> 3) The grub.cfg I used was
>
> menuentry 'Debian Installer' {
> insmod part_msdos
> insmod ext4
> set root='(hd0,msdos1)'
> linux /vmlinuz priority=medium
> initrd /initrd.gz
> }
>
> I suggest the use of priority=medium which allows you to
> choose which [*]partitions are searched for the iso, which might help.
> Once the problem is resolved you can remove that or
> change it to what you prefer: low or high (which eg specifies
> that only a few high priority questions are asked during install).
… and low gives you expert installation.
Cheers,
David.
Re: Installation instructions.
On Fri, 4 Dec 2020 at 20:00, David wrote:
> On Fri, 4 Dec 2020 at 03:39, wrote:
> > > David, the current procedure is simple enough. Have you or anyone you
> > > trust run the procedure with the specific three (iso, vmlinuz,
> > > initrd.gz) files you cited?
> > Yes ...
> Looking now, I can confirm that I did a Debian installation here on 20
> Oct 2020 using these files. There is no doubt because they are still
> on the hard drive.
Actually it was 14 Oct, just for the record :)
I have just now done another fresh install, this time using the same 3 files
on a blank hard drive, it worked to completion without your complaint
occurring.
Due to actually going through the entire procedure on a blank drive
so as to catch any unanticipated hiccups due to the process being
different to my usual one, I can add some more thoughts about that:
1) grub needs a partition table on the target device so it can do
embedding, so the target device can't be an entire block device (eg
sdx) it must be a partition[*] (eg sdxN where N is some natural number)
2) And you probably need at least N=2 on an older machine.
If there is sufficient RAM, the installer offers to load itself
into RAM which frees up the partition where the iso is, so that it can
be overwritten by the new install. If the RAM is insufficient this is
not possible, so the partition where the iso is must be specified
"do not use" because it is mounted and in use by the installer, so
the new install must be done into another partition. I would
deal with this by converting our installer boot partition to a /boot
partition manually after the install is complete and rebooted
into the new partition.
3) The grub.cfg I used was
menuentry 'Debian Installer' {
insmod part_msdos
insmod ext4
set root='(hd0,msdos1)'
linux /vmlinuz priority=medium
initrd /initrd.gz
}
I suggest the use of priority=medium which allows you to
choose which [*]partitions are searched for the iso, which might help.
Once the problem is resolved you can remove that or
change it to what you prefer: low or high (which eg specifies
that only a few high priority questions are asked during install).
Re: Installation instructions.
On Fri, 4 Dec 2020 at 03:39, wrote: > > David, the current procedure is simple enough. Have you or anyone you > > trust run the procedure with the specific three (iso, vmlinuz, > > initrd.gz) files you cited? > > Yes ... Looking now, I can confirm that I did a Debian installation here on 20 Oct 2020 using these files. There is no doubt because they are still on the hard drive. I give their md5sums below so you can check we are using the same files. On Thu, 3 Dec 2020 at 09:27, David wrote: > The starting point is that you have chosen > https://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-10.6.0-i386-netinst.iso > (current, stable, i386) $ md5sum *iso f327723426dc90a4daaf1609595d8306 debian-10.6.0-i386-netinst.iso > Per the "paragraph 3" I mentioned previously and quoted at the top > of this message, the required vmlinuz and initrd.gz for (current, stable, > i386) > can be downloaded from: > http://ftp.debian.org/debian/dists/stable/main/installer-i386/current/images/hd-media/ $ md5sum * d3f41e1b683fa87cca189f8595b80a7c initrd.gz b30966bc534a606bb8dafab40e106ca9 vmlinuz What next? I suggest to check the installer log just after the search fails. The method of doing that is here: https://www.debian.org/releases/stable/i386/ch06s03.en.html#di-miscellaneous I think the logs are usually scrolling into virtual console 4, or you could start a shell on virtual console 2 and look for them. in the /var/log directory. See if you can find any error messages from the 'iso-scan' process in the file /var/log/syslog. The installer main menu offers a method of saving the log files if you want to paste anything you find here.
Re: Installation instructions.
On Fri, 4 Dec 2020 at 10:05, Brian wrote: > On Fri 04 Dec 2020 at 07:20:19 +1100, David wrote: > > I think this is an area that possibly needs some investigation or > > improvement. I would like to know how this ISO search is being done > > and what is the reason for the failure (and why can't I just specify > > the ISO I want to use, no compulsory search!). However I've not spent > > Preseeding paramters on the linux line may be used to specify where the > ISO resides: > > shared/ask_device=manual > shared/enter_device=/dev/disk/by-label/ Great tip, thank you! That will give me the ability to find out what kind of errors occur when I deliberately specify the wrong one, I might learn something useful from that exercise. > The response from the OP was > > > vmlinuz and initrd.gz are in the .iso. No need to retrieve again. > > This will almost certainly lead to a failure to discover and mount the > ISO. BootFromISOinHD.jpg (provided by the OP) provides confirmation of > this assertion. Yep, knew that for sure. And thanks for your previous tip about looking for the loop module in the initrd, that was educational for me and I have put that on my list of interesting things to look into. It's a long list :D
Re: Installation instructions.
On Fri 04 Dec 2020 at 07:20:19 +1100, David wrote: [...] > I think this is an area that possibly needs some investigation or > improvement. I would like to know how this ISO search is being done > and what is the reason for the failure (and why can't I just specify > the ISO I want to use, no compulsory search!). However I've not spent Preseeding paramters on the linux line may be used to specify where the ISO resides: shared/ask_device=manual shared/enter_device=/dev/disk/by-label/ [...] > That's why I asked exactly which files you are using. It's good that You certainly did ask that earlier: > 2) Given that choice (para 2 or 3), where did you get the vmlinuz and > initrd.gz you are using? The response from the OP was > vmlinuz and initrd.gz are in the .iso. No need to retrieve again. This will almost certainly lead to a failure to discover and mount the ISO. BootFromISOinHD.jpg (provided by the OP) provides confirmation of this assertion. -- Brian.
Re: Installation instructions.
Hi Peter, Replies below ... On Fri, 4 Dec 2020 at 03:39, wrote: > From: David Date: Thu, 3 Dec 2020 09:27:45 +1100 > > These are different to the ones inside the iso ... > Thanks. My assumption of no difference was/is lethal. Any chance of > mentioning the distinction in the instructions? The instructions can be modified by anyone who is sufficiently motivated to submit a patch to their maintainer. That's how this project works, it's not a "we will hold everyone's hand" project. That's one reason why there are dozens of distributions that are "based on Debian". I understand Debian more as, "if you make an effort to contribute in a meaningful and compatible way, we will work with you". > (For interest. > An .iso image could be booted from a HDD by 2010 at least. > https://antixlinux.com/forum-archive/problems-with-boot-from-iso-on-hard-disk-t2683.html > > In that method, the vmlinuz and initrd.gz inside the .iso were used. > > Kernel parameters "from", "fromhd" and "fromiso" existed back then. > Examples are in AntiX pages including that cited above. The from > parameters are no longer listed. > https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html ) Those might never have been kernel parameters, but rather parameters that the kernel passed to the installer init process. > > That should work, let us know if it doesn't. > > http://easthope.ca/BootFromISOinHD.jpg ["Failed to find an installer image"] Sorry to see that :( But I have seen this occur from time to time without understanding exactly why it happens. > David, the current procedure is simple enough. Have you or anyone you > trust run the procedure with the specific three (iso, vmlinuz, > initrd.gz) files you cited? Yes ... On Wed, 2 Dec 2020 at 13:11, David wrote: > In my recent experience (using para 3 method), the installer searches the > local hard drives for files that it recognises. And this search can > fail to succeed if I haven't done the proper dance first. The vmlinuz > and initrd must match the iso. I use the hd-media method for pretty much every install that I do, I never use removable media. I do quite a lot of installs for a home user. I have about half a dozen machines and they all have between 4 and 8 working installs (multiboot hdd) at any one time. I don't begin with a blank drive so I skip the grub steps. I just put the 3 required files into my unencrypted boot partition (it's big enough to hold plenty of them), and I use them to install, mostly into a new LVM volume on the rest of the HDD which is encrypted using LUKS. Years back when I had less knowledge about all things, I occasionally would try a hd-media install and *not unusually* see these "Failed to find an installer image" messages and suspect that there was some bug and give up. But maybe the problem was my lack of knowledge at that time, combined with the many ways to get this wrong. I think this is an area that possibly needs some investigation or improvement. I would like to know how this ISO search is being done and what is the reason for the failure (and why can't I just specify the ISO I want to use, no compulsory search!). However I've not spent any time attempting to understand or debug or even find and read the installer code. The installer programming environment is an unfamiliar and complicated situation for me to explore. Once I realised that it had something to do with matching everything up I had fewer failures. "Matching everything up" becomes more of a challenge when working with the wide range of "official" and "unofficial" (containing non-free firmware) ISO images, and working with "unstable" or "testing" suites, different kernel versions, and perhaps using under-development versions of the installer as well. I have seen this failure recently during something more exotic than a "stable" install, I don't recall the details. I tried again (because these days this has become my standard procedure and I expect it to work) with a different hd-media and it worked. That's why I asked exactly which files you are using. It's good that everything is from "official" and "stable", and I have sufficient passing interest to investigate further and I'm happy to test with the same files that you are using. I can't do it immediately because there are some practical complications: to duplicate here what you are doing exactly requires a 32bit machine plus a spare hard drive. My 32bit machines require 2.5" or 3.5" PATA drives. I know I have a spare 2.5" PATA drive but connecting it to my 3.5" host system requires opening up the case and finding adapters, blah blah. I have other commitments and priorities but I probably can do it sometime over the weekend if needed.
Re: Installation instructions.
On Thu 03 Dec 2020 at 08:22:52 -0800, pe...@easthope.ca wrote: > From: David > Date: Thu, 3 Dec 2020 09:27:45 +1100 > > Per the "paragraph 3" I mentioned previously and quoted at the top > > of this message, the required vmlinuz and initrd.gz for (current, stable, > > i386) > > can be downloaded from: > > http://ftp.debian.org/debian/dists/stable/main/installer-i386/current/images/hd-media/ > > OK, got them. > > > These are different to the ones inside the iso ... > > Thanks. My assumption of no difference was/is lethal. Any chance of > mentioning the distinction in the instructions? Users make all sorts of assumptions. Do they all require catering for? But you can try a wishlist bug against the Installation Guide. > (For interest. > An .iso image could be booted from a HDD by 2010 at least. > https://antixlinux.com/forum-archive/problems-with-boot-from-iso-on-hard-disk-t2683.html > > In that method, the vmlinuz and initrd.gz inside the .iso were used. A red herring in the context of your initial inquiry. Nothing to do with Debian. And its from 2010! > > Kernel parameters "from", "fromhd" and "fromiso" existed back then. > Examples are in AntiX pages including that cited above. The from > parameters are no longer listed. > https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html ) Another red herring. > > ... no need to use gparted beforehand although that could work ... > > I understand but find gparted easier to use. > > > That should work, let us know if it doesn't. > > http://easthope.ca/BootFromISOinHD.jpg > > David, the current procedure is simple enough. Have you or anyone you > trust run the procedure with the specific three (iso, vmlinuz, > initrd.gz) files you cited? Yes. I trust me! -- Brian.
Re: Installation instructions.
From: David Date: Thu, 3 Dec 2020 09:27:45 +1100 > Per the "paragraph 3" I mentioned previously and quoted at the top > of this message, the required vmlinuz and initrd.gz for (current, stable, > i386) > can be downloaded from: > http://ftp.debian.org/debian/dists/stable/main/installer-i386/current/images/hd-media/ OK, got them. > These are different to the ones inside the iso ... Thanks. My assumption of no difference was/is lethal. Any chance of mentioning the distinction in the instructions? (For interest. An .iso image could be booted from a HDD by 2010 at least. https://antixlinux.com/forum-archive/problems-with-boot-from-iso-on-hard-disk-t2683.html In that method, the vmlinuz and initrd.gz inside the .iso were used. Kernel parameters "from", "fromhd" and "fromiso" existed back then. Examples are in AntiX pages including that cited above. The from parameters are no longer listed. https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html ) > ... no need to use gparted beforehand although that could work ... I understand but find gparted easier to use. > That should work, let us know if it doesn't. http://easthope.ca/BootFromISOinHD.jpg David, the current procedure is simple enough. Have you or anyone you trust run the procedure with the specific three (iso, vmlinuz, initrd.gz) files you cited? Thx,... P. -- Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: Installation instructions.
On Mi, 02 dec 20, 12:10:33, pe...@easthope.ca wrote: > > > https://www.debian.org/releases/stable/i386/ch05s01.en.html#boot-initrd > > > > Quoting paragraphs 2 and 3 from your link above ... > > > > Alternatively, if you intend to keep an existing partition on the hard > > drive unchanged during the install, you can download the > > hd-media/initrd.gz file and its kernel, as well as copy a CD (or DVD) > > iso to the drive (make sure the file is named ending in .iso). The > > installer can then boot from the drive and install from the CD/DVD > > image, without needing the network. > > > 1) Which of the above are you attempting? Paragraph 2 or paragraph 3? > > 3. > > > Please describe what is on the hard drive before the installation, ... > > Before the installation, the HDD can have any information at all. It > can be new, fresh from the factory. It can be an old drive with a > bootable MS Windows system. Any information be overwritten or > dereferenced by steps below. Write one of these images to the hard disk (cp, dd, etc.), boot and install. http://ftp.nl.debian.org/debian/dists/buster/main/installer-amd64/current/images/netboot/mini.iso http://ftp.nl.debian.org/debian/dists/buster/main/installer-amd64/current/images/netboot/gtk/mini.iso (note the 'gtk' in the path for the second image) As far as I recall (it's been a while) these particular images (are the only ones that) can be used to install Debian to the block device used for booting. It may be that this is not documented anywhere except in some blog post of Joey Hess when he made this particular change. > > 2) Given that choice (para 2 or 3), where did you get the vmlinuz and > > initrd.gz you are using? > > vmlinuz and initrd.gz are in the .iso. No need to retrieve again. You are assuming all of the vmlinuz and initrd.gz files are identical, but there is a reason for the guide to point to specific files. In case this is not clear please do suggest wording improvements, e.g. via a bug of apropiate severity against 'installation-guide'. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Re (2): Installation instructions.
On Wed 02 Dec 2020 at 13:19:39 -0800, pe...@easthope.ca wrote: > From: Brian > Date: Wed, 2 Dec 2020 18:51:38 + > > As David asks - where are vmlinuz and initrd.gz from? And what CD (?) > > image is being used? > > Answered in my reply to David here. > https://lists.debian.org/debian-user/2020/12/msg00045.html > > If David finds an error in my procedure or insists that it works for > him, I'll go through it again. David will go for the first option. The initrd from the iso does not contain a loop module. The hd-media's initrd does. -- Brian.
Re: Installation instructions.
On Thu, 3 Dec 2020 at 07:54, wrote:
> > > https://www.debian.org/releases/stable/i386/ch05s01.en.html#boot-initrd
> > Quoting paragraphs 2 and 3 from your link above ...
> > Alternatively, if you intend to keep an existing partition on the hard
> > drive unchanged during the install, you can download the
> > hd-media/initrd.gz file and its kernel, as well as copy a CD (or DVD)
> > iso to the drive (make sure the file is named ending in .iso). The
> > installer can then boot from the drive and install from the CD/DVD
> > image, without needing the network.
> > 1) Which of the above are you attempting? Paragraph 2 or paragraph 3?
> 3.
Ok great. Thanks for putting a decent effort into your reply, it helps greatly
to know better the situation we are responding to :)
Looking at your method, it looks quite misguided and over complicated,
perhaps you are working from obsolete information sources. The current
method is much easier.
The starting point is that you have chosen
https://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-10.6.0-i386-netinst.iso
(current, stable, i386)
Per the "paragraph 3" I mentioned previously and quoted at the top
of this message, the required vmlinuz and initrd.gz for (current, stable, i386)
can be downloaded from:
http://ftp.debian.org/debian/dists/stable/main/installer-i386/current/images/hd-media/
These are different to the ones inside the iso (because those don't
support the installation method that you have chosen).
Now we have obtained the 3 files required for installation, we can
next prepare the target HDD on your workstation. The only necessary
steps are to make the target HDD bootable with at least one ext4
partition containing our 3 files. Let's name that parition INSTLR as
you did. Next do these steps ...
> Mount INSTLR at /mnt/.
> mount /dev/sdx4 /mnt/ # x represents the actual drive letter. Eg.
> "c".
> Make a grub directory.
> mkdir /mnt/grub
> Install grub on the target HDD.
> grub-install --boot-directory=/mnt/ /dev/sdx
> open /mnt/grub/grub.cfg with an editor. If the following stanza is
> not present, add it. Note that we have the files at /, not at
> /boot/newinstall/ as the example.
> menuentry 'CDless CD install' {
> insmod part_msdos
> insmod ext2
> set root='(hd0,msdos1)'
> linux /vmlinuz
> initrd /initrd.gz
> }
Next copy our 3 files from above (vmlinuz, intird.gz, and iso)
to the target HDD.
cp /mnt
Now put the target HDD into the target machine, boot it, and run the
installer. It can do the rest of the partitioning you want, there's no
need to use gparted beforehand although that could work as an
alternative method, it's not required.
That should work, let us know if it doesn't.
Re: Installation instructions.
On 2020-12-01 5:50 p.m., pe...@easthope.ca wrote:
but the CD image is not found.
Peter,
Can you please confirm if you are/are not trying to boot the ISO image
from a USB stick?
If you _are_ you are may be running into the same head-banging situation
I was having the past week. It was a combination of flakey motherboard
BIOS configuration and one kernel commandline parameter ("iommu=soft")
that needed to be specified to deal with the flakey m/b.
Until I configured the m/b to process Legacy first (before UEFI),
disabled IOMMU, selected the UEFI instance of the USB stick and
specified the above kernel parameter by editing the GRUB configuration,
I could not get _two_ different Gigabyte motherboards to find the USB
stick as a CDROM. On one of them I had to go into the BIOS to explicitly
specify "USB Mass Storage" as "CDROM", in addition to the above. Both
m/b's are using an AMI BIOS.
--
Regards,
John Boxall
Re (2): Installation instructions.
From: Brian Date: Wed, 2 Dec 2020 18:51:38 + > As David asks - where are vmlinuz and initrd.gz from? And what CD (?) > image is being used? Answered in my reply to David here. https://lists.debian.org/debian-user/2020/12/msg00045.html If David finds an error in my procedure or insists that it works for him, I'll go through it again. Regards, ... P. -- Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: Installation instructions.
On Wed 02 Dec 2020 at 12:10:33 -0800, pe...@easthope.ca wrote: > > 2) Given that choice (para 2 or 3), where did you get the vmlinuz and > > initrd.gz you are using? > > vmlinuz and initrd.gz are in the .iso. No need to retrieve again. You have a complete misunderstanding of what you are doing. The vmlinuz and initrd.gz in the .iso will not enable you to boot using the hd-media technique. -- Brian
Re: Installation instructions.
> > https://www.debian.org/releases/stable/i386/ch05s01.en.html#boot-initrd
>
> Quoting paragraphs 2 and 3 from your link above ...
>
> Alternatively, if you intend to keep an existing partition on the hard
> drive unchanged during the install, you can download the
> hd-media/initrd.gz file and its kernel, as well as copy a CD (or DVD)
> iso to the drive (make sure the file is named ending in .iso). The
> installer can then boot from the drive and install from the CD/DVD
> image, without needing the network.
> 1) Which of the above are you attempting? Paragraph 2 or paragraph 3?
3.
> Please describe what is on the hard drive before the installation, ...
Before the installation, the HDD can have any information at all. It
can be new, fresh from the factory. It can be an old drive with a
bootable MS Windows system. Any information be overwritten or
dereferenced by steps below.
> ... and what you want to be there after.
After the installation the drive should have Debian 10 system from
which the target machine can boot and work.
Required ingredients.
* Debian workstation with network connection. (In fact any Linux or Unix
should work. A few details below may vary.)
* Target machine with hardware allowing a network connection.
* HDD which will work in the target machine when this process is
complete.
This procedure is performed. Most steps require root priviledge. On
the workstation use su or sudo.
The system is to be installed on a "target HDD". Connect the target
HDD to a Debian workstation using a ATA cable or USB-ATA adapter. To
my understanding the machine should be unpowered when ATA is connected
or disconnected. USB can be hot-plugged.
Using gparted in the workstation, make these four parts on the target
HDD.
Part 1 labeled ROOT. 7 GB. Format ext4.
Part 2 labeled SWAP. 1 GB. Format swap or linux-swap.
Part 3 labeled HOME. 3.5 GB. Format ext4.
Part 4 labeled INSTLR. 520 MB. Format ext4.
Mount INSTLR at /mnt/.
mount /dev/sdx4 /mnt/ # x represents the actual drive letter. Eg.
"c".
Make a grub directory.
mkdir /mnt/grub
Install grub on the target HDD.
grub-install --boot-directory=/mnt/ /dev/sdx
Ref. 5.1.5. Booting from Linux using LILO or GRUB
https://www.debian.org/releases/stable/i386/ch05s01.en.html#boot-initrd
Note the GRUB2 example stanza.
open /mnt/grub/grub.cfg with an editor. If the following stanza is
not present, add it. Note that we have the files at /, not at
/boot/newinstall/ as the example.
menuentry 'CDless CD install' {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
linux /vmlinuz
initrd /initrd.gz
}
> 3) Which CD image are you using?
https://cdimage.debian.org/debian-cd/current/i386/iso-cd/debian-10.6.0-i386-netinst.iso
(I'd be happy to retrieve the image from a local server,
http://mirror.it.ubc.ca/debian/dists, but did not find it there.)
Put that .iso file in /mnt/
> 2) Given that choice (para 2 or 3), where did you get the vmlinuz and
> initrd.gz you are using?
vmlinuz and initrd.gz are in the .iso. No need to retrieve again.
mkdir /loop
mount -t iso9660 -o loop,ro /mnt/debian-10.6.0-i386-netinst.iso /loop
cp /loop/initrd.gz /mnt/
cp /loop/vmlinuz /mnt/
Verify that INSTLR is organized.
ls /mnt
debian-10.6.0-i386-netinst.iso grub initrd.gz lost+found vmlinuz
Good.
umount /mnt
Disconnect the HDD from the workstation and connect it to the target
machine. Connect, keyboard, monitor, mouse and power cord. Turn on
power. The GRUB2 menu should appear. The title of the GRUB2 stanza
above should appear. "CDless CD install" Scroll to that and press
the key.
vmlinuz should load and execute. Then the initrd.gz.
If there is a complaint about low memory, go to and "Execute
a shell". The swap part can be verified with "blkid /dev/sdy". Note
that y # x, x mentioned above. If the machine has only one HDD, y = "a".
Execute "swapon /dev/sdy". Eg. "swapon /dev/sda". Exit the shell and
continue the installation process.
After setting location and language the installer will search for the
CD. Ideally the .iso image should be found as you suggested. Here
this message appears.
"No common CD-ROM dirve was detected. ..."
No obvious way to proceed.
Regards,... P.
--
Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: Installation instructions.
On Tue 01 Dec 2020 at 14:50:52 -0800, pe...@easthope.ca wrote:
> https://www.debian.org/releases/stable/i386/ch05s01.en.html#boot-initrd
> gives this sample Grub2 configuration.
>
> menuentry 'New Install' {
> insmod part_msdos
> insmod ext2
> set root='(hd0,msdos1)'
> linux /boot/newinstall/vmlinuz
> initrd /boot/newinstall/initrd.gz
> }
>
> No problem with vmlinuz and initrd.gz but the CD image is not found.
As David asks - where are vmlinuz and initrd.gz from? And what CD (?)
image is being used?
> The configuration which worked in the past had parameters on the linux
> command. Similar to this.
>
> linux /vmlinuz root=UUID=50e0fa4b-6c62-40f8-8a84-46ab1413eb5a ro from=hd
> fromiso=debian-10.6.0-i386-netinst.iso load=all reboot=bios
I think you are misremembering something? If that is incorrect, you are
applying something to an inappropriate situation.
> The instructions at the URL above appear incomplete. Does anyone
> happen to know how the ISO should be accessed? Loop mount at
> /dev/cdrom?
The instructions are complete. Loop mount? No!
--
Brian.
Re: Installation instructions.
On Wed, 2 Dec 2020 at 10:06, wrote: > Installation instructions. > the CD image is not found. Please describe at exactly what point in your attempt you reached this conclusion. What screen messages did you see exactly? Due to the flexibility of Debian installation there are so many possible scenarios that to write a comprehensive reply would be time consuming for us and probably lack clarity for you (eg the existing documentation). If you provide more information (requested below) to exactly describe your situation, someone might be able to offer custom suggestions or even a tested solution ... > https://www.debian.org/releases/stable/i386/ch05s01.en.html#boot-initrd Quoting paragraphs 2 and 3 from your link above ... """ If you intend to use the hard drive only for booting and then download everything over the network, you should download the netboot/debian-installer/i386/initrd.gz file and its corresponding kernel netboot/debian-installer/i386/linux. This will allow you to repartition the hard disk from which you boot the installer, although you should do so with care. Alternatively, if you intend to keep an existing partition on the hard drive unchanged during the install, you can download the hd-media/initrd.gz file and its kernel, as well as copy a CD (or DVD) iso to the drive (make sure the file is named ending in .iso). The installer can then boot from the drive and install from the CD/DVD image, without needing the network. """ So: 1) Which of the above are you attempting? Paragraph 2 or paragraph 3? Please describe what is on the hard drive before the installation, and what you want to be there after. 2) Given that choice (para 2 or 3), where did you get the vmlinuz and initrd.gz you are using? Please provide a full URL to them so we can reproduce your situation. 3) Which CD image are you using? Please provide a full URL to it so we can reproduce your situation. 4) The instructions that you linked to begin with this sentence: """ To boot the installer from hard disk ... """ So from that we might assume (you didn't explicitly say yet) that your goal is to run the Debian installer from a CD image data that is available in a file on an ext4 partition on a local hard drive. Is that correct? And your CD image is *not* on a removable media, is that correct? > Does anyone > happen to know how the ISO should be accessed? Loop mount at > /dev/cdrom? In my recent experience (using para 3 method), the installer searches the local hard drives for files that it recognises. And this search can fail to succeed if I haven't done the proper dance first. The vmlinuz and initrd must match the iso. I don't know about para 2 method, I never tried that.
Installation instructions.
https://www.debian.org/releases/stable/i386/ch05s01.en.html#boot-initrd
gives this sample Grub2 configuration.
menuentry 'New Install' {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
linux /boot/newinstall/vmlinuz
initrd /boot/newinstall/initrd.gz
}
No problem with vmlinuz and initrd.gz but the CD image is not found.
The configuration which worked in the past had parameters on the linux
command. Similar to this.
linux /vmlinuz root=UUID=50e0fa4b-6c62-40f8-8a84-46ab1413eb5a ro from=hd
fromiso=debian-10.6.0-i386-netinst.iso load=all reboot=bios
The instructions at the URL above appear incomplete. Does anyone
happen to know how the ISO should be accessed? Loop mount at
/dev/cdrom?
Thx, ... P.
--
Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re: need google chrome installation instructions that work
On Thu, Nov 22, 2018 at 10:07:51AM -0600, David Wright wrote: > It works fine for me, as shown by the output below. However, I notice > there's a line: > > Note, selecting 'xtoolwait' instead of ' … … /xtoolwait_1.3-6.2_amd64.deb' Yeah, my own tests always gave me that too, so I decided not to post my results here. Apparently the only way I can *test* this and *post* my results would be if I use a .deb file that does *not* correspond to a package that is known to apt on my system. Which would mean either I'd have to find a random third-party repository that has a *small* package that I could download and install with apt-get install ./ for testing purposes, or I would have to purge my web browser, purge the Google repository from my sources.list.d, apt-get update to purge it from the cached lists, and then repeat the basic procedure of installing google-chrome-stable from scratch. I was not willing to do all of that just to prove people wrong on the Internet. I have some limits. If someone still claims that it "doesn't work", then for the love of RMS, post: * which VERSION of Debian you are using, * the EXACT command you used, and * the FULL and EXACT output of that command. One person who claimed it "didn't work" went through those steps and discovered that the wrong command had been used.
Re: need google chrome installation instructions that work
On Wed 21 Nov 2018 at 11:44:02 (-0800), Patrick Bartek wrote: > On Wed, 21 Nov 2018 11:21:15 -0500 > Greg Wooledge wrote: > > On Wed, Nov 21, 2018 at 08:02:23AM -0800, Patrick Bartek wrote: > > > I use gdebi (it's in the repos) to install locally saved .deb files. > > > Apt-get won't install local files, that is, not in a repo. > > > > Yes, it will. But you have to supply the filename with a > > leading / or ./ or ../ prefix. > > > > sudo apt-get install ./google-chrome-stable*.deb > > That never worked for me. I've tried. Numerous times. Even with > complete paths, changing to directory where file was, full names, etc., > etc. Both with Wheezy & Stretch. Read somewhere when troubleshooting, > apt-get wouldn't install local .deb. Only way it would was if you > created a local repo and put it in your sources.list. Too much > trouble. That's why I starting using gdebi for those very rare times > I need to. > > Don't know if apt does. Never tried. It works fine for me, as shown by the output below. However, I notice there's a line: Note, selecting 'xtoolwait' instead of ' … … /xtoolwait_1.3-6.2_amd64.deb' which could suggest that the internals of the .deb file are being taken account of; I haven't studied the output from strace. xtoolwait is a legitimate Debian package, but it hasn't been available since squeeze. I also haven't checked wheezy: all this could postdate wheezy/jessie anyway. For a full path, the output from apt and apt-get is identical (except that apt produces a progress bar, which is later overwritten). - Full path succeeds: ~# apt-get install /home/debian/squeeze/xtoolwait_1.3-6.2_amd64.deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'xtoolwait' instead of '/home/debian/squeeze/xtoolwait_1.3-6.2_amd64.deb' The following NEW packages will be installed: xtoolwait 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/13.1 kB of archives. After this operation, 77.8 kB of additional disk space will be used. Get:1 /home/debian/squeeze/xtoolwait_1.3-6.2_amd64.deb xtoolwait amd64 1.3-6.2 [13.1 kB] Retrieving bug reports... Done Parsing Found/Fixed information... Done Selecting previously unselected package xtoolwait. (Reading database ... 261615 files and directories currently installed.) Preparing to unpack .../xtoolwait_1.3-6.2_amd64.deb ... Unpacking xtoolwait (1.3-6.2) ... Setting up xtoolwait (1.3-6.2) ... Processing triggers for man-db (2.7.6.1-2) ... Scanning processes... Scanning linux images... Running kernel seems to be up-to-date. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. N: Download is performed unsandboxed as root as file '/home/debian/squeeze/xtoolwait_1.3-6.2_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) ~# - Filename alone fails: /home/debian/squeeze# apt-get install xtoolwait_1.3-6.2_amd64.deb Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package xtoolwait_1.3-6.2_amd64.deb E: Couldn't find any package by glob 'xtoolwait_1.3-6.2_amd64.deb' E: Couldn't find any package by regex 'xtoolwait_1.3-6.2_amd64.deb' 100 /home/debian/squeeze# - ./ path succeeds (and ../ likewise): /home/debian/squeeze# apt-get install ./xtoolwait_1.3-6.2_amd64.deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'xtoolwait' instead of './xtoolwait_1.3-6.2_amd64.deb' The following NEW packages will be installed: xtoolwait 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/13.1 kB of archives. After this operation, 77.8 kB of additional disk space will be used. Get:1 /home/debian/squeeze/xtoolwait_1.3-6.2_amd64.deb xtoolwait amd64 1.3-6.2 [13.1 kB] Retrieving bug reports... Done Parsing Found/Fixed information... Done Selecting previously unselected package xtoolwait. (Reading database ... 261615 files and directories currently installed.) Preparing to unpack .../xtoolwait_1.3-6.2_amd64.deb ... Unpacking xtoolwait (1.3-6.2) ... Setting up xtoolwait (1.3-6.2) ... Processing triggers for man-db (2.7.6.1-2) ... Scanning processes... Scanning linux images... Running kernel seems to be up-to-date. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. N: Download is performed unsandboxed as root as file '/home/debian/squeeze/xtoolwait_1.3-6.2_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
Re: need google chrome installation instructions that work
On 11/21/18, Patrick Bartek wrote: > On Wed, 21 Nov 2018 11:21:15 -0500 > Greg Wooledge wrote: > >> On Wed, Nov 21, 2018 at 08:02:23AM -0800, Patrick Bartek wrote: >> > I use gdebi (it's in the repos) to install locally saved .deb files. >> > Apt-get won't install local files, that is, not in a repo. >> >> Yes, it will. But you have to supply the filename with a >> leading / or ./ or ../ prefix. >> >> sudo apt-get install ./google-chrome-stable*.deb > > That never worked for me. I've tried. Numerous times. Even with > complete paths, changing to directory where file was, full names, etc., > etc. Both with Wheezy & Stretch. Read somewhere when troubleshooting, > apt-get wouldn't install local .deb. Only way it would was if you > created a local repo and put it in your sources.list. Too much > trouble. That's why I starting using gdebi for those very rare times > I need to. Ditto on that experience for me. Didn't work, but can't remember the (fairly straight up) process to repeat to better understand why not. Had seen the "./" reference on Debian-User in the last week so I tried it while consciously thinking, "WHAT are we doing here?!" In my case, "we" ended up doing nothing because it didn't work. I dropped it and kept moving while thinking I had simply missed some setup detail that would have caused success instead of failure. > Don't know if apt does. Never tried. > > Just occurred to me that since I did customized installs of both Wheezy > and Stretch (No desktop environment, window manager only) starting with > a terminal only system that could be why apt-get won't install > local .deb. Doesn't matter. Gdebi works fine. Have tripped over gdebi a few times in the last year or so. Those sightings were most likely most often as an apt-get suggested download. Will have to give it a try now that this thread has highlighted its usefulness. It's good to have alternative tools when individual Life needs mandate making difficult package usage decisions. We just had that recent thread about playing the escalating dependency game by hand. I broke one my setups k/t that very thing only hours after having commented on that same thread. Fix-missing/fix-broken both shoved a hand in my face while yelling, *Uh-uh, YOU made this mess, YOU clean it up by yourself!* PS I did clean it up, hence the newest debootstrap. :) Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with duct tape *
Re: need google chrome installation instructions that work
On Wed, 21 Nov 2018 11:21:15 -0500 Greg Wooledge wrote: > On Wed, Nov 21, 2018 at 08:02:23AM -0800, Patrick Bartek wrote: > > I use gdebi (it's in the repos) to install locally saved .deb files. > > Apt-get won't install local files, that is, not in a repo. > > Yes, it will. But you have to supply the filename with a > leading / or ./ or ../ prefix. > > sudo apt-get install ./google-chrome-stable*.deb That never worked for me. I've tried. Numerous times. Even with complete paths, changing to directory where file was, full names, etc., etc. Both with Wheezy & Stretch. Read somewhere when troubleshooting, apt-get wouldn't install local .deb. Only way it would was if you created a local repo and put it in your sources.list. Too much trouble. That's why I starting using gdebi for those very rare times I need to. Don't know if apt does. Never tried. Just occurred to me that since I did customized installs of both Wheezy and Stretch (No desktop environment, window manager only) starting with a terminal only system that could be why apt-get won't install local .deb. Doesn't matter. Gdebi works fine. B
Re: need google chrome installation instructions that work
On Wed, Nov 21, 2018 at 7:46 AM Greg Wooledge wrote: > > On Wed, Nov 21, 2018 at 04:44:14AM -0500, Felix Miata wrote: > > It seems Curt's instructions to use dpkg to install the downloaded deb > > resulted in > > creation of /etc/apt/sources.list.d/google-chrome.list containing > > > > deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main > > > > With any luck the next to search for such instruction will find this post > > instead of needing to > > ask here, or better yet a Debian wiki page somewhere updated or created to > > include them and > > googling to produce on first results page. :-p > > Or, and I know this is like SUPER surprising, right, but... > > ... maybe you could try searching on Google's web search engine for the > way to install Google's web browser. > > Having just done this myself, the surprising part is that the answer was > NOT the first result. It was part way down the first page for me: > > https://www.google.com/chrome/ > > On this page, there is a "Download Chrome" button. Clicking this > gives me a pop-up overlay panel thingy which asks me to select > between "64 bit .deb" and "64 bit .rpm". There is a note that tells > me how to avoid adding the Google repository if for some reason I > wouldn't want that. > > I'm not going to go through the entire download process again here, > having already done it long ago. Suffice to say, there are no > detailed instructions on the wiki for how to do this, because it's > incredibly simple and obvious, and nobody should NEED detailed > instructions. > > You download the .deb from Google and you install it with dpkg -i > or apt install ./ or whatever you prefer. Then you're done. > > Those are the instructions. > This is the way I install Google Chrome from the terminal. cd Downloads && wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb && sudo apt install gdebi -y && sudo gdebi google*
Re: need google chrome installation instructions that work
Greg Wooledge composed on 2018-11-21 11:50 (UTC-0500): > On Wed, Nov 21, 2018 at 11:31:53AM -0500, Felix Miata wrote: >> I did try ./google-chrome... but apt wouldn't find it. > In stretch, right? What was the exact command you used, and the exact > output? Sorry, I thought I had, but NAICT from .bash_history what I keyed in Stretch was: cd /tmp aptitude install ./google-chr Can't be sure what the actual filename was on disk because of the move from $HOME/Downloads to /tmp which was since emptied. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: need google chrome installation instructions that work
On Wed, Nov 21, 2018 at 11:31:53AM -0500, Felix Miata wrote: > I did try ./google-chrome... but apt wouldn't find it. In stretch, right? What was the exact command you used, and the exact output?
Re: need google chrome installation instructions that work
Greg Wooledge composed on 2018-11-21 11:21 (UTC-0500): > On Wed, Nov 21, 2018 at 08:02:23AM -0800, Patrick Bartek wrote: >> I use gdebi (it's in the repos) to install locally saved .deb files. >> Apt-get won't install local files, that is, not in a repo. > Yes, it will. But you have to supply the filename with a > leading / or ./ or ../ prefix. > sudo apt-get install ./google-chrome-stable*.deb > It will resolve the dependencies from your repositories and everything, > just like gdebi. I did try ./google-chrome... but apt wouldn't find it. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: need google chrome installation instructions that work
On Wed, Nov 21, 2018 at 08:02:23AM -0800, Patrick Bartek wrote: > I use gdebi (it's in the repos) to install locally saved .deb files. > Apt-get won't install local files, that is, not in a repo. Yes, it will. But you have to supply the filename with a leading / or ./ or ../ prefix. sudo apt-get install ./google-chrome-stable*.deb It will resolve the dependencies from your repositories and everything, just like gdebi.
Re: need google chrome installation instructions that work
On Wed, 21 Nov 2018 03:30:26 -0500 Felix Miata wrote: > (Stretch) > Downloading Chrome is easy. Installing is not. The download page says > "download and install", > but all that happens is firefox fetches, and no auto install via apt* or dpkg > is attempted. Apt > and aptitude won't install the local file because it "isn't found". The > https://www.google.com/linuxrepositories/ "Google Linux Software > Repositories" page says how to > configure GPG, but nothing about configuring repo in sources.list. Where are > the secret > incantations to be found? I use gdebi (it's in the repos) to install locally saved .deb files. Apt-get won't install local files, that is, not in a repo. GDebi also takes care of dependencies which dpkg does not. I use the commandline version. IIRC, there's GUI interface, too, if you prefer that. B
Re: need google chrome installation instructions that work
On 21-11-18, Felix Miata wrote: > john doe composed on 2018-11-21 10:06 (UTC+0100): > > > Felix Miata wrote: > > >> (Stretch) > >> Downloading Chrome is easy. Installing is not. The download page says > >> "download and install", > >> but all that happens is firefox fetches, and no auto install via apt* or > >> dpkg is attempted. Apt > >> and aptitude won't install the local file because it "isn't found". The > >> https://www.google.com/linuxrepositories/ "Google Linux Software > >> Repositories" page says how to > >> configure GPG, but nothing about configuring repo in sources.list. Where > >> are the secret > >> incantations to be found? > > > The below link might be useful: > > > https://www.wikihow.com/Install-Google-Chrome-Using-Terminal-on-Linux > > It worked. I had tried on previous occasions downloaded debs with 'dpkg -i' > without any > successes that I can recall. The provided deps on that page did the trick. > > > you should also consider googling "installing chrome on linux". > > Before posting here that's sort of what I did with DuckDuckGo: > > google chrome debian sources.list > google chrome for debian configuration > > Nothing I had clicked on seemed appropriate to the expected task. I'm not a > Chrome user. This is > for a friend whose vision is about 5% and tasks me with his upgrades. > > Thanks! > -- > Evolution as taught in public schools is religion, not science. > > Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! > > Felix Miata *** http://fm.no-ip.com/ > Bit late on party, but as others already said dpkg -i followed by apt-get -f ( --fix-broken ) should do the trick. It will add it to the sources list. One new thing to add would be that it will very annoyingly mess up with alternatives and after install and after every damn update/upgrade it will set itself up with crazy high preference in alternatives, that will always be with priority higher than other browsers. So, if you want to keep some other browser as your x-www-browser, or gnome-www-browser as primary, you will need to amend those settings. All best, Dejan
Re: need google chrome installation instructions that work
On Wed, Nov 21, 2018 at 04:44:14AM -0500, Felix Miata wrote: > It seems Curt's instructions to use dpkg to install the downloaded deb > resulted in > creation of /etc/apt/sources.list.d/google-chrome.list containing > > deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main > > With any luck the next to search for such instruction will find this post > instead of needing to > ask here, or better yet a Debian wiki page somewhere updated or created to > include them and > googling to produce on first results page. :-p Or, and I know this is like SUPER surprising, right, but... ... maybe you could try searching on Google's web search engine for the way to install Google's web browser. Having just done this myself, the surprising part is that the answer was NOT the first result. It was part way down the first page for me: https://www.google.com/chrome/ On this page, there is a "Download Chrome" button. Clicking this gives me a pop-up overlay panel thingy which asks me to select between "64 bit .deb" and "64 bit .rpm". There is a note that tells me how to avoid adding the Google repository if for some reason I wouldn't want that. I'm not going to go through the entire download process again here, having already done it long ago. Suffice to say, there are no detailed instructions on the wiki for how to do this, because it's incredibly simple and obvious, and nobody should NEED detailed instructions. You download the .deb from Google and you install it with dpkg -i or apt install ./ or whatever you prefer. Then you're done. Those are the instructions.
Re: need google chrome installation instructions that work
One suggestion (and, yes, I'm intentionally top posting) -- why don't you repost you're reply with: * the Subject changed to say Solved (was: need G...) * Top post the solution in as concise a fashion as you can -- my first feeble partial attempt: "I had trouble installing Google Chrome using dpkg -i until I followed the instructions at which required that I add a line in /etc/apt/sources.list.d/google-chrome.list containing deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main " I am not sure of the accuracy of what I wrote as I only read the other posts in this thread superficially. For extra credit, you could modify the wiki page you mention if appropriate. regards, and if you celebrate (American) thanksgiving, happy Thanksgiving. Randy Kramer On Wednesday, November 21, 2018 04:44:14 AM Felix Miata wrote: > Curt composed on 2018-11-21 09:15 (UTC): > > Felix Miata wrote: > >> (Stretch) > >> Downloading Chrome is easy. Installing is not. The download page says > >> "download and install", but all that happens is firefox fetches, and no > >> auto install via apt* or dpkg is attempted. Apt and aptitude won't > >> install the local file because it "isn't found". The > >> https://www.google.com/linuxrepositories/ "Google Linux Software > >> Repositories" page says how to configure GPG, but nothing about > >> configuring repo in sources.list. Where are the secret incantations to > >> be found? > > > > deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main > > > > in /etc/apt/sources.list > > It seems Curt's instructions to use dpkg to install the downloaded deb > resulted in creation of /etc/apt/sources.list.d/google-chrome.list > containing > > deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main > > With any luck the next to search for such instruction will find this post > instead of needing to ask here, or better yet a Debian wiki page somewhere > updated or created to include them and googling to produce on first > results page. :-p
Re: need google chrome installation instructions that work
On Wed, Nov 21, 2018 at 04:44:14AM -0500, Felix Miata wrote: [...] > It seems Curt's instructions to use dpkg to install the downloaded deb > resulted in > creation of /etc/apt/sources.list.d/google-chrome.list containing > > deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main Yiiikes. Comfy, yes. Possible, too (after all, pre- and post-install scripts run as root and can do anything). But scary... a bit. Installing a browser reachs deep into the whole system. Not *my* cup of tea, to be honest. Cheers -- tomás signature.asc Description: Digital signature
Re: need google chrome installation instructions that work
Curt composed on 2018-11-21 09:15 (UTC): > Felix Miata wrote: >> (Stretch) >> Downloading Chrome is easy. Installing is not. The download page says >> "download and install", >> but all that happens is firefox fetches, and no auto install via apt* or >> dpkg is attempted. Apt >> and aptitude won't install the local file because it "isn't found". The >> https://www.google.com/linuxrepositories/ "Google Linux Software >> Repositories" page says how to >> configure GPG, but nothing about configuring repo in sources.list. Where are >> the secret >> incantations to be found? > deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main > in /etc/apt/sources.list It seems Curt's instructions to use dpkg to install the downloaded deb resulted in creation of /etc/apt/sources.list.d/google-chrome.list containing deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main With any luck the next to search for such instruction will find this post instead of needing to ask here, or better yet a Debian wiki page somewhere updated or created to include them and googling to produce on first results page. :-p -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: need google chrome installation instructions that work
john doe composed on 2018-11-21 10:06 (UTC+0100): > Felix Miata wrote: >> (Stretch) >> Downloading Chrome is easy. Installing is not. The download page says >> "download and install", >> but all that happens is firefox fetches, and no auto install via apt* or >> dpkg is attempted. Apt >> and aptitude won't install the local file because it "isn't found". The >> https://www.google.com/linuxrepositories/ "Google Linux Software >> Repositories" page says how to >> configure GPG, but nothing about configuring repo in sources.list. Where are >> the secret >> incantations to be found? > The below link might be useful: > https://www.wikihow.com/Install-Google-Chrome-Using-Terminal-on-Linux It worked. I had tried on previous occasions downloaded debs with 'dpkg -i' without any successes that I can recall. The provided deps on that page did the trick. > you should also consider googling "installing chrome on linux". Before posting here that's sort of what I did with DuckDuckGo: google chrome debian sources.list google chrome for debian configuration Nothing I had clicked on seemed appropriate to the expected task. I'm not a Chrome user. This is for a friend whose vision is about 5% and tasks me with his upgrades. Thanks! -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: need google chrome installation instructions that work
On 2018-11-21, Felix Miata wrote: > (Stretch) > Downloading Chrome is easy. Installing is not. The download page says > "download and install", > but all that happens is firefox fetches, and no auto install via apt* or dpkg > is attempted. Apt > and aptitude won't install the local file because it "isn't found". The > https://www.google.com/linuxrepositories/ "Google Linux Software > Repositories" page says how to > configure GPG, but nothing about configuring repo in sources.list. Where are > the secret > incantations to be found? deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main in /etc/apt/sources.list -- He used sentences differently from any other prose writer. He always sounded like a slightly drunk man who is very melancholy, who has no illusions about life, who is very strong but whose strength is entirely unnecessary. --Krasznahorkai on Krúdy
Re: need google chrome installation instructions that work
On 11/21/2018 9:30 AM, Felix Miata wrote: > (Stretch) > Downloading Chrome is easy. Installing is not. The download page says > "download and install", > but all that happens is firefox fetches, and no auto install via apt* or dpkg > is attempted. Apt > and aptitude won't install the local file because it "isn't found". The > https://www.google.com/linuxrepositories/ "Google Linux Software > Repositories" page says how to > configure GPG, but nothing about configuring repo in sources.list. Where are > the secret > incantations to be found? > The below link might be useful: https://www.wikihow.com/Install-Google-Chrome-Using-Terminal-on-Linux you should also consider googling "installing chrome on linux". -- John Doe
need google chrome installation instructions that work
(Stretch) Downloading Chrome is easy. Installing is not. The download page says "download and install", but all that happens is firefox fetches, and no auto install via apt* or dpkg is attempted. Apt and aptitude won't install the local file because it "isn't found". The https://www.google.com/linuxrepositories/ "Google Linux Software Repositories" page says how to configure GPG, but nothing about configuring repo in sources.list. Where are the secret incantations to be found? -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Installation Instructions for Building and Installing Xen 4.x and Linux Kernel 3.x on Ubuntu and Debian Linux
PDF Download Links = Version 1.0: http://www.sgvideoman.com/xen/Installation%20Instructions%20for%20Xen%204.1.3-rc1-pre%20and%20Linux%20Kernel%203.3.0-rc7%20on%20Ubuntu%2011.10%20Release%20-%20Version%201.0.pdf Version 1.1: http://www.sgvideoman.com/xen/Installation%20Instructions%20for%20Xen%204.1.x%20or%204.2-unstable%20and%20Linux%20Kernel%203.x.x%20on%20Ubuntu%20and%20Debian%20Linux%20-%20Version%201.1.pdf Version 1.2: http://www.sgvideoman.com/xen/Installation%20Instructions%20for%20Xen%204.1.x%20or%204.2-unstable%20and%20Linux%20Kernel%203.x.x%20on%20Ubuntu%20and%20Debian%20Linux%20-%20Version%201.2.pdf Yours sincerely, Teo En Ming (Zhang Enming) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f65c788.2090...@gmail.com
Installation Instructions for Xen 4.1.3-rc1-pre and Linux Kernel 3.3.0-rc7 on Ubuntu and Debian Linux
Dear All, I have written a set of installation instructions for building and installing Xen 4.1.3-rc1-pre hypervisor and Linux kernel 3.3.0-rc7 / 3.2.11 on Ubuntu and Debian Linux in PDF format. The mediafire.com download link for the PDF document I have written is Download link: http://www.mediafire.com/?w1arfubbwsc3171 There is a total of 254 pages in the PDF document, but the most important steps are in the first 8 pages. Thank you very much. Yours sincerely, Teo En Ming (Zhang Enming) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f64645a.30...@gmail.com
Debian installation instructions [was: Installing Debian over a Suse system]
On Mon, May 07, 2001 at 11:33:22PM +0200, [EMAIL PROTECTED] wrote: I have installed Suse 7.0, but want to shift to Debian 2.2. I have read installation manuals and FAQs regarding installing Debian, but have not found anything on this item. have a look at http://www.debian.org/releases/2.2/i386/install for x86 installation instructions or at http://www.debian.de/releases/stable/ to select platform and language. debian 2.2 potato (the stable release) uses kernel 2.2 and xfree 3.3.6. if you really need /want to user kernel 2.4 and xfree 4 you can use unofficial debian packages for both or upgrade your system to woody (the testing release) or sid (the unstable release). but a system upgrade is an irreversable upgrade. once you find out sid is too unstable for you it's too late. yours martin -- GnuPG 1024D/3E8DCCC0 30DC 1D28 1D79 32F5 5E67 3ABB 28EE B35A 3E8D CCC0 work: factline Krisper Fabro Harnoncourt OEG (www.factline.com)
FTP Installation Instructions
I would like to begin downloading Debian Linux but I remain a little puzzled as to how this procedure really works. I have RedHat 6.1 on an old P133 (64MB) 1 GB system at home I can play around with. The RedHat install works fine and we use the same release at work where I am a unix admin for HPUX AIX systems. However, for reasons I can't really explain, I would like to delve deeper into Linux and begin working with current builds - a yearning likely to yield as much grief as pleasure, but I can't help myself. With RedHat I have always used the boot floppy and the cdrom. That's fairly simple nowadays, but one remains dependent on the prepackaged releases and I end up with a very generic installation. That's functional enough, but its boring. I imagine performing installs off the web will require a little more Linux savvy, which is agreeable enough. So my question is, assuming I start from the 6.1 platform I have, how would I go about downloading and converting to the most recent / stable Debian release? By asking that I don't really expect anyone to lead me through the process step by step and I have read through at least some of the installation documentation on the web site. However, in spite of that, I remain unclear where I deposit the Debian ftp download and how I initiate the installation. Do I create a boot floppy and point it to a installation directory? Can someone point me to some documentation that addresses installing from a ftp download? Hagen Finley Longs Drugs Walnut Creek, CA
Re: FTP Installation Instructions
Hi Hagen Welcome to Debian. I'm assuming that you're planning on wiping out the disk and starting over once you've created the base system floppies? If so, point your browser at http://www.debian.org/releases/slink/i386/install and look at Chapter 5. The subsections cover just about everything you need including how to create the floppy disks (9) that will install your base system. If you have any problems holler again on this list. If not, take a look at the thread Moving from RedHat to Debian currently active on the list. John I would like to begin downloading Debian Linux but I remain a little puzzled as to how this procedure really works. I have RedHat 6.1 on an old P133 (64MB) 1 GB system at home I can play around with. The RedHat install works fine and we use the same release at work where I am a unix admin for HPUX AIX systems. However, for reasons I can't really explain, I would like to delve deeper into Linux and begin working with current builds - a yearning likely to yield as much grief as pleasure, but I can't help myself. With RedHat I have always used the boot floppy and the cdrom. That's fairly simple nowadays, but one remains dependent on the prepackaged releases and I end up with a very generic installation. That's functional enough, but its boring. I imagine performing installs off the web will require a little more Linux savvy, which is agreeable enough. So my question is, assuming I start from the 6.1 platform I have, how would I go about downloading and converting to the most recent / stable Debian release? By asking that I don't really expect anyone to lead me through the process step by step and I have read through at least some of the installation documentation on the web site. However, in spite of that, I remain unclear where I deposit the Debian ftp download and how I initiate the installation. Do I create a boot floppy and point it to a installation directory? Can someone point me to some documentation that addresses installing from a ftp download? Hagen Finley Longs Drugs Walnut Creek, CA -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Powered by the Penguin
Re: FTP Installation Instructions
On Sat, 25 Dec 1999, Hagen Finley wrote: site. However, in spite of that, I remain unclear where I deposit the Debian ftp download and how I initiate the installation. Do I create a boot floppy and point it to a installation directory? Can someone point me to some documentation that addresses installing from a ftp download? This is why I think Debian is the distribution which is easiest to install. If you are going to an FTP install, you only need to download approximately 10 MB of files (the base files). If you are installing Debian onto a machine that is in a networked environment (such as your work place, where you have access to other *nix machines), you can copy these files to one of those other machines (if you can mount one of their directories via NFS). Otherwise, you'll need to copy the base files to floppies (I believe it takes 7 3.5 floppies). And, of course, you'll need a boot floppy. You start the installation with the boot floppy, tell it (the installation program) where the base files are located (on floppies, on an NFS share, etc.) and it will install those. Debian's automated installation then takes over. You go through the list of available packages and select which ones you want installed. The installation program will then connect to an FTP server, download the packages you selected, and install them, without any work from you. I tried to explain it briefly and simply, but it sounds more complicated than it is. When I was new to linux, I tried installing both Slackware and Redhat, having different problems with each. I then moved to Debian, and I've been running it on multiple machines every since. HTH.
