- WLUG - wlug.mailman3.com

Re: (list behavior)

by Danil Smirnov

Hi Doug, See https://wiki.list.org/x/4030680 Sincerely, Danil Smirnov On Sat, Mar 11, 2023 at 9:20 PM Doug Mildram via WLUG <wlug(a)lists.wlug.org> wrote: > Our list server has that quirk, such that > when you post a new item OR reply, > everyone on the list except you > gets a copy/email. I think. > > Probably? the code/coder decided > that you'll know what you sent, and > that you have faith in the list server. > Also.... you can check the "archive". > > Correct me if I'm wrong, anyone! > You did say: usually you get your own > copy/email usually, so it seems a debate. > > I wouldn't know if tweaking the config > to be more giving is an option. > _______________________________________________ > WLUG mailing list -- wlug(a)lists.wlug.org > To unsubscribe send an email to wlug-leave(a)lists.wlug.org > Create Account: https://wlug.mailman3.com/accounts/signup/ > Change Settings: > https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/ > Web Forum/Archive: > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/message/QFH7L… >

March 11, 2023

Re: (list behavior)

by Doug Mildram

Our list server has that quirk, such that when you post a new item OR reply, everyone on the list except you gets a copy/email. I think. Probably? the code/coder decided that you'll know what you sent, and that you have faith in the list server. Also.... you can check the "archive". Correct me if I'm wrong, anyone! You did say: usually you get your own copy/email usually, so it seems a debate. I wouldn't know if tweaking the config to be more giving is an option.

March 11, 2023

Re: Next Meeting

by John Stoffel

>>>>> "Keith" == Keith Wright via WLUG <wlug(a)lists.wlug.org> writes: > Keith Wright <kwright(a)keithdiane.us> writes: >> Tim Keller via WLUG <wlug(a)lists.wlug.org> writes: >> >>> I'm thinking of moving the next meeting to Thursday of next week since we >>> just had a meeting. >>> >>> Any objections? >> >> Not here. All days are much the same to me. > This is a test. I answered this question yesterday and > asked one of my own. It was sent to the list, but did > not come back to me as it usually does. > Maybe Microsoft or Amazon didn't like the link I included. > Does it work this time? I just saw (and answered!) your previous email. Let me know if you still have questions.

March 11, 2023

Re: Next Meeting

by John Stoffel

>>>>> "Keith" == Keith Wright via WLUG <wlug(a)lists.wlug.org> writes: > Tim Keller via WLUG <wlug(a)lists.wlug.org> writes: >> I'm thinking of moving the next meeting to Thursday of next week since we >> just had a meeting. >> >> Any objections? > Not here. All days are much the same to me. > But you remind me that I have been meaning to > ask a question of the WLUG: Does anybody have > thoughts on Linux-compatible printers? I really like Brother printers, especially the laser ones. My last one lasted 14+ years before I replaced it with another Brother printer. I now have an MFC-L2750DW (duplexing, scanning (though NOT duplex scanning with the ADF (Automatic Document Feeder) using gscan2pdf, you have to flip them by hand) and it's working out well. Ethernet, wifi, latest PostSCript 4 drivers from Brother, etc. Works well. > Here is a block diagram of my network > http://www.free-comp-shop.com/none/wireless.html#diagram > Here is a sample of the kind of things I print > http://www.free-comp-shop.com/texscm.html All should work just find with this sucker.

March 11, 2023

Re: Next Meeting

by Keith Wright

Keith Wright <kwright(a)keithdiane.us> writes: > Tim Keller via WLUG <wlug(a)lists.wlug.org> writes: > >> I'm thinking of moving the next meeting to Thursday of next week since we >> just had a meeting. >> >> Any objections? > > Not here. All days are much the same to me. This is a test. I answered this question yesterday and asked one of my own. It was sent to the list, but did not come back to me as it usually does. Maybe Microsoft or Amazon didn't like the link I included. Does it work this time? -- Keith

March 10, 2023

Re: Next Meeting

by Keith Wright

