On Fri, Oct 28, 2022 at 05:03:34PM +0200, Mario Marietto wrote:
> Greg,are you talking about this :
>
> find . -depth -type f | cpio --create --format='newc' >
> ../../initrd.img-5.10.0-18-amd64
>
> or this :
>
> find . -depth | cpio --create --format='newc' >
> ../../initrd.img-5.10.0-18-amd64
Hello.
It's me again. I have another question to ask,another problem to fix,this
time I'm really sure,it's easier to understand and to fix. When I load the
LIVE version of debian 11 (xfce edition),I can't login using the login and
password live / user,but I should use root / root. On the preseed f
Ok. Thanks to everyone for the valuable help. In the end I have developed
this elementary script. I feel like a dwarf on the shoulders of giants,but
that's it :
#!/bin/bash
if [ "`id -u`" -ne 0 ]; then
echo "Switching from `id -un` to root"
exec sudo "$0"
exit 99
fi
# Lets check the kernel v
On Fri 28 Oct 2022 at 12:44:43 (+0200), Thomas Schmitt wrote:
> Mario Marietto wrote:
> > There are some kb of difference between the files produced by the two
> > techniques :
> > 79.3 MiB (83,106,001 byte) : find . -print -depth | cpio --create
> > --format='newc' > ../../initrd.img-5.10.0-18-amd
Greg,are you talking about this :
find . -depth -type f | cpio --create --format='newc' >
../../initrd.img-5.10.0-18-amd64
or this :
find . -depth | cpio --create --format='newc' >
../../initrd.img-5.10.0-18-amd64
or are they equivalent ? Thanks.
Il giorno ven 28 ott 2022 alle ore 16:49 Greg W
On Fri, Oct 28, 2022 at 09:32:00AM +0700, Max Nikulin wrote:
> On 28/10/2022 07:07, Mario Marietto wrote:
> >
> > find . | cpio --create
> I rarely use cpio, but recently there was a thread on tar and unwanted hard
> links in the created archive. "find" output mixes regular files and
> directories
On Fri, 28 Oct 2022 15:54:00 +0200
Mario Marietto wrote:
> Hello Charles.
>
> Can you write the full command ? I don't understand what you mean
> with " find … -type f …". I'm orienting myself to use this :
>
> find . -depth | cpio --create --format='newc' >
> /boot/$CURRENT_KERNEL_VERSION_NO_G
Hello Charles.
Can you write the full command ? I don't understand what you mean with "
find … -type f …". I'm orienting myself to use this :
find . -depth | cpio --create --format='newc' >
/boot/$CURRENT_KERNEL_VERSION_NO_GZ
as suggested by Thomas. In this command I don't see any "-type f". Ver
On Fri, 28 Oct 2022 09:32:00 +0700
Max Nikulin wrote:
> On 28/10/2022 07:07, Mario Marietto wrote:
> >
> > find . | cpio --create
> I rarely use cpio, but recently there was a thread on tar and
> unwanted hard links in the created archive. "find" output mixes
> regular files and directories. I
This command does not reports the warning :
find . -depth -print | cpio --create --format='newc' >
../../initrd.img-5.10.0-19-amd64
554538 blocks.
and :
# cat initrd.img-5.10.0-19-amd64-depth | cpio -t | sort >/tmp/with_depth
554538 blocks
# cat initrd.img-5.10.0-19-amd64-depth | cpio -t | sort
Hi,
Mario Marietto wrote:
> There are some kb of difference between the files produced by the two
> techniques :
> 79.3 MiB (83,106,001 byte) : find . -print -depth | cpio --create
> --format='newc' > ../../initrd.img-5.10.0-18-amd64
> 79.3 MiB (83,108,291 byte) : find . | cpio --create --format='
On 2022-10-28 at 06:14, Mario Marietto wrote:
> Hello. Both these commands :
>
> # find . -print -depth | cpio --create --format='newc' > ../../i
> nitrd.img-5.19.0-15.2-liquorix-amd64
>
> # find . | cpio --create --format='newc' > ../../initrd.img-5.10.0-18-amd64
>
> produce this warning :
>
Hello. Both these commands :
# find . -print -depth | cpio --create --format='newc' > ../../i
nitrd.img-5.19.0-15.2-liquorix-amd64
# find . | cpio --create --format='newc' > ../../initrd.img-5.10.0-18-amd64
produce this warning :
find: warning: you have specified the global option -depth after
There are some kb of difference between the files produced by the two
techniques :
79.3 MiB (83,106,001 byte) : find . -print -depth | cpio --create
--format='newc' > ../../initrd.img-5.10.0-18-amd64
79.3 MiB (83,108,291 byte) : find . | cpio --create --format='newc' >
../../initrd.img-5.10.0-18-a
If I have understood correctly,is this the correct form ?
find . -print -depth | cpio --create --format='newc' >
../../initrd.img-5.10.0-18-amd64
Il giorno ven 28 ott 2022 alle ore 04:32 Max Nikulin
ha scritto:
> On 28/10/2022 07:07, Mario Marietto wrote:
> >
> > find . | cpio --create
> I ra
On 28/10/2022 07:07, Mario Marietto wrote:
find . | cpio --create
I rarely use cpio, but recently there was a thread on tar and unwanted
hard links in the created archive. "find" output mixes regular files and
directories. If the archiver recursively walks through received
directories then re
I've found the error. This command is not good :
find . -print -depth | cpio -o > ../../initrd.img-5.10.0-18-amd64
this one can allow the new generated kernel image to boot :
find . | cpio --create --format='newc' > ../../initrd.img-5.10.0-18-amd64
I'm not a pro,as I said,but I suspect that the
Maybe it won't boot because I should sign again the new kernel file
produced ?
Il giorno gio 27 ott 2022 alle ore 22:37 Mario Marietto <
marietto2...@gmail.com> ha scritto:
> You are extremely technical or cpio is extremely technical. Or both,I
> don't know. For sure I'm a hobbyist and I have tro
You are extremely technical or cpio is extremely technical. Or both,I don't
know. For sure I'm a hobbyist and I have trouble understanding some
technical concepts. So,I'm not sure that I have understood. But I tried to
follow your directions,issuing the commands below. But I've got the same
error a
On Thu 27 Oct 2022 at 14:22:45 (+0200), Mario Marietto wrote:
> I tried to follow your directions,using cp
> usr/share/plymouth/debian-logo.png instead of cp
> /usr/share/plymouth/debian-logo.png. I hope that this is what you intend.
Not really. As far as cp is concerned, it copies file1 to file2,
Don't care about :
rm
/home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64/usr/share/plymouth/debian-logo*.png
rm
/home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-19-amd64/usr/share/plymouth/debian-logo*.png
rm
/home/ziomario/Scrivania/PassT-Cubic
I tried to follow your directions,using cp
usr/share/plymouth/debian-logo.png instead of cp
/usr/share/plymouth/debian-logo.png. I hope that this is what you intend.
So,below there are the commands that I have issued :
cd /home/ziomario/Scrivania/PassT-Cubic/kernels/
gunzip -k initrd.img-5.10.0-1
On Thu 27 Oct 2022 at 01:48:44 (+0200), Mario Marietto wrote:
> Il giorno gio 27 ott 2022 alle ore 01:01 David Wright ha scritto:
> > On Thu 27 Oct 2022 at 00:21:50 (+0200), Mario Marietto wrote:
> > > Please,check the images below. The image 1 and 2 come from the kernel
> > file
> > > unpacked wit
Hello David,
I don't want to bother you,but did you read my first message ? You replied
only to the second one and I don't know if you have read or understood the
first one. I ask because it seems there may be some other problems
explained there. Do you want to give it a look ? Thank you very much
On Thu 27 Oct 2022 at 00:21:50 (+0200), Mario Marietto wrote:
> Please,check the images below. The image 1 and 2 come from the kernel file
> unpacked with the cpio command (cpio -idv < initrd.img-5.10.0-18-amd64 -D
> /home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64),
Please,check the images below. The image 1 and 2 come from the kernel file
unpacked with the cpio command (cpio -idv < initrd.img-5.10.0-18-amd64 -D
/home/ziomario/Scrivania/PassT-Cubic/kernels/unzipped/initrd.img-5.10.0-18-amd64),while
on the picture n. 3 You can see all the pictures that are insi
Hello to everyone.
I'm trying to understand the reasons why the kernel file that I generate
does not work correctly. Maybe I've understood something,but I don't have a
clear picture of the problem. I want to try to explain what's wrong using
my method of expression because I find it easier. A more
Hi,
Mario Marietto wrote:
> You seem to understand well what I'm trying to do and you are
> able to give good suggestions.
Probably i only have a good run of guessing here.
> It seems that there isn't any CPIO
> parameter that overwrites the old image. Is this correct ?
I am not aware of any.
I wrote this a few days ago, but then you posted a follow-up to the
same post that used a different method, and so I never bothered to
send this.
I don't know how other people's tolerance compares with mine, but
I tried to follow some of what you did and was frustrated by what
seemed to be inconsi
You are right. The kernel file grows and grows and grows. I never said that
it's perfect. You seem to understand well what I'm trying to do and you are
able to give good suggestions. It's me that I'm not a pro. I'm a hobbyist.
Anyway,you suggested the road to take. It seems that there isn't any CPI
On 2022-10-25, Thomas Schmitt wrote:
> Hi,
>
> Mario Marietto wrote:
>> I've realized that as soon as a
>> new kernel has been installed by the user,logos and images
>> should be added automatically inside the initrd.img* file. For
>> this reason,I've created the bash script below. It works,I've
>
Hi,
Mario Marietto wrote:
> I've realized that as soon as a
> new kernel has been installed by the user,logos and images
> should be added automatically inside the initrd.img* file. For
> this reason,I've created the bash script below. It works,I've
> tested it. Now I should understand where to pl
I've renamed the previous script as "check-kernels" and I've saved it on
/usr/sbin ; I've added this line inside the file /etc/sudoers :
ALL ALL = NOPASSWD: /usr/sbin/check-kernels
and I've created the file below that I have saved inside the folder
/etc/xdg/autostart :
check-nvidia-kernel.de
Almost,but not fully. Because I've realized that as soon as a new kernel
has been installed by the user,logos and images should be added
automatically inside the initrd.img* file. For this reason,I've created the
bash script below. It works,I've tested it. Now I should understand where
to place it
Hi,
Mario Marietto wrote:
> But the technique below worked :
So your initrd problems are solved now and you managed to modify a Debian
Live ISO by help of Cubic ?
Have a nice day :)
Thomas
The technique to unpack the files from the cpio archive with :
cpio -idv < tree.cpio
and then packing them up with :
find . -print -depth | cpio -ov > tree.cpio
didn't work for some unknown reason. But the technique below worked :
mkdir -p
/root/Scrivania/Scrivania/PassT-Cubic/Debian-new/custo
This is what I did. I gone into this folder :
/home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/boot/ and I
have renamed the file "initrd.gz" into "initrd_.gz" and I've burnt a new
ISO image. I have soon realized that that file has been regenerated. The
initrd_.gz file disappeared and a n
On Sat, Oct 22, 2022 at 05:13:18PM +0200, Thomas Schmitt wrote:
> Hi,
>
> Mario Marietto wrote:
> > I'm trying to change the pictures inside the /live/initrd.gz file.
>
> I really wonder where this file comes from.
>
>
> > BUT after having "burned" another ISO image using Cubic,I've seen that i
Hi,
Mario Marietto wrote:
> I'm trying to change the pictures inside the /live/initrd.gz file.
I really wonder where this file comes from.
> I have followed your suggestions,doing something like this :
> gunzip /live/initrd.gz
I also wonder about the absolute path "/live/initrd.gz".
You have a
>Didn't you strive for manipulating the initrd in /d-i/gtk/initrd.gz of the
ISO ?
I have already changed the pictures inside the /d-i/gtk/initrd.gz file,now
I'm trying to change the pictures inside the /live/initrd.gz file. The
initrd.img-5.10.0-18-amd64 file is in the /custom-root/boot folder,but
Hi,
Mario Marietto wrote:
> echo /usr/share/plymouth/themes/homeworld/logo.png | cpio -H newc -o -A -F
> /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/live/initrd
Didn't you strive for manipulating the initrd in /d-i/gtk/initrd.gz of
the ISO ?
(Are you still with debian-live-11.5.0-
On Sat 22 Oct 2022 at 01:46:05 (+0200), Mario Marietto wrote:
>
> Below you can see what's the real problem : inside the archive there are
> two files with the same name. They seem to be different because their kb
> are different,but I have opened both files with "engrampa" and I saw that
> they a
At least I found what's the correct command to issue :
echo /usr/share/plymouth/debian-logo.png | cpio -H newc -o -A -F initrd
Below you can see what's the real problem : inside the archive there are
two files with the same name. They seem to be different because their kb
are different,but I have
Hello again to everyone. I've tried many times to change the pictures that
I'd previously added inside the initrd file located inside the folder
"/home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/live/initrd"
of my "BridgeVmOS-live-11.5.0-2022.10.07-amd64-xfce.iso" image file and it
seems
Your last comment does not seem to be properly nice,when you say "your
verbose thread". Anyway,this is what you missed : "I want to achieve (to
create a debian distro ready for passing through every nvidia gpu which
works out of the box + various tools for achieving that goal and some
pre-made conf
On 2022-10-17, Mario Marietto wrote:
>
> Hello to everyone.
>
> I'm building my debian derivative distro not for business purposes,but to
> be useful to someone. Maybe I will ask for some money as a donation,but I'm
In what way would it be more useful, or useful in a different way for
different p
It seems complicated to understand what I can do and what I can't. So,my
idea is to prepare everything and then I will give my github repo (maybe
configured as a private repo) to a debian legal representative hoping that
he/she will tell me precisely where the project needs to be changed. But I
als
[Title of the mail changed to reflect a new subject and topic following
the suggestions in the FAQ and mailing list code of conduct.]
Forwarded to the list as I sent this only to Mario by mistake.
On Mon, Oct 17, 2022 at 06:29:45PM +0200, Mario Marietto wrote:
> Hello to everyone.
>
Hi Mario,
>
Hello to everyone.
I'm building my debian derivative distro not for business purposes,but to
be useful to someone. Maybe I will ask for some money as a donation,but I'm
not even sure. When I will have created the first stable version,I will put
it in my github with all the scripts that I have adde
Hi,
David Wright wrote:
> they are no longer Debian logos. You
> should give names to your edited files that indicate what they are:
> /your/ images for /your/ derivative. Add them to the archive and
> change the symlinks there.
I found
https://wiki.debian.org/Derivatives/Guidelines
which Mario
On Sun 16 Oct 2022 at 17:24:05 (+0200), Mario Marietto wrote:
> Il giorno dom 16 ott 2022 alle ore 10:50 Thomas Schmitt ha scritto:
> > On Sat 15 Oct 2022 at 23:03:41 (+0200), Mario Marietto wrote:
> > > echo logo_debian_dark.png | cpio -H newc -o -A -F
> > > initrd/usr/share/graphics
> > > cpio:
Thanks very much. It worked : https://ibb.co/GHHDQ3H ; I'm at a good point
by creating this derivative debian distro.
Il giorno dom 16 ott 2022 alle ore 10:50 Thomas Schmitt
ha scritto:
> Hi,
>
> Mario Marietto wrote:
> > echo logo_debian_dark.png | cpio -H newc -o -A -F
> initrd/usr/share/graph
Hi,
Mario Marietto wrote:
> echo logo_debian_dark.png | cpio -H newc -o -A -F initrd/usr/share/graphics
> cpio: can't open initrd/usr/share/graphics: Is not a directory
cpio option -F expects the path to the archive as argument. I.e. the path
to the uncompressed initrd.
> The images that I shou
Hello.
I have understood that the graphic files I need to change are inside the
file called "initrd.gz" that's inside this folder :
/home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/d-i/gtk/
I should decompress it and I will have the file called "initrd",that's a
cpio file. The images
Hello to everyone.
I'm trying to customize the debian 11 and I'm creating a derivative distro
for debian 11. I've changed a lot of logos,images and pictures,but not
everything. For example I'm not able to understand which file belongs to
the image and the logo that you see in this picture : https:
😂
Il giorno gio 13 ott 2022 alle ore 22:35 Thomas Schmitt
ha scritto:
> Hi,
>
> Mario Marietto wrote:
> > anyway,using another append shouldn't be wrong because the debian
> developers
> > used,not me,in this way
>
> Oh. In this case we should not bet against their wisdom.
>
> If it is by mistak
Hi,
Mario Marietto wrote:
> anyway,using another append shouldn't be wrong because the debian developers
> used,not me,in this way
Oh. In this case we should not bet against their wisdom.
If it is by mistake, then it is harmless and heavily tested during the
last years.
(Regrettably i have not m
Is it like this ?
LABEL Custom Graphical Debian Installer
SAY "Booting Custom Graphical Debian Installer..."
linux /d-i/gtk/vmlinuz
APPEND file=/cdrom/preseed/preseed.cfg auto=true
initrd=/d-i/gtk/initrd.gz video=vesa:ywrap,mtrr vga=788
anyway,using another append shouldn't be wrong because
Hi,
Mario Marietto wrote:
> You are right. It works without using the APPEND option
Yeah. Once again guessed right. :))
> I don't know if it's correct to use something like this in the
ISOLINUX/menu.cfg file :
> LABEL Custom Graphical Debian Installer
> SAY "Booting Custom Graphical Debian In
You are right. It works without using the APPEND option,like this : (inside
the file grub.cfg)
menuentry "Custom Graphical Debian Installer" {
linux /d-i/gtk/vmlinuz file=/cdrom/preseed/preseed.cfg auto=true
video=vesa:ywrap,mtrr vga=788 "${loopback}"
initrd /d-i/gtk/initrd.gz
}
anyway,I don
Hi,
Mario Marietto wrote:
> ... > menuentry "Debian Custom Graphical Debian Installer" {
> ... > linux /d-i/gtk/vmlinuz APPEND file=/cdrom/preseed/preseed.cfg
auto=true video=vesa:ywrap,mtrr vga=788 "${loopback}"
> ... > initrd /d-i/gtk/initrd.gz
> If I remove the argument APPEND,the only oth
On Thu, 2022-10-13 at 17:02 +0200, Mario Marietto wrote:
> If I remove the argument APPEND,the only other chance that I have to pass
> the preseed file is to add it inside the initrd file.
What effect do we think the word 'APPEND' below is having in the grub
config file?
menuentry "Debian GNU/L
If I remove the argument APPEND,the only other chance that I have to pass
the preseed file is to add it inside the initrd file. But this is not the
official method suggested by the cubic developers. If you will read on the
preseed tab on cubic you will see that they suggest to prefix the preseed
fi
Hi,
Mario Marietto wrote:
> > > menuentry "Debian Custom Graphical Debian Installer" {
> > > linux /d-i/gtk/vmlinuz APPEND file=/cdrom/preseed/preseed.cfg
> > > auto=true video=vesa:ywrap,mtrr vga=788 "${loopback}"
> > > initrd /d-i/gtk/initrd.gz
> > >
> > > Does it make more sense ?
I wrote
ok. If you don't like to append,tell me what you would like to do because I
didn't understand.
Il giorno gio 13 ott 2022 alle ore 13:07 Thomas Schmitt
ha scritto:
> Hi,
>
> > menuentry "Debian Custom Graphical Debian Installer" {
> > linux /d-i/gtk/vmlinuz APPEND file=/cdrom/preseed/preseed.c
Hi,
> menuentry "Debian Custom Graphical Debian Installer" {
> linux /d-i/gtk/vmlinuz APPEND file=/cdrom/preseed/preseed.cfg auto=true
> video=vesa:ywrap,mtrr vga=788 "${loopback}"
> initrd /d-i/gtk/initrd.gz
>
> Does it make more sense ?
In the interest of future readers who seek the same s
I've removed the "APPEND file=/cdrom/preseed/preseed.cfg auto=true"
parameter(s) from the live menu entry,even because it makes no sense to
keep it. The live system does not imply that the user can choose some
parameters. It is not an installer at all,all parameters have been decided
from the begin
Hi,
Mario Marietto wrote:
> What I haven't understood well is if, in your opinion, this "code" is well
> written or not :
>
> menuentry "Debian GNU/Linux Custom (kernel 5.10.0-18-amd64)" {
> linux /d-i/gtk/vmlinuz APPEND file=/cdrom/preseed/preseed.cfg auto=true
> initrd=/live/initrd.gz boot=li
Hello.
What I haven't understood well is if, in your opinion, this "code" is well
written or not :
menuentry "Debian GNU/Linux Custom (kernel 5.10.0-18-amd64)" {
linux /d-i/gtk/vmlinuz APPEND file=/cdrom/preseed/preseed.cfg auto=true
initrd=/live/initrd.gz boot=live components locales=en_US.UTF
Actually I'm using only UEFI and the file that I should modify is located
on
/home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/boot/grub/grub.cfg.
What works is this :
menuentry "Debian GNU/Linux Custom (kernel 5.10.0-18-amd64)" {
linux /d-i/gtk/vmlinuz APPEND file=/cdrom/preseed/prese
Hi,
Mario Marietto wrote:
> In the end I found the solution.
Congrats.
-
Some remarks on the way to success:
> isolinux/menu.cfg
> LABEL English (en)
> SAY "Booting English (en)..."
> linux /live/vmlinuz boot=casper APP
On Tue, 11 Oct 2022 23:35:48 +0200
Mario Marietto wrote:
> > isolinux/menu.cfg
> >
> > LABEL English (en)
> > SAY "Booting English (en)..."
> > linux /live/vmlinuz boot=casper APPEND
> > file=/cdrom/preseed/preseed.cfg auto=true initrd=/live/initrd.gz
> > boot=live components locales=en_US.UT
In the end I found the solution. I've added these lines on top of the file
:
/home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/boot/grub/grub.cfg,with
this content :
menuentry "Debian GNU/Linux Custom (kernel 5.10.0-18-amd64)" {
linux /d-i/gtk/vmlinuz APPEND file=/cdrom/preseed/preseed
It is on the file
/home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-disk/boot/grub/grub.cfg,with
this content :
https://pastebin.ubuntu.com/p/gHwWXPvXB2/
The preseed file is still ignored.
Il giorno mer 12 ott 2022 alle ore 00:06 Greg Wooledge
ha scritto:
> On Tue, Oct 11, 2022 at 11:55:5
On Tue, Oct 11, 2022 at 11:55:56PM +0200, Mario Marietto wrote:
> What is "${loopback}" in the context below ?
[...]
> insmod play
> play 960 440 1 0 4 440 1
> if [ ${iso_path} ] ; then
> set loopback="findiso=${iso_path}"
> export loopback
> fi
If this is supposed to be a shell script, that "se
What is "${loopback}" in the context below ?
if loadfont $prefix/font.pf2 ; then
set gfxmode=800x600
set gfxpayload=keep
insmod efi_gop
insmod efi_uga
insmod video_bochs
insmod video_cirrus
insmod gfxterm
insmod png
terminal_output gfxterm
fi
if background_image /isolinux/splash
I've added the string in both config files (menu.cfg and grub.cfg) and then
I have rebuilt the ISO with cubic but the preseed file has been ignored by
the graphical debian installer.
Il giorno mar 11 ott 2022 alle ore 23:17 Mario Marietto <
marietto2...@gmail.com> ha scritto:
> I'm trying to modi
I'm trying to modify them as follows :
isolinux/menu.cfg
LABEL English (en)
SAY "Booting English (en)..."
linux /live/vmlinuz boot=casper APPEND file=/cdrom/preseed/preseed.cfg
auto=true initrd=/live/initrd.gz boot=live components locales=en_US.UTF-8
quiet splash intel_iommu=on
boot/grub/gru
Hi,
Mario Marietto wrote:
> Finally I found something that's very close to the solution :
> https://askubuntu.com/questions/1228909/preseed-config-using-cubic-is-ignored-during-installation
If this shall be the solution then the files to change would probably be
isolinux/menu.cfg
boot/grub/gr
Finally I found something that's very close to the solution :
https://askubuntu.com/questions/1228909/preseed-config-using-cubic-is-ignored-during-installation
Il giorno mar 11 ott 2022 alle ore 21:43 Mario Marietto <
marietto2...@gmail.com> ha scritto:
> Maybe we reach the goal faster if we und
Maybe we reach the goal faster if we understand what the "cubic" developer
wants us to do by reading the message that appears on top of the preseed
tab ? Some step is missed and I'm not able to understand which one : give a
look here : https://ibb.co/9N0zL2P
Il giorno mar 11 ott 2022 alle ore 21
I always choose "Graphical Debian Installer" ,but I have to curb your
enthusiasm. Yesterday I added the preseed.cfg file inside the
/d-i/gtk/initrd.gz file and it has been ignored as well.
Il giorno mar 11 ott 2022 alle ore 21:16 Thomas Schmitt
ha scritto:
> Hi,
>
> i should have looked into the
Hi,
i should have looked into the boot/grub/grub.cfg file for initrd usage:
...
menuentry "Debian GNU/Linux Live (kernel 5.10.0-18-amd64)" {
linux /live/vmlinuz-5.10.0-18-amd64 boot=live components splash quiet
"${loopback}"
initrd /live/initrd.img-5.10.0-18-amd64
}
... many la
Hi,
Mario Marietto wrote:
> Does it make sense to insert the preseed file inside this file ? >
> /home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-root/boot/initrd.img-5.10.0-18-amd64
?
> What's the difference between initrd and initrd.img-5.10.0-18-amd64 ?
Interesting question. (You see
On Tue, Oct 11, 2022 at 06:36:26PM +0200, Mario Marietto wrote:
> You entered in a kind of analysis that I'm not able to do without the help
> of someone else more skilled than me. I've tried to add the preseed file
> even on the initrd file located on the live folder,but it didn't work. I
> don't
Does it make sense to insert the preseed file inside this file ? >
/home/ziomario/Scrivania/PassT-Cubic/Debian-new/custom-root/boot/initrd.img-5.10.0-18-amd64
?
What's the difference between initrd and initrd.img-5.10.0-18-amd64 ?
Instructions says :
Regenerating md5sum.txt
cd isofileschmod +
You entered in a kind of analysis that I'm not able to do without the help
of someone else more skilled than me. I've tried to add the preseed file
even on the initrd file located on the live folder,but it didn't work. I
don't know what to do further,but you gave me more material to post another
qu
Hi,
Mario Marietto wrote:
> Can you suggest some other nice places where I can post the
> question again ?
No. This list here and debian-live are the best places to ask.
At least i know of no better ones.
If i were in your situation i would try to find out how the software
in the initrd is supp
Sometimes it happens that no one replied to a specific ML. Anyway I have
some experience in linux and freebsd management. I have used Linux,as a
hobbyist ,since the 1990's. But it happens rarely. More often happens that
inside the IRC channels no one will help. I've always found a lot of bots
and n
Hi,
Mario Marietto wrote:
> I suppose that the ML debian-live is not
> active or it is a very very low level of activity.
It's what exists in respect to Debian Live ISOs.
https://www.debian.org/devel/debian-live/
mentions the bug tracking system, the debian-live mailing list, and an
IRC channel
Nope. My project is not compatible with that. I want to re-distribute the
ISO,so if I do that I should keep online a server only for the distribution
of the preseed file. This costs money. And furthermore there is something
that is not working. Your job should be to understand the reasons and
help,
I would recommend to put the preseed file on a HTTP/FTP server. Then the file
is easier to edit, and it saves you the effort to customize an ISO.
- Tim
On 2022-10-09 23:38+0200, Mario Marietto wrote:
I have also tried this version :
xorriso \
-outdev debian-live-11.5.0-amd64-xfce.iso \
-v
Hi,
i wrote:
> > ( cd /home/ziomario/Scrivania/PassT-Cubic/ISO/preseed/
> > echo preseed.cfg | cpio -H newc -o -A -F
> > /home/ziomario/Scrivania/PassT-Cubic/ISO/debian-live-11.5.0-amd64-xfce/d-i/initrd
> > )
Mario Marietto wrote in a mail Cc'ed to debian-user@lists.debian.org:
> ok. I did it
Hi,
Mario Marietto wrote:
> I've found this tutorial and I've followed,integrating the Thomas
> suggestions :
> https://github.com/Nidouille/Debian-Automated-Installation
The section "Creation de l'ISO" is outdated since Debian 7.
The excuse "UEFI : grub Modification non faite, car je suis en vm
Hello again.
Now it's the right time to explain the whole project that I'm working on to
you,because now I have the missing piece,thanks to Thomas and I can exclude
one of the reasons why it does not work. What I would like to do is to use
a preseed file to preconfigure some options,so that the de
Finally,this version works as expected :
script2.sh
orig_iso=debian-live-11.5.0-amd64-xfce.iso
new_iso=debian-live-11.5.0-amd64-modified-xfce.iso
mbr_template=isohdpfx.bin
# Extract MBR template file to disk
dd if="$orig_iso" bs=1 count=432 of="$mbr_template"
xorriso \
-outdev "$new_iso"
Hi,
Mario Marietto wrote:
> Drive current: -outdev 'debian-live-11.5.0-amd64-xfce.iso'
> Media current: stdio file, overwriteable
> Media status : is written , is appendable
> Media summary: 1 session, 1310720 data blocks, 2560m data, 40.3g free
> ...
> xorriso : FAILURE : -indev differs from -out
Thanks. I've replied to ubuntuforums. Concerning the first
attempt,instead,I have created the folder iso_unpacked_and_modified and
inside of it I have placed the folder isolinux with the file isolinux.bin.
This is what happened :
script2.sh
orig_iso=debian-live-11.5.0-amd64-xfce.iso
new_files=deb
Hi,
Mario Marietto wrote:
> I've replied on the ubuntuforums.
The deficiency of your run in
https://ubuntuforums.org/showthread.php?t=2479825&p=14115075#post14115075
is that you did not give the options for creating EFI boot lures.
Your VM states to have OVMF as firmware.
> I have also tried
I have also tried this version :
xorriso \
-outdev debian-live-11.5.0-amd64-xfce.iso \
-volid d-live \
-padding 0 \
-map /home/ziomario/Scrivania/PassT-Cubic/ISO/iso_unpacked_and_modified
/ \
-chmod 0755 / -- \
-boot_image isolinux dir=/isolinux \
-boot_image isolinux
system_a
1 - 100 of 102 matches
Mail list logo
