Re: how to debootstrap Debian 8 Jessie released 2015-04-25 on Ubuntu 14.04
On Sun, Jun 18, 2023 at 10:22:56AM +0200, Mario Marietto wrote: > ok. these works : > > debootstrap --foreign --arch=armhf jessie jessie-armhf > http://archive.debian.org/debian > > debootstrap --foreign --arch=armhf strech strech-armhf > http://archive.debian.org/debian > > but not this : > > root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros# > debootstrap --foreign --arch=armhf buster buster-armhf > http://archive.debian.org/debian Buster is not archived yet. It's still receiving some support. So, you should use the regular mirror set for buster.
Re: how to debootstrap Debian 8 Jessie released 2015-04-25 on Ubuntu 14.04
Hello, El dom., 18 jun. 2023 10:23, Mario Marietto escribió: > ok. these works : > > debootstrap --foreign --arch=armhf jessie jessie-armhf > http://archive.debian.org/debian > > debootstrap --foreign --arch=armhf strech strech-armhf > http://archive.debian.org/debian > > but not this : > > root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros# > debootstrap --foreign --arch=armhf buster buster-armhf > http://archive.debian.org/debian > > W: Cannot check Release signature; keyring file not available > /usr/share/keyrings/debian-archive-keyring.gpg > I: Retrieving Release > > E: Failed getting release file > http://archive.debian.org/debian/dists/buster/Release > > root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros# > debootstrap --foreign --arch=armhf buster buster-armhf > > I: Keyring file not available at > /usr/share/keyrings/debian-archive-keyring.gpg; switching to https mirror > https://mirrors.kernel.org/debian > I: Retrieving Release > > E: Failed getting release file > https://mirrors.kernel.org/debian/dists/buster/Release > > thanks. > > On Sun, Jun 18, 2023 at 10:14 AM Mario Marietto > wrote: > >> Can you elaborate the full command ? thanks. >> >> On Sun, Jun 18, 2023 at 10:12 AM Javier Barroso >> wrote: >> >>> Hello, >>> >>> El dom., 18 jun. 2023 9:56, Mario Marietto >>> escribió: >>> >>>> I'm running Ubuntu 14.04 and I would like to debootstrap debian jessie >>>> 8. I've found this tutorial and I tried , but it didn't work : >>>> >>>> from here : >>>> >>>> https://blog.lazy-evaluation.net/posts/linux/debian-armhf-bootstrap.html >>>> >>>> >>>> he says to do : >>>> >>>> >>>> # debootstrap --foreign --arch=armhf jessie jessie-armhf >>>> >>>> >>>> but unfortunately : >>>> >>>> >>>> I: Keyring file not available at >>>> /usr/share/keyrings/debian-archive-keyring.gpg; switching to https mirror >>>> https://mirrors.kernel.org/debian >>>> >>>> I: Retrieving Release >>>> >>>> E: Failed getting release file >>>> https://mirrors.kernel.org/debian/dists/jessie/Release >>>> >>>> how to fix it ? thanks. >>>> >>>> -- >>>> Mario. >>>> >>> >>> You need to add http://archive.debian.org/debian yo the debootstrap >>> command >>> >>> Jessie was archived a long time ago >>> >>>> >> >> -- >> Mario. >> > > > -- > Mario. > There are old releases archived, and other which are not archived still You can see the info in Debían web: https://www.debian.org/releases/ For no archived releases I think no need to add a URL (or maybe then oficial one) Regards >
Re: how to debootstrap Debian 8 Jessie released 2015-04-25 on Ubuntu 14.04
ok. these works : debootstrap --foreign --arch=armhf jessie jessie-armhf http://archive.debian.org/debian debootstrap --foreign --arch=armhf strech strech-armhf http://archive.debian.org/debian but not this : root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros# debootstrap --foreign --arch=armhf buster buster-armhf http://archive.debian.org/debian W: Cannot check Release signature; keyring file not available /usr/share/keyrings/debian-archive-keyring.gpg I: Retrieving Release E: Failed getting release file http://archive.debian.org/debian/dists/buster/Release root@marietto-Z87-HD3:/home/marietto/Scrivania/Chromebook/linux-distros# debootstrap --foreign --arch=armhf buster buster-armhf I: Keyring file not available at /usr/share/keyrings/debian-archive-keyring.gpg; switching to https mirror https://mirrors.kernel.org/debian I: Retrieving Release E: Failed getting release file https://mirrors.kernel.org/debian/dists/buster/Release thanks. On Sun, Jun 18, 2023 at 10:14 AM Mario Marietto wrote: > Can you elaborate the full command ? thanks. > > On Sun, Jun 18, 2023 at 10:12 AM Javier Barroso > wrote: > >> Hello, >> >> El dom., 18 jun. 2023 9:56, Mario Marietto >> escribió: >> >>> I'm running Ubuntu 14.04 and I would like to debootstrap debian jessie >>> 8. I've found this tutorial and I tried , but it didn't work : >>> >>> from here : >>> >>> https://blog.lazy-evaluation.net/posts/linux/debian-armhf-bootstrap.html >>> >>> >>> he says to do : >>> >>> >>> # debootstrap --foreign --arch=armhf jessie jessie-armhf >>> >>> >>> but unfortunately : >>> >>> >>> I: Keyring file not available at >>> /usr/share/keyrings/debian-archive-keyring.gpg; switching to https mirror >>> https://mirrors.kernel.org/debian >>> >>> I: Retrieving Release >>> >>> E: Failed getting release file >>> https://mirrors.kernel.org/debian/dists/jessie/Release >>> >>> how to fix it ? thanks. >>> >>> -- >>> Mario. >>> >> >> You need to add http://archive.debian.org/debian yo the debootstrap >> command >> >> Jessie was archived a long time ago >> >>> > > -- > Mario. > -- Mario.
Re: how to debootstrap Debian 8 Jessie released 2015-04-25 on Ubuntu 14.04
Can you elaborate the full command ? thanks. On Sun, Jun 18, 2023 at 10:12 AM Javier Barroso wrote: > Hello, > > El dom., 18 jun. 2023 9:56, Mario Marietto > escribió: > >> I'm running Ubuntu 14.04 and I would like to debootstrap debian jessie 8. >> I've found this tutorial and I tried , but it didn't work : >> >> from here : >> >> https://blog.lazy-evaluation.net/posts/linux/debian-armhf-bootstrap.html >> >> >> he says to do : >> >> >> # debootstrap --foreign --arch=armhf jessie jessie-armhf >> >> >> but unfortunately : >> >> >> I: Keyring file not available at >> /usr/share/keyrings/debian-archive-keyring.gpg; switching to https mirror >> https://mirrors.kernel.org/debian >> >> I: Retrieving Release >> >> E: Failed getting release file >> https://mirrors.kernel.org/debian/dists/jessie/Release >> >> how to fix it ? thanks. >> >> -- >> Mario. >> > > You need to add http://archive.debian.org/debian yo the debootstrap > command > > Jessie was archived a long time ago > >> -- Mario.
Re: how to debootstrap Debian 8 Jessie released 2015-04-25 on Ubuntu 14.04
Hello, El dom., 18 jun. 2023 9:56, Mario Marietto escribió: > I'm running Ubuntu 14.04 and I would like to debootstrap debian jessie 8. > I've found this tutorial and I tried , but it didn't work : > > from here : > > https://blog.lazy-evaluation.net/posts/linux/debian-armhf-bootstrap.html > > > he says to do : > > > # debootstrap --foreign --arch=armhf jessie jessie-armhf > > > but unfortunately : > > > I: Keyring file not available at > /usr/share/keyrings/debian-archive-keyring.gpg; switching to https mirror > https://mirrors.kernel.org/debian > > I: Retrieving Release > > E: Failed getting release file > https://mirrors.kernel.org/debian/dists/jessie/Release > > how to fix it ? thanks. > > -- > Mario. > You need to add http://archive.debian.org/debian yo the debootstrap command Jessie was archived a long time ago >
how to debootstrap Debian 8 Jessie released 2015-04-25 on Ubuntu 14.04
I'm running Ubuntu 14.04 and I would like to debootstrap debian jessie 8. I've found this tutorial and I tried , but it didn't work : from here : https://blog.lazy-evaluation.net/posts/linux/debian-armhf-bootstrap.html he says to do : # debootstrap --foreign --arch=armhf jessie jessie-armhf but unfortunately : I: Keyring file not available at /usr/share/keyrings/debian-archive-keyring.gpg; switching to https mirror https://mirrors.kernel.org/debian I: Retrieving Release E: Failed getting release file https://mirrors.kernel.org/debian/dists/jessie/Release how to fix it ? thanks. -- Mario.
Re: Re: (Thread restarted!) Debian installation using debootstrap and grub-install - no entry in ESC boot menu
Hello everyone, I partly solved my problem and I would like to share my solution: Until now, I thought that the EFI removable media path (\EFI\BOOT\BOOTX64.EFI) is really a fallback location, i.e. a location for putting the boot loader that just always works. Therefore I thought that I could forget about EFI variables altogether if I just put the boot loader there. My recipes don't bind-mount /sys/firmware/efi/efivars for that reason. And when trying things out with the emulator, this assumption holds true, i.e. running "qemu-system-x86_64 -accel kvm -bios /usr/share/ovmf/OVMF.fd ..." will create a virtual machine that behaves like I expected. However, my Asus UX31A does things differently and insists on EFI variables being used for the internal drive, i.e. it doesn't look at the fallback location (\EFI\BOOT\BOOTX64.EFI) of the internal drive. That's the solution for the EFI boot interface, use EFI variables. For the BIOS boot interface, I'm still clueless why it doesn't work. However, I'll leave it at that. Thanks to everyone who helped! Kind regards, Valentin Caracalla
Re: (Thread restarted!) Debian installation using debootstrap and grub-install - no entry in ESC boot menu
On Thu 27 Apr 2023 at 10:18:56 (+0700), Max Nikulin wrote: > On 26/04/2023 22:57, Valentin Caracalla wrote: > > the issue with the BIOS boot interface (see my original posting) is still > > unsolved > > I had impression that there was no issue with booting in BIOS (legacy, > compatibility, CSM) mode, of course when it is chosen in firmware/BIOS > setup (requires disabling of secure boot). Well, the OP wrote: "Previously, I've successfully installed Debian using official installation media on this machine (also using BIOS boot interface), so I know that it works in principle. But now I want to do it using command line utilities like debootstrap and grub-install." But: "the problem is that the ESC boot menu doesn't show an entry for (the model name of) /dev/sda, so I can't boot into it." My first question would be whether it makes a difference to use [F2] and enter the BIOS/CMOS, rather than [ESC] to get just the boot list. As you could read in another thread, I have been testing the d-i installing on a BIOS machine, using a spare partition, in order to see how it behaves with and without a BIOS Boot partition. However, blanking the entire internal drive on a machine just for this exercise is pushing things a bit too far, sorry. And I'm not sure that results from one of /my/ machines would be particularly useful either. They are either native BIOS booters, or have a compatibility mode that just works, without requiring anything out of the ordinary configured for a GPT disk in BIOS mode. That might not be true for your Asus UX31A. At this point, my action would be to install in BIOS mode using your two methods, conventional d-i and debootstrap, and run bootinfoscript (from package boot-info-script) on each, to look for differences. I would avoid doing any UEFI booting between these runs. Cheers, David.
Re: (Thread restarted!) Debian installation using debootstrap and grub-install - no entry in ESC boot menu
On 26/04/2023 22:57, Valentin Caracalla wrote: the issue with the BIOS boot interface (see my original posting) is still unsolved I had impression that there was no issue with booting in BIOS (legacy, compatibility, CSM) mode, of course when it is chosen in firmware/BIOS setup (requires disabling of secure boot). Perhaps I confused it with qemu instead of bare metal. I tried using the EFI removable media path (which should bypass any issues with EFI variables) without success. This statement might be too strong. Internal drive is not a removable media. My impression is that you can boot from removable media (live CD), but not from internal drive. - Is booting from that internal drive enabled in firmware setup? - Is shim-signed package installed? Just shim is not enough when secure boot is enabled in firmware. I want to install Debian on my Asus UX31A UEFI implementation may have some peculiarities, likely you will find more pages: https://wiki.osdev.org/Broken_UEFI_implementations https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface#Troubleshooting I want to install it to the internal drive /dev/sda, and I want to do so by executing commands on an installer system, which is a system already installed on the external drive /dev/sdb. Does it mean that you have another linux installed and there is no issue with its booting? Is it debian? For now, I only want to get a GRUB command line, because that appears to be the difficult part. Then you do not need debian installer at all. To debug such issues it is enough to copy files to EFI/debian and to run a couple of efibootmgr commands. By the way, you have not posted "efibootmgr -v" or at least "efibootmgr" output. Running it from an existing install or a live media is OK. For the BIOS boot interface: sudo parted /dev/sda mklabel gpt sudo parted /dev/sda mkpart root 512MiB 100% sudo parted /dev/sda set 1 bios_grub on Perhaps you may create both BIOS Boot and EFI System partitions on the same disk to support both modes. For the EFI boot interface: sudo parted /dev/sda mklabel gpt sudo parted /dev/sda mkpart init 0% 512MiB sudo parted /dev/sda set 1 boot on sudo mkfs.vfat /dev/sda1 I do not remember if the "boot" flag sets proper GUID for ESP. I have heard that there may be issues if fat16 is used instead of fat32 https://www.rodsbooks.com/gdisk/booting.html file --special /dev/sda1 parted /dev/sda print sgdisk -p /dev/sda (Some people may be more familiar with output of sgdisk than parted) sudo mount --bind /sys /mnt/sys sudo mount --bind /proc /mnt/proc sudo mount --bind /dev /mnt/dev sudo mount --bind /dev/pts /mnt/dev/pts sudo mount --bind /run /mnt/run I still do not see /sys/firmware/efi/efivars here. Check /mnt/sys/firmware/efi/efivars Frankly speaking, I am confused by your description. I suspect it is a mix of - What you are going to do in future (having working install, prepare a disk for another machine or install a fresh system for the same computer) - What you are really doing - Recipe which way others may try reproduce (boot from a live media and install to an internal drive) Let's concentrate on UEFI. Unless you faced an Asus-specific issue, it should be possible to use qemu+OVMF.
(Thread restarted!) Debian installation using debootstrap and grub-install - no entry in ESC boot menu
Hello Max, thanks a lot for your input! I do, however, believe that the problem has a different cause. I came to that conclusion, mainly because the issue with the BIOS boot interface (see my original posting) is still unsolved, but also because I tried using the EFI removable media path (which should bypass any issues with EFI variables) without success. Therefore, and to make it easier for new people entering this thread, I restart the thread now by asking my original question again, in a single and well arranged posting. You can forget everything you read in the thread before if you just read this one post: Hello everyone, I want to install Debian on my Asus UX31A using command line utilities like debootstrap and grub-install. I want to install it to the internal drive /dev/sda, and I want to do so by executing commands on an installer system, which is a system already installed on the external drive /dev/sdb. To reproduce the issue, you should use a current stable Debian Live-CD as the installer system. Just write the Live-CD image to the external drive /dev/sdb using dd. For now, I only want to get a GRUB command line, because that appears to be the difficult part. Here are the step-by-step instructions to reproduce the problem: 1.: On the installer system, type "sudo apt install ..." to install any dependencies required by the recipe (see below). 2.: On the installer system, exercise one of the following two recipes: For the BIOS boot interface: sudo parted /dev/sda mklabel gpt sudo parted /dev/sda mkpart init 0% 512MiB sudo parted /dev/sda mkpart root 512MiB 100% sudo parted /dev/sda set 1 bios_grub on sudo mkfs.ext4 /dev/sda2 sudo mount /dev/sda2 /mnt sudo debootstrap stable /mnt sudo mount --bind /sys /mnt/sys sudo mount --bind /proc /mnt/proc sudo mount --bind /dev /mnt/dev sudo mount --bind /dev/pts /mnt/dev/pts sudo mount --bind /run /mnt/run sudo chroot /mnt apt install grub-pc sudo chroot /mnt grub-install /dev/sda sudo umount /mnt/run sudo umount /mnt/dev/pts sudo umount /mnt/dev sudo umount /mnt/proc sudo umount /mnt/sys sudo umount /mnt For the EFI boot interface: sudo parted /dev/sda mklabel gpt sudo parted /dev/sda mkpart init 0% 512MiB sudo parted /dev/sda mkpart root 512MiB 100% sudo parted /dev/sda set 1 boot on sudo mkfs.vfat /dev/sda1 sudo mkfs.ext4 /dev/sda2 sudo mount /dev/sda2 /mnt sudo mkdir /mnt/boot sudo mkdir /mnt/boot/efi sudo mount /dev/sda1 /mnt/boot/efi sudo debootstrap stable /mnt sudo mount --bind /sys /mnt/sys sudo mount --bind /proc /mnt/proc sudo mount --bind /dev /mnt/dev sudo mount --bind /dev/pts /mnt/dev/pts sudo mount --bind /run /mnt/run sudo chroot /mnt apt install grub-efi sudo chroot /mnt grub-install --target=x86_64-efi /dev/sda sudo chroot /mnt grub-install --target=x86_64-efi --removable /dev/sda sudo umount /mnt/runsudo umount /mnt/dev/pts sudo umount /mnt/dev sudo umount /mnt/proc sudo umount /mnt/sys sudo umount /mnt/boot/efi sudo umount /mnt Please check every command's output before entering the next one. 3.: Shut down the installer system and disconnect the external drive /dev/sdb. 4.: Start the computer with the ESC key pressed. This will show a list of boot options (the ESC boot menu). The expected behavior is that the list contains an entry for the installed system. Selecting that entry will give you a GRUB command line. The actual behavior is that there is only the "Enter Setup" entry in the list, which is always there and does not do what we want (boot to GRUB command line). That much for the step-by-step instructions. Notice that the EFI variant of the recipe does set the "boot" and "esp" flags and the partition has the recommended size. Also notice that the EFI recipe will create the following directory structure on /dev/sda1: drwxr-xr-x 3 root root 16384 Jan 1 1970 /mnt/boot/efi drwxr-xr-x 4 root root 8192 Apr 26 09:33 /mnt/boot/efi/EFI drwxr-xr-x 2 root root 8192 Apr 26 09:33 /mnt/boot/efi/EFI/BOOT -rwxr-xr-x 1 root root 108 Apr 26 09:33 /mnt/boot/efi/EFI/BOOT/BOOTX64.CSV -rwxr-xr-x 1 root root 934240 Apr 26 09:33 /mnt/boot/efi/EFI/BOOT/BOOTX64.EFI -rwxr-xr-x 1 root root 84648 Apr 26 09:33 /mnt/boot/efi/EFI/BOOT/fbx64.efi -rwxr-xr-x 1 root root 126 Apr 26 09:33 /mnt/boot/efi/EFI/BOOT/grub.cfg -rwxr-xr-x 1 root root 3827136 Apr 26 09:33 /mnt/boot/efi/EFI/BOOT/grubx64.efi -rwxr-xr-x 1 root root 845480 Apr 26 09:33 /mnt/boot/efi/EFI/BOOT/mmx64.efi drwxr-xr-x 2 root root 8192 Apr 26 09:33 /mnt/boot/efi/EFI/debian -rwxr-xr-x 1 root root 108 Apr 26 09:33 /mnt/boot/efi/EFI/debian/BOOTX64.CSV -rwxr-xr-x 1 root root 84648 Apr 26 09:33 /mnt/boot/efi/EFI/debian/fbx64.efi -rwxr-xr-x 1 root root 126 Apr 26 09:33 /mnt/boot/efi/EFI/debian/grub.cfg -rwxr-xr-x 1 root root 4150720 Apr 26 09:33 /mnt/boot/efi/EFI/debian/grubx64.efi -rwxr-xr-x 1 root root 845480 Apr 26 09:33 /mnt/boot/efi/EFI/debian/mmx64.efi -rwxr-xr-x 1 root roo
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
David Wright (12023-04-25): > Don't knock it! The Human Era is much easier for us to parse than ;-) > the French Republican calendar (pre 2018). I had not realized I had fans devoted to the point of tracking the eras of my mail attribution. ;-)² Regards, -- Nicolas George signature.asc Description: PGP signature
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
Greg Wooledge (12023-04-25):
> find /mnt/boot/efi -exec ls -dl {} +
zsh
ls -dl /mnt/boot/efi/**/*
Regards,
--
Nicolas George
signature.asc
Description: PGP signature
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
On Wed 26 Apr 2023 at 09:14:25 (+0700), Max Nikulin wrote: > On 26/04/2023 00:42, Nicolas George wrote: > > Steve McIntyre (12023-04-25): [ … ] > P.S. Nicolas, it seems your mailer has issues with parsing or > formatting timestamps. Don't knock it! The Human Era is much easier for us to parse than the French Republican calendar (pre 2018). Fortunately, we didn't have to deal with decimal time. Cheers, David.
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
On Wed, Apr 26, 2023 at 09:34:11AM +0700, Max Nikulin wrote:
> On 26/04/2023 05:02, Valentin Caracalla wrote:
> >
> > user@host:~$ ls -dl $(find /mnt/boot/efi)
>
> find /mnt/boot/efi -print0 | xargs -0 ls -dl --
>
> should be more resistant to peculiar file names, but it does not matter in
> this case.
find /mnt/boot/efi -exec ls -dl {} +
Also, GNU find has a -ls action, which has a different format, but is
worth a look:
find /mnt/boot/efi -ls
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
On 26/04/2023 05:02, Valentin Caracalla wrote: user@host:~$ ls -dl $(find /mnt/boot/efi) find /mnt/boot/efi -print0 | xargs -0 ls -dl -- should be more resistant to peculiar file names, but it does not matter in this case. ... -rwxr-xr-x 1 root root 126 Apr 25 13:59 /mnt/boot/efi/EFI/debian/grub.cfg -rwxr-xr-x 1 root root 4150720 Apr 25 13:59 /mnt/boot/efi/EFI/debian/grubx64.efi ... Unless firmware is buggy and it requires EFI/BOOT/BOOTX64.EFI removable layout, it should be enough (of course with other files that I removed from the quote). user@host:~$ efibootmgr -v EFI variables are not supported on this system. Either you run it from qemu booted in BIOS mode or you did not mount to chroot (I have never tried to manage EFI variables from chroot) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) Likely it is the reason why installer was not able to create a Boot entry and to adjust BootOrder.
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
On 26/04/2023 00:42, Nicolas George wrote: Steve McIntyre (12023-04-25): If you do not intend to install a Microsoft bootloader or anything besides GRUB, 16 megaoctets is plenty enough, probably can work with less. Please STOP giving this advice to people! That was not advice, that was information. Make your own advice with it. Unified Kernel Images are coming (kernel + initramfs e.g. to avoid separate unencrypted /boot), so even 550MiB may become too small partition in a couple of years. P.S. Nicolas, it seems your mailer has issues with parsing or formatting timestamps.
Re: Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
Valentin Caracalla (12023-04-26): > EFI variables are not supported on this system. To install GRUB in UEFI, you need to have booted the kernel in UEFI. Try to find a live image that does, and you can reinstall GRUB from there. Regards, -- Nicolas George signature.asc Description: PGP signature
Re: Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
Here's the output you requested: user@host:~$ ls -dl $(find /mnt/boot/efi) drwxr-xr-x 3 root root 32768 Jan 1 1970 /mnt/boot/efi drwxr-xr-x 3 root root 32768 Apr 25 13:59 /mnt/boot/efi/EFI drwxr-xr-x 2 root root 32768 Apr 25 13:59 /mnt/boot/efi/EFI/debian -rwxr-xr-x 1 root root 108 Apr 25 13:59 /mnt/boot/efi/EFI/debian/BOOTX64.CSV -rwxr-xr-x 1 root root 84648 Apr 25 13:59 /mnt/boot/efi/EFI/debian/fbx64.efi -rwxr-xr-x 1 root root 126 Apr 25 13:59 /mnt/boot/efi/EFI/debian/grub.cfg -rwxr-xr-x 1 root root 4150720 Apr 25 13:59 /mnt/boot/efi/EFI/debian/grubx64.efi -rwxr-xr-x 1 root root 845480 Apr 25 13:59 /mnt/boot/efi/EFI/debian/mmx64.efi -rwxr-xr-x 1 root root 934240 Apr 25 13:59 /mnt/boot/efi/EFI/debian/shimx64.efiuser@host:~$ efibootmgr -v EFI variables are not supported on this system.
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
Steve McIntyre (12023-04-25): > >If you do not intend to install a Microsoft bootloader or anything > >besides GRUB, 16 megaoctets is plenty enough, probably can work with > >less. > Please STOP giving this advice to people! That was not advice, that was information. Make your own advice with it. -- Nicolas George signature.asc Description: PGP signature
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
Nicolas George wrote: >Max Nikulin (12023-04-25): >> 0.5GB is usually enough, e.g. 550MiB recommended by >> https://www.rodsbooks.com/gdisk/advice.html#esp_sizing) > >If you do not intend to install a Microsoft bootloader or anything >besides GRUB, 16 megaoctets is plenty enough, probably can work with >less. Please STOP giving this advice to people! Running out of space on the ESP may cause a lot of hassle later. *Right now*, GRUB is small. But things do grow over time. Also, if anybody wants to install an extra OS, or use fwupd to install firmware updates (for example), saving a small amount of disk space here could cause a massive PITA later. -- Steve McIntyre, Cambridge, UK.st...@einval.com < sladen> I actually stayed in a hotel and arrived to find a post-it note stuck to the mini-bar saying "Paul: This fridge and fittings are the correct way around and do not need altering"
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
Max Nikulin (12023-04-25): > 0.5GB is usually enough, e.g. 550MiB recommended by > https://www.rodsbooks.com/gdisk/advice.html#esp_sizing) If you do not intend to install a Microsoft bootloader or anything besides GRUB, 16 megaoctets is plenty enough, probably can work with less. Regards, -- Nicolas George signature.asc Description: PGP signature
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
On 25/04/2023 21:40, Valentin Caracalla wrote: I checked my partition table using "sudo parted /dev/sda print" Number Start End Size File system Name Flags 1 1049kB 128GB 128GB fat32 init boot, esp 2 128GB 256GB 128GB ext4 root Please, show ls -lA EFI/BOOT ls -lA EFI/debian residing on /dev/sda1 (128GB sounds like unreasonable large ESP partition, 0.5GB is usually enough, e.g. 550MiB recommended by https://www.rodsbooks.com/gdisk/advice.html#esp_sizing) efibootmgr -v See https://wiki.debian.org/UEFI
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
vorubergeh...@tutanota.com wrote: >By the way: > >The disadvantage of using EFI is that it doesn't work in QEMU, i.e. the >following will not show a GRUB command line: > >sudo qemu-system-x86_64 -accel kvm -smp 2 -m 2G /dev/sda > >The same thing works for the BIOS boot interface, however (as in my original >recipe). That's just qemu-system-x86_64 defaulting to using SeaBIOS for firmware. I boot VMs in UEFI mode all the time, using the EDK2 binary builds in the ovmf package. -- Steve McIntyre, Cambridge, UK.st...@einval.com < sladen> I actually stayed in a hotel and arrived to find a post-it note stuck to the mini-bar saying "Paul: This fridge and fittings are the correct way around and do not need altering"
Re: Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
Valentin Caracalla (12023-04-25): > The disadvantage of using EFI is that it doesn't work in QEMU, i.e. the > following will not show a GRUB command line: > > sudo qemu-system-x86_64 -accel kvm -smp 2 -m 2G /dev/sda Oh, I must check if the KVM virtual machine booting on UEFI I have been toying with these lasts few weeks really exists then. Regards, -- Nicolas George signature.asc Description: PGP signature
Re: Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
By the way: The disadvantage of using EFI is that it doesn't work in QEMU, i.e. the following will not show a GRUB command line: sudo qemu-system-x86_64 -accel kvm -smp 2 -m 2G /dev/sda The same thing works for the BIOS boot interface, however (as in my original recipe).
Re: Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
I apologize for the formatting in my last post, I don't know what happened. And many thanks for your help! I checked my partition table using "sudo parted /dev/sda print" and it didn't show any flags for partition 1 (the "init" partition). Therefore I manually set the flags using "sudo parted /dev/sda set 1 boot on" and now it shows both flags, "boot" and "esp": Model: ATA ADATA XM11 256GB (scsi) Disk /dev/sda: 256GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 128GB 128GB fat32 init boot, esp 2 128GB 256GB 128GB ext4 root However, after reboot, the ESC boot menu still doesn't show an entry for the installed system.
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
Valentin Caracalla writes: > But this doesn't work either. Same problem here. However I can make > such an EFI installation using official installation media on the same > machine and that does work. That recipe (and the whole post) was hard to read but don't you need some flags for the ESP partition, like esp and possibly boot as well? The partition table on one EFI system I have looks like this, I think it's probably what Debian installer created: # parted /dev/nvme0n1 print Model: KINGSTON SA2000M8250G (nvme) Disk /dev/nvme0n1: 250GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start EndSizeFile system NameFlags 1 1049kB 538MB 537MB fat32 boot, esp 2 538MB 249GB 248GB ext4Zippy root 3 249GB 250GB 1024MB linux-swap(v1) Zippy swap swap
Re: Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
> I can't see anything wrong with the script. Did that installation use> GPT > and a BIOS Boot Partition though?The successful installation (with official > installation media) used aBIOS partition table, but I prefer GPT.> I guess I > have to ask, why not just use UEFI?I also tried that and I considered posting > a similar recipe for EFI in thefirst message. But it doesn't work either, so > I thought it is better toask the question with BIOS, because it seemed easier > to me.Here's the recipe for EFI: sudo parted /dev/sda mklabel gpt sudo parted /dev/sda mkpart init 0% 50% sudo parted /dev/sda mkpart root 50% 100% sudo mkfs.vfat /dev/sda1 sudo mkfs.ext4 /dev/sda2 sudo mount /dev/sda2 /mnt sudo mkdir /mnt/boot sudo mkdir /mnt/boot/efi sudo mount /dev/sda1 /mnt/boot/efi sudo debootstrap stable /mnt sudo mount --bind /sys /mnt/sys sudo mount --bind /proc /mnt/proc sudo mount --bind /dev /mnt/dev sudo mount --bind /dev/pts /mnt/dev/pts sudo mount --bind /run /mnt/run sudo chroot /mnt apt install grub-efi sudo chroot /mnt grub-install /dev/sda sudo umount /mnt/run sudo umount /mnt/dev/pts sudo umount /mnt/dev sudo umount /mnt/proc sudo umount /mnt/sys sudo umount /mnt/boot/efi sudo umount /mntBut this doesn't work either. Same problem here. However I can make such anEFI installation using official installation media on the same machine andthat does work.
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
There are a few things I forgot to say: The recipe I posted earlier is executed on a system installed on the external drive /dev/sdb, which I call the installer system. It is also a Debian system, with the recipe's dependencies installed. To reproduce the issue (if you want), I suggest using a Debian Live-CD. After installation and before attempting to boot I unplug the external drive to make sure it doesn't interfere with the boot process. With the external drive unplugged, there should be exactly one entry in the ESC boot menu, but there is none: It only offers me to enter setup, and that is what it does when I boot without pressing ESC. Instead of booting the computer directly, I also tried booting the internal drive in a VM executed on the installer system using the following command: sudo qemu-system-x86_64 -accel kvm -smp 2 -m 2G /dev/sda This will show a GRUB command line as I expected. It just doesn't work on the real system, but in the VM it works (I hate that).
Re: Debian installation using debootstrap and grub-install - no entry in ESC boot menu
Valentin Caracalla writes: > Previously, I've successfully installaed Debian using official > installation media on this machine (also using BIOS boot interface), > so I know that it works in principle. I can't see anything wrong with the script. Did that installation use GPT and a BIOS Boot Partition though? I guess I have to ask, why not just use UEFI?
Debian installation using debootstrap and grub-install - no entry in ESC boot menu
Hello everyone, I'm trying to install Debian on my Asus UX31A using command line utilities like debootstrap and grub-install. However, the installed system is not bootable. The problem is that the internal drive (which I install the system to) doesn't show up in the boot menu (which is what the user sees when pressing ESC during power-on). I created a minimalist recipe demonstrating the issue: sudo parted /dev/sda mklabel gpt sudo parted /dev/sda mkpart init 0% 50% sudo parted /dev/sda mkpart root 50% 100% sudo parted /dev/sda set 1 bios_grub on sudo mkfs.ext4 /dev/sda2 sudo mount /dev/sda2 /mnt sudo debootstrap stable /mnt sudo mount --bind /sys /mnt/sys sudo mount --bind /proc /mnt/proc sudo mount --bind /dev /mnt/dev sudo mount --bind /dev/pts /mnt/dev/pts sudo mount --bind /run /mnt/run sudo chroot /mnt apt install grub-pc sudo chroot /mnt grub-install /dev/sda sudo umount /mnt/run sudo umount /mnt/dev/pts sudo umount /mnt/dev sudo umount /mnt/proc sudo umount /mnt/sys sudo umount /mnt I've intentionally stripped the parts concerning installation of a kernel and creating configuration files like grub.cfg and fstab, these things work already. For now, all I want to see is that the user can get a GRUB command line after power-on. The grub-install command outputs "Installation finished. No error reported." and therefore I expect being able to boot into the GRUB command line. But again, the problem is that the ESC boot menu doesn't show an entry for (the model name of) /dev/sda, so I can't boot into it. Previously, I've successfully installed Debian using official installation media on this machine (also using BIOS boot interface), so I know that it works in principle. But now I want to do it using command line utilities like debootstrap and grub-install. Any help would be very appreciated. Kind regards, Valentin Caracalla
Re: (deb-cat) Actualitzar Debootstrap
_ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 10/9/22 a les 11:45, Xavier Drudis Ferran ha escrit: M'alegro que ho hagis arreglat. El Fri, Sep 09, 2022 at 01:56:06PM +0200, Narcis Garcia deia: El què esperava és una manera més ben prevista d'afrontar aquestes situacions, en comptes d'haver de collir Debootstrap de repositoris no previstos. Per exemple, un web amb la última versió i binaris descarregables per a les distribucions. Per a mi un repositori ja és una web amb la última versió i binaris descarregables. Hi ha massa distribucions per fer un paquet per a cadascuna i anar-los mantenint. I aparentment no cal. O que el mateix Debootstrap tingués alguna opció de descàrrega dels últims «scripts» (deboostrap update-scripts). No sé, no hi haurà conflictes quan després actualizessis el debootstrap pel repositori de la distro d'on el vas instal·lar inicialment ? La manera és que els «scripts» nous es descarreguessin a: /var/debootstrap/scripts/ I que si el mateix nom tant existeix a /usr/share/debootstrap/scripts/ com a /var/debootstrap/scripts/ aleshores prevalgui el nou. D'aquesta manera, al paquet només ha de constar el directori /var/debootstrap/scripts i no cap contingut a dins.
Re: (deb-cat) Actualitzar Debootstrap
M'alegro que ho hagis arreglat. El Fri, Sep 09, 2022 at 01:56:06PM +0200, Narcis Garcia deia: > > El què esperava és una manera més ben prevista d'afrontar aquestes > situacions, en comptes d'haver de collir Debootstrap de repositoris no > previstos. > Per exemple, un web amb la última versió i binaris descarregables per a les > distribucions. Per a mi un repositori ja és una web amb la última versió i binaris descarregables. Hi ha massa distribucions per fer un paquet per a cadascuna i anar-los mantenint. I aparentment no cal. > O que el mateix Debootstrap tingués alguna opció de > descàrrega dels últims «scripts» (deboostrap update-scripts). > No sé, no hi haurà conflictes quan després actualizessis el debootstrap pel repositori de la distro d'on el vas instal·lar inicialment ?
Re: (deb-cat) Actualitzar Debootstrap
Hola, Narcis: > El què esperava és una manera més ben prevista d'afrontar > aquestes situacions, en comptes d'haver de collir Debootstrap > de repositoris no previstos. Una manera més fàcil d'obtenir totes les versions és amb debsnap. > un web amb la última versió i binaris descarregables per a les > distribucions. Aquesta web ja existeix: https://salsa.debian.org/installer-team/debootstrap/-/tree/master/scripts > O que el mateix Debootstrap tingués alguna opció de descàrrega > dels últims «scripts» (deboostrap update-scripts) T'animo a suggerir aquesta funcionalitat amb el reportbug. Salut, Alex -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Re: (deb-cat) Actualitzar Debootstrap
__ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 10/9/22 a les 8:01, Eloi ha escrit: El 8/9/22 a les 11:58, Narcis Garcia ha escrit: Bon dia, Tinc un ordinador amb Ubuntu GNU/Linux 14.04 (trusty) i386, i hi vull fer un «debootstrap» per a instal·lar Debian 9 (stretch) amd64 en un subdirectori. El cas és que l'últim perfil de Debian que té el Debootstrap en aquest entorn tant antic (que no haig d'actualitzar) és per a «jessie» (Debian 8). Hi ha alguna font d'actualització de «scripts» de Debian per a casos així? Gràcies. https://packages.debian.org/sid/debootstrap En aquest cas en particular, les dependències del paquet són tan poques i tan fàcilment resolubles (l'únic requisit indispensable és wget i ni tan sols està versionat) que et permeten poder agafar el .deb de sid fàcilment i instal·lar-lo manualment on vulguis. Tot i que només s'hi publica paquet «binari» per a Debian i derivats (dpkg), veig que el codi font que també hi ha empaquetat (.tar.gz) és executable directament a qualsevol sistema GNU. Gràcies.
Re: (deb-cat) Actualitzar Debootstrap
El 8/9/22 a les 11:58, Narcis Garcia ha escrit: Bon dia, Tinc un ordinador amb Ubuntu GNU/Linux 14.04 (trusty) i386, i hi vull fer un «debootstrap» per a instal·lar Debian 9 (stretch) amd64 en un subdirectori. El cas és que l'últim perfil de Debian que té el Debootstrap en aquest entorn tant antic (que no haig d'actualitzar) és per a «jessie» (Debian 8). Hi ha alguna font d'actualització de «scripts» de Debian per a casos així? Gràcies. https://packages.debian.org/sid/debootstrap En aquest cas en particular, les dependències del paquet són tan poques i tan fàcilment resolubles (l'únic requisit indispensable és wget i ni tan sols està versionat) que et permeten poder agafar el .deb de sid fàcilment i instal·lar-lo manualment on vulguis.
Re: (deb-cat) Actualitzar Debootstrap
__ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors. El 9/9/22 a les 13:02, Xavier Drudis Ferran ha escrit: El Thu, Sep 08, 2022 at 11:58:01AM +0200, Narcis Garcia deia: Bon dia, Tinc un ordinador amb Ubuntu GNU/Linux 14.04 (trusty) i386, i hi vull fer un «debootstrap» per a instal·lar Debian 9 (stretch) amd64 en un subdirectori. El cas és que l'últim perfil de Debian que té el Debootstrap en aquest entorn tant antic (que no haig d'actualitzar) és per a «jessie» (Debian 8). Hi ha alguna font d'actualització de «scripts» de Debian per a casos així? Gràcies. No sé si t'entenc, però debootstrap no és un paquet normal, és més portable. https://wiki.debian.org/Debootstrap Potser pots instal·lar un debootstrap de Debian >= 9 a l'Ubuntu directament. I si no vol, agafes un deboostrap instal·lat a un altre ordinador i copies els fitxers del paquet a l'Ubuntu. hauria de ser només /usr/share/debootstrap/* i /usr/sbin/debootstrap si passes de la documentació. I si no dpkg -L debootstrap et dirà quins fitxers té la versió que tinguis instal·lada. No ho he provat mai, però igual cola. Potser li has de passar més parametres sobre repositoris o alguna cosa, però vaja... Una altra cosa es veure com arrenques del directori un cop instal·lat si no és l'arrel d'alguna partició. Ho tens pensat ? Ja ho tinc més o menys fet: He instal·lat «manualment» el paquet Debootstrap d'Ubuntu 16.04, he creat una memòria USB arrencable (Debian 9), i una vegada iniciat allà he fet això per a convertir-ho a 64Bits: sudo dpkg --add-architecture amd64 sudo apt-get update sudo apt-get install linux-image-amd64 sudo reboot sudo apt-get install dpkg:amd64 tar:amd64 apt:amd64 sudo apt-get -f install Després ja només ha estat qüestió de fer servir Debootstrap una altra vegada per a instal·lar Debian versió Stable al disc dur (formatejat), en la nova arquitectura. El què esperava és una manera més ben prevista d'afrontar aquestes situacions, en comptes d'haver de collir Debootstrap de repositoris no previstos. Per exemple, un web amb la última versió i binaris descarregables per a les distribucions. O que el mateix Debootstrap tingués alguna opció de descàrrega dels últims «scripts» (deboostrap update-scripts). Salut.
Re: (deb-cat) Actualitzar Debootstrap
El Thu, Sep 08, 2022 at 11:58:01AM +0200, Narcis Garcia deia: > Bon dia, > > Tinc un ordinador amb Ubuntu GNU/Linux 14.04 (trusty) i386, i hi vull fer un > «debootstrap» per a instal·lar Debian 9 (stretch) amd64 en un subdirectori. > > El cas és que l'últim perfil de Debian que té el Debootstrap en aquest > entorn tant antic (que no haig d'actualitzar) és per a «jessie» (Debian 8). > Hi ha alguna font d'actualització de «scripts» de Debian per a casos així? > > Gràcies. > No sé si t'entenc, però debootstrap no és un paquet normal, és més portable. https://wiki.debian.org/Debootstrap Potser pots instal·lar un debootstrap de Debian >= 9 a l'Ubuntu directament. I si no vol, agafes un deboostrap instal·lat a un altre ordinador i copies els fitxers del paquet a l'Ubuntu. hauria de ser només /usr/share/debootstrap/* i /usr/sbin/debootstrap si passes de la documentació. I si no dpkg -L debootstrap et dirà quins fitxers té la versió que tinguis instal·lada. No ho he provat mai, però igual cola. Potser li has de passar més parametres sobre repositoris o alguna cosa, però vaja... Una altra cosa es veure com arrenques del directori un cop instal·lat si no és l'arrel d'alguna partició. Ho tens pensat ?
(deb-cat) Actualitzar Debootstrap
Bon dia, Tinc un ordinador amb Ubuntu GNU/Linux 14.04 (trusty) i386, i hi vull fer un «debootstrap» per a instal·lar Debian 9 (stretch) amd64 en un subdirectori. El cas és que l'últim perfil de Debian que té el Debootstrap en aquest entorn tant antic (que no haig d'actualitzar) és per a «jessie» (Debian 8). Hi ha alguna font d'actualització de «scripts» de Debian per a casos així? Gràcies. -- Narcis Garcia __ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors.
Re: Buster install using debootstrap. (SOLVED)
On 6/5/20 6:31 PM, Marc Shapiro wrote: On 6/4/20 11:30 PM, Sven Hartge wrote: Marc Shapiro wrote: I also don't understand why it says that it could not create temporary files in /tmp. I am running this as root and /tmp is owned by root. What am I missing? /tmp (and /var/tmp/) should have the following permissions and rights: root:root 1777/drwxrwxrwt apt runs its I/O processes as a different user "_apt" and if /tmp does not have the sticky bit set, then it cannot create any files there, causing the error. Grüße, Sven. Thanks! That took care of all the debian repositories. Third party repositories are now having public key issues (not surprising). How do I get and install the public key for deb-multimedia.org and virtualbox.org? Marc I got the public keys for deb-multimedia.org and virtualbox.org and all is good. I just needed to google a little more (after having some dinner). Marc
Re: Buster install using debootstrap.
On 6/4/20 11:30 PM, Sven Hartge wrote: Marc Shapiro wrote: I also don't understand why it says that it could not create temporary files in /tmp. I am running this as root and /tmp is owned by root. What am I missing? /tmp (and /var/tmp/) should have the following permissions and rights: root:root 1777/drwxrwxrwt apt runs its I/O processes as a different user "_apt" and if /tmp does not have the sticky bit set, then it cannot create any files there, causing the error. Grüße, Sven. Thanks! That took care of all the debian repositories. Third party repositories are now having public key issues (not surprising). How do I get and install the public key for deb-multimedia.org and virtualbox.org? Marc
Re: Buster install using debootstrap.
On Fri, Jun 05, 2020 at 08:30:16AM +0200, Sven Hartge wrote:
> Marc Shapiro wrote:
>
> > I also don't understand why it says that it could not create temporary
> > files in /tmp. I am running this as root and /tmp is owned by root.
> > What am I missing?
>
> /tmp (and /var/tmp/) should have the following permissions and rights:
>
> root:root 1777/drwxrwxrwt
>
> apt runs its I/O processes as a different user "_apt" and if /tmp does
> not have the sticky bit set, then it cannot create any files there,
> causing the error.
>
Another thing to check (which may or may not apply in this particular
instance) is any special TMP/TEMP/TMPDIR/TEMPDIR environment variable
handling in the host environment. On my systems I use pam_tmpdir, which
creates a user-specific temporary directory (/tmp/user/${UID}) and then
sets the TMP/TEMP/TMPDIR/TEMPDIR environment variables to that path.
When I chroot into an environment, I must take care to either ensure
those variables are unset inside the chroot or to create the necessary
directory structure with matching ownership and permissions.
Another solution is to bind mount /tmp from the host into the chroot.
Regards,
-Roberto
--
Roberto C. Sánchez
Re: Buster install using debootstrap.
Greg Wooledge wrote: > On Fri, Jun 05, 2020 at 08:30:16AM +0200, Sven Hartge wrote: >> Marc Shapiro wrote: >>> I also don't understand why it says that it could not create temporary >>> files in /tmp. I am running this as root and /tmp is owned by root. >>> What am I missing? >> >> /tmp (and /var/tmp/) should have the following permissions and rights: >> >> root:root 1777/drwxrwxrwt >> >> apt runs its I/O processes as a different user "_apt" and if /tmp does >> not have the sticky bit set, then it cannot create any files there, >> causing the error. > To be completely clear, it's the world-write bit that allows _apt to > create files/subdirectories there. The sticky bit prevents other > users from removing or renaming said files/subdirectories while _apt > is using them. Eh, yes, of course. Was ahead in my thoughts and mixed both facts together. Grüße, Sven. -- Sigmentation fault. Core dumped.
Re: Buster install using debootstrap.
On Fri, Jun 05, 2020 at 08:30:16AM +0200, Sven Hartge wrote: > Marc Shapiro wrote: > > > I also don't understand why it says that it could not create temporary > > files in /tmp. I am running this as root and /tmp is owned by root. > > What am I missing? > > /tmp (and /var/tmp/) should have the following permissions and rights: > > root:root 1777/drwxrwxrwt > > apt runs its I/O processes as a different user "_apt" and if /tmp does > not have the sticky bit set, then it cannot create any files there, > causing the error. To be completely clear, it's the world-write bit that allows _apt to create files/subdirectories there. The sticky bit prevents other users from removing or renaming said files/subdirectories while _apt is using them.
Re: Buster install using debootstrap.
Marc Shapiro wrote: > I also don't understand why it says that it could not create temporary > files in /tmp. I am running this as root and /tmp is owned by root. > What am I missing? /tmp (and /var/tmp/) should have the following permissions and rights: root:root 1777/drwxrwxrwt apt runs its I/O processes as a different user "_apt" and if /tmp does not have the sticky bit set, then it cannot create any files there, causing the error. Grüße, Sven. -- Sigmentation fault. Core dumped.
Buster install using debootstrap.
I have just installed Buster on a spare set of partitions using debootstrap, as documented in: Appendix D.3 of the Installation Guide. When I got to configuring networking, I just copied /etc/networking/interfaces, /etc/hosts, /etc/hostname, and /etc/resolv.conf from my Stretch partitions/directories to the Buster partitions/directories. I also copied /etc/apt/sources.list and /etc/fstab from Stretch to Buster, editing them as needed. I have chrooted into Buster and everything looks good. I can run 'apt show' and 'dpkg -l' (I like the way the new dpkg lets you scroll through the list instead of just running to the end.) What I can not do is 'apt update'. When I try that, I get the following output: # apt update Get:1 http://security.debian.org buster/updates InRelease [65.4 kB] Err:1 http://security.debian.org buster/updates InRelease Couldn't create temporary file /tmp/apt.conf.UOJmdX for passing config to apt-key Get:2 http://download.virtualbox.org/virtualbox/debian buster InRelease [7736 B] Err:2 http://download.virtualbox.org/virtualbox/debian buster InRelease Couldn't create temporary file /tmp/apt.conf.9n943a for passing config to apt-key Get:4 http://http.us.debian.org/debian buster InRelease [121 kB] Err:4 http://http.us.debian.org/debian buster InRelease Couldn't create temporary file /tmp/apt.conf.1btx9y for passing config to apt-key Get:3 http://cdn-fastly.deb.debian.org/debian buster-backports InRelease [46.7 kB] Err:3 http://cdn-fastly.deb.debian.org/debian buster-backports InRelease Couldn't create temporary file /tmp/apt.conf.G6FHYS for passing config to apt-key Get:5 http://www.deb-multimedia.org buster InRelease [19.5 kB] Err:5 http://www.deb-multimedia.org buster InRelease Couldn't create temporary file /tmp/apt.conf.Iqzykk for passing config to apt-key Get:6 http://www.deb-multimedia.org buster-backports InRelease [10.4 kB] Err:6 http://www.deb-multimedia.org buster-backports InRelease Couldn't create temporary file /tmp/apt.conf.Sb90kl for passing config to apt-key Reading package lists... Done W: GPG error: http://security.debian.org buster/updates InRelease: Couldn't create temporary file /tmp/apt.conf.UOJmdX for passing config to apt-key E: The repository 'http://security.debian.org buster/updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://download.virtualbox.org/virtualbox/debian buster InRelease: Couldn't create temporary file /tmp/apt.conf.9n943a for passing config to apt-key E: The repository 'http://download.virtualbox.org/virtualbox/debian buster InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://http.us.debian.org/debian buster InRelease: Couldn't create temporary file /tmp/apt.conf.1btx9y for passing config to apt-key E: The repository 'http://http.us.debian.org/debian buster InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://cdn-fastly.deb.debian.org/debian buster-backports InRelease: Couldn't create temporary file /tmp/apt.conf.G6FHYS for passing config to apt-key E: The repository 'http://http.debian.net/debian buster-backports InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://www.deb-multimedia.org buster InRelease: Couldn't create temporary file /tmp/apt.conf.Iqzykk for passing config to apt-key E: The repository 'http://www.deb-multimedia.org buster InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://www.deb-multimedia.org buster-backports InRelease: Couldn't create temporary file /tmp/apt.conf.Sb90kl for passing config to apt-key E: The repository 'http://www.deb-multimedia.org buster-backports InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. I read the manpage for apt-secure and I am assuming that I am missing the GPG keys, but I did not see anything about this in the Installation Guide. I'm sure that I missed something, somewhere, but I don't know what. I also don't understand why it says that it could not create temporary files in /tmp. I
Re: Cross debootstrap without root rights
Hi Josch, [I did not get your email, I just saw it in the mail archives...] thanks for the overview and the reference to the bug ticket. I've succeeded with the fakechroot/fakeroot approach and got the required inspiration for setting LD_LIBRARY_PATH from your tool and https://bugs.debian.org/855234 <https://bugs.debian.org/829134> (libsystemd-shared wanted to be found as well). Thanks for your help, Christoph Hi, > > (please CC me, I'm not subscribed to d-user@l.d.o) > > Quoting Christoph Müllner (2020-02-09 12:54:56) > > I'd like to run the second stage of debootstrap without root rights, but > for > > another architecture (host is x86_64 and target is arm64). > > > > I know how to do all that with root rights (i.e qemu-aarch64-static works > > perfectly here, also, I can recommend using qemu-debootstrap), but I > can't > > figure out a way how to do that without root rights. > > > > I was expecting that fakechroot and fakeroot will do the necessary > "magic" to > > make chroot work for my use-case, but that's not the case (I need to have > > libfakeroot.so and libfakechroot.so in the target rootfs, but I could not > > find a reliable way to get them in). > > > > I found some emails in the archives about similar use cases (from ~10 > years > > ago). But I failed to identify the solution in those cases. > > > > Therefore I'd like to ask if anyone has a solution for my use case or > some > > hints/pointers. > > yes, there are several solutions. Either: > > a) You can use mmdebstrap which is a debootstrap replacement that focuses > on >not requiring superuser privileges and has foreign architecture support >built in: > >$ mmdebstrap --arch=arm64 unstable debian-unstable.tar > > b) There is a proof-of-concept that allows one to run debootstrap with >unprivileged usernamespaces here: https://bugs.debian.org/829134 This > will >probably also work with --second-stage > > c) Getting fakechroot and fakeroot to work with foreign architectures is > tricky >and requires the right libfakechroot.so being installed and several >environment variables to be set differently. You can have a look at how >mmdebstrap does this so that you can maybe replicate that for > debootstrap: >https://sources.debian.org/src/mmdebstrap/0.6.0-4/mmdebstrap/#L1942 > > Thanks! > > cheers, josch > > On Sun, Feb 9, 2020 at 12:54 PM Christoph Müllner > wrote: > >> Hi Debian users, >> >> I'd like to run the second stage of debootstrap without root rights, >> but for another architecture (host is x86_64 and target is arm64). >> >> I know how to do all that with root rights (i.e qemu-aarch64-static works >> perfectly here, >> also, I can recommend using qemu-debootstrap), but I can't figure out a >> way how to do >> that without root rights. >> >> I was expecting that fakechroot and fakeroot will do the necessary "magic" >> to make chroot work for my use-case, but that's not the case (I need to >> have libfakeroot.so >> and libfakechroot.so in the target rootfs, but I could not find a >> reliable way to get them in). >> >> I found some emails in the archives about similar use cases (from ~10 >> years ago). >> But I failed to identify the solution in those cases. >> >> Therefore I'd like to ask if anyone has a solution for my use case or >> some hints/pointers. >> >> Thanks, >> Christoph >> >>
Re: Cross debootstrap without root rights
Hi Hector, thanks for the pointer to debos. That tool seems to fit quite well (especially the ability to invoke user scripts for customizations), although access to /dev/kvm is quite some price to pay (but already much much better than root rights). Thanks a lot, Christoph On Sun, Feb 9, 2020 at 6:14 PM Hector Oron wrote: > > Hello Christoph, > > Missatge de Christoph Müllner del dia dg., 9 > de febr. 2020 a les 12:55: > > > I was expecting that fakechroot and fakeroot will do the necessary "magic" > > to make chroot work for my use-case, but that's not the case (I need to have libfakeroot.so > > and libfakechroot.so in the target rootfs, but I could not find a reliable way to get them in). > > > > I found some emails in the archives about similar use cases (from ~10 years ago). > > But I failed to identify the solution in those cases. > > Nowadays I use debos if I need to create rootless filesystems, you can > read the following article to get an idea how it works: > https://ekaia.org/blog/2018/07/03/introducing-debos/ > > Regards > -- > Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.
Re: Cross debootstrap without root rights
Hi Jonas, thanks for the pointer. I was hoping for a solution like mmdebstrap. Will give it a try or will at least use it as inspiration. Thanks a lot, Christoph On Sun, Feb 9, 2020 at 1:25 PM Jonas Smedegaard wrote: > Hi Christoph, > > Quoting Christoph Müllner (2020-02-09 12:54:56) > > I'd like to run the second stage of debootstrap without root rights, > > but for another architecture (host is x86_64 and target is arm64). > > > > I know how to do all that with root rights (i.e qemu-aarch64-static > > works perfectly here, also, I can recommend using qemu-debootstrap), > > but I can't figure out a way how to do that without root rights. > > > > I was expecting that fakechroot and fakeroot will do the necessary > > "magic" to make chroot work for my use-case, but that's not the case > > (I need to have libfakeroot.so and libfakechroot.so in the target > > rootfs, but I could not find a reliable way to get them in). > > > > I found some emails in the archives about similar use cases (from ~10 > > years ago). But I failed to identify the solution in those cases. > > > > Therefore I'd like to ask if anyone has a solution for my use case or > > some hints/pointers. > > Have a look at mmdebstrap! > > The author of that tool - Johannes Schauer - has long fought for ways to > eliminate the need for being root to bootstrap Debian, and mmdebstrap is > as I understand it the state of the art of that! > > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private >
Re: Cross debootstrap without root rights
Hello Christoph, Missatge de Christoph Müllner del dia dg., 9 de febr. 2020 a les 12:55: > I was expecting that fakechroot and fakeroot will do the necessary "magic" > to make chroot work for my use-case, but that's not the case (I need to have > libfakeroot.so > and libfakechroot.so in the target rootfs, but I could not find a reliable > way to get them in). > > I found some emails in the archives about similar use cases (from ~10 years > ago). > But I failed to identify the solution in those cases. Nowadays I use debos if I need to create rootless filesystems, you can read the following article to get an idea how it works: https://ekaia.org/blog/2018/07/03/introducing-debos/ Regards -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.
Re: Cross debootstrap without root rights
Hi, (please CC me, I'm not subscribed to d-user@l.d.o) Quoting Christoph Müllner (2020-02-09 12:54:56) > I'd like to run the second stage of debootstrap without root rights, but for > another architecture (host is x86_64 and target is arm64). > > I know how to do all that with root rights (i.e qemu-aarch64-static works > perfectly here, also, I can recommend using qemu-debootstrap), but I can't > figure out a way how to do that without root rights. > > I was expecting that fakechroot and fakeroot will do the necessary "magic" to > make chroot work for my use-case, but that's not the case (I need to have > libfakeroot.so and libfakechroot.so in the target rootfs, but I could not > find a reliable way to get them in). > > I found some emails in the archives about similar use cases (from ~10 years > ago). But I failed to identify the solution in those cases. > > Therefore I'd like to ask if anyone has a solution for my use case or some > hints/pointers. yes, there are several solutions. Either: a) You can use mmdebstrap which is a debootstrap replacement that focuses on not requiring superuser privileges and has foreign architecture support built in: $ mmdebstrap --arch=arm64 unstable debian-unstable.tar b) There is a proof-of-concept that allows one to run debootstrap with unprivileged usernamespaces here: https://bugs.debian.org/829134 This will probably also work with --second-stage c) Getting fakechroot and fakeroot to work with foreign architectures is tricky and requires the right libfakechroot.so being installed and several environment variables to be set differently. You can have a look at how mmdebstrap does this so that you can maybe replicate that for debootstrap: https://sources.debian.org/src/mmdebstrap/0.6.0-4/mmdebstrap/#L1942 Thanks! cheers, josch signature.asc Description: signature
Re: Cross debootstrap without root rights
[ sent again, without 8bit headers to please Debian MTAs ] Hi Christoph, Quoting Christoph Müllner (2020-02-09 12:54:56) > I'd like to run the second stage of debootstrap without root rights, > but for another architecture (host is x86_64 and target is arm64). > > I know how to do all that with root rights (i.e qemu-aarch64-static > works perfectly here, also, I can recommend using qemu-debootstrap), > but I can't figure out a way how to do that without root rights. > > I was expecting that fakechroot and fakeroot will do the necessary > "magic" to make chroot work for my use-case, but that's not the case > (I need to have libfakeroot.so and libfakechroot.so in the target > rootfs, but I could not find a reliable way to get them in). > > I found some emails in the archives about similar use cases (from ~10 > years ago). But I failed to identify the solution in those cases. > > Therefore I'd like to ask if anyone has a solution for my use case or > some hints/pointers. Have a look at mmdebstrap! The author of that tool - Johannes Schauer - has long fought for ways to eliminate the need for being root to bootstrap Debian, and mmdebstrap is as I understand it the state of the art of that! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Cross debootstrap without root rights
Hi Debian users, I'd like to run the second stage of debootstrap without root rights, but for another architecture (host is x86_64 and target is arm64). I know how to do all that with root rights (i.e qemu-aarch64-static works perfectly here, also, I can recommend using qemu-debootstrap), but I can't figure out a way how to do that without root rights. I was expecting that fakechroot and fakeroot will do the necessary "magic" to make chroot work for my use-case, but that's not the case (I need to have libfakeroot.so and libfakechroot.so in the target rootfs, but I could not find a reliable way to get them in). I found some emails in the archives about similar use cases (from ~10 years ago). But I failed to identify the solution in those cases. Therefore I'd like to ask if anyone has a solution for my use case or some hints/pointers. Thanks, Christoph
Re: debootstrap et après ?
Merci pour le coup de main, je viens de finir l'installation et ça marche ! Mais j'ai une petite chose qui m'énerve ! Lors de 'installation j'ai entré un mot de passe pour root et je n'ai pas créé de compte utilisateur. Evidemment une fois fini j'ai créé un compte utilisateur et installé sudo. Pour configurer sudo j'ai créé un fichier dans le répertoire "sudoers.d" dans lequel j'ai écris la ligne : "moiALL=(ALL:ALL) ALL" Puis j'ai installé le paquet "lxpolkit" pour monter facilement les partitons sous le gestionnaire de fichier "pcmanfm". Mais lorsque je veux monter une partition la fenêtre de "lxpolkit" affiche "root" et seulement "root" puis je rentre le mot de passe correspondant et cela fonctionne mais je n'arrive pas à faire afficher "moi" dans cette fenêtre ! J'ai désactivé le compte "root" avec "usermod -L root" puis avec "usermod -e 1 -L root" mais dans les 2 cas la fenêtre de "lxpolkit" continu à afficher "root" et bien sûr comme j'ai désativé le compte "root" le mot de passe ne fonctionne plus. Enfin j'ai essayé de supprimer le compte "root" en m'assurant que "sudo" fonctionné bien avec le compte "moi" mais la commande suivante : "deluser --force root" indique le message d'erreur numéro 8 correspondant à un problème "perl". J'ai rinstallé le paquet "perl" mais rien n'y fait : impossible de supprimer "root". Une précision qui n'a peut être aucune importance je ne suis pas sous un bureau mais sous openbox. Si vous avez une idée ? Merci d'avance pour l'aide. -- Sent from: http://debian.2.n7.nabble.com/debian-user-french-f1152225.html
Re: debootstrap et après ?
13 novembre 2019 07:52 "machinSuite" a écrit: > Pour buster 10.1.0 je suppose que l'installateur classique de debian > (graphique ou non) fait le choix d'un noyau modulaire et des fichiers > dynamiques (utilisation de udev). Aussi je souhaite maintenant faire la même > chose mais à la main et c'est là que cela coince ! Faut-il installer un > paquet qui finie de remplir le répertoire /dev des fichiers de périphériques > comme je le souhaite ? Le montage bind est la solution la plus directe. Avant d'entrer dans ton chroot : mount /dev /mnt/debinst/ -o bind Tu auras besoin de le faire avec d'autres points de montage (de mémoire) : - /dev/pts - /proc - /sys Sinon, tu peux remplacer l'utilisation de `chroot` par `schroot` (paquet éponyme) qui se chargera pour toi de tout ça (et bien plus encore). Sébastien
debootstrap et après ?
Bonjour à tous. Aujourd'hui je cherche à savoir comment créer les fichiers périphériques manuellement sous buster 10.1.0 après avoir fait une installation minimale à l'aide de debootstrap. Dans la documentation officielle d'installation de debian concernant debootstrap j'ai tapé en adapatant : * mes commandes mkfs.ext4 -v /dev/sda4 mkswap /dev/sda5 sync swapon /dev/sda5 mkdir /mnt/debinst mount /dev/sda4 /mnt/debinst mount firmware-10.1.0-amd64-DVD-1.iso /median/cdrom/ debootstrap --no-check-gpg buster /mnt/debinst/ file:///media/cdrom/debian/ LANG=C.UTF-8 chroot /mnt/debinst /bin/bash * fin C'est alors que je dois créer les fichiers périphériques ! Dans la documentation d'installation les choses suivantes sont indiquées : * documentation d'installation Pour l'instant, /dev/ contient seulement des fichiers élémentaires. D'autres fichiers seront nécessaires pour les prochaines étapes de l'installation. La manière de les créer dépend du système sur lequel l'installation se fait ; elle dépend aussi du noyau que vous utiliserez (modulaire ou pas) et du choix entre fichiers dynamiques (en utilisant udev) ou fichiers statiques pour le nouveau système. Voici quelques options disponibles : - installer le paquet makedev et créer un ensemble standard de fichiers de périphériques statiques avec : # apt install makedev # mount none /proc -t proc # cd /dev # MAKEDEV generic - créer seulement quelques fichiers choisis avec la commande MAKEDEV ; - monter (option bind) le répertoire /dev du système hôte sur le répertoire /dev du système cible. Il faut remarquer que les scripts postinst de certains paquets peuvent essayer de créer des fichiers de périphériques ; cette option doit être employée avec précaution. * fin Pour buster 10.1.0 je suppose que l'installateur classique de debian (graphique ou non) fait le choix d'un noyau modulaire et des fichiers dynamiques (utilisation de udev). Aussi je souhaite maintenant faire la même chose mais à la main et c'est là que cela coince ! Faut-il installer un paquet qui finie de remplir le répertoire /dev des fichiers de périphériques comme je le souhaite ? Merci d'avance pour les infos ou docs à lire. -- Sent from: http://debian.2.n7.nabble.com/debian-user-french-f1152225.html
Re: fakeroot fakechroot debootstrap fails on buster
On 2/3/19, Per Sandberg wrote:
> To reproduce:
>
> On a plain debian buster:
>
> Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US:en (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Run the command:
> fakeroot fakechroot debootstrap --verbose --variant=fakechroot
> buster ${WORKSPACE}/buster
>
> Ends up with a lot of warnings
> dpkg: warning: ignoring pre-dependency problem!
>
> And fails finally with a lot of errors with this pattern:
> --
> Adding 'diversion of /bin/sh to /bin/sh.distrib by dash'
> mv: cannot move '/bin/sh.tmp' to '/bin/sh': No such file or directory
> dpkg: error processing package dash (--configure):
> installed dash package post-installation script subprocess returned
> error exit status 1
> Setting up init-system-helpers (1.56+nmu1) ...
> Setting up binutils (2.31.1-11) ...
> Setting up libpam0g:amd64 (1.1.8-4) ...
> dpkg (subprocess): unable to execute installed libpam0g:amd64 package
> post-installation script (/var/lib/dpkg/info/libpam0g:amd64.postinst):
> No such file or directory
> dpkg: error processing package libpam0g:amd64 (--configure):
> installed libpam0g:amd64 package post-installation script subprocess
> returned error exit status 2
> dpkg: adduser: dependency problems, but configuring anyway as you
> requested:
> adduser depends on passwd.
> -'
> Seems to be something with the faked-root since the postinstall files
> are visible in the file-system.
>
> Any ideas ?
Ditto. It no works. :)
And I didn't do it totally quite the same as you, either. I tweaked
mine slightly to this:
fakeroot fakechroot debootstrap --verbose --variant=fakechroot buster
/path/to/buster http://distro.ibiblio.org/debian
I also cheated and stuck my pre-existing /var/lib/apt/lists in there
BECAUSE I'm on dialup. It'd STILL be another couple hours for it
to just get through setting up those lists.
AND my hoard/stash of pre-existing dotDeb archives was "mount -B" to
/path/to/buster/var/cache/apt/archives to save wear-and-tear there,
too.
BUT... same error messages in the end with this being the starter
while debootstrap was setting the packages up after downloading:
I: Configuring passwd...
I: Configuring apt...
W: Failure while configuring required packages.
W: See /path/to/buster/debootstrap/debootstrap.log for details
(possibly the package dash is at fault)
The rest was found in that debootstrap log file.
I'm going to give my old, not faked way a quick shot to make sure it
runs fine... or not. Yes, I know likely apples and oranges, but it
will only take a few minutes to make sure. :)
NOTE TO SELF: UNMOUNT the... hoard NOW before you forget and delete
the failed debootstrap.. which will then PERMANENTLY delete the entire
~19GB of dotDeb archives. CHECK!
Cindy :)
--
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *
fakeroot fakechroot debootstrap fails on buster
To reproduce:
On a plain debian buster:
Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Run the command:
fakeroot fakechroot debootstrap --verbose --variant=fakechroot
buster ${WORKSPACE}/buster
Ends up with a lot of warnings
dpkg: warning: ignoring pre-dependency problem!
And fails finally with a lot of errors with this pattern:
--
Adding 'diversion of /bin/sh to /bin/sh.distrib by dash'
mv: cannot move '/bin/sh.tmp' to '/bin/sh': No such file or directory
dpkg: error processing package dash (--configure):
installed dash package post-installation script subprocess returned
error exit status 1
Setting up init-system-helpers (1.56+nmu1) ...
Setting up binutils (2.31.1-11) ...
Setting up libpam0g:amd64 (1.1.8-4) ...
dpkg (subprocess): unable to execute installed libpam0g:amd64 package
post-installation script (/var/lib/dpkg/info/libpam0g:amd64.postinst):
No such file or directory
dpkg: error processing package libpam0g:amd64 (--configure):
installed libpam0g:amd64 package post-installation script subprocess
returned error exit status 2
dpkg: adduser: dependency problems, but configuring anyway as you requested:
adduser depends on passwd.
-'
Seems to be something with the faked-root since the postinstall files
are visible in the file-system.
Any ideas ?
/Regards
/P
Re: [Progress Report1] Re: Using debootstrap
On 04/29/2018 07:11 AM, Andy Smith wrote:
Hi Richard,
On Sun, Apr 29, 2018 at 06:43:42AM -0500, Richard Owlett wrote:
On 04/29/2018 12:59 AM, Richard Owlett wrote:
On 04/28/2018 10:57 PM, Kushal Kumaran wrote:
You can try it out to verify after you fix the mount options to not
include nodev.
[…]
The man page for mount hints its possible to remove nodev but there is a
dearth of useful examples.
# mount -o remount,dev /dev/sdc1
"man mount" says:
If you want to override mount options from /etc/fstab you have to
use the -o option:
mount device|dir -o options
That got me further :}
But still nothing got written to target :{
I have a secondary machine on which I've made space for a Debian install
and a target partition. >50 years of trouble shooting has taught me to
eliminate as many unknowns as possible. The primary reason I was using
the flash drive was I could not make enough space on this hard drive.
as regards "remount" option it later says:
remount
Attempt to remount an already-mounted filesystem.
This is commonly used to change the mount flags
for a filesystem, especially to make a readonly
filesystem writable. It does not change device or
mount point.
Also have not found a good description of "nodev".
Same man page:
devInterpret character or block special devices on the
filesystem.
nodev Do not interpret character or block special
devices on the file system.
While a filesystem is mounted "nodev", it can't have device special
files created on it.
I had read, but not understood, those passages.
As I've said on occasion, "If retirement isn't for learning, what use is
it?" ;/
Thanks
Cheers,
Andy
Re: [Progress Report1] Re: Using debootstrap
Hi Richard, On Sun, Apr 29, 2018 at 06:43:42AM -0500, Richard Owlett wrote: > On 04/29/2018 12:59 AM, Richard Owlett wrote: > >On 04/28/2018 10:57 PM, Kushal Kumaran wrote: > >>You can try it out to verify after you fix the mount options to not > >>include nodev. […] > The man page for mount hints its possible to remove nodev but there is a > dearth of useful examples. # mount -o remount,dev /dev/sdc1 "man mount" says: If you want to override mount options from /etc/fstab you have to use the -o option: mount device|dir -o options as regards "remount" option it later says: remount Attempt to remount an already-mounted filesystem. This is commonly used to change the mount flags for a filesystem, especially to make a readonly filesystem writable. It does not change device or mount point. > Also have not found a good description of "nodev". Same man page: devInterpret character or block special devices on the filesystem. nodev Do not interpret character or block special devices on the file system. While a filesystem is mounted "nodev", it can't have device special files created on it. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: [Progress Report1] Re: Using debootstrap
On 04/29/2018 12:59 AM, Richard Owlett wrote: On 04/28/2018 10:57 PM, Kushal Kumaran wrote: Richard Owlett <rowl...@cloud85.net> writes: On 04/27/2018 12:06 PM, Felix Dietrich wrote: [SNIP] Script started on Fri 27 Apr 2018 02:22:42 PM CDT ls -Rdl /media/root/rco1 ls -Rdl /usr/sbin/debootstrap ls -Rdl /media/root/rco1 debootstrap --verbose --arch=i386 --include=apt-get --variant=minbase --no-check-gpg stable /media/root/rco1 file:media/cdrom0/debian/ exit root@debian-jan13:~# root@debian-jan13:~# ls -Rdl /media/root/rco1 drwxr-xr-x 3 root root 4096 Apr 27 14:08 /media/root/rco1 root@debian-jan13:~# root@debian-jan13:~# root@debian-jan13:~# ls -Rdl /usr/sbin/debootstrap -rwxr-xr-x 1 root root 18981 Mar 10 2017 /usr/sbin/debootstrap root@debian-jan13:~# root@debian-jan13:~# root@debian-jan13:~# ls -Rdl /media/root/rco1 drwxr-xr-x 3 root root 4096 Apr 27 14:08 /media/root/rco1 root@debian-jan13:~# root@debian-jan13:~# root@debian-jan13:~# debootstrap --verbose --arch=i386 --include=apt-get --variant=minbase --no-check-gpg stable /media/root/rco1 file:media/cdrom0/debian/ /usr/sbin/debootstrap: 1454: /usr/sbin/debootstrap: cannot create /media/root/rco1/test-dev-null: Permission denied E: Cannot install into target '/media/root/rco1' mounted with noexec or nodev root@debian-jan13:~# root@debian-jan13:~# root@debian-jan13:~# exit exit Script done on Fri 27 Apr 2018 02:22:42 PM CDT The error says the filesystem containing /media/root/rco1 is mounted with noexec or nodev. Is that in fact the case? I don't know. > Look at the /proc/mounts entry for that mountpoint. I used Caja (MATE's file manager) to look at /proc/mounts without finding anything resembling the needed information. I'm missing some understanding. mount -l gives /dev/sdc1 on /media/richard/rco1 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2) [rco1] The operation debootstrap is attempting appears to be the equivalent of mknod /media/root/rco1/test-dev-null c 1 3 You can try it out to verify after you fix the mount options to not include nodev. I started with the man page for "mknod" and followed links 2 or 3 levels discovering how little I know ;/ It's 1 AM my time to quit for "day". Much reading to do. The man page for mount hints its possible to remove nodev but there is a dearth of useful examples. Also have not found a good description of "nodev".
Re: [Progress Report1] Re: Using debootstrap
On 04/28/2018 10:57 PM, Kushal Kumaran wrote: Richard Owlett <rowl...@cloud85.net> writes: On 04/27/2018 12:06 PM, Felix Dietrich wrote: [SNIP] Do not specify „--print-debs” if you want „debootstrap” to install the packages. *BINGO* Proofreading one's own work is intrinsically error prone ;/ But it doesn't solve all my problems. Captured the session with SCRIPT(1). I haven't yet decoded the permission bits displayed by the "ls -Rdl ..." lines. I don't see the two error messages being consistent with what I *think* I see when using Caja. Yepp, I have some homework to do. ;} Script started on Fri 27 Apr 2018 02:22:42 PM CDT ls -Rdl /media/root/rco1 ls -Rdl /usr/sbin/debootstrap ls -Rdl /media/root/rco1 debootstrap --verbose --arch=i386 --include=apt-get --variant=minbase --no-check-gpg stable /media/root/rco1 file:media/cdrom0/debian/ exit root@debian-jan13:~# root@debian-jan13:~# ls -Rdl /media/root/rco1 drwxr-xr-x 3 root root 4096 Apr 27 14:08 /media/root/rco1 root@debian-jan13:~# root@debian-jan13:~# root@debian-jan13:~# ls -Rdl /usr/sbin/debootstrap -rwxr-xr-x 1 root root 18981 Mar 10 2017 /usr/sbin/debootstrap root@debian-jan13:~# root@debian-jan13:~# root@debian-jan13:~# ls -Rdl /media/root/rco1 drwxr-xr-x 3 root root 4096 Apr 27 14:08 /media/root/rco1 root@debian-jan13:~# root@debian-jan13:~# root@debian-jan13:~# debootstrap --verbose --arch=i386 --include=apt-get --variant=minbase --no-check-gpg stable /media/root/rco1 file:media/cdrom0/debian/ /usr/sbin/debootstrap: 1454: /usr/sbin/debootstrap: cannot create /media/root/rco1/test-dev-null: Permission denied E: Cannot install into target '/media/root/rco1' mounted with noexec or nodev root@debian-jan13:~# root@debian-jan13:~# root@debian-jan13:~# exit exit Script done on Fri 27 Apr 2018 02:22:42 PM CDT The error says the filesystem containing /media/root/rco1 is mounted with noexec or nodev. Is that in fact the case? I don't know. Look at the /proc/mounts entry for that mountpoint. I used Caja (MATE's file manager) to look at /proc/mounts without finding anything resembling the needed information. I'm missing some understanding. The operation debootstrap is attempting appears to be the equivalent of mknod /media/root/rco1/test-dev-null c 1 3 You can try it out to verify after you fix the mount options to not include nodev. I started with the man page for "mknod" and followed links 2 or 3 levels discovering how little I know ;/ It's 1 AM my time to quit for "day". Much reading to do. Thanks.
Re: [Progress Report1] Re: Using debootstrap
Richard Owlett <rowl...@cloud85.net> writes: > On 04/27/2018 12:06 PM, Felix Dietrich wrote: >>[SNIP] >> >> Do not specify „--print-debs” if you want „debootstrap” to install the >> packages. > > *BINGO* > Proofreading one's own work is intrinsically error prone ;/ > > But it doesn't solve all my problems. Captured the session with > SCRIPT(1). I haven't yet decoded the permission bits displayed by > the "ls -Rdl ..." lines. I don't see the two error messages being > consistent with what I *think* I see when using Caja. > Yepp, I have some homework to do. ;} > > >> Script started on Fri 27 Apr 2018 02:22:42 PM CDT >> >> ls -Rdl /media/root/rco1 >> >> >> ls -Rdl /usr/sbin/debootstrap >> >> >> ls -Rdl /media/root/rco1 >> >> >> debootstrap --verbose --arch=i386 --include=apt-get --variant=minbase >> --no-check-gpg stable /media/root/rco1 file:media/cdrom0/debian/ >> >> >> exit >> root@debian-jan13:~# root@debian-jan13:~# ls -Rdl /media/root/rco1 >> drwxr-xr-x 3 root root 4096 Apr 27 14:08 /media/root/rco1 >> root@debian-jan13:~# root@debian-jan13:~# root@debian-jan13:~# ls >> -Rdl /usr/sbin/debootstrap >> -rwxr-xr-x 1 root root 18981 Mar 10 2017 /usr/sbin/debootstrap >> root@debian-jan13:~# root@debian-jan13:~# root@debian-jan13:~# ls >> -Rdl /media/root/rco1 >> drwxr-xr-x 3 root root 4096 Apr 27 14:08 /media/root/rco1 >> root@debian-jan13:~# root@debian-jan13:~# root@debian-jan13:~# >> debootstrap --verbose --arch=i386 --include=apt-get >> --variant=minbase --no-check-gpg stable /media/root/rco1 >> file:media/cdrom0/debian/ >> /usr/sbin/debootstrap: 1454: /usr/sbin/debootstrap: cannot create >> /media/root/rco1/test-dev-null: Permission denied >> E: Cannot install into target '/media/root/rco1' mounted with noexec or nodev >> root@debian-jan13:~# root@debian-jan13:~# root@debian-jan13:~# exit >> exit >> >> Script done on Fri 27 Apr 2018 02:22:42 PM CDT The error says the filesystem containing /media/root/rco1 is mounted with noexec or nodev. Is that in fact the case? Look at the /proc/mounts entry for that mountpoint. The operation debootstrap is attempting appears to be the equivalent of mknod /media/root/rco1/test-dev-null c 1 3 You can try it out to verify after you fix the mount options to not include nodev. -- regards, kushal
Re: [Progress Report1] Re: Using debootstrap
On 04/27/2018 09:54 AM, rhkra...@gmail.com wrote: On Friday, April 27, 2018 10:16:22 AM Richard Owlett wrote: I thought I was doing that. My TARGET is "/media/richard/rco" where "rco" is the label of a partition on the flash drive. Just chiming in from left field: have you mounted that partition? Yes. I've pulled boners like that. But not this time ;/ Thanks
Re: [Progress Report1] Re: Using debootstrap
On 04/27/2018 12:06 PM, Felix Dietrich wrote: [SNIP] Do not specify „--print-debs” if you want „debootstrap” to install the packages. *BINGO* Proofreading one's own work is intrinsically error prone ;/ But it doesn't solve all my problems. Captured the session with SCRIPT(1). I haven't yet decoded the permission bits displayed by the "ls -Rdl ..." lines. I don't see the two error messages being consistent with what I *think* I see when using Caja. Yepp, I have some homework to do. ;} Script started on Fri 27 Apr 2018 02:22:42 PM CDT ls -Rdl /media/root/rco1 ls -Rdl /usr/sbin/debootstrap ls -Rdl /media/root/rco1 debootstrap --verbose --arch=i386 --include=apt-get --variant=minbase --no-check-gpg stable /media/root/rco1 file:media/cdrom0/debian/ exit root@debian-jan13:~# root@debian-jan13:~# ls -Rdl /media/root/rco1 drwxr-xr-x 3 root root 4096 Apr 27 14:08 /media/root/rco1 root@debian-jan13:~# root@debian-jan13:~# root@debian-jan13:~# ls -Rdl /usr/sbin/debootstrap -rwxr-xr-x 1 root root 18981 Mar 10 2017 /usr/sbin/debootstrap root@debian-jan13:~# root@debian-jan13:~# root@debian-jan13:~# ls -Rdl /media/root/rco1 drwxr-xr-x 3 root root 4096 Apr 27 14:08 /media/root/rco1 root@debian-jan13:~# root@debian-jan13:~# root@debian-jan13:~# debootstrap --verbose --arch=i386 --include=apt-get --variant=minbase --no-check-gpg stable /media/root/rco1 file:media/cdrom0/debian/ /usr/sbin/debootstrap: 1454: /usr/sbin/debootstrap: cannot create /media/root/rco1/test-dev-null: Permission denied E: Cannot install into target '/media/root/rco1' mounted with noexec or nodev root@debian-jan13:~# root@debian-jan13:~# root@debian-jan13:~# exit exit Script done on Fri 27 Apr 2018 02:22:42 PM CDT
Re: [Progress Report1] Re: Using debootstrap
Richard Owlett <rowl...@cloud85.net> writes: > On 04/25/2018 09:19 AM, Richard Owlett wrote: >> My goal is a very minimalist install to a flash drive. It will NOT >> have GRUB - GRUB on this machine is on a dedicated partition for >> convenience in some of my experiments. > > Doing: > debootstrap --verbose --arch=i386 --include=apt-get \ > --variant=minbase --no-check-gpg --print-debs \ > --keep-debootstrap-dir stable /media/richard/rco \ > file:media/cdrom0/debian/ > > generates no error messages. HOWEVER, very few files are actually > written to the flash drive at /media/richard/rco and a subsequent run > of "debootstrap --second-stage" yields a file not found message. You are providing „--print-debs” as an argument to „debootstrap” which will cause „debootstrap” to print the packages it would install and exit. Here is the manual entry for „--print-debs”: Print the packages to be installed, and exit. Note that a TARGET directory must be specified so debootstrap can download Packages files to determine which packages should be installed, and to resolve dependencies. The TARGET directory will be deleted unless --keep-debootstrap-dir is specified. Do not specify „--print-debs” if you want „debootstrap” to install the packages. Also: if you run debootstrap from the same target architecture (or a very similar one like creating an i386 environment from an amd64 host, I suspect) you do not need to run the second stage manually. -- Felix Dietrich
Re: [Progress Report1] Re: Using debootstrap
Richard Owlett wrote: > The error message when attempting "debootstrap --second-stage" is > "cat: /usr/share/debootstrap/suite: No such file or directory". I don't recall to be using second stage. I just make debootstrap with perhaps architecture and I think it takes the minimal as default. Systems$ ls ARM BUSTER GEOD Geode_Old JESSIE RaspBerryPI SID STRETCH Systems$ ls */usr/share/debootstrap/ BUSTER/usr/share/debootstrap/: functions scripts SID/usr/share/debootstrap/: functions scripts AFAIR all is installed via debootstrap. There is a small chance that before Buster it was installed somehow different, but could be that it is something new with this second stage regards
Re: [Progress Report1] Re: Using debootstrap
On Friday, April 27, 2018 10:16:22 AM Richard Owlett wrote: > I thought I was doing that. My TARGET is "/media/richard/rco" where > "rco" is the label of a partition on the flash drive. Just chiming in from left field: have you mounted that partition?
Re: [Progress Report1] Re: Using debootstrap
On 04/27/2018 08:49 AM, deloptes wrote: Richard Owlett wrote: QUESTION: Has anyone personally used debootstrap to install to a flash drive? I do install in a directory and then copy the content to the flash drive then chroot and make it bootable I was installing to the flash drive because I have less than 1GB available on my hard drive. alternatively you ma install into directory where flash drive is mounted I thought I was doing that. My TARGET is "/media/richard/rco" where "rco" is the label of a partition on the flash drive. and then chroot and make it bootable I'm not that far yet. My immediate goal is for debootstrap to write what would "resemble" a system to the flash drive. The error message when attempting "debootstrap --second-stage" is "cat: /usr/share/debootstrap/suite: No such file or directory". forget not that you need to mount the system related /proc/ etc. this is what I am using mount --make-unbindable -obind /proc/ $SYSTEM/proc/ && \ mount --make-unbindable -obind /dev/ $SYSTEM/dev/ && \ mount --make-unbindable -obind /dev/pts $SYSTEM/dev/pts && \ mount --make-unbindable -obind /run $SYSTEM/run && \ mount --make-unbindable -obind /sys $SYSTEM/sys/ && \ chroot $SYSTEM su - For the umount umount $SYSTEM/proc/ && \ umount $SYSTEM/dev/pts && \ umount $SYSTEM/dev/ && \ umount $SYSTEM/run/ && \ umount $SYSTEM/sys/ regards
Re: [Progress Report1] Re: Using debootstrap
Richard Owlett wrote: > QUESTION: > Has anyone personally used debootstrap to install to a flash drive? I do install in a directory and then copy the content to the flash drive then chroot and make it bootable alternatively you ma install into directory where flash drive is mounted and then chroot and make it bootable forget not that you need to mount the system related /proc/ etc. this is what I am using mount --make-unbindable -obind /proc/ $SYSTEM/proc/ && \ mount --make-unbindable -obind /dev/ $SYSTEM/dev/ && \ mount --make-unbindable -obind /dev/pts $SYSTEM/dev/pts && \ mount --make-unbindable -obind /run $SYSTEM/run && \ mount --make-unbindable -obind /sys $SYSTEM/sys/ && \ chroot $SYSTEM su - For the umount umount $SYSTEM/proc/ && \ umount $SYSTEM/dev/pts && \ umount $SYSTEM/dev/ && \ umount $SYSTEM/run/ && \ umount $SYSTEM/sys/ regards
Re: [Progress Report1] Re: Using debootstrap
On 04/27/2018 08:00 AM, songbird wrote:
Richard Owlett wrote:
...
QUESTION:
Has anyone personally used debootstrap to install to a flash drive?
not yet... :)
i'm currently having other bigger fish to fry...
My environment is:
OS is i386 Debian stable
DVD is DVD-1 of Debian 9.1.0
Flash drive has a:
4 GB ext2 partition
4 GB swap partition
get rid of swap partition and change ext2 to ext4 and use all
space on drive for that.
Done. No change :{
don't ask me what i think of uefi...
when using flash drive on main system you can use the
main system drive swap (modify /etc/fstab on flash drive to use
main system drive swap).
I know. When my first attempt failed I added the swap partition "just in
case" debootstrap expected to see it on the destination device.
songbird
Re: [Progress Report1] Re: Using debootstrap
Richard Owlett wrote: ... > QUESTION: > Has anyone personally used debootstrap to install to a flash drive? not yet... :) i'm currently having other bigger fish to fry... > My environment is: >OS is i386 Debian stable >DVD is DVD-1 of Debian 9.1.0 >Flash drive has a: > 4 GB ext2 partition > 4 GB swap partition get rid of swap partition and change ext2 to ext4 and use all space on drive for that. don't ask me what i think of uefi... when using flash drive on main system you can use the main system drive swap (modify /etc/fstab on flash drive to use main system drive swap). songbird
Re: [Progress Report1] Re: Using debootstrap
On 04/27/2018 06:38 AM, Richard Owlett wrote: Doing: debootstrap --verbose --arch=i386 --include=apt-get --variant=minbase --no-check-gpg --print-debs --keep-debootstrap-dir stable /media/richard/rco file:media/cdrom0/debian/ generates no error messages. HOWEVER, very few files are actually written to the flash drive at /media/richard/rco and a subsequent run of "debootstrap --second-stage" yields a file not found message. I have some ideas about my problems and will have time this weekend. I just ran a couple of quick tests of what should be a more typical case with no different results. QUESTION: Has anyone personally used debootstrap to install to a flash drive? My environment is: OS is i386 Debian stable DVD is DVD-1 of Debian 9.1.0 Flash drive has a: 4 GB ext2 partition 4 GB swap partition TIA
[Progress Report1] Re: Using debootstrap
On 04/25/2018 09:19 AM, Richard Owlett wrote: My goal is a very minimalist install to a flash drive. It will NOT have GRUB - GRUB on this machine is on a dedicated partition for convenience in some of my experiments. From reading several references I believe my command should be: debootstrap --arch=i386 --include=apt-get --variant=minbase --no-check-gpg --print-debs --keep-debootstrap-dir stable /media/richard/rco /media/cdrom0/ I have two questions: 1. What should replace "" as I'll be using DVD1 of Debian 9.1.0 as my "repository"? 2. As I expect the console display may exceed the scroll back limits, I wish to pipe the console display for later reference without impeding answering any prompts I get. I've seen a description for doing that, but I can't remember it. Pointers? Taking those questions in reverse order ;} SCRIPT(1) was the command I had been trying to recall. I does things in a comfortable way. I was reading man page for SCREEN(1) when SCRIPT(1) was suggested. Part of the recommendation for SCREEN(1) was it being mentioned in the release notes for *upgrades*. In fact the release notes describe using it for _remote_ upgrades, not local new installs via debootstrap. Doing: debootstrap --verbose --arch=i386 --include=apt-get --variant=minbase --no-check-gpg --print-debs --keep-debootstrap-dir stable /media/richard/rco file:media/cdrom0/debian/ generates no error messages. HOWEVER, very few files are actually written to the flash drive at /media/richard/rco and a subsequent run of "debootstrap --second-stage" yields a file not found message. I have some ideas about my problems and will have time this weekend. Thank you.
Re: Using debootstrap
On 04/26/2018 02:43 PM, Henning Follmann wrote: On Thu, Apr 26, 2018 at 08:02:38PM +0200, deloptes wrote: Henning Follmann wrote: Happy to read the man page to you buddy. -H while I can understand your feeling quite well, I had to teach myself either to ignore affecting questions or to answer for the sake of the answer. sometimes it is really frustrating how one can not understand obvious things, however not all are same age, have same background or level of intelligence. its better you give example in such case debootstrap [OPTION...] stable /mypath/to/target/installation file:///DVD1 this is how I understand it, correct if I'm wrong I am no expert on the install ISO images but if I understand correctly there is a "debian" directory on it. So I guess: debootstrap [OPTION...] stable /mypath/to/target/installation file:///DVD1/debian however just hope that the current DVD is also "stable" The purchased DVD is Debian 9.1.0. My OS used is stable installed via netinst.
Re: Using debootstrap
On 04/26/2018 02:39 PM, Felix Dietrich wrote: deloptes <delop...@gmail.com> writes: its better you give example in such case debootstrap [OPTION...] stable /mypath/to/target/installation file:///DVD1 this is how I understand it, correct if I'm wrong Almost: as has been stated elsewhere in this thread, at least according to Appendix D of the Debian Installation Guide [1] you may provide a „file://” URL to the debian/ directory below the mount point of the disc for the MIRROR parameter, e.g.: file:///cdrom/debian/ Admittedly, I have not to tested either this or your variant. [1] https://www.debian.org/releases/stable/i386/apds03.html.en#idm46014282700896 Apparently file:media/cdrom0/debian/ work. I say "apparently" because: 1. I get no "file not found" messages. 2. I have some undiagnosed problems using debootstrap.
Re: Using debootstrap
On Thu 26 Apr 2018 at 15:43:32 (-0400), Henning Follmann wrote: > On Thu, Apr 26, 2018 at 08:02:38PM +0200, deloptes wrote: > > Henning Follmann wrote: > > > > > Happy to read the man page to you buddy. > > > > > > > > > -H > > > > while I can understand your feeling quite well, I had to teach myself either > > to ignore affecting questions or to answer for the sake of the answer. > > > > sometimes it is really frustrating how one can not understand obvious > > things, however not all are same age, have same background or level of > > intelligence. > > > > its better you give example in such case > > > > debootstrap [OPTION...] stable /mypath/to/target/installation file:///DVD1 > > > > this is how I understand it, correct if I'm wrong > > > > I am no expert on the install ISO images but if I understand correctly > there is a "debian" directory on it. So I guess: > debootstrap [OPTION...] stable /mypath/to/target/installation > file:///DVD1/debian > > however just hope that the current DVD is also "stable" I haven't used a full CD/DVD for years, only netinst, so I'm reduced to guessing like everyone else here. My guess is a simple file:///media/cdrom0/ If the usual link is there, then file:///media/cdrom/ would be as good. Justifications: netinst has top level directories like .disk/, dists/ and pool/, and a README.html file which corresponds to what's outlined at the start of https://www.debian.org/CD/faq/ The build log for the 14 disk set at https://cdimage.debian.org/debian-cd/current/amd64/log/20180310/ contains lines like these three: libisofs: WARNING : Cannot add /debian to Joliet tree. Symlinks can only be added to a Rock Ridge tree. libisofs: WARNING : Cannot add /dists/stable to Joliet tree. Symlinks can only be added to a Rock Ridge tree. libisofs: WARNING : File "/pool/main/g/golang-github-shurcool-sanitized-anchor-name/golang-github-shurcool-sanitized-anchor-name-dev_0.0~git20160918.0.1dba4b3-1_all.deb" can't be added to Joliet tree, because its path length is larger than 240 which imply that pool is top-level, and that debian is a symlink which would almost certainly point to ./ and likewise dists/stable would point to dists/stretch (but netinst doesn't bother with these symlinks). Cheers, David.
Re: Using debootstrap
deloptes <delop...@gmail.com> writes: > its better you give example in such case > > debootstrap [OPTION...] stable /mypath/to/target/installation file:///DVD1 > > this is how I understand it, correct if I'm wrong Almost: as has been stated elsewhere in this thread, at least according to Appendix D of the Debian Installation Guide [1] you may provide a „file://” URL to the debian/ directory below the mount point of the disc for the MIRROR parameter, e.g.: file:///cdrom/debian/ Admittedly, I have not to tested either this or your variant. [1] https://www.debian.org/releases/stable/i386/apds03.html.en#idm46014282700896 -- Felix Dietrich
Re: Using debootstrap
On Thu, Apr 26, 2018 at 08:02:38PM +0200, deloptes wrote: > Henning Follmann wrote: > > > Happy to read the man page to you buddy. > > > > > > -H > > while I can understand your feeling quite well, I had to teach myself either > to ignore affecting questions or to answer for the sake of the answer. > > sometimes it is really frustrating how one can not understand obvious > things, however not all are same age, have same background or level of > intelligence. > > its better you give example in such case > > debootstrap [OPTION...] stable /mypath/to/target/installation file:///DVD1 > > this is how I understand it, correct if I'm wrong > I am no expert on the install ISO images but if I understand correctly there is a "debian" directory on it. So I guess: debootstrap [OPTION...] stable /mypath/to/target/installation file:///DVD1/debian however just hope that the current DVD is also "stable" -H -- Henning Follmann | hfollm...@itcfollmann.com
Re: Using debootstrap
Henning Follmann wrote: > Happy to read the man page to you buddy. > > > -H while I can understand your feeling quite well, I had to teach myself either to ignore affecting questions or to answer for the sake of the answer. sometimes it is really frustrating how one can not understand obvious things, however not all are same age, have same background or level of intelligence. its better you give example in such case debootstrap [OPTION...] stable /mypath/to/target/installation file:///DVD1 this is how I understand it, correct if I'm wrong regards
Re: Using debootstrap
On 2018-04-25, Richard Owlett <rowl...@cloud85.net> wrote: > My goal is a very minimalist install to a flash drive. It will NOT have > GRUB - GRUB on this machine is on a dedicated partition for convenience > in some of my experiments. > > From reading several references I believe my command should be: > > debootstrap --arch=i386 --include=apt-get --variant=minbase > --no-check-gpg --print-debs --keep-debootstrap-dir stable > /media/richard/rco /media/cdrom0/ > I have two questions: >1. What should replace "" as I'll be using DVD1 of Debian 9.1.0 > as my "repository"? https://www.debian.org/releases/stable/amd64/apds03.html.en "if you have a stretch Debian GNU/Linux CD mounted at /cdrom, you could substitute a file URL instead of the http URL: file:/cdrom/debian/" so if this info isn't obsolete, in your case, I dunno: file:/media/cdrom0/debian/ ? >2. As I expect the console display may exceed the scroll back limits, > I wish to pipe the console display for later reference without > impeding answering any prompts I get. I've seen a description for > doing that, but I can't remember it. Pointers? > > -- "Three prisoners were locked in a cell. When the largest of them finished his food, he immediately ate the others. Too bad. An apostrophe in the right place might have prevented a horrible crime." Joe Gunn
Re: Using debootstrap
On Wednesday, April 25, 2018 03:17:40 PM Richard Owlett wrote: > How does one search for some concept for which you have no keywords? Well: * think about it, even some phrases if not keywords * describe what you are looking for here--maybe someone can help you with some keywords (but, start a new thread, as what you're looking for is presumably not related to Using debootstrap
Re: Using debootstrap
On 04/25/2018 11:03 AM, Greg Wooledge wrote: ... I meant a script(1) session. Sorry. But I bet screen also has some logging capabilities, if you want to do it that way. As the man page says: It is useful for students who need a hardcopy record of an interactive session as proof of an assignment, ... Just the tool, though screen(1) may be useful for other projects. Thanks.
Re: Using debootstrap
On 04/25/2018 10:47 AM, Greg Wooledge wrote: On Wed, Apr 25, 2018 at 06:45:32PM +0300, Abdullah Ramazanoglu wrote: On Wed, 25 Apr 2018 09:19:13 -0500 Richard Owlett said: I have two questions: 1. What should replace "" as I'll be using DVD1 of Debian 9.1.0 as my "repository"? 2. As I expect the console display may exceed the scroll back limits, I wish to pipe the console display for later reference without impeding answering any prompts I get. I've seen a description for doing that, but I can't remember it. Pointers? No idea about (1), but for (2) you can use this: ~# command 2>&1 | tee command.log With "tee" you create/squash the output file anew. With "tee -a" you append to it. Or run the commands inside a screen(1) session. That's what the release notes advise for distribution upgrades. I've just browsed the first few paragraphs of the man page. It looks fascinating. Will have to experiment. Thank you.
Re: Using debootstrap
On 04/25/2018 10:45 AM, Abdullah Ramazanoglu wrote: On Wed, 25 Apr 2018 09:19:13 -0500 Richard Owlett said: I have two questions: 1. What should replace "" as I'll be using DVD1 of Debian 9.1.0 as my "repository"? 2. As I expect the console display may exceed the scroll back limits, I wish to pipe the console display for later reference without impeding answering any prompts I get. I've seen a description for doing that, but I can't remember it. Pointers? No idea about (1), but for (2) you can use this: ~# command 2>&1 | tee command.log With "tee" you create/squash the output file anew. With "tee -a" you append to it. Regards That's what I had seen. Thank you. How does one search for some concept for which you have no keywords? TIA
Re: Using debootstrap
Henning Follmann <hfollm...@itcfollmann.com> writes: > On Wed, Apr 25, 2018 at 09:19:13AM -0500, Richard Owlett wrote: >> From reading several references I believe my command should be: >> >> debootstrap --arch=i386 --include=apt-get --variant=minbase --no-check-gpg >> --print-debs --keep-debootstrap-dir stable /media/richard/rco >> /media/cdrom0/ >> >> I have two questions: >> 1. What should replace "" as I'll be using DVD1 of Debian 9.1.0 >> as my "repository"? > > How about man debootstrap? > > I'll copy the synopsys for you(r lazy ...) here > debootstrap [OPTION...] SUITE TARGET [MIRROR [SCRIPT]] > > after stable you provide the target (your usb stick) Am I misunderstanding you here? Your answer seems unnecessarily curt and actually misses his question (the question marks he used to indicate his point of confusion are at the MIRROR parameter). Even if he had been confused about the usage of the TARGET parameter he deserved a more polite and helpful answer because, as you have just experienced, sometimes one misunderstands, what has been written. Maybe I am just to sensitive, though. -- Felix Dietrich
Re: Using debootstrap
> From reading several references I believe my command should be: > > debootstrap --arch=i386 --include=apt-get --variant=minbase \ > --no-check-gpg --print-debs --keep-debootstrap-dir stable \ > /media/richard/rco /media/cdrom0/ > What should replace "" as I'll be using DVD1 of Debian 9.1.0 as my > "repository"? Have a look at the Debian GNU/Linux Installation Guide under Appendix D [1]. The guide suggests that you can use a cdrom mounted on /cdrom by providing a file URL for the MIRROR parameter: file:///cdrom/debian/ . The same might work for an installation DVD. > 2. As I expect the console display may exceed the scroll back limits, > I wish to pipe the console display for later reference without > impeding answering any prompts I get. I've seen a description for > doing that, but I can't remember it. Pointers? The _tee_ program writes output passed to it over STDIN both to its STDOUT (the terminal) and a file provided as an argument: debootstrap … | tee /tmp/debootstrap.output Though by piping the output to _tee_ graphical prompts will no longer work. You could also just increase your scrollback buffer size or use a screen multiplexer, like _tmux_, if your terminal emulator does not allow setting an high enough value. [1] https://www.debian.org/releases/stable/i386/apds03.html.en#idm46014282700896 -- Felix Dietrich
Re: Using debootstrap
... I meant a script(1) session. Sorry. But I bet screen also has some logging capabilities, if you want to do it that way.
Re: Using debootstrap
On Wed, Apr 25, 2018 at 06:45:32PM +0300, Abdullah Ramazanoglu wrote: > On Wed, 25 Apr 2018 09:19:13 -0500 Richard Owlett said: > > > I have two questions: > >1. What should replace "" as I'll be using DVD1 of Debian 9.1.0 > > as my "repository"? > >2. As I expect the console display may exceed the scroll back limits, > > I wish to pipe the console display for later reference without > > impeding answering any prompts I get. I've seen a description for > > doing that, but I can't remember it. Pointers? > > No idea about (1), but for (2) you can use this: > > ~# command 2>&1 | tee command.log > > With "tee" you create/squash the output file anew. With "tee -a" you append to > it. Or run the commands inside a screen(1) session. That's what the release notes advise for distribution upgrades.
Re: Using debootstrap
On Wed, 25 Apr 2018 09:19:13 -0500 Richard Owlett said: > I have two questions: >1. What should replace "" as I'll be using DVD1 of Debian 9.1.0 > as my "repository"? >2. As I expect the console display may exceed the scroll back limits, > I wish to pipe the console display for later reference without > impeding answering any prompts I get. I've seen a description for > doing that, but I can't remember it. Pointers? No idea about (1), but for (2) you can use this: ~# command 2>&1 | tee command.log With "tee" you create/squash the output file anew. With "tee -a" you append to it. Regards -- Abdullah Ramazanoglu
Re: Using debootstrap
On Wed, Apr 25, 2018 at 10:21:21AM -0500, Richard Owlett wrote: > On 04/25/2018 10:12 AM, Henning Follmann wrote: > > On Wed, Apr 25, 2018 at 09:19:13AM -0500, Richard Owlett wrote: > > > My goal is a very minimalist install to a flash drive. It will NOT have > > > GRUB > > > - GRUB on this machine is on a dedicated partition for convenience in some > > > of my experiments. > > > > > > From reading several references I believe my command should be: > > > > > > debootstrap --arch=i386 --include=apt-get --variant=minbase --no-check-gpg > > > --print-debs --keep-debootstrap-dir stable /media/richard/rco > > > /media/cdrom0/ > > > > > > I have two questions: > > >1. What should replace "" as I'll be using DVD1 of Debian 9.1.0 > > > as my "repository"? > > >2. As I expect the console display may exceed the scroll back limits, > > > I wish to pipe the console display for later reference without > > > impeding answering any prompts I get. I've seen a description for > > > doing that, but I can't remember it. Pointers? > > > > > > > How about > > man debootstrap > > ? > > > > I'll copy the synopsys for you(r lazy ...) here > >debootstrap [OPTION...] SUITE TARGET [MIRROR [SCRIPT]] > > > > after stable you provide the target (your usb stick) > > > > > Two problems with with your answer > 1. the man page was one of my half-dozen references. > 2. you answered neither of my questions. > > > > What did you not understand in the man page? can I continue copying stuff from the man page to you: debootstrap bootstraps a basic Debian system of SUITE into TARGET from MIRROR by running SCRIPT. MIRROR can be an http:// or https:// URL, a file:/// URL, or an ssh:/// URL. if you don't provide a Mirror it will consult your sources list. Happy to read the man page to you buddy. -H -- Henning Follmann | hfollm...@itcfollmann.com
Re: Using debootstrap
On 04/25/2018 10:12 AM, Henning Follmann wrote: On Wed, Apr 25, 2018 at 09:19:13AM -0500, Richard Owlett wrote: My goal is a very minimalist install to a flash drive. It will NOT have GRUB - GRUB on this machine is on a dedicated partition for convenience in some of my experiments. From reading several references I believe my command should be: debootstrap --arch=i386 --include=apt-get --variant=minbase --no-check-gpg --print-debs --keep-debootstrap-dir stable /media/richard/rco /media/cdrom0/ I have two questions: 1. What should replace "" as I'll be using DVD1 of Debian 9.1.0 as my "repository"? 2. As I expect the console display may exceed the scroll back limits, I wish to pipe the console display for later reference without impeding answering any prompts I get. I've seen a description for doing that, but I can't remember it. Pointers? How about man debootstrap ? I'll copy the synopsys for you(r lazy ...) here debootstrap [OPTION...] SUITE TARGET [MIRROR [SCRIPT]] after stable you provide the target (your usb stick) Two problems with with your answer 1. the man page was one of my half-dozen references. 2. you answered neither of my questions.
Re: Using debootstrap
On Wed, Apr 25, 2018 at 09:19:13AM -0500, Richard Owlett wrote: > My goal is a very minimalist install to a flash drive. It will NOT have GRUB > - GRUB on this machine is on a dedicated partition for convenience in some > of my experiments. > > From reading several references I believe my command should be: > > debootstrap --arch=i386 --include=apt-get --variant=minbase --no-check-gpg > --print-debs --keep-debootstrap-dir stable /media/richard/rco > /media/cdrom0/ > > I have two questions: > 1. What should replace "" as I'll be using DVD1 of Debian 9.1.0 > as my "repository"? > 2. As I expect the console display may exceed the scroll back limits, > I wish to pipe the console display for later reference without > impeding answering any prompts I get. I've seen a description for > doing that, but I can't remember it. Pointers? > How about man debootstrap ? I'll copy the synopsys for you(r lazy ...) here debootstrap [OPTION...] SUITE TARGET [MIRROR [SCRIPT]] after stable you provide the target (your usb stick) -H -- Henning Follmann | hfollm...@itcfollmann.com
Using debootstrap
My goal is a very minimalist install to a flash drive. It will NOT have GRUB - GRUB on this machine is on a dedicated partition for convenience in some of my experiments. From reading several references I believe my command should be: debootstrap --arch=i386 --include=apt-get --variant=minbase --no-check-gpg --print-debs --keep-debootstrap-dir stable /media/richard/rco /media/cdrom0/ I have two questions: 1. What should replace "" as I'll be using DVD1 of Debian 9.1.0 as my "repository"? 2. As I expect the console display may exceed the scroll back limits, I wish to pipe the console display for later reference without impeding answering any prompts I get. I've seen a description for doing that, but I can't remember it. Pointers?
Re: DEBOOTSTRAP or GRML-DEBOOTSTRAP more suitable?
Richard Owlett wrote: > I suspect the first is closer to my mental image. Did you use > debootstrap with --variant=minbase, grml-debootstrap with --nopackages, > OR something else? For the first to work, I just copy the boot directory to the card/usb stick and make it bootable (grub install). The thing here is that kernel must be same version as on the system - thus after kernel or initrd update procedure should be repeated. I don't use apt in general and regarding debootstrap with --variant=minbase is OK regards
Re: DEBOOTSTRAP or GRML-DEBOOTSTRAP more suitable?
On 04/15/2018 03:58 PM, Brian wrote: On Sun 15 Apr 2018 at 14:19:50 -0500, Richard Owlett wrote: On 04/15/2018 12:43 PM, Brian wrote: On Sun 15 Apr 2018 at 08:55:45 -0500, Richard Owlett wrote: What are the trade-offs of choosing between debootstrap and grml-debootstap? I understand that either way I have some reading to do ;/ Does this relate to your suspicions? Or, is it an unrelated question? It *IS* the question. Is there a difference in capability between DEBOOTSTRAP and GRML-DEBOOTSTRAP? Or is it *ONLY* a difference of perceived convenience which will differ between individuals and/or projects From my reading of https://grml.org/grml-debootstrap/ I think it is the latter. I had visited that page and had suspected that. I was looking for confirmation. Thank you.
Re: DEBOOTSTRAP or GRML-DEBOOTSTRAP more suitable?
On Sun 15 Apr 2018 at 14:19:50 -0500, Richard Owlett wrote: > On 04/15/2018 12:43 PM, Brian wrote: > > On Sun 15 Apr 2018 at 08:55:45 -0500, Richard Owlett wrote: > > > > > > What are the trade-offs of choosing between debootstrap and > > > grml-debootstap? > > > I understand that either way I have some reading to do ;/ > > > > Does this relate to your suspicions? Or, is it an unrelated question? > > > > It *IS* the question. > Is there a difference in capability between DEBOOTSTRAP and > GRML-DEBOOTSTRAP? > Or is it *ONLY* a difference of perceived convenience which will differ > between individuals and/or projects >From my reading of https://grml.org/grml-debootstrap/ I think it is the latter. -- Brian.
Re: DEBOOTSTRAP or GRML-DEBOOTSTRAP more suitable?
On 04/15/2018 02:32 PM, Forest Dean Feighner wrote:
Could you skip all that and use something like busybox or buildroot?
I hadn't recalled either at the moment. Busybox might have an edge as it
in the Debian repository {and I even have it installed - will have to
investigate why I installed it}
Thank you.
Re: DEBOOTSTRAP or GRML-DEBOOTSTRAP more suitable?
Could you skip all that and use something like busybox or buildroot? On Sun, Apr 15, 2018, 3:20 PM Richard Owlett <rowl...@cloud85.net> wrote: > On 04/15/2018 12:43 PM, Brian wrote: > > On Sun 15 Apr 2018 at 08:55:45 -0500, Richard Owlett wrote: > > > >> I wish to do an _*EXTREMELY*_ minimalist install of Debian to a USB > flash > >> drive (aka /dev/sdb1) assuming use as a MBR device. > >> > >> I currently use the i386 flavor of Stretch. > >> My hardware allows choosing to boot from a flash drive. > >> > >> I suspect that if using deboostrap the closest I can come is using > >> "--variant=minbase" which apparently installs apt. My definition of > >> "minimalist" would prefer not to. > > > > I decided to answer this post without equating "idiosyncratic" with > > "bonkers". > > ROFL <*GRIN*> > "bonkers" implies "not of sound mind. > "idiosyncratic" explicitly states my assumption that no-one else may > have _exactly_ my goals > > > > > apt is Priority: important. Try removing it from any Debian system. > > For installing, your definition of "minimalist" is of no importance > > or consequence. > > To you, likely . > BTW, you just reminded me that apt has a "purge" command. > If DEBOOTSTRAP / GRML-DEBOOTSTRAP installs "cruft", that could be useful. > Might even attempt using apt to remove itself ;/ > > Suggested reading: > https://www.debian.org/doc/manuals/debian-faq/ch-pkg_basics.en supports > my contention that only "Priority: Required" packages are absolutely > necessary. > > It states (in part): > > Systems with only the Required packages are probably unusable, but they > > do have enough functionality to allow the sysadmin to boot > > and install more software. > > > > > > > >> For my definitely idiosyncratic purposes *absolutely NOTHING* but grub > >> related tools will _ever_ be run from this device. > >> > >> What are the trade-offs of choosing between debootstrap and > grml-debootstap? > >> I understand that either way I have some reading to do ;/ > > > > Does this relate to your suspicions? Or, is it an unrelated question? > > > > It *IS* the question. > Is there a difference in capability between DEBOOTSTRAP and > GRML-DEBOOTSTRAP? > Or is it *ONLY* a difference of perceived convenience which will differ > between individuals and/or projects? > > > >
Re: DEBOOTSTRAP or GRML-DEBOOTSTRAP more suitable?
On 04/15/2018 12:43 PM, Brian wrote: On Sun 15 Apr 2018 at 08:55:45 -0500, Richard Owlett wrote: I wish to do an _*EXTREMELY*_ minimalist install of Debian to a USB flash drive (aka /dev/sdb1) assuming use as a MBR device. I currently use the i386 flavor of Stretch. My hardware allows choosing to boot from a flash drive. I suspect that if using deboostrap the closest I can come is using "--variant=minbase" which apparently installs apt. My definition of "minimalist" would prefer not to. I decided to answer this post without equating "idiosyncratic" with "bonkers". ROFL <*GRIN*> "bonkers" implies "not of sound mind. "idiosyncratic" explicitly states my assumption that no-one else may have _exactly_ my goals apt is Priority: important. Try removing it from any Debian system. For installing, your definition of "minimalist" is of no importance or consequence. To you, likely . BTW, you just reminded me that apt has a "purge" command. If DEBOOTSTRAP / GRML-DEBOOTSTRAP installs "cruft", that could be useful. Might even attempt using apt to remove itself ;/ Suggested reading: https://www.debian.org/doc/manuals/debian-faq/ch-pkg_basics.en supports my contention that only "Priority: Required" packages are absolutely necessary. It states (in part): Systems with only the Required packages are probably unusable, but they do have enough functionality to allow the sysadmin to boot and install more software. For my definitely idiosyncratic purposes *absolutely NOTHING* but grub related tools will _ever_ be run from this device. What are the trade-offs of choosing between debootstrap and grml-debootstap? I understand that either way I have some reading to do ;/ Does this relate to your suspicions? Or, is it an unrelated question? It *IS* the question. Is there a difference in capability between DEBOOTSTRAP and GRML-DEBOOTSTRAP? Or is it *ONLY* a difference of perceived convenience which will differ between individuals and/or projects?