Tim Keller via WLUG <wlug(a)lists.wlug.org> writes: > I'm thinking of moving the next meeting to Thursday of next week since we > just had a meeting. > > Any objections? Not here. All days are much the same to me. But you remind me that I have been meaning to ask a question of the WLUG: Does anybody have thoughts on Linux-compatible printers? I have an HP Laserjet attached via parallel port to an old Linux machine running a CUPS server. (Common Unix Print system) It works, but they no longer make the print cartridges and the old ones are dryed out and printing grey ghosts all over that make it ugly and nearly unreadable. I print about a dozen pages/month of black and white Postscript or PDF documents, so I don't need speed. Color is just troublesome. I would like to continue to use CUPS through an ethernet cable with RJ-45 plugs. Here is a block diagram of my network http://www.free-comp-shop.com/none/wireless.html#diagram Here is a sample of the kind of things I print http://www.free-comp-shop.com/texscm.html -- Keith

March 10, 2023

Next Meeting

by Tim Keller

I'm thinking of moving the next meeting to Thursday of next week since we just had a meeting. Any objections? Thanks, Tim. -- I am leery of the allegiances of any politician who refers to their constituents as "consumers".

March 7, 2023

Re: Re-Roll RHEL isos to skip the 60sec countdown and media check

by John Stoffel

And thanks for sharing the solution as well! I'll keep it around just in case... Also, were you using the full install media, or the smallest bootable media whch then requires the network to install packages? > That's cool, I'm glad you got it working. > Tim. > On Sat, Mar 4, 2023, 10:01 PM Dan Davis via WLUG <wlug(a)lists.wlug.org> wrote: > Good evening, > I don't know if anyone saw this, but I found my answer at: > https://docs.centos.org/en-US/8-docs/advanced-install/assembly_kickstart-an… > In the note saying: > By default, the inst.stage2= boot option is used on the installation media and is set to a > specific label, for example, inst.stage2=hd:LABEL=CentOS-8-BaseOS-x86_64. If you modify the > default label of the file system containing the runtime image, or if you use a customized > procedure to boot the installation system, you must verify that the inst.stage2= boot option > is set to the correct value. > So it was a label problem. I was calling mkisofs with the -V switch and an argument that did > not match the label in isolinux.cfg for inst.stage2. This caused the boot stall. > If anyone saw this, thanks for your consideration. > Best Regards, > Dan > On Sat, Mar 4, 2023 at 2:18 PM Dan Davis <davis.dan.c(a)gmail.com> wrote: > Good Afternoon, > I'm trying to re-roll a RHEL9 iso to remove the media check and 60s timeout that occurs > because rd.live.check is baked into the kernel command line and grub menu. I'd like to use > the result with an unattended install. > I start by loop mounting the OEM iso image and extracting the contents to a working dir. > In the working directory, I've attempted to edit EFI/BOOT/grub.cfg an isolinux/grub.cfg > before rerolling the disk with: > mkisofs -o output.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot > -boot-load-size 4 -boot-info-table workingdir > But after editing either or both, I'm still presented with the 60s default timeout and the > media check (rd.live.check) in the kernel commandline. > Is there something akin to grub2-mkisofs that I need to do for my changes to the grub.cfg > for this iso prior to my re-rolling it? > Thank you, > Dan > _______________________________________________ > WLUG mailing list -- wlug(a)lists.wlug.org > To unsubscribe send an email to wlug-leave(a)lists.wlug.org > Create Account: https://wlug.mailman3.com/accounts/signup/ > Change Settings: https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/ > Web Forum/Archive: > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/message/PP4MH… > _______________________________________________ > WLUG mailing list -- wlug(a)lists.wlug.org > To unsubscribe send an email to wlug-leave(a)lists.wlug.org > Create Account: https://wlug.mailman3.com/accounts/signup/ > Change Settings: https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/ > Web Forum/Archive: https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/message/4ZUZQ…

March 6, 2023

Re: Re-Roll RHEL isos to skip the 60sec countdown and media check

by Tim Keller

