Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Installing Debian from a hard disk with Windows to a USB stick
192 views
Skip to first unread message
Cmdte Alpha Tigre Z
Mar 25, 2021, 9:20:04 PM3/25/21
to
Hi.
I'm trying to install Debian 10.8 on a USB stick, and it is not Debian Live,
from a hard disk that has Windows 7 installed. Since I don't have
any CD or DVD, and I need the USB stick to install Debian on it,
I can't use the USB stick to put the ISO image on it.
I have downloaded the first ISO DVD image, hd-media/vmlinuz and
hd-media/initrd.gz. As I understand, the standalone win32-loader
downloads its own Debian image, so I supposed I needed the setup.exe
from the ISO image. I put debian-10.8.0-i386-DVD-1.iso, g2ldr, g2ldr.mbr
(these two from the ISO), initrd.gz, setup.exe, vmlinuz and win32-loader.ini
on the root of C:
I modified win32-loader.ini from:
[installer]
kernel=linux
arch=i386
i386/linux=install.386/vmlinuz
i386/initrd=install.386/initrd.gz
i386/gtk/linux=install.386/vmlinuz
i386/gtk/initrd=install.386/gtk/initrd.gz
[grub]
g2ldr=g2ldr
g2ldr.mbr=g2ldr.mbr
to:
[installer]
kernel=linux
arch=i386
i386/linux=vmlinuz
i386/initrd=initrd.gz
[grub]
g2ldr=g2ldr
g2ldr.mbr=g2ldr.mbr
The problem is that I don't know if modifying win32-loader.ini that way
I can make debian-installer boot from the files on C: instead from a CD or
a DVD or an USB stick; nor I know if GRUB2 will load successfully itself
and linux and the RAM disk.
Please, could you help me?
Thanks in advance.
I'm trying to install Debian 10.8 on a USB stick, and it is not Debian Live,
from a hard disk that has Windows 7 installed. Since I don't have
any CD or DVD, and I need the USB stick to install Debian on it,
I can't use the USB stick to put the ISO image on it.
I have downloaded the first ISO DVD image, hd-media/vmlinuz and
hd-media/initrd.gz. As I understand, the standalone win32-loader
downloads its own Debian image, so I supposed I needed the setup.exe
from the ISO image. I put debian-10.8.0-i386-DVD-1.iso, g2ldr, g2ldr.mbr
(these two from the ISO), initrd.gz, setup.exe, vmlinuz and win32-loader.ini
on the root of C:
I modified win32-loader.ini from:
[installer]
kernel=linux
arch=i386
i386/linux=install.386/vmlinuz
i386/initrd=install.386/initrd.gz
i386/gtk/linux=install.386/vmlinuz
i386/gtk/initrd=install.386/gtk/initrd.gz
[grub]
g2ldr=g2ldr
g2ldr.mbr=g2ldr.mbr
to:
[installer]
kernel=linux
arch=i386
i386/linux=vmlinuz
i386/initrd=initrd.gz
[grub]
g2ldr=g2ldr
g2ldr.mbr=g2ldr.mbr
The problem is that I don't know if modifying win32-loader.ini that way
I can make debian-installer boot from the files on C: instead from a CD or
a DVD or an USB stick; nor I know if GRUB2 will load successfully itself
and linux and the RAM disk.
Please, could you help me?
Thanks in advance.
Cmdte Alpha Tigre Z
Mar 28, 2021, 8:50:04 PM3/28/21
to
El jue, 25 mar 2021 a las 21:11, Cmdte Alpha Tigre Z
(<santia...@gmail.com>) escribió:
> I'm trying to install Debian 10.8 on a USB stick, and it is not Debian Live,
> from a hard disk that has Windows 7 installed. Since I don't have
> any CD or DVD, and I need the USB stick to install Debian on it,
> I can't use the USB stick to put the ISO image on it.
>
> I have downloaded the first ISO DVD image, hd-media/vmlinuz and
> hd-media/initrd.gz. As I understand, the standalone win32-loader
> downloads its own Debian image, so I supposed I needed the setup.exe
> from the ISO image. I put debian-10.8.0-i386-DVD-1.iso, g2ldr, g2ldr.mbr
> (these two from the ISO), initrd.gz, setup.exe, vmlinuz and win32-loader.ini
> on the root of C:
> (...)
Hi.
I tried to run setup.exe and it stored all the files necessary for booting
inside a directory at C:
Apparently, it does that for any files you use with it. The only files it puts
on the root are g2ldr and g2ldr.mbr. The files were almost successfully copied.
I suppose that win32-loader does its job for any files you give it.
The only problems are these two:
setup.exe could not copy g2ldr and g2ldr.mbr to C: because they
already were in C:
so it "failed". I will try to put the files on another folder to see
if setup.exe does
the same as before but without failing.
The other problem is, even that grub2 should load and then load linux and the
ram disk and everything should go fine from there, I don't know
if the debian-installer from hd-media searches the ISO at the root directory
or at the same directory where linux and the ram disk are located.
The documentation says to put linux, the ram disk and the ISO at the root,
but since setup.exe puts the first two in some directory and
configures everything
to run from there, I don't know if I should leave the ISO at the root or instead
move it to where linux and the ram disk are.
Any help?
Thanks in advance.
--
Time zone: GMT-4
(<santia...@gmail.com>) escribió:
> I'm trying to install Debian 10.8 on a USB stick, and it is not Debian Live,
> from a hard disk that has Windows 7 installed. Since I don't have
> any CD or DVD, and I need the USB stick to install Debian on it,
> I can't use the USB stick to put the ISO image on it.
>
> I have downloaded the first ISO DVD image, hd-media/vmlinuz and
> hd-media/initrd.gz. As I understand, the standalone win32-loader
> downloads its own Debian image, so I supposed I needed the setup.exe
> from the ISO image. I put debian-10.8.0-i386-DVD-1.iso, g2ldr, g2ldr.mbr
> (these two from the ISO), initrd.gz, setup.exe, vmlinuz and win32-loader.ini
> on the root of C:
Hi.
I tried to run setup.exe and it stored all the files necessary for booting
inside a directory at C:
Apparently, it does that for any files you use with it. The only files it puts
on the root are g2ldr and g2ldr.mbr. The files were almost successfully copied.
I suppose that win32-loader does its job for any files you give it.
The only problems are these two:
setup.exe could not copy g2ldr and g2ldr.mbr to C: because they
already were in C:
so it "failed". I will try to put the files on another folder to see
if setup.exe does
the same as before but without failing.
The other problem is, even that grub2 should load and then load linux and the
ram disk and everything should go fine from there, I don't know
if the debian-installer from hd-media searches the ISO at the root directory
or at the same directory where linux and the ram disk are located.
The documentation says to put linux, the ram disk and the ISO at the root,
but since setup.exe puts the first two in some directory and
configures everything
to run from there, I don't know if I should leave the ISO at the root or instead
move it to where linux and the ram disk are.
Any help?
Thanks in advance.
--
Time zone: GMT-4
Andrei POPESCU
Apr 5, 2021, 10:10:08 AM4/5/21
to
On Jo, 25 mar 21, 21:11:33, Cmdte Alpha Tigre Z wrote:
>
> I'm trying to install Debian 10.8 on a USB stick, and it is not Debian Live,
> from a hard disk that has Windows 7 installed. Since I don't have
> any CD or DVD, and I need the USB stick to install Debian on it,
> I can't use the USB stick to put the ISO image on it.
Why not?
>
> I'm trying to install Debian 10.8 on a USB stick, and it is not Debian Live,
> from a hard disk that has Windows 7 installed. Since I don't have
> any CD or DVD, and I need the USB stick to install Debian on it,
> I can't use the USB stick to put the ISO image on it.
Hint: the mini.iso does support installing to the same storage device
used to start the installer. It also needs internet access for basically
everything, so you might need a way to pass firmware to the installer in
case the firmware can't be on the same device.
Hope this helps,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Cmdte Alpha Tigre Z
Apr 9, 2021, 5:50:05 PM4/9/21
to
El vie, 9 abr 2021 a las 17:43, Cmdte Alpha Tigre Z
(<santia...@gmail.com>) escribió:
>
> El lun, 5 abr 2021 a las 10:04, Andrei POPESCU
> (<andreim...@gmail.com>) escribió:
>
> I'm sorry Mr. Popescu, I didn't read this mailing list for days.
> Thanks for your help, I have found how to do this and I'll be
> posting here my findings. Perhaps someone else can pass
> that post to the Wiki, I don't know how to use that.
>
> --
> Time zone: GMT-4
I forgot to send this message to this list. Sorry.
(<santia...@gmail.com>) escribió:
>
> El lun, 5 abr 2021 a las 10:04, Andrei POPESCU
> (<andreim...@gmail.com>) escribió:
> > Hint: the mini.iso does support installing to the same storage device
> > used to start the installer. It also needs internet access for basically
> > everything, so you might need a way to pass firmware to the installer in
> > case the firmware can't be on the same device.
>
> Hi.
> > used to start the installer. It also needs internet access for basically
> > everything, so you might need a way to pass firmware to the installer in
> > case the firmware can't be on the same device.
>
>
> I'm sorry Mr. Popescu, I didn't read this mailing list for days.
> Thanks for your help, I have found how to do this and I'll be
> posting here my findings. Perhaps someone else can pass
> that post to the Wiki, I don't know how to use that.
>
> --
> Time zone: GMT-4
I forgot to send this message to this list. Sorry.
Cmdte Alpha Tigre Z
Apr 26, 2021, 8:40:03 PM4/26/21
to
El jue, 25 mar 2021 a las 21:11, Cmdte Alpha Tigre Z
(<santia...@gmail.com>) escribió:
> (...lots of things...)
Hi.
I'm going to post a tutorial to do what I did to achieve the
installation of Debian
in the USB stick from Windows' NTFS-formatted partition.
Please, review it and give your opinions/suggestions/fixes.
It would be great if someone could repost this tutorial at the Debian Wiki.
--
Time zone: GMT-4
(<santia...@gmail.com>) escribió:
> (...lots of things...)
Hi.
I'm going to post a tutorial to do what I did to achieve the
installation of Debian
in the USB stick from Windows' NTFS-formatted partition.
Please, review it and give your opinions/suggestions/fixes.
It would be great if someone could repost this tutorial at the Debian Wiki.
--
Time zone: GMT-4
Cmdte Alpha Tigre Z
Apr 26, 2021, 9:20:05 PM4/26/21
to
On the 25th of March of 2021, I wrote a message asking for help
to install Debian 10.8 (now 10.9) on a USB stick, booting the Debian-installer
from Windows 7's Boot Manager and having the ISO only on the hard disk drive
with only the Windows' partition and its filesystem.
Many thanks in advance to the great Debian developers that have put so much
functionality on the Debian-installer and related stuff.
Here is what I did to reach my goal:
Copyright (c) 2021 Santiago Pinto
Licensed under the Creative Commons Attribution-ShareAlike 4.0
International Public License
(https://creativecommons.org/licenses/by-sa/4.0/legalcode).
This tutorial comes with "ABSOLUTELY NO WARRANTY".
Tutorial version 1.0
0. TABLE OF CONTENTS
1. PREINSTALLATION.
1.1. Downloading required files.
1.2. Arranging files for preinstallation.
1.3. Modification of configuration file, "win32-loader.ini".
1.4. Starting preinstallation program.
1.5. Preparing the USB stick.
2. INSTALLATION.
2.1. Preparing for the special installation procedure.
2.2. Special installation procedure.
3. SUMMARY.
3.1. Preinstallation.
3.2. Installation.
4. FINAL CONSIDERATIONS.
5. FOOTNOTES.
1. PREINSTALLATION
As with any Debian installation, it is recommended to have the installation
manual at hand, just in case... Please, read at least every step completely
before doing it. I use quotes to give clarity to the tutorial, do not include
them when I ask you to write something unless I specifically say to
include them.
1.1. Downloading required files.
1.1.1. Download the first ISO DVD image for Debian. You can do it by
any medium:
http, bittorrent, jigdo, etc.
1.1.2. From the directory at
http://<debian-mirror>/debian/dists/buster/main/installer-<arch>/current/images/hd-media/
download the files "initrd.gz" and "vmlinuz" there if you would like to install
using the text interface or those inside the directory "gtk" if you would rather
prefer the graphical interface. <debian-mirror> is any debian mirror you want
to use like ftp.debian.org and <arch> is the processor architecture's
corresponding suffix (i386, amd64, etc.) which must be the same as the ISO image
you downloaded previously. Please take into account that if you want to do
the installation in normal mode and not expert mode, you can only choose to use
the graphical interface.
1.1.3. From the directory at http://<debian-mirror>/debian/pool/main/p/pcre3/
download the file "libpcre3-udeb_8.39-12_i386.udeb".
1.1.4. If you don't already have 7-Zip, find it here https://www.7-zip.org/
and install it. (The installation procedure for 7-Zip is not covered
in this tutorial)
1.2. Arranging files for preinstallation.
1.2.1. Make a temporary folder to store some files for preinstallation.
It is better to make it at the root of C:. I will assume it is "C:\tmpx\".
1.2.2. Optionally, if you want to be sure that no important installation file
gets accidentally modified, you can make the ISO image, "initrd.gz"
and "vmlinuz"
to be read-only files. This can be done in the files' properties window or
in cmd.exe with the command attrib.
1.2.3. Move the ISO image to "C:\".
1.2.4. Move "initrd.gz" and "vmlinuz" to "C:\tmpx\".
1.2.5. Open the ISO image with 7-Zip and extract "g2ldr" and "g2ldr.mbr"
from there to "C:\tmpx\".
1.2.6. With the ISO still open, extract "setup.exe" and "win32-loader.ini"
to "C:\".
1.3. Modification of configuration file, "win32-loader.ini".
1.3.1. Open "win32-loader.ini" with Notepad and, if you downloaded the files
for the text installer, delete the two lines that contain the text "gtk",
but if you downloaded the others for the graphical installer, then delete
the two lines above that contain nearly the same text except "gtk".
1.3.2. At the other two lines that you did not deleted, replace the text
from just after the equal sign to just before the last slash
with the name of the temporary folder you made previously, here "tmpx".
1.3.3. At the last two lines, after [grub], add just after the equal sign
"tmpx/".
1.3.4. Double check that you did these three previous steps right.
You should write the name of the temporary folder you made instead of "tmpx"
if you gave it another name. Do not include the double quotes into the file,
I write them only here for clarity.
1.3.5. Save the file, "win32-loader.ini".
1.4. Starting preinstallation program.
1.4.1. Run "setup.exe" from "C:\". Follow the instructions there.
If it tells you that you should use a 64-bits version but you are sure
that you need the 32-bits one, then just click on "No", else you should use
the installer and ISO image for that architecture. I tried the installation
in expert mode but normal might work fine too. If this preinstallation fails,
retry one more time.
1.5. Preparing the USB stick.
1.5.1. You should backup now anything you don't want to lose from the USB stick.
1.5.2. Make a temporary folder in your hard disk to put some files there.
1.5.3. Open the DVD ISO image again with 7-Zip if you closed it.
1.5.4. Inside 7-Zip, navigate to "pool\main\f\fuse\".
1.5.5. Open "fuse-udeb_2.9.9-1+deb10u1_i386.udeb" (just double click it
or select it and press enter, it will be opened inside 7-Zip).
I will not mention this again, I will write them in the paths in this tutorial
as if those files were folders.
1.5.6. Open "data.tar" (if you think that 7-Zip is buggy because it omitted
some files, read this footnote [1], ignore this if you don't know what I'm
talking about), then open ".".
1.5.7. Extract everything in there from 7-Zip to the temporary folder
(the last one I mentioned at step 1.5.2.). You can drag and drop to do this.
1.5.8. In 7-Zip, go back into the folder "main". To do this you can:
click the icon at the left of the path bar, double click the folder "..",
or press Backspace (not Del).
1.5.9. Repeat the steps 1.5.6. to 1.5.8. every time after going to the
following paths one at a time. If Windows asks you whether you would like
to mix the folders or not, then click on Yes.
"f\fuse\libfuse2-udeb_2.9.9-1+deb10u1_i386.udeb\"
"l\linux-signed-i386\fuse-modules-4.19.0-16-686-pae-di_4.19.181-1_i386.udeb\"
"libs\libselinux\libselinux1-udeb_2.8-1+b1_i386.udeb\"
"n\ntfs-3g\ntfs-3g-udeb_2017.3.23AR.3-3_i386.udeb\"
1.5.10. Look for the file "libpcre3-udeb_8.39-12_i386.udeb" you downloaded
at step 1.1.3. and open it with 7-Zip. Do the same as the step 1.5.9. before
with the files inside it.
1.5.11. Look for the following files inside the temporary folder
and delete them; do it by clicking on them and pressing Shift+Del one by one,
and please make sure you're deleting the right files. If you look close,
the files' type is shown as ".symlink".
"lib/libpcre.so.3"
"lib/libpcreposix.so.3"
"lib/i386-linux-gnu/libfuse.so.2"
"lib/i386-linux-gnu/libulockmgr.so.1"
"lib/i386-linux-gnu/libntfs-3g.so.883"
"sbin/mount.ntfs"
"sbin/mount.ntfs-3g"
"usr/lib/i386-linux-gnu/libeatmydata.so"
"usr/lib/i386-linux-gnu/libeatmydata.so.1"
If you ask yourself why you need to do this, it is because Windows can not copy
the symlinks to the USB stick. We will be creating those files again later.
1.5.12. You backed up your important files from your USB stick at step 1.5.1.,
right? After this process gets finished, all your files that are
in your USB stick will be deleted. Now format the USB stick by right clicking
on it in Windows Explorer (Windows' file manager) and click on "Format...".
Make sure that these things are selected/marked: "FAT32" below "File System"
and "Quick format", if not, do it. Finally click on "Start".
1.5.13. Copy the whole contents of the temporary folder to the root
of the USB stick where you will be installing Debian on.
2. INSTALLATION
2.1. Preparing for the special installation procedure.
2.1.1. Now you will be doing the installation process, but you still need to do
some things before proceeding with the normal installation of Debian.
I advise you to read the remaining of this tutorial and take some notes.
If you have never installed Debian before, read/take a copy of the manual.
2.1.2. From now on, you can follow two paths to finish this special
installation procedure: (A) run a script attached to this tutorial that will
make almost everything for you, or (B) do the same things that the script does
manually. When I write A or B at the step number in this tutorial is because
it depends on the path you choose here.
2.1.3.A. Copy the script file "prepare-ntfs.sh" attached to this tutorial
to the root of your USB stick. Do not modify it unless you have the right tools
and you know what you are doing.
2.1.3.B. If you want, copy the file "steps.txt" attached to this tutorial
to the root of your USB stick. This will make it easier to follow the manual
steps later.
2.2. Special installation procedure.
2.2.1. Insert the USB stick in the USB port of your computer if its not already
there.
2.2.2. Reboot your computer. When you see a black screen with some
white letters
on it saying "Windows" and "Debian GNU/Linux", use your keyboard arrows
to select "Debian GNU/Linux" and press Enter.
2.2.3. After you get presented with the installer's interface, follow the normal
installation process until you reach the ISO image detection step.
If you are in the normal mode for the installation, that detection
step will fail;
don't worry, just go back and the installer will present you with options
to look for the ISO image, and stop there.
2.2.4. If you are using the text interface, press Alt+F2, but if you are
using the graphical interface, press Ctrl+Alt+F2. Then press Enter.
2.2.5. Write "blkid | grep 'TYPE="vfat"'" (without the outer quotes)
and press Enter.
2.2.6. If only one line gets displayed, then take note of the path shown
at the start of the line, it should be something like "/dev/sdX1" where X
could be any letter. If not, then press Alt+F4, unplug and plug in again
the USB stick. Some information will be displayed and you will see a line
that contains "sdX" where X can be any letter; take note of that "sdX".
2.2.7. Write "mount" (again without the quotes) and press Enter.
2.2.8. Look for a line that has the "sdX1" you took note of before.
If you find it, then take note of the path after it (probably "/media").
If you can not find it, write "ls /media/" and press Enter; if it shows nothing,
write "mount -t vfat -o ro /dev/sdX1 /media/" where X should be the letter
you took note of before and press Enter, else write "umount /media/"
and then write "mount -t vfat -o ro /dev/sdX1 /media/" and press Enter.
2.2.9. Write "cd /media/" and press Enter, then write "ls" and press Enter.
You should see a list of what is inside the USB stick,
if not, review what you did or look for help.
2.2.10.A. Write "sh ./prepare-ntfs.sh /media/" (without the quotes)
and press Enter.
When everything finishes, jump to step 2.2.13. in this tutorial.
2.2.10.B. As a reminder, you should not follow these steps in this tutorial
marked as B if you did the previous one for the automatic procedure.
If you follow these manual steps marked with B I will suppose you know a bit
about Unix based systems. Use "cd" to navigate through the directory structure
starting from "/media/" and copy the contents with "cp" from every directory
to the corresponding location without the "/media/". Create any directory
as you see necessary. If you know how to do it better, then do it.
2.2.11.B. Press Alt+F3 and then Enter. Use "cat" or "nano" to read the file
"steps.txt" you should have copied to the USB stick at step 2.1.3.B.
It should be at "/media/steps.txt". Make the links specified there
with "ln -s".
Use Alt+F2 and Alt+F3 to switch between consoles to run the commands and read
the steps at the same time. You should go to every destination directory
with "cp" and use relative paths except for "/bin/ntfs-3g"
if you want to replicate the original symbolic links.
Of course, if you know how to do it better, then do it that way.
2.2.12.B. Write "depmod" and press Enter, then write "modprobe fuse"
and press Enter.
2.2.13. Write "cd /" and press Enter, then write "umount /media/" and
press Enter.
2.2.14. Write "blkid | grep 'TYPE="ntfs"'" and press Enter.
2.2.15. You should see your hard disk with Windows there. If there is
only one line, take note of the "/dev/sdXY" where X could be any letter
and Y could be any number. If there are many you will have to take note of
all those "/dev/sdXY".
2.2.16. If you got only one line with the previous step,
write "ntfs-3g -o ro /dev/sdXY /mnt/" where X is a letter and Y is a number
you took note of before and press Enter. If you got many lines,
then you will have to write "mkdir /mnt/sdXY/" and press Enter as many times
as lines you got at the previous step, replacing each time X and Y with each
combination you took note of before; then do the same with
"ntfs-3g -o ro /dev/sdXY /mnt/sdXY/".
2.2.17. If you are using the text installer, press Alt+F1, but if you are using
the graphical installer, press Alt+F5.
2.2.18. In the installer's step to look for the ISO image, scan the disk
marked as the "/dev/sdXY" you took note of before at step 2.2.15
or all the disks if you got several "/dev/sdXY". Use the keyboard
arrows and Enter
or your mouse to select and start the search.
2.2.19. When finished, select the found ISO image and continue.
2.2.20. Then, if you have the text installer, press Alt+F2, else Ctrl+Alt+F2.
2.2.21. If you got only one "/dev/sdXY" before at step 2.2.15., write
"umount /mnt/",
but if you got several, write "umount /mnt/sdXY/" and press Enter as many times
as "sdXY" you got before replacing each time X and Y with each combination.
2.2.22. Finally, if you have the text installer, press Alt+F1, but if you have
the graphical one, press "Alt+F5". Now you can proceed with the normal
installation process of Debian.
3. SUMMARY
3.1. Preinstallation.
3.1.1. Download Debian's ISO image, the "initrd.gz" and "vmlinuz" from
"hd-media", "libpcre3-udeb_8.39-12_i386.udeb" and 7-Zip, and install 7-Zip.
3.1.2. In a temporary folder (preferably at the root of C:), put "initrd.gz",
"vmlinuz", and "g2ldr" and "g2ldr.mbr" from the ISO image.
3.1.3. At "C:\", put the ISO image, and "setup.exe" and "win32-loader.ini"
from the ISO image.
3.1.4. Modify carefully "win32-loader.ini" giving the path to "initrd.gz",
"vmlinuz", "g2ldr" and "g2ldr.mbr" as indicated at steps 1.3.
3.1.5. Run the preinstallation program "setup.exe".
3.1.6. In another temporary folder, extract from the ISO image the "data"
contents of packages: "fuse-udeb", "libfuse2-udeb", "fuse-modules" from Linux,
"libselinux1-udeb" and "ntfs-3g-udeb", and from the already downloaded
"libpcre3-udeb".
3.1.7. Delete the symbolic links (".symlink" files) and move the contents
of that temporary folder to the root of the USB stick after you format it
with FAT32.
3.2. Installation.
3.2.1. Copy the script "prepare-ntfs.sh" or the file "steps.txt", both attached
to this tutorial at the root of your USB stick.
3.2.2. Plug in the USB stick, reboot the PC, start the installer and continue
until the ISO image detection step.
3.2.3. Use the key combinations Alt+F2, Ctrl+Alt+F2, Alt+F3, Alt+F1, Alt+F5
accordingly to switch between consoles/installer.
3.2.4. Find out the device path of your USB stick ("/dev/sdX1") and mount it
with "mount" at "/media/".
3.2.5. Execute the script "prepare-ntfs.sh" found into "/media/" or do the steps
manually.
3.2.6. Unmount your USB stick with "umount" and mount your NTFS disk(s)
("/dev/sdXY") with "ntfs-3g" at "/mnt/".
3.2.7. Follow the ISO image detection procedure in the installer's menu.
When finished, unmount your disk(s) from "/mnt/".
3.2.8. Install Debian.
4. FINAL CONSIDERATIONS
4.1. If you will be using your system Debian for quite some time
from your USB stick, you should consider disabling the access time feature
of the file system. This can be done by a manual partitioning of your
USB stick.
If you are in normal mode and not expert mode, you can go back in the menus
until you reach the main menu and then select the partitioning step.
If you disable the access time, you will be extending the lifetime of your
USB stick (yes, they can "die").
4.2. You should read the installation manual anyway for any question you might
have about the installation process.
5. FOOTNOTES
5.1. By default, 7-Zip opens many archive/compression layers in one step
if they are followed one by the other. Indeed, it is ignoring the control
archive; but if you right click and press the "Open inside *" option, it will
open one layer at a time.
to install Debian 10.8 (now 10.9) on a USB stick, booting the Debian-installer
from Windows 7's Boot Manager and having the ISO only on the hard disk drive
with only the Windows' partition and its filesystem.
Many thanks in advance to the great Debian developers that have put so much
functionality on the Debian-installer and related stuff.
Here is what I did to reach my goal:
Copyright (c) 2021 Santiago Pinto
Licensed under the Creative Commons Attribution-ShareAlike 4.0
International Public License
(https://creativecommons.org/licenses/by-sa/4.0/legalcode).
This tutorial comes with "ABSOLUTELY NO WARRANTY".
Tutorial version 1.0
0. TABLE OF CONTENTS
1. PREINSTALLATION.
1.1. Downloading required files.
1.2. Arranging files for preinstallation.
1.3. Modification of configuration file, "win32-loader.ini".
1.4. Starting preinstallation program.
1.5. Preparing the USB stick.
2. INSTALLATION.
2.1. Preparing for the special installation procedure.
2.2. Special installation procedure.
3. SUMMARY.
3.1. Preinstallation.
3.2. Installation.
4. FINAL CONSIDERATIONS.
5. FOOTNOTES.
1. PREINSTALLATION
As with any Debian installation, it is recommended to have the installation
manual at hand, just in case... Please, read at least every step completely
before doing it. I use quotes to give clarity to the tutorial, do not include
them when I ask you to write something unless I specifically say to
include them.
1.1. Downloading required files.
1.1.1. Download the first ISO DVD image for Debian. You can do it by
any medium:
http, bittorrent, jigdo, etc.
1.1.2. From the directory at
http://<debian-mirror>/debian/dists/buster/main/installer-<arch>/current/images/hd-media/
download the files "initrd.gz" and "vmlinuz" there if you would like to install
using the text interface or those inside the directory "gtk" if you would rather
prefer the graphical interface. <debian-mirror> is any debian mirror you want
to use like ftp.debian.org and <arch> is the processor architecture's
corresponding suffix (i386, amd64, etc.) which must be the same as the ISO image
you downloaded previously. Please take into account that if you want to do
the installation in normal mode and not expert mode, you can only choose to use
the graphical interface.
1.1.3. From the directory at http://<debian-mirror>/debian/pool/main/p/pcre3/
download the file "libpcre3-udeb_8.39-12_i386.udeb".
1.1.4. If you don't already have 7-Zip, find it here https://www.7-zip.org/
and install it. (The installation procedure for 7-Zip is not covered
in this tutorial)
1.2. Arranging files for preinstallation.
1.2.1. Make a temporary folder to store some files for preinstallation.
It is better to make it at the root of C:. I will assume it is "C:\tmpx\".
1.2.2. Optionally, if you want to be sure that no important installation file
gets accidentally modified, you can make the ISO image, "initrd.gz"
and "vmlinuz"
to be read-only files. This can be done in the files' properties window or
in cmd.exe with the command attrib.
1.2.3. Move the ISO image to "C:\".
1.2.4. Move "initrd.gz" and "vmlinuz" to "C:\tmpx\".
1.2.5. Open the ISO image with 7-Zip and extract "g2ldr" and "g2ldr.mbr"
from there to "C:\tmpx\".
1.2.6. With the ISO still open, extract "setup.exe" and "win32-loader.ini"
to "C:\".
1.3. Modification of configuration file, "win32-loader.ini".
1.3.1. Open "win32-loader.ini" with Notepad and, if you downloaded the files
for the text installer, delete the two lines that contain the text "gtk",
but if you downloaded the others for the graphical installer, then delete
the two lines above that contain nearly the same text except "gtk".
1.3.2. At the other two lines that you did not deleted, replace the text
from just after the equal sign to just before the last slash
with the name of the temporary folder you made previously, here "tmpx".
1.3.3. At the last two lines, after [grub], add just after the equal sign
"tmpx/".
1.3.4. Double check that you did these three previous steps right.
You should write the name of the temporary folder you made instead of "tmpx"
if you gave it another name. Do not include the double quotes into the file,
I write them only here for clarity.
1.3.5. Save the file, "win32-loader.ini".
1.4. Starting preinstallation program.
1.4.1. Run "setup.exe" from "C:\". Follow the instructions there.
If it tells you that you should use a 64-bits version but you are sure
that you need the 32-bits one, then just click on "No", else you should use
the installer and ISO image for that architecture. I tried the installation
in expert mode but normal might work fine too. If this preinstallation fails,
retry one more time.
1.5. Preparing the USB stick.
1.5.1. You should backup now anything you don't want to lose from the USB stick.
1.5.2. Make a temporary folder in your hard disk to put some files there.
1.5.3. Open the DVD ISO image again with 7-Zip if you closed it.
1.5.4. Inside 7-Zip, navigate to "pool\main\f\fuse\".
1.5.5. Open "fuse-udeb_2.9.9-1+deb10u1_i386.udeb" (just double click it
or select it and press enter, it will be opened inside 7-Zip).
I will not mention this again, I will write them in the paths in this tutorial
as if those files were folders.
1.5.6. Open "data.tar" (if you think that 7-Zip is buggy because it omitted
some files, read this footnote [1], ignore this if you don't know what I'm
talking about), then open ".".
1.5.7. Extract everything in there from 7-Zip to the temporary folder
(the last one I mentioned at step 1.5.2.). You can drag and drop to do this.
1.5.8. In 7-Zip, go back into the folder "main". To do this you can:
click the icon at the left of the path bar, double click the folder "..",
or press Backspace (not Del).
1.5.9. Repeat the steps 1.5.6. to 1.5.8. every time after going to the
following paths one at a time. If Windows asks you whether you would like
to mix the folders or not, then click on Yes.
"f\fuse\libfuse2-udeb_2.9.9-1+deb10u1_i386.udeb\"
"l\linux-signed-i386\fuse-modules-4.19.0-16-686-pae-di_4.19.181-1_i386.udeb\"
"libs\libselinux\libselinux1-udeb_2.8-1+b1_i386.udeb\"
"n\ntfs-3g\ntfs-3g-udeb_2017.3.23AR.3-3_i386.udeb\"
1.5.10. Look for the file "libpcre3-udeb_8.39-12_i386.udeb" you downloaded
at step 1.1.3. and open it with 7-Zip. Do the same as the step 1.5.9. before
with the files inside it.
1.5.11. Look for the following files inside the temporary folder
and delete them; do it by clicking on them and pressing Shift+Del one by one,
and please make sure you're deleting the right files. If you look close,
the files' type is shown as ".symlink".
"lib/libpcre.so.3"
"lib/libpcreposix.so.3"
"lib/i386-linux-gnu/libfuse.so.2"
"lib/i386-linux-gnu/libulockmgr.so.1"
"lib/i386-linux-gnu/libntfs-3g.so.883"
"sbin/mount.ntfs"
"sbin/mount.ntfs-3g"
"usr/lib/i386-linux-gnu/libeatmydata.so"
"usr/lib/i386-linux-gnu/libeatmydata.so.1"
If you ask yourself why you need to do this, it is because Windows can not copy
the symlinks to the USB stick. We will be creating those files again later.
1.5.12. You backed up your important files from your USB stick at step 1.5.1.,
right? After this process gets finished, all your files that are
in your USB stick will be deleted. Now format the USB stick by right clicking
on it in Windows Explorer (Windows' file manager) and click on "Format...".
Make sure that these things are selected/marked: "FAT32" below "File System"
and "Quick format", if not, do it. Finally click on "Start".
1.5.13. Copy the whole contents of the temporary folder to the root
of the USB stick where you will be installing Debian on.
2. INSTALLATION
2.1. Preparing for the special installation procedure.
2.1.1. Now you will be doing the installation process, but you still need to do
some things before proceeding with the normal installation of Debian.
I advise you to read the remaining of this tutorial and take some notes.
If you have never installed Debian before, read/take a copy of the manual.
2.1.2. From now on, you can follow two paths to finish this special
installation procedure: (A) run a script attached to this tutorial that will
make almost everything for you, or (B) do the same things that the script does
manually. When I write A or B at the step number in this tutorial is because
it depends on the path you choose here.
2.1.3.A. Copy the script file "prepare-ntfs.sh" attached to this tutorial
to the root of your USB stick. Do not modify it unless you have the right tools
and you know what you are doing.
2.1.3.B. If you want, copy the file "steps.txt" attached to this tutorial
to the root of your USB stick. This will make it easier to follow the manual
steps later.
2.2. Special installation procedure.
2.2.1. Insert the USB stick in the USB port of your computer if its not already
there.
2.2.2. Reboot your computer. When you see a black screen with some
white letters
on it saying "Windows" and "Debian GNU/Linux", use your keyboard arrows
to select "Debian GNU/Linux" and press Enter.
2.2.3. After you get presented with the installer's interface, follow the normal
installation process until you reach the ISO image detection step.
If you are in the normal mode for the installation, that detection
step will fail;
don't worry, just go back and the installer will present you with options
to look for the ISO image, and stop there.
2.2.4. If you are using the text interface, press Alt+F2, but if you are
using the graphical interface, press Ctrl+Alt+F2. Then press Enter.
2.2.5. Write "blkid | grep 'TYPE="vfat"'" (without the outer quotes)
and press Enter.
2.2.6. If only one line gets displayed, then take note of the path shown
at the start of the line, it should be something like "/dev/sdX1" where X
could be any letter. If not, then press Alt+F4, unplug and plug in again
the USB stick. Some information will be displayed and you will see a line
that contains "sdX" where X can be any letter; take note of that "sdX".
2.2.7. Write "mount" (again without the quotes) and press Enter.
2.2.8. Look for a line that has the "sdX1" you took note of before.
If you find it, then take note of the path after it (probably "/media").
If you can not find it, write "ls /media/" and press Enter; if it shows nothing,
write "mount -t vfat -o ro /dev/sdX1 /media/" where X should be the letter
you took note of before and press Enter, else write "umount /media/"
and then write "mount -t vfat -o ro /dev/sdX1 /media/" and press Enter.
2.2.9. Write "cd /media/" and press Enter, then write "ls" and press Enter.
You should see a list of what is inside the USB stick,
if not, review what you did or look for help.
2.2.10.A. Write "sh ./prepare-ntfs.sh /media/" (without the quotes)
and press Enter.
When everything finishes, jump to step 2.2.13. in this tutorial.
2.2.10.B. As a reminder, you should not follow these steps in this tutorial
marked as B if you did the previous one for the automatic procedure.
If you follow these manual steps marked with B I will suppose you know a bit
about Unix based systems. Use "cd" to navigate through the directory structure
starting from "/media/" and copy the contents with "cp" from every directory
to the corresponding location without the "/media/". Create any directory
as you see necessary. If you know how to do it better, then do it.
2.2.11.B. Press Alt+F3 and then Enter. Use "cat" or "nano" to read the file
"steps.txt" you should have copied to the USB stick at step 2.1.3.B.
It should be at "/media/steps.txt". Make the links specified there
with "ln -s".
Use Alt+F2 and Alt+F3 to switch between consoles to run the commands and read
the steps at the same time. You should go to every destination directory
with "cp" and use relative paths except for "/bin/ntfs-3g"
if you want to replicate the original symbolic links.
Of course, if you know how to do it better, then do it that way.
2.2.12.B. Write "depmod" and press Enter, then write "modprobe fuse"
and press Enter.
2.2.13. Write "cd /" and press Enter, then write "umount /media/" and
press Enter.
2.2.14. Write "blkid | grep 'TYPE="ntfs"'" and press Enter.
2.2.15. You should see your hard disk with Windows there. If there is
only one line, take note of the "/dev/sdXY" where X could be any letter
and Y could be any number. If there are many you will have to take note of
all those "/dev/sdXY".
2.2.16. If you got only one line with the previous step,
write "ntfs-3g -o ro /dev/sdXY /mnt/" where X is a letter and Y is a number
you took note of before and press Enter. If you got many lines,
then you will have to write "mkdir /mnt/sdXY/" and press Enter as many times
as lines you got at the previous step, replacing each time X and Y with each
combination you took note of before; then do the same with
"ntfs-3g -o ro /dev/sdXY /mnt/sdXY/".
2.2.17. If you are using the text installer, press Alt+F1, but if you are using
the graphical installer, press Alt+F5.
2.2.18. In the installer's step to look for the ISO image, scan the disk
marked as the "/dev/sdXY" you took note of before at step 2.2.15
or all the disks if you got several "/dev/sdXY". Use the keyboard
arrows and Enter
or your mouse to select and start the search.
2.2.19. When finished, select the found ISO image and continue.
2.2.20. Then, if you have the text installer, press Alt+F2, else Ctrl+Alt+F2.
2.2.21. If you got only one "/dev/sdXY" before at step 2.2.15., write
"umount /mnt/",
but if you got several, write "umount /mnt/sdXY/" and press Enter as many times
as "sdXY" you got before replacing each time X and Y with each combination.
2.2.22. Finally, if you have the text installer, press Alt+F1, but if you have
the graphical one, press "Alt+F5". Now you can proceed with the normal
installation process of Debian.
3. SUMMARY
3.1. Preinstallation.
3.1.1. Download Debian's ISO image, the "initrd.gz" and "vmlinuz" from
"hd-media", "libpcre3-udeb_8.39-12_i386.udeb" and 7-Zip, and install 7-Zip.
3.1.2. In a temporary folder (preferably at the root of C:), put "initrd.gz",
"vmlinuz", and "g2ldr" and "g2ldr.mbr" from the ISO image.
3.1.3. At "C:\", put the ISO image, and "setup.exe" and "win32-loader.ini"
from the ISO image.
3.1.4. Modify carefully "win32-loader.ini" giving the path to "initrd.gz",
"vmlinuz", "g2ldr" and "g2ldr.mbr" as indicated at steps 1.3.
3.1.5. Run the preinstallation program "setup.exe".
3.1.6. In another temporary folder, extract from the ISO image the "data"
contents of packages: "fuse-udeb", "libfuse2-udeb", "fuse-modules" from Linux,
"libselinux1-udeb" and "ntfs-3g-udeb", and from the already downloaded
"libpcre3-udeb".
3.1.7. Delete the symbolic links (".symlink" files) and move the contents
of that temporary folder to the root of the USB stick after you format it
with FAT32.
3.2. Installation.
3.2.1. Copy the script "prepare-ntfs.sh" or the file "steps.txt", both attached
to this tutorial at the root of your USB stick.
3.2.2. Plug in the USB stick, reboot the PC, start the installer and continue
until the ISO image detection step.
3.2.3. Use the key combinations Alt+F2, Ctrl+Alt+F2, Alt+F3, Alt+F1, Alt+F5
accordingly to switch between consoles/installer.
3.2.4. Find out the device path of your USB stick ("/dev/sdX1") and mount it
with "mount" at "/media/".
3.2.5. Execute the script "prepare-ntfs.sh" found into "/media/" or do the steps
manually.
3.2.6. Unmount your USB stick with "umount" and mount your NTFS disk(s)
("/dev/sdXY") with "ntfs-3g" at "/mnt/".
3.2.7. Follow the ISO image detection procedure in the installer's menu.
When finished, unmount your disk(s) from "/mnt/".
3.2.8. Install Debian.
4. FINAL CONSIDERATIONS
4.1. If you will be using your system Debian for quite some time
from your USB stick, you should consider disabling the access time feature
of the file system. This can be done by a manual partitioning of your
USB stick.
If you are in normal mode and not expert mode, you can go back in the menus
until you reach the main menu and then select the partitioning step.
If you disable the access time, you will be extending the lifetime of your
USB stick (yes, they can "die").
4.2. You should read the installation manual anyway for any question you might
have about the installation process.
5. FOOTNOTES
5.1. By default, 7-Zip opens many archive/compression layers in one step
if they are followed one by the other. Indeed, it is ignoring the control
archive; but if you right click and press the "Open inside *" option, it will
open one layer at a time.
Cmdte Alpha Tigre Z
Apr 26, 2021, 10:20:05 PM4/26/21
to
Hi.
I saw at the Debian Lists' archive
that my attached files were not
shown as attached (as in the
BTS archive), but instead as inserted
into the body of the message.
Is there some other way to attach
the files correctly?
Would it work and could I send the
attachments with HTML?
Well, thanks in advance.
I saw at the Debian Lists' archive
that my attached files were not
shown as attached (as in the
BTS archive), but instead as inserted
into the body of the message.
Is there some other way to attach
the files correctly?
Would it work and could I send the
attachments with HTML?
Well, thanks in advance.
Andrei POPESCU
Apr 27, 2021, 2:50:05 AM4/27/21
to
On Lu, 26 apr 21, 20:34:58, Cmdte Alpha Tigre Z wrote:
>
> It would be great if someone could repost this tutorial at the Debian
> Wiki.
Feel free to do so yourself.
>
> It would be great if someone could repost this tutorial at the Debian
> Wiki.
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Andrei POPESCU
Apr 27, 2021, 2:50:05 AM4/27/21
to
On Lu, 26 apr 21, 22:16:34, Cmdte Alpha Tigre Z wrote:
> Hi.
>
> I saw at the Debian Lists' archive
> that my attached files were not
> shown as attached (as in the
> BTS archive), but instead as inserted
> into the body of the message.
This is just how the archive software shows them, they arrived as
> Hi.
>
> I saw at the Debian Lists' archive
> that my attached files were not
> shown as attached (as in the
> BTS archive), but instead as inserted
> into the body of the message.
separate attachments here.
> Is there some other way to attach
> the files correctly?
> Would it work and could I send the
> attachments with HTML?
davidson
Apr 27, 2021, 7:40:04 AM4/27/21
to
On Mon, 26 Apr 2021 Cmdte Alpha Tigre Z wrote:
> Hi.
>
> I saw at the Debian Lists' archive that my attached files were not
> shown as attached (as in the BTS archive), but instead as inserted
> into the body of the message.
I have not examined your how-to in detail, but from brief examination
> Hi.
>
> I saw at the Debian Lists' archive that my attached files were not
> shown as attached (as in the BTS archive), but instead as inserted
> into the body of the message.
I am impressed by its organised format. It is clear to me that you put
substantial effort into that aspect, and that anyone who uses it will
be grateful for that.
I imagine it is disappointing to see some of that meticulous structure
stripped away unexpectedly, no matter how minor the difference.
> Is there some other way to attach the files correctly?
treat attached files the way you want.
In the past on this list, I have occassionally sent the content of
such plain-text attachments in the body of replies to my original
message, usually with a brief explanatory introduction. Something
like, "The rest of this message body consists of the script referred
to in my tutorial at
CAMGm-vV655QmbJ73OOGbDe6O...@mail.gmail.com ")
> Would it work and could I send the attachments with HTML?
archive treats html attachments.
--
Ce qui est important est rarement urgent
et ce qui est urgent est rarement important
-- Dwight David Eisenhower
davidson
Apr 27, 2021, 7:50:04 AM4/27/21
to
On Tue, 27 Apr 2021 davidson wrote:
> On Mon, 26 Apr 2021 Cmdte Alpha Tigre Z wrote:
>> Hi.
>>
>> I saw at the Debian Lists' archive that my attached files were not
>> shown as attached (as in the BTS archive), but instead as inserted
>> into the body of the message.
[dd]
> On Mon, 26 Apr 2021 Cmdte Alpha Tigre Z wrote:
>> Hi.
>>
>> I saw at the Debian Lists' archive that my attached files were not
>> shown as attached (as in the BTS archive), but instead as inserted
>> into the body of the message.
>> Is there some other way to attach the files correctly?
>
> I don't know of any way to get the debian-user list's web archive to
> treat attached files the way you want.
>
> In the past on this list, I have occassionally sent the content of
> such plain-text attachments in the body of replies to my original
> message, usually with a brief explanatory introduction. Something
> like, "The rest of this message body consists of the script referred
> to in my tutorial at
> CAMGm-vV655QmbJ73OOGbDe6O...@mail.gmail.com ")
That last bit would be more helpful like so:
>
> I don't know of any way to get the debian-user list's web archive to
> treat attached files the way you want.
>
> In the past on this list, I have occassionally sent the content of
> such plain-text attachments in the body of replies to my original
> message, usually with a brief explanatory introduction. Something
> like, "The rest of this message body consists of the script referred
> to in my tutorial at
> CAMGm-vV655QmbJ73OOGbDe6O...@mail.gmail.com ")
https://lists.debian.org/msgid-search/CAMGm-vV655QmbJ73OOGbDe6O...@mail.gmail.com
Cmdte Alpha Tigre Z
Apr 27, 2021, 11:20:05 AM4/27/21
to
El mar, 27 abr 2021 a las 2:45, Andrei POPESCU
(<andreim...@gmail.com>) escribió:
> > Is there some other way to attach
> > the files correctly?
> > Would it work and could I send the
> > attachments with HTML?
>
> What problem are you trying to solve?
Well, I intentionally wrote the script with Unix-style LF line endings.
I don't know if "ash" from Busybox will complain or do something
weird if it finds CR LF line endings instead. I just wanted to avoid
troubles.
On the other hand, as Mr. Davidson said, it is not very clear
where do one file starts and where do it ends. In the tutorial,
I refer to them as attached files; but people reading the tutorial
through the archive won't see any "attached file". If I knew this would
happen, I would rather have put some ---HEADERS--- and
---FOOTERS--- to the files. It is good to know that they were
correctly sent through email.
--
Time zone: GMT-4
(<andreim...@gmail.com>) escribió:
> On Lu, 26 apr 21, 22:16:34, Cmdte Alpha Tigre Z wrote:
> > Hi.
> >
> > I saw at the Debian Lists' archive
> > that my attached files were not
> > shown as attached (as in the
> > BTS archive), but instead as inserted
> > into the body of the message.
>
> This is just how the archive software shows them, they arrived as
> separate attachments here.
Ok, thanks for that.
> > Hi.
> >
> > I saw at the Debian Lists' archive
> > that my attached files were not
> > shown as attached (as in the
> > BTS archive), but instead as inserted
> > into the body of the message.
>
> This is just how the archive software shows them, they arrived as
> separate attachments here.
> > Is there some other way to attach
> > the files correctly?
> > Would it work and could I send the
> > attachments with HTML?
>
> What problem are you trying to solve?
I don't know if "ash" from Busybox will complain or do something
weird if it finds CR LF line endings instead. I just wanted to avoid
troubles.
On the other hand, as Mr. Davidson said, it is not very clear
where do one file starts and where do it ends. In the tutorial,
I refer to them as attached files; but people reading the tutorial
through the archive won't see any "attached file". If I knew this would
happen, I would rather have put some ---HEADERS--- and
---FOOTERS--- to the files. It is good to know that they were
correctly sent through email.
--
Time zone: GMT-4
Cmdte Alpha Tigre Z
Apr 27, 2021, 11:30:04 AM4/27/21
to
El mar, 27 abr 2021 a las 7:33, davidson (<davi...@freevolt.org>) escribió:
> On Mon, 26 Apr 2021 Cmdte Alpha Tigre Z wrote:
> > Hi.
> >
> > I saw at the Debian Lists' archive that my attached files were not
> > shown as attached (as in the BTS archive), but instead as inserted
> > into the body of the message.
>
> I have not examined your how-to in detail, but from brief examination
> I am impressed by its organised format. It is clear to me that you put
> substantial effort into that aspect, and that anyone who uses it will
> be grateful for that.
>
> I imagine it is disappointing to see some of that meticulous structure
> stripped away unexpectedly, no matter how minor the difference.
Thanks.
> On Mon, 26 Apr 2021 Cmdte Alpha Tigre Z wrote:
> > Hi.
> >
> > I saw at the Debian Lists' archive that my attached files were not
> > shown as attached (as in the BTS archive), but instead as inserted
> > into the body of the message.
>
> I have not examined your how-to in detail, but from brief examination
> I am impressed by its organised format. It is clear to me that you put
> substantial effort into that aspect, and that anyone who uses it will
> be grateful for that.
>
> I imagine it is disappointing to see some of that meticulous structure
> stripped away unexpectedly, no matter how minor the difference.
Yes, it is indeed a little disappointing to see my tutorial screwed up.
--
Time zone: GMT-4
Cmdte Alpha Tigre Z
Apr 27, 2021, 11:40:04 AM4/27/21
to
El mar, 27 abr 2021 a las 10:35, David Wright
(<deb...@lionunicorn.co.uk>) escribió:
> You might attach the shell script as application/x-sh rather
> than text/x-sh¹. That should encode it, and display it as an
> attachment on the web, as with:
>
> https://lists.debian.org/debian-user/2021/03/msg01494.html
>
> making it easier to download. And mutt, for example, would
> display it via the attachment menu, ready for downloading.
>
> AIUI, the policy is to immediately display text/… attachments,
> though mutt demarcates them better than firefox does. I suppose
> one could always wrap the text file into a trivial shell script.
> However, before doing this as a general policy, it's worth
> checking that websites you expect to be archiving/forwarding
> your posts are not stripping attachments. (Some do.)
>
> ¹ I have no idea how different MUAs, and posting sites like
> gmail, would force this. Mutt does it as a matter of course,
> and that can be checked before sending, by first postponing
> the message, and then searching the contents of the Postponed
> mailbox for "Content-Type: application/x-sh".
>
> Cheers,
> David.
Thank you a lot, sir!
Could you repost my attachments as replies to my tutorial
that way, please? For now, I have no way of changing
the content type for attachments. If you do so, please
include also a short note in the body of your message
like "Here are the attachments referred to in the tutorial."
(<deb...@lionunicorn.co.uk>) escribió:
> than text/x-sh¹. That should encode it, and display it as an
> attachment on the web, as with:
>
> https://lists.debian.org/debian-user/2021/03/msg01494.html
>
> making it easier to download. And mutt, for example, would
> display it via the attachment menu, ready for downloading.
>
> AIUI, the policy is to immediately display text/… attachments,
> though mutt demarcates them better than firefox does. I suppose
> one could always wrap the text file into a trivial shell script.
> However, before doing this as a general policy, it's worth
> checking that websites you expect to be archiving/forwarding
> your posts are not stripping attachments. (Some do.)
>
> ¹ I have no idea how different MUAs, and posting sites like
> gmail, would force this. Mutt does it as a matter of course,
> and that can be checked before sending, by first postponing
> the message, and then searching the contents of the Postponed
> mailbox for "Content-Type: application/x-sh".
>
> Cheers,
> David.
Thank you a lot, sir!
Could you repost my attachments as replies to my tutorial
that way, please? For now, I have no way of changing
the content type for attachments. If you do so, please
include also a short note in the body of your message
like "Here are the attachments referred to in the tutorial."
Cmdte Alpha Tigre Z
Apr 27, 2021, 11:50:04 AM4/27/21
to
El mar, 27 abr 2021 a las 11:24, <to...@tuxteam.de> escribió:
> On Tue, Apr 27, 2021 at 11:16:44AM -0400, Cmdte Alpha Tigre Z wrote:
>
> [...]
>
> A civilised mail user agent will show MIME part boundaries in
> a suitable way. I think you don't need to worry too much about
> uncivilised MUAs. It's people's choice, after all :-)
>
> Cheers
> - t
Thanks. I'm not worrying anymore for the mail messages,
but the problem is the Debian Lists archive's web interface
that doesn't work as a civilised mail user agent.
--
Time zone: GMT-4
> On Tue, Apr 27, 2021 at 11:16:44AM -0400, Cmdte Alpha Tigre Z wrote:
>
> [...]
>
> > On the other hand, as Mr. Davidson said, it is not very clear
> > where do one file starts and where do it ends [...]
> > On the other hand, as Mr. Davidson said, it is not very clear
>
> A civilised mail user agent will show MIME part boundaries in
> a suitable way. I think you don't need to worry too much about
> uncivilised MUAs. It's people's choice, after all :-)
>
> Cheers
> - t
Thanks. I'm not worrying anymore for the mail messages,
but the problem is the Debian Lists archive's web interface
that doesn't work as a civilised mail user agent.
--
Time zone: GMT-4
Cmdte Alpha Tigre Z
Apr 27, 2021, 11:50:04 AM4/27/21
to
El mar, 27 abr 2021 a las 11:44, <to...@tuxteam.de> escribió:
>
> But back to topic, thanks for your nice HOWTO :)
>
> Cheers
> - t
He he, thank you.
--
Time zone: GMT-4
> On Tue, Apr 27, 2021 at 11:41:16AM -0400, Cmdte Alpha Tigre Z wrote:
> [...]
> > > A civilised mail user agent will show MIME part boundaries [...]
> [...]
>
> > Thanks. I'm not worrying anymore for the mail messages,
> > but the problem is the Debian Lists archive's web interface
> > that doesn't work as a civilised mail user agent.
>
> ...which is a pity ;-/
> > Thanks. I'm not worrying anymore for the mail messages,
> > but the problem is the Debian Lists archive's web interface
> > that doesn't work as a civilised mail user agent.
>
>
> But back to topic, thanks for your nice HOWTO :)
>
> Cheers
> - t
He he, thank you.
--
Time zone: GMT-4
Brian
Apr 27, 2021, 3:20:05 PM4/27/21
to
On Tue 27 Apr 2021 at 11:55:52 -0400, Cmdte Alpha Tigre Z wrote:
> El mar, 27 abr 2021 a las 2:43, Andrei POPESCU
> (<andreim...@gmail.com>) escribió:
"Umm, well" is hardly an adequate reponse to Andrei POPESCU's
suggestion. If you are waiting for someone like me to step up,
you will be waiting a long time.
Users employ the wiki to write what they feel comfortable about,
not to act as a proxy for someone else's thoughts and writing.
> If someone else can repost it under some of the installation
> sections of the Wiki, I could give any necessary additional license
> to complete the repost after knowing, of course, which license does
> that need. If done, please include a little reference to the tutorial
> at https://wiki.debian.org/DebianInstaller/Loader , if you can,
> of course.
Your effort. Your creative activity. Your wiki. Your decision.
--
Brian.
> El mar, 27 abr 2021 a las 2:43, Andrei POPESCU
> (<andreim...@gmail.com>) escribió:
> > On Lu, 26 apr 21, 20:34:58, Cmdte Alpha Tigre Z wrote:
> > > It would be great if someone could repost this tutorial at the Debian
> > > Wiki.
> >
> > Feel free to do so yourself.
>
> Umm, well. That will have to wait.
> > > It would be great if someone could repost this tutorial at the Debian
> > > Wiki.
> >
> > Feel free to do so yourself.
>
"Umm, well" is hardly an adequate reponse to Andrei POPESCU's
suggestion. If you are waiting for someone like me to step up,
you will be waiting a long time.
Users employ the wiki to write what they feel comfortable about,
not to act as a proxy for someone else's thoughts and writing.
> If someone else can repost it under some of the installation
> sections of the Wiki, I could give any necessary additional license
> to complete the repost after knowing, of course, which license does
> that need. If done, please include a little reference to the tutorial
> at https://wiki.debian.org/DebianInstaller/Loader , if you can,
> of course.
Your effort. Your creative activity. Your wiki. Your decision.
--
Brian.
Cmdte Alpha Tigre Z
Apr 29, 2021, 9:30:04 PM4/29/21
to
El mar, 27 abr 2021 a las 15:11, Brian (<ad...@cityscape.co.uk>) escribió:
>
> "Umm, well" is hardly an adequate reponse to Andrei POPESCU's
> suggestion. If you are waiting for someone like me to step up,
> you will be waiting a long time.
>
> Users employ the wiki to write what they feel comfortable about,
> not to act as a proxy for someone else's thoughts and writing.
Yes sir, you're right. I'm sorry, I was not clear when I wrote
>
> "Umm, well" is hardly an adequate reponse to Andrei POPESCU's
> suggestion. If you are waiting for someone like me to step up,
> you will be waiting a long time.
>
> Users employ the wiki to write what they feel comfortable about,
> not to act as a proxy for someone else's thoughts and writing.
my message. I do plan to repost it by myself at the wiki,
but it won't be in the near future. I just wanted to see if someone
else could get it there sooner than me, so I would benefit more
people right now.
I won't be waiting for someone else, it is just that I can't do it
for now. But thanks for your advice.
Have a nice day everyone.
PS: I forgot to send this message to the list.
--
Time zone: GMT-4
Andrei POPESCU
May 8, 2021, 7:50:05 AM5/8/21
to
On Lu, 05 apr 21, 17:03:46, Andrei POPESCU wrote:
>
> Hint: the mini.iso does support installing to the same storage device
> used to start the installer. It also needs internet access for basically
> everything, so you might need a way to pass firmware to the installer in
> case the firmware can't be on the same device.
To follow-up on this, the mini.iso also creates a partition labeled
>
> Hint: the mini.iso does support installing to the same storage device
> used to start the installer. It also needs internet access for basically
> everything, so you might need a way to pass firmware to the installer in
> case the firmware can't be on the same device.
"Firmware" on the device. As one might guess, it can be used to store
firmware to be used by the installer.
In case the GPT partition table created by the mini.iso is kept[1] it
will have a funny ISO signature that fdisk will offer to delete (at
least in bullseye).
[1] It didn't occur to me at first that I can delete the entire
partition table if I select the device at the installer's manual
partitioning stage. It's faster than deleting partitions one by one ;)
0 new messages