On Sat, 11 Apr 2020 at 11:09, Sreyan Chakravarty wrote:
> > There are no tutorials or docs out there laying out how you are suppose
> to do a Kickstart install with NFS.
>
> Whoops, I mean USB not NFS.
>
> Ok, I don't mean to rude or flippant, but I these requests mainly don't
> get answered. I m
> There are no tutorials or docs out there laying out how you are suppose
to do a Kickstart install with NFS.
Whoops, I mean USB not NFS.
Ok, I don't mean to rude or flippant, but I these requests mainly don't get
answered. I mean dont get me wrong I owe all my progress to Thomas and you.
Anyway
On 4/11/20 1:09 AM, Sreyan Chakravarty wrote:
> If you were using USB flash, it would be simple.
How would it be simple ? There are no tutorials or docs out there laying
out how you are suppose to do a Kickstart install with NFS.
There are. Also, you could ask here as there are several acti
> If you were using USB flash, it would be simple.
How would it be simple ? There are no tutorials or docs out there laying
out how you are suppose to do a Kickstart install with NFS.
On Sat, Apr 11, 2020 at 12:25 PM Samuel Sieb wrote:
> On 4/10/20 1:46 PM, Sreyan Chakravarty wrote:
> > > Hm.
On 4/10/20 1:46 PM, Sreyan Chakravarty wrote:
> Hm. This should yield the same result as -dev test.iso.
> I still get
mount: /dev/loop0p1: can't read superblock
May be I am doing something wrong.
Without your help I think I would have left Fedora since there are no
tutorials as to how I
Hi,
i wrote:
> > I still get
> > mount: /dev/loop0p1: can't read superblock
Sreyan Chakravarty wrote:
> May be I am doing something wrong.
Success by mistake is a classical pattern. :))
We will learn more when success vanishes righteously.
> I did not even know that USB sticks had a MBR part
> Hm. This should yield the same result as -dev test.iso.
> I still get
> mount: /dev/loop0p1: can't read superblock
May be I am doing something wrong.
Without your help I think I would have left Fedora since there are no
tutorials as to how I can get a Kickstart file on to a disk. You have
hel
Hi,
> But when I add an output device to the image like
> xorriso -indev test.iso \
> -boot_image any keep \
> -map "$file_or_tree_on_disk" "$path_in_iso" \
> -outdev test.iso
>
> Everything magically works.
> Weird.
Hm. This should yield the same result as -dev tes
Hi,
Sreyan Chakravarty wrote:
> Okay, so what you are doing is actually against convention.
It's fully compliant. Just moving apart the default mountable superblock
from the chain of session superblocks which need an extra option to
mount(8) in order to get mounted.
> Essentially, the OS assume
> In Nautilus, if I right-click an .iso file, I have the option to open
> with the disk image mounter. That works.
Ok, using the command:
xorriso -dev test.iso \
-boot_image any keep \
-map "$file_or_tree_on_disk" "$path_in_iso"
Does not work even if I use right-click and
> That's the reason for my invention of emulated table of content.
> The first session does not get written to block 0 but rather to block 32.
> This leaves room for an official superblock at block 0 and thus saves
> the superblock of the first session from being overwritten by session 2.
> Now the
Hi,
Sreyan Chakravarty wrote:
> I am kind of confused as to the difference/advantage between keeping the old
> boot image versus rebuilding one.
My first multi-session proposal was to keep as much of the boot equipment
as possible.
After all, we began with the riddle why your genisoimage produced
Sorry rather why are you disabling session history ?
Any particular reason?
On Wed, Apr 8, 2020 at 11:54 PM Thomas Schmitt wrote:
> Hi,
>
> Sreyan Chakravarty wrote:
> > xorriso -dev Fedora-Workstation-Live-x86_64-31-1.9.iso -boot_image any
> keep
> > -map /home/sreyan/anaconda-ks.cfg /isolinux
> Is there any noteworthy text to see, beyond what is quoted above ?
No you can ignore it. It was just a screenshot from VirtualBox describing
the superblocks problem I typed out.
I can't thank you enough for your in-depth explanations. Not only are you
helping me with my problem but I also lear
> I only see a black rectangle (with some framing ornaments).
> My web browser is old.
>
> Is there any noteworthy text to see, beyond what is quoted above ?
Nothing of value. You can ignore it.
I could not be more grateful for your in-depth replies. Not only are you
helping me with my problem
On 4/8/20 10:37 PM, Sreyan Chakravarty wrote:
On 4/8/20 11:03 AM, Sreyan Chakravarty wrote:
Gnome Disks is expecting a disk and the .iso file looks like one:
# file Fedora-Workstation-Live-x86_64-31-1.9.iso
Fedora-Workstation-Live-x86_64-31-1.9.iso: DOS/MBR boot sector;
partition 2 : ID=0xef, sta
> On 4/8/20 11:03 AM, Sreyan Chakravarty wrote:
>
> Yes.
>
>
> Gnome Disks is expecting a disk and the .iso file looks like one:
> # file Fedora-Workstation-Live-x86_64-31-1.9.iso
> Fedora-Workstation-Live-x86_64-31-1.9.iso: DOS/MBR boot sector;
> partition 2 : ID=0xef, start-CHS (0x3ff,254,63)
Hi,
i wrote falsely:
> $ sudo -P -f Fedora-Workstation-Live-x86_64-31-1.9.iso
That should of course have been a losetup run:
sudo losetup -P -f Fedora-Workstation-Live-x86_64-31-1.9.iso
Have a nice day :)
Thomas
___
users mailing list -- users@l
Hi,
Sreyan Chakravarty wrote:
> xorriso -dev Fedora-Workstation-Live-x86_64-31-1.9.iso -boot_image any keep
> -map /home/sreyan/anaconda-ks.cfg /isolinux/anacondaks.cfg
Looks ok. But see below for a variation that pleases GNOME Disks.
First some diagnosis:
> double clicking in GNOME File Manage
On 4/8/20 11:03 AM, Sreyan Chakravarty wrote:
So if I put the image into a USB can I boot it ?
Yes.
My question is that why can't GNOME disks mount it ?
Gnome Disks is expecting a disk and the .iso file looks like one:
# file Fedora-Workstation-Live-x86_64-31-1.9.iso
Fedora-Workstation-Live
So if I put the image into a USB can I boot it ?
My question is that why can't GNOME disks mount it ?
On Wed, Apr 8, 2020 at 10:36 PM Samuel Sieb wrote:
> On 4/8/20 9:57 AM, Sreyan Chakravarty wrote:
> > It ran perfectly, but when I tried mounting the now modified ISO image
> > by double clicki
On 4/8/20 9:57 AM, Sreyan Chakravarty wrote:
It ran perfectly, but when I tried mounting the now modified ISO image
by double clicking in GNOME File Manager which uses GNOME Disks to mount
ISO files I get the error:
Error mounting /dev/loop0p1 at /run/media/sreyan/Fedora-WS-Live-31-1-9:
can't
Sorry I forgot to attach the dmesg log:
[ 591.907687] loop: module loaded
[ 591.916803] loop0: p1 p2 p3
[ 592.293941] ISOFS: unable to read i-node block
[ 592.293945] isofs_fill_super: get root inode failed
[ 593.806597] ISOFS: unable to read i-node block
[ 593.806600] isofs_fill_super: get
Its not everyday that I have the honor of talking to an actual developer
for a GNU utility. I am extremely lucky, grateful and honored to have your
input on my problem. Thank you so much for that.
The idea of using multi-session to add the file to the ISO image is genius
by the way.
There is howe
Hi,
i wrote:
> The resulting ISO will grow by the size of the whole ISO directory tree
> and the size of the data files which get added.
Clarification:
"size of the whole ISO directory tree" means the size of the meta-data,
not the size of the data files in the tree.
The meta-data in Fedora-Works
Hi,
Sreyan Chakravarty wrote:
> If someone asked you to create a custom Fedora ISO that you could use in
> VirtualBox/DVD/USB, what would you do ?
(As first i'd try what you did: Build a new ISO from the mounted original.
Then i'd try whether the original works in the test situation.
Then i'd i
> Hi,
> So i assume you see an ISOLINUX menu with the labels you expect from your
> isolinux.cfg file. (If not, then this would make much more sense to me,
> though.)
>
> Since i assume that your "." directory was the mounted original ISO
> or a copy of the mounted file tree of that ISO, the diffe
Hi,
Sreyan Chakravarty wrote here:
> Its stuck at the bootmenu.
and at sysli...@syslinux.org:
> Unfortunately when I boot and press enter nothing happens.
So i assume you see an ISOLINUX menu with the labels you expect from your
isolinux.cfg file. (If not, then this would make much more sense to
If anyone knows how the official images are compiled please let me know.
On Tue, Apr 7, 2020 at 5:23 PM Sreyan Chakravarty
wrote:
> I am unable to boot the custom ISO I have created.
>
> I have just created a Custom ISO from the Fedora Live ISO using the
> following command:
>
> genisoimage -U -
I am unable to boot the custom ISO I have created.
I have just created a Custom ISO from the Fedora Live ISO using the
following command:
genisoimage -U -r -v -T -J -joliet-long -V "Fedora-WS-Live-31-1-9" -volset
"Fedora-WS-Live-31-1-9" -A "CDLABEL=Fedora-WS-Live-31-1-9" -b
isolinux/isolinux.bin
30 matches
Mail list logo