Dan, That's cool, I'm glad you got it working. Tim. On Sat, Mar 4, 2023, 10:01 PM Dan Davis via WLUG <wlug(a)lists.wlug.org> wrote: > Good evening, > > I don't know if anyone saw this, but I found my answer at: > > > https://docs.centos.org/en-US/8-docs/advanced-install/assembly_kickstart-an… > > In the note saying: > > By default, the inst.stage2= boot option is used on the installation > media and is set to a specific label, for example, > inst.stage2=hd:LABEL=CentOS-8-BaseOS-x86_64. If you modify the default > label of the file system containing the runtime image, or if you use a > customized procedure to boot the installation system, you must verify that > the inst.stage2= boot option is set to the correct value. > > So it was a label problem. I was calling mkisofs with the -V switch and an > argument that did not match the label in isolinux.cfg for inst.stage2. This > caused the boot stall. > > If anyone saw this, thanks for your consideration. > > Best Regards, > Dan > > On Sat, Mar 4, 2023 at 2:18 PM Dan Davis <davis.dan.c(a)gmail.com> wrote: > >> Good Afternoon, >> >> I'm trying to re-roll a RHEL9 iso to remove the media check and 60s >> timeout that occurs because rd.live.check is baked into the kernel command >> line and grub menu. I'd like to use the result with an unattended install. >> >> I start by loop mounting the OEM iso image and extracting the contents to >> a working dir. In the working directory, I've attempted to edit >> EFI/BOOT/grub.cfg an isolinux/grub.cfg before rerolling the disk with: >> >> mkisofs -o output.iso -b isolinux/isolinux.bin -c isolinux/boot.cat >> -no-emul-boot -boot-load-size 4 -boot-info-table workingdir >> >> But after editing either or both, I'm still presented with the 60s >> default timeout and the media check (rd.live.check) in the kernel >> commandline. >> >> Is there something akin to grub2-mkisofs that I need to do for my changes >> to the grub.cfg for this iso prior to my re-rolling it? >> >> Thank you, >> >> Dan >> > _______________________________________________ > WLUG mailing list -- wlug(a)lists.wlug.org > To unsubscribe send an email to wlug-leave(a)lists.wlug.org > Create Account: https://wlug.mailman3.com/accounts/signup/ > Change Settings: > https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/ > Web Forum/Archive: > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/message/PP4MH… >

March 5, 2023

Re: Re-Roll RHEL isos to skip the 60sec countdown and media check

by Dan Davis

Good evening, I don't know if anyone saw this, but I found my answer at: https://docs.centos.org/en-US/8-docs/advanced-install/assembly_kickstart-an… In the note saying: By default, the inst.stage2= boot option is used on the installation media and is set to a specific label, for example, inst.stage2=hd:LABEL=CentOS-8-BaseOS-x86_64. If you modify the default label of the file system containing the runtime image, or if you use a customized procedure to boot the installation system, you must verify that the inst.stage2= boot option is set to the correct value. So it was a label problem. I was calling mkisofs with the -V switch and an argument that did not match the label in isolinux.cfg for inst.stage2. This caused the boot stall. If anyone saw this, thanks for your consideration. Best Regards, Dan On Sat, Mar 4, 2023 at 2:18 PM Dan Davis <davis.dan.c(a)gmail.com> wrote: > Good Afternoon, > > I'm trying to re-roll a RHEL9 iso to remove the media check and 60s > timeout that occurs because rd.live.check is baked into the kernel command > line and grub menu. I'd like to use the result with an unattended install. > > I start by loop mounting the OEM iso image and extracting the contents to > a working dir. In the working directory, I've attempted to edit > EFI/BOOT/grub.cfg an isolinux/grub.cfg before rerolling the disk with: > > mkisofs -o output.iso -b isolinux/isolinux.bin -c isolinux/boot.cat > -no-emul-boot -boot-load-size 4 -boot-info-table workingdir > > But after editing either or both, I'm still presented with the 60s default > timeout and the media check (rd.live.check) in the kernel commandline. > > Is there something akin to grub2-mkisofs that I need to do for my changes > to the grub.cfg for this iso prior to my re-rolling it? > > Thank you, > > Dan >

March 5, 2023