From joern.rink at googlemail.com Fri Apr 2 13:35:02 2021 From: joern.rink at googlemail.com (Niene Rink) Date: Fri, 2 Apr 2021 15:35:02 +0200 Subject: Official way to add files to a livecd with livemedia-creator Message-ID: <20210402153502.328bf961f4a9d1f48152c498@gmail.com> Hello, really sorry when this is not the right place for the question. I want to add own files to the home of liveuser. I read many tutorials and the last one notes, that you have to add this in the %post nochroot section of the flatks file. I am using a mock environment and add the specific files to the root of my mock, than add the section with: tar -xvf test.tar.gz -C $INSTALL_ROOT/home/liveuser/ also the comand: setxkbmap -de in the section does not work. Than i recreate the iso, putting the stuff into the %post section, as mentioned also in a blog, no effort. So, my question: Is it possible to add files to the lived userhome directory or to the livecd filesystem? If yes, what is the official or best way to do this? thx and greetings from germany J?rn Rink From joern.rink at googlemail.com Sat Apr 3 12:39:55 2021 From: joern.rink at googlemail.com (Niene Rink) Date: Sat, 3 Apr 2021 14:39:55 +0200 Subject: Official way to add files to a livecd with livemedia-creator In-Reply-To: <20210402153502.328bf961f4a9d1f48152c498@gmail.com> References: <20210402153502.328bf961f4a9d1f48152c498@gmail.com> Message-ID: <20210403143955.0f2b2efa8a5c2cd770d1dee6@gmail.com> Am Fri, 2 Apr 2021 15:35:02 +0200 hat Niene Rink (Niene Rink) folgendes geschrieben: Hello, since yesterday i am a step further. from a post which is closed: https://github.com/weldr/lorax/issues/197 a guy describes exact my problem. Brian ansers and closed this threat with the info to use --add-arch-template. I recognize, that lmc has not the parameter, i look into the default arch templates, i found a section, but this section is not in the template which livemediacreator uses. so i add this section in the usr/share/lorax/templates.d/99-generic/live/x86.tmpl template. Cause i am not familar with the mako language, after trial and error a lot, i set the workdir, which is not set to "." in the live/x68.tmpl. i create a iso-graft in my mock chroot root and move a testfile inside. build the live iso and, voila, its there, but not where i am expect it. As i remember correctly, it was in the /run/.... tree, not in the root filesystem. I still try to search a method to put files into the live os tree. i am able to create a directory there (with the post section of the flatten ks file) but i am not able to move a file inside that directory. So, is there an easy way to move files to a liveos with lmc from a mock environment? > Hello, > really sorry when this is not the right place for the question. > > I want to add own files to the home of liveuser. > > I read many tutorials and the last one notes, that you have to add > this in the %post nochroot section of the flatks file. > > I am using a mock environment and add the specific files to the root > of my mock, than add the section with: > > tar -xvf test.tar.gz -C $INSTALL_ROOT/home/liveuser/ > > also the comand: > setxkbmap -de > > in the section does not work. > > Than i recreate the iso, putting the stuff into the %post section, as > mentioned also in a blog, no effort. > > So, my question: > Is it possible to add files to the lived userhome directory or to the > livecd filesystem? > If yes, what is the official or best way to do this? > > thx and greetings from germany > > J?rn Rink From gregory.young at solarwinds.com Mon Apr 5 16:50:46 2021 From: gregory.young at solarwinds.com (Young, Gregory) Date: Mon, 5 Apr 2021 16:50:46 +0000 Subject: `inst.ks` hides installation source on an ISO? In-Reply-To: <1b4dea70-601d-1720-509e-5ffea0d39279@dafydd.com> References: <1b4dea70-601d-1720-509e-5ffea0d39279@dafydd.com> Message-ID: >From your description, I suspect when you generated the iso, you didn?t label it, or you gave it a different label than ?CentOS-8-3-2011-x86_64-dvd?. Also be careful of spaces in the label name. Here is the entry I use: append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 inst.ks=hd:LABEL=CentOS\x207\x20x86_64:/ks.cfg inst.sshd inst.graphical inst.noninteractive inst.noshell net.ifnames=0 selinux=0 rhgb quiet vga=792 modprobe.blacklist=floppy consoleblank=0 biosdevname=0 rdblacklist=nouveau nouveau.modeset=0 And this is the genisoimage command: genisoimage \ -input-charset default \ -U \ -r \ -v \ -T \ -J \ -joliet-long \ -V "CentOS 7 x86_64" \ -volset "CentOS 7 x86_64" \ -A "CentOS 7 x86_64" \ -b "isolinux/isolinux.bin" \ -c "isolinux/boot.cat" \ -no-emul-boot \ -boot-load-size 4 \ -boot-info-table \ -eltorito-alt-boot \ -e "images/efiboot.img" \ -no-emul-boot \ -o "${SCRIPT_DIR}/disk.iso" \ "${BUILDDIR}/" Greg From: kickstart-list-bounces at redhat.com on behalf of David Barr Date: Saturday, March 27, 2021 at 17:26 To: kickstart-list at redhat.com Subject: `inst.ks` hides installation source on an ISO? Good Morning! Duck Duck Go searches haven't helped me, and this problem feels like it has an obvious answer if I put the question in front of the right person. I'm adding a kickstart reference to an ISO. When I do, Anaconda (I think) can't find the Installation Source. If I drop the "inst.ks" the Installation Source is autodetected. So, an unmodified entry in isolinux/isolinux.cfg looks like this: ``` label linux menu label ^Install CentOS Linux 8 kernel vmlinuz append initrd=initrd.img inst.stage2=hd:LABEL=CentOS-8-3-2011-x86_64-dvd quiet ``` This will autodetect the Installation Source. If I add a kickstart reference: ``` label linux menu label ^Install CentOS Linux 8 kernel vmlinuz append initrd=initrd.img inst.stag2=hd:LABEL=CentOS-8-3-2011-x86_64-dvd quiet inst.ks=hd:LABEL=CentOS-8-3-2011-x86_64-dvd ``` No Installation Source is found, but any `repo` entries in the kickstart file will be listed as "Additional Repositories." This is true for any variety of inst.ks reference. ("inst.ks=hd:/dev/sdb", "inst.ks=hd:/dev/sdb:/ks.cfg", etc.) Am I not seeing a kickstart entry that specifies the Installation Source? Do I have to add another `append` argument that specifies the Installation Source? What am I missing? Thanks! David Previous problems and solutions: - https://unix.stackexchange.com/questions/640232/verified-good-mkisofs-for-centos-8/640786 - https://unix.stackexchange.com/questions/641277/centos-8-custom-iso-adding-ks-cdrom-ks-cfg-hangs-the-installer/641278 -- David/dafydd PGP Public Key ?The hardest thing in the world is to change the minds of people who keep saying, ?But we?ve always done it this way.? These are days of fast changes and if we don?t change with them, we can get hurt or lost.? -- Admiral Grace Hopper -------------- next part -------------- An HTML attachment was scrubbed... URL: From dafydd at dafydd.com Wed Apr 7 03:32:36 2021 From: dafydd at dafydd.com (David Barr) Date: Tue, 6 Apr 2021 20:32:36 -0700 Subject: `inst.ks` hides installation source on an ISO? In-Reply-To: References: <1b4dea70-601d-1720-509e-5ffea0d39279@dafydd.com> Message-ID: <41a00f99-7adb-ec89-2e45-1266fb0ce77f@dafydd.com> Hi, Greg, My scripted ISO creation process is at https://github.com/dafydd2277/systemAdmin/tree/main/kickstart/centos8 It includes executing `blkid` on the exemplar ISO, and storing that volume label in a variable to add to `mkisofs -V...` I've run into so many challenges with kickstart on CentOS 8 that I have three issues in that GitHub repository for keeping track. I've turned two of those issues into bugs at bugzilla.redhat.com. Thanks! David On 4/5/21 09:50, Young, Gregory wrote: > > From your description, I suspect when you generated the iso, you > didn?t label it, or you gave it a different label than > ?CentOS-8-3-2011-x86_64-dvd?. Also be careful of spaces in the label > name. Here is the entry I use: > > ? > > append initrd=initrd.img inst.stage2=hd:LABEL=CentOS\x207\x20x86_64 > inst.ks=hd:LABEL=CentOS\x207\x20x86_64:/ks.cfg inst.sshd > inst.graphical inst.noninteractive inst.noshell net.ifnames=0 > selinux=0 rhgb quiet vga=792 modprobe.blacklist=floppy consoleblank=0 > biosdevname=0 rdblacklist=nouveau nouveau.modeset=0 > > ? > > And this is the genisoimage command: > > ? > > genisoimage \ > > ??? -input-charset default \ > > ??? -U \ > > ??? -r \ > > ??? -v \ > > ??? -T \ > > ??? -J \ > > ??? -joliet-long \ > > ??? -V "CentOS 7 x86_64"\ > > ??? -volset "CentOS 7 x86_64"\ > > ??? -A "CentOS 7 x86_64"\ > > ??? -b "isolinux/isolinux.bin"\ > > ??? -c "isolinux/boot.cat"\ > > ??? -no-emul-boot \ > > ??? -boot-load-size 4 \ > > ??? -boot-info-table \ > > ??? -eltorito-alt-boot \ > > ??? -e "images/efiboot.img"\ > > ??? -no-emul-boot \ > > ??? -o "${SCRIPT_DIR}/disk.iso"\ > > ??? "${BUILDDIR}/" > > ? > > ? > > Greg > > ? > > *From: *kickstart-list-bounces at redhat.com > on behalf of David Barr > > *Date: *Saturday, March 27, 2021 at 17:26 > *To: *kickstart-list at redhat.com > *Subject: *`inst.ks` hides installation source on an ISO? > > Good Morning! > > Duck Duck Go searches haven't helped me, and this problem feels like > it has an obvious answer if I put the question in front of the right > person. > > I'm adding a kickstart reference to an ISO. When I do, Anaconda (I > think) can't find the Installation Source. If I drop the "inst.ks" the > Installation Source is autodetected. So, an unmodified entry in > isolinux/isolinux.cfg looks like this: > > ``` > label linux > ? menu label ^Install CentOS Linux 8 > ? kernel vmlinuz > ? append initrd=initrd.img > inst.stage2=hd:LABEL=CentOS-8-3-2011-x86_64-dvd quiet > ``` > > This will autodetect the Installation Source. If I add a kickstart > reference: > > ``` > label linux > ? menu label ^Install CentOS Linux 8 > ? kernel vmlinuz > ? append initrd=initrd.img? > inst.stag2=hd:LABEL=CentOS-8-3-2011-x86_64-dvd quiet > inst.ks=hd:LABEL=CentOS-8-3-2011-x86_64-dvd > ``` > > No Installation Source is found, but any `repo` entries in the > kickstart file will be listed as "Additional Repositories." This is > true for any variety of inst.ks reference. ("inst.ks=hd:/dev/sdb", > "inst.ks=hd:/dev/sdb:/ks.cfg", etc.) > > Am I not seeing a kickstart entry that specifies the Installation > Source? Do I have to add another `append` argument that specifies the > Installation Source? What am I missing? > > Thanks! > David > > Previous problems and solutions: > > - > https://unix.stackexchange.com/questions/640232/verified-good-mkisofs-for-centos-8/640786 > > - > https://unix.stackexchange.com/questions/641277/centos-8-custom-iso-adding-ks-cdrom-ks-cfg-hangs-the-installer/641278 > > > -- > > David/dafydd > > PGP Public Key > > > ?The hardest thing in the world > is to change > the minds of people who keep saying, ?But we?ve always done it this > way.? These are days of fast changes and if we don?t change with them, > we can get hurt or lost.? -- Admiral Grace Hopper > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://listman.redhat.com/mailman/listinfo/kickstart-list -- David/dafydd PGP Public Key ?The hardest thing in the world is to change the minds of people who keep saying, ?But we?ve always done it this way.? These are days of fast changes and if we don?t change with them, we can get hurt or lost.? -- Admiral Grace Hopper -------------- next part -------------- An HTML attachment was scrubbed... URL: