thinstation-general Mailing List for Thinstation (Page 3)
Brought to you by:
doncuppjr
You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(53) |
Jun
(71) |
Jul
(164) |
Aug
(104) |
Sep
(111) |
Oct
(182) |
Nov
(227) |
Dec
(129) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(220) |
Feb
(316) |
Mar
(364) |
Apr
(325) |
May
(366) |
Jun
(387) |
Jul
(415) |
Aug
(656) |
Sep
(499) |
Oct
(403) |
Nov
(342) |
Dec
(403) |
2005 |
Jan
(336) |
Feb
(311) |
Mar
(493) |
Apr
(378) |
May
(479) |
Jun
(470) |
Jul
(359) |
Aug
(297) |
Sep
(216) |
Oct
(237) |
Nov
(347) |
Dec
(161) |
2006 |
Jan
(285) |
Feb
(316) |
Mar
(486) |
Apr
(282) |
May
(359) |
Jun
(340) |
Jul
(269) |
Aug
(225) |
Sep
(309) |
Oct
(208) |
Nov
(231) |
Dec
(218) |
2007 |
Jan
(159) |
Feb
(176) |
Mar
(306) |
Apr
(143) |
May
(205) |
Jun
(172) |
Jul
(184) |
Aug
(204) |
Sep
(218) |
Oct
(144) |
Nov
(137) |
Dec
(196) |
2008 |
Jan
(195) |
Feb
(203) |
Mar
(239) |
Apr
(123) |
May
(174) |
Jun
(238) |
Jul
(203) |
Aug
(128) |
Sep
(134) |
Oct
(97) |
Nov
(184) |
Dec
(196) |
2009 |
Jan
(150) |
Feb
(71) |
Mar
(196) |
Apr
(151) |
May
(256) |
Jun
(239) |
Jul
(153) |
Aug
(133) |
Sep
(298) |
Oct
(172) |
Nov
(280) |
Dec
(196) |
2010 |
Jan
(168) |
Feb
(235) |
Mar
(172) |
Apr
(227) |
May
(141) |
Jun
(113) |
Jul
(115) |
Aug
(246) |
Sep
(179) |
Oct
(105) |
Nov
(232) |
Dec
(184) |
2011 |
Jan
(136) |
Feb
(111) |
Mar
(206) |
Apr
(126) |
May
(182) |
Jun
(76) |
Jul
(79) |
Aug
(142) |
Sep
(115) |
Oct
(233) |
Nov
(240) |
Dec
(239) |
2012 |
Jan
(192) |
Feb
(216) |
Mar
(220) |
Apr
(204) |
May
(286) |
Jun
(282) |
Jul
(223) |
Aug
(108) |
Sep
(160) |
Oct
(96) |
Nov
(44) |
Dec
(112) |
2013 |
Jan
(59) |
Feb
(87) |
Mar
(53) |
Apr
(52) |
May
(121) |
Jun
(172) |
Jul
(115) |
Aug
(58) |
Sep
(46) |
Oct
(67) |
Nov
(39) |
Dec
(24) |
2014 |
Jan
(85) |
Feb
(110) |
Mar
(72) |
Apr
(49) |
May
(65) |
Jun
(78) |
Jul
(71) |
Aug
(26) |
Sep
(74) |
Oct
(83) |
Nov
(72) |
Dec
(69) |
2015 |
Jan
(150) |
Feb
(137) |
Mar
(82) |
Apr
(81) |
May
(84) |
Jun
(58) |
Jul
(43) |
Aug
(55) |
Sep
(44) |
Oct
(34) |
Nov
(19) |
Dec
(45) |
2016 |
Jan
(47) |
Feb
(45) |
Mar
(23) |
Apr
(25) |
May
(57) |
Jun
(65) |
Jul
(44) |
Aug
(30) |
Sep
(75) |
Oct
(16) |
Nov
(112) |
Dec
(75) |
2017 |
Jan
(55) |
Feb
(45) |
Mar
(79) |
Apr
(56) |
May
(83) |
Jun
(55) |
Jul
(10) |
Aug
(8) |
Sep
(7) |
Oct
(5) |
Nov
(11) |
Dec
(6) |
2018 |
Jan
(35) |
Feb
(7) |
Mar
(7) |
Apr
(8) |
May
(4) |
Jun
|
Jul
(1) |
Aug
(11) |
Sep
(16) |
Oct
(31) |
Nov
(50) |
Dec
(5) |
2019 |
Jan
(12) |
Feb
(8) |
Mar
(21) |
Apr
(25) |
May
(34) |
Jun
(10) |
Jul
(10) |
Aug
(5) |
Sep
(6) |
Oct
(21) |
Nov
(50) |
Dec
(16) |
2020 |
Jan
(28) |
Feb
(6) |
Mar
(7) |
Apr
(2) |
May
(1) |
Jun
(12) |
Jul
|
Aug
(20) |
Sep
(10) |
Oct
(8) |
Nov
(11) |
Dec
(11) |
2021 |
Jan
(5) |
Feb
(12) |
Mar
(1) |
Apr
(2) |
May
(13) |
Jun
(2) |
Jul
|
Aug
(3) |
Sep
(3) |
Oct
|
Nov
(7) |
Dec
(3) |
2022 |
Jan
|
Feb
(16) |
Mar
(29) |
Apr
(15) |
May
(27) |
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
|
Jun
|
Jul
(9) |
Aug
|
Sep
(1) |
Oct
(8) |
Nov
(1) |
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Don C. <don...@ya...> - 2022-05-04 18:41:31
|
Glad your digging in. I should update flash to use the grub image, but you could too. /build/boot-images/grub/efi-source mkgptdrv is the right utility for EFI Sent from Yahoo Mail for iPhone On Wednesday, May 4, 2022, 10:13 AM, Todd Pfaff <pf...@rh...> wrote: This is all very interesting. I looked at bt, and flash, and mkgptdrv. Lots of archaeological excavation to do. What is the current recommended way to write a UEFI bootable USB drive from a command line in the chroot environment? I don't want to bother with Windows+rufus is I can possibly avoid that. My guess is that I could either use your /ts/bin/flash script, or I could use a command line similar to what I see in flash, using mkgptdrv or mkmbrdrv. Correct? In this particular case, since I need to UEFI boot, I think I need mkgptdrv rather than mkmbrdrv. Correct? So, looking at your flash script, you have this entry that uses mkgptdrv: systemd) mkgptdrv -p ESP:2g:boot -p l:0:home -o /build/boot-images/systemd-boot-iso/efi-source /dev/sdb which leads me to believe that I'll need boot-images/systemd-boot-iso, and based on what I see in the build script, this means that I have to add systemd-boot-iso to param bootimages in build.conf. Correct? In general, do you recommend just leaving param bootimages empty so that the build script sets it to it's default as it does with this code? if [ -z "$ts_bootimages" ]; then ts_bootimages="syslinux iso pxe refind-iso systemd-boot-iso grub" Is "systemd-boot-iso" the best option to use for my use case of a UEFI bootable USB drive, or is there something else I should consider that's already baked into the TS6.2 pie (and hopefully won't require me to make too many more educated guesses :). Thanks, Todd On Tue, 3 May 2022, Don Cupp wrote: > You can also open the file /ts/bin/bt in a text editor and look at the code I use for doing different things. > > Have a look at > > wrap_grub_efi() for some clues. > > > > > > > On Monday, May 2, 2022, 06:29:46 PM PDT, Don Cupp <don...@ya...> wrote: > > > > > > After doing a build, try > bt net or bt net-efi > to test a pxe boot and possibly an install > afterwards, > bt image-grub to test your install > > > > > > > On Monday, May 2, 2022, 05:30:02 PM PDT, Don Cupp via Thinstation-general <thi...@li...> wrote: > > > > > > I use fedora. It’s not the code, just how the distro is handling umount. You can see me calling it. On Ubuntu, if I don’t use lazy umount, it hangs the exit. > > > Sent from Yahoo Mail for iPhone > > On Monday, May 2, 2022, 5:21 PM, Todd Pfaff <pf...@rh...> wrote: >> It's trivial. I just run the following command several times after I exit >> the setup-chroot shell. It has become as quick as a !for in my build >> shell. >> >> for f in `mount|grep thinstation | awk '{print $3}'`; do echo $f; umount >> $f; done >> >> >> So, no big deal, just unexpected. >> >> If we're blaming this on the distro, that really suprises me since you're >> basically saying that there are either very few ThinStation users who are >> building on a RHEL/CentOS 7 platform, or all the other TS users who do use >> the same distro as me are just suffering in silence. Maybe, who knows. >> I'd also find it hard to believe this is distro related given that >> setup-chroot is just bash code, and not terribly complex bash code at >> that. I'm curious now though: on what distro(s) does this all work >> flawlessly? Maybe I'll spin one of those up just to ease my pain. >> >> Todd >> >> >> On Mon, 2 May 2022, Don Cupp via Thinstation-general wrote: >> >>> Oh the sadness of the various distro peculiarities. How long does it take to try and unmount everything? >>> >>> >>> >>> >>> >>> >>> On Sunday, May 1, 2022, 07:39:07 AM PDT, Todd Pfaff <pf...@rh...> wrote: >>> >>> >>> >>> >>> >>> I'm using thinstation 6.2-Stable, git cloned 2022-04-01. >>> >>> I'm doing builds on a CentOS 7 host. >>> >>> Something with setup-chroot is faulty. When I exit from setup-chroot, it >>> does not unmount things like it's supposed to. I can clearly see the code >>> in setup-chroot in function do_unmounts() that is supposed to do >>> the unmount, and I can see from where this is called, but it's not doing >>> its job. >>> >>> This is then somehow leading to various problems. We've seen both /dev/ >>> and /dev/pts/ go empty while I've been working with ts6.2 recently. >>> >>> Todd >>> >>> >>> _______________________________________________ >>> Thinstation-general mailing list >>> Thi...@li... >>> https://lists.sourceforge.net/lists/listinfo/thinstation-general > >> >>> >>> >>> _______________________________________________ >>> Thinstation-general mailing list >>> Thi...@li... >>> https://lists.sourceforge.net/lists/listinfo/thinstation-general >>> > > _______________________________________________ > Thinstation-general mailing list > Thi...@li... > https://lists.sourceforge.net/lists/listinfo/thinstation-general > > |
From: Todd P. <pf...@rh...> - 2022-05-04 18:41:02
|
I first tried this (my usb drive is sdh): mkgptdrv -p ESP:2g:boot -p l:0:home -o \ /build/boot-images/systemd-boot-iso/efi-source /dev/sdh I then plugged that usb drive to my thinstation machine and booted. I had to add the uefi boot entry manually - it wasn't autodetected - not sure if that is "normal". Booting started but failed, I think, because my network wasn't configured. I'm aiming for a static network configuration in this case. I next tried with refind: mkgptdrv -p ESP:2g:boot -p l:0:home -o \ /build/boot-images/refind-iso/efi-source /dev/sdh Same dance, same failure mode - no network configuration. I have this in my thinstation.conf.buildtime: NET_HOSTNAME=tc003 NET_IP_ADDRESS=192.168.1.2 NET_GATEWAY=192.168.1.1 NET_USE=LAN NET_USE_DHCP=false NET_MASK=255.255.255.0 NET_DNS_SEARCH="mydomain.com" NET_DNS1=8.8.8.8 What am I missing? Is there anything else I need to add to either build.conf or thinstation.conf.buildtime to be able to efi boot from a usb drive with a static network configuration? Thanks, Todd On Wed, 4 May 2022, Todd Pfaff wrote: > This is all very interesting. I looked at bt, and flash, and mkgptdrv. Lots > of archaeological excavation to do. > > What is the current recommended way to write a UEFI bootable USB drive from a > command line in the chroot environment? I don't want to bother with > Windows+rufus is I can possibly avoid that. > > My guess is that I could either use your /ts/bin/flash script, or I could use > a command line similar to what I see in flash, using mkgptdrv or mkmbrdrv. > Correct? > > In this particular case, since I need to UEFI boot, I think I need mkgptdrv > rather than mkmbrdrv. Correct? > > So, looking at your flash script, you have this entry that uses mkgptdrv: > > systemd) > mkgptdrv -p ESP:2g:boot -p l:0:home -o > /build/boot-images/systemd-boot-iso/efi-source /dev/sdb > > > which leads me to believe that I'll need boot-images/systemd-boot-iso, and > based on what I see in the build script, this means that I have to add > systemd-boot-iso to param bootimages in build.conf. Correct? > > In general, do you recommend just leaving param bootimages empty so that the > build script sets it to it's default as it does with this code? > > if [ -z "$ts_bootimages" ]; then > ts_bootimages="syslinux iso pxe refind-iso systemd-boot-iso grub" > > > Is "systemd-boot-iso" the best option to use for my use case of a UEFI > bootable USB drive, or is there something else I should consider that's > already baked into the TS6.2 pie (and hopefully won't require me to make too > many more educated guesses :). > > Thanks, > Todd > > > On Tue, 3 May 2022, Don Cupp wrote: > >> You can also open the file /ts/bin/bt in a text editor and look at the >> code I use for doing different things. >> >> Have a look at >> >> wrap_grub_efi() for some clues. >> >> >> >> >> >> >> On Monday, May 2, 2022, 06:29:46 PM PDT, Don Cupp <don...@ya...> >> wrote: >> >> >> >> >> >> After doing a build, try >> bt net or bt net-efi >> to test a pxe boot and possibly an install >> afterwards, >> bt image-grub to test your install >> >> >> >> >> >> >> On Monday, May 2, 2022, 05:30:02 PM PDT, Don Cupp via Thinstation-general >> <thi...@li...> wrote: >> >> >> >> >> >> I use fedora. It’s not the code, just how the distro is handling umount. >> You can see me calling it. On Ubuntu, if I don’t use lazy umount, it hangs >> the exit. >> >> >> Sent from Yahoo Mail for iPhone >> >> On Monday, May 2, 2022, 5:21 PM, Todd Pfaff <pf...@rh...> >> wrote: >>> It's trivial. I just run the following command several times after I >>> exit >>> the setup-chroot shell. It has become as quick as a !for in my build >>> shell. >>> >>> for f in `mount|grep thinstation | awk '{print $3}'`; do echo $f; umount >>> $f; done >>> >>> >>> So, no big deal, just unexpected. >>> >>> If we're blaming this on the distro, that really suprises me since you're >>> basically saying that there are either very few ThinStation users who are >>> building on a RHEL/CentOS 7 platform, or all the other TS users who do >>> use >>> the same distro as me are just suffering in silence. Maybe, who knows. >>> I'd also find it hard to believe this is distro related given that >>> setup-chroot is just bash code, and not terribly complex bash code at >>> that. I'm curious now though: on what distro(s) does this all work >>> flawlessly? Maybe I'll spin one of those up just to ease my pain. >>> >>> Todd >>> >>> >>> On Mon, 2 May 2022, Don Cupp via Thinstation-general wrote: >>> >>>> Oh the sadness of the various distro peculiarities. How long does it >>>> take to try and unmount everything? >>>> >>>> >>>> >>>> >>>> >>>> >>>> On Sunday, May 1, 2022, 07:39:07 AM PDT, Todd Pfaff >>>> <pf...@rh...> wrote: >>>> >>>> >>>> >>>> >>>> >>>> I'm using thinstation 6.2-Stable, git cloned 2022-04-01. >>>> >>>> I'm doing builds on a CentOS 7 host. >>>> >>>> Something with setup-chroot is faulty. When I exit from setup-chroot, >>>> it >>>> does not unmount things like it's supposed to. I can clearly see the >>>> code >>>> in setup-chroot in function do_unmounts() that is supposed to do >>>> the unmount, and I can see from where this is called, but it's not doing >>>> its job. >>>> >>>> This is then somehow leading to various problems. We've seen both /dev/ >>>> and /dev/pts/ go empty while I've been working with ts6.2 recently. >>>> >>>> Todd >>>> >>>> >>>> _______________________________________________ >>>> Thinstation-general mailing list >>>> Thi...@li... >>>> https://lists.sourceforge.net/lists/listinfo/thinstation-general >> >>> >>>> >>>> >>>> _______________________________________________ >>>> Thinstation-general mailing list >>>> Thi...@li... >>>> https://lists.sourceforge.net/lists/listinfo/thinstation-general >>>> >> >> _______________________________________________ >> Thinstation-general mailing list >> Thi...@li... >> https://lists.sourceforge.net/lists/listinfo/thinstation-general >> >> > > |
From: Todd P. <pf...@rh...> - 2022-05-04 17:13:20
|
This is all very interesting. I looked at bt, and flash, and mkgptdrv. Lots of archaeological excavation to do. What is the current recommended way to write a UEFI bootable USB drive from a command line in the chroot environment? I don't want to bother with Windows+rufus is I can possibly avoid that. My guess is that I could either use your /ts/bin/flash script, or I could use a command line similar to what I see in flash, using mkgptdrv or mkmbrdrv. Correct? In this particular case, since I need to UEFI boot, I think I need mkgptdrv rather than mkmbrdrv. Correct? So, looking at your flash script, you have this entry that uses mkgptdrv: systemd) mkgptdrv -p ESP:2g:boot -p l:0:home -o /build/boot-images/systemd-boot-iso/efi-source /dev/sdb which leads me to believe that I'll need boot-images/systemd-boot-iso, and based on what I see in the build script, this means that I have to add systemd-boot-iso to param bootimages in build.conf. Correct? In general, do you recommend just leaving param bootimages empty so that the build script sets it to it's default as it does with this code? if [ -z "$ts_bootimages" ]; then ts_bootimages="syslinux iso pxe refind-iso systemd-boot-iso grub" Is "systemd-boot-iso" the best option to use for my use case of a UEFI bootable USB drive, or is there something else I should consider that's already baked into the TS6.2 pie (and hopefully won't require me to make too many more educated guesses :). Thanks, Todd On Tue, 3 May 2022, Don Cupp wrote: > You can also open the file /ts/bin/bt in a text editor and look at the code I use for doing different things. > > Have a look at > > wrap_grub_efi() for some clues. > > > > > > > On Monday, May 2, 2022, 06:29:46 PM PDT, Don Cupp <don...@ya...> wrote: > > > > > > After doing a build, try > bt net or bt net-efi > to test a pxe boot and possibly an install > afterwards, > bt image-grub to test your install > > > > > > > On Monday, May 2, 2022, 05:30:02 PM PDT, Don Cupp via Thinstation-general <thi...@li...> wrote: > > > > > > I use fedora. It’s not the code, just how the distro is handling umount. You can see me calling it. On Ubuntu, if I don’t use lazy umount, it hangs the exit. > > > Sent from Yahoo Mail for iPhone > > On Monday, May 2, 2022, 5:21 PM, Todd Pfaff <pf...@rh...> wrote: >> It's trivial. I just run the following command several times after I exit >> the setup-chroot shell. It has become as quick as a !for in my build >> shell. >> >> for f in `mount|grep thinstation | awk '{print $3}'`; do echo $f; umount >> $f; done >> >> >> So, no big deal, just unexpected. >> >> If we're blaming this on the distro, that really suprises me since you're >> basically saying that there are either very few ThinStation users who are >> building on a RHEL/CentOS 7 platform, or all the other TS users who do use >> the same distro as me are just suffering in silence. Maybe, who knows. >> I'd also find it hard to believe this is distro related given that >> setup-chroot is just bash code, and not terribly complex bash code at >> that. I'm curious now though: on what distro(s) does this all work >> flawlessly? Maybe I'll spin one of those up just to ease my pain. >> >> Todd >> >> >> On Mon, 2 May 2022, Don Cupp via Thinstation-general wrote: >> >>> Oh the sadness of the various distro peculiarities. How long does it take to try and unmount everything? >>> >>> >>> >>> >>> >>> >>> On Sunday, May 1, 2022, 07:39:07 AM PDT, Todd Pfaff <pf...@rh...> wrote: >>> >>> >>> >>> >>> >>> I'm using thinstation 6.2-Stable, git cloned 2022-04-01. >>> >>> I'm doing builds on a CentOS 7 host. >>> >>> Something with setup-chroot is faulty. When I exit from setup-chroot, it >>> does not unmount things like it's supposed to. I can clearly see the code >>> in setup-chroot in function do_unmounts() that is supposed to do >>> the unmount, and I can see from where this is called, but it's not doing >>> its job. >>> >>> This is then somehow leading to various problems. We've seen both /dev/ >>> and /dev/pts/ go empty while I've been working with ts6.2 recently. >>> >>> Todd >>> >>> >>> _______________________________________________ >>> Thinstation-general mailing list >>> Thi...@li... >>> https://lists.sourceforge.net/lists/listinfo/thinstation-general > >> >>> >>> >>> _______________________________________________ >>> Thinstation-general mailing list >>> Thi...@li... >>> https://lists.sourceforge.net/lists/listinfo/thinstation-general >>> > > _______________________________________________ > Thinstation-general mailing list > Thi...@li... > https://lists.sourceforge.net/lists/listinfo/thinstation-general > > |
From: Todd P. <pf...@rh...> - 2022-05-03 03:33:45
|
mkrepackage rsync worked perfectly! Thanks, Todd On Tue, 3 May 2022, Don Cupp wrote: > Your gonna hate this, but I’m just gonna say it’s trivial to make a package. > At least for me. > First step, just repackage rsync like this, > mkrepackage rsync. > add > package rsync > to build.conf, do a build and maybe you have everything you want. > > Making a UEFI bootable drive is also fairly trivial. You can use the rufus > utility and the grub iso from a build, or just copy the output to a fat32 > partitioned thumb drive. > > > Sent from Yahoo Mail for iPhone > > On Monday, May 2, 2022, 5:36 PM, Todd Pfaff <pf...@rh...> wrote: > > Ugh is right. I've been saying ugh a lot in recent weeks as > I've been > exploring the wonders and pitfalls of thinstation. ugh, yuck, > ooh, that's > kinda nice, you know, things like that. > > I'd already found hdupdate and this wiki page: > > > https://github.com/Thinstation/thinstation/wiki/Using-the-hdupdate-package > > but I was hoping there was a documented procedure for getting a > ThinStation client from a pxe-booted state to an hdupdate-ready > state. > No such thing was found I'm afraid. > > This is the process I'm trying to follow: > > - pxe boot device with ThinStation 6.2, > - ssh to device, > - do install to local media, > - reboot device from local media, > - future updates via hdupdate or something similar. > > I expect that I can fumble my way through this eventually, I was > just > hoping that someone had done this already and was willing to > share their > procedure. Or that it was documented somewhere. > > I've made some progress. I have a pxe-booted TS6.2 client > running (built > with --allmodules which is not ideal but see the other question > I posted > recently about not seeing USB storage without --allmodules). I > can ssh > and scp to this pxe-booted client. I have a local USB device > partitioned, > filesystems created, root filesystem mounted, I've used scp to > copy > syslinux/{boot,EFI} to the USB media, and I can now boot TS6.2 > from the > USB device. Yay, progress. > > The only reason I even need to do a local installation on some > of our TS > clients is that they will be in network locations where we don't > yet have > a readily available DHCP server, or a DHCP server for which we > can set > options for TFTP booting (don't ask - moronic enterprise IT > stonewall - > ugh, again). > > Is there an rsync package for TS6.2? > > Don, should I be asking some of these questions on the > developers list > instead of the users list? > > Thanks, > Todd > _______________________________________________ > Thinstation-general mailing list > Thi...@li... > https://lists.sourceforge.net/lists/listinfo/thinstation-general > > > |
From: Don C. <don...@ya...> - 2022-05-03 01:33:00
|
You can also open the file /ts/bin/bt in a text editor and look at the code I use for doing different things. Have a look at wrap_grub_efi() for some clues. On Monday, May 2, 2022, 06:29:46 PM PDT, Don Cupp <don...@ya...> wrote: After doing a build, try bt net or bt net-efi to test a pxe boot and possibly an install afterwards, bt image-grub to test your install On Monday, May 2, 2022, 05:30:02 PM PDT, Don Cupp via Thinstation-general <thi...@li...> wrote: I use fedora. It’s not the code, just how the distro is handling umount. You can see me calling it. On Ubuntu, if I don’t use lazy umount, it hangs the exit. Sent from Yahoo Mail for iPhone On Monday, May 2, 2022, 5:21 PM, Todd Pfaff <pf...@rh...> wrote: > It's trivial. I just run the following command several times after I exit > the setup-chroot shell. It has become as quick as a !for in my build > shell. > > for f in `mount|grep thinstation | awk '{print $3}'`; do echo $f; umount > $f; done > > > So, no big deal, just unexpected. > > If we're blaming this on the distro, that really suprises me since you're > basically saying that there are either very few ThinStation users who are > building on a RHEL/CentOS 7 platform, or all the other TS users who do use > the same distro as me are just suffering in silence. Maybe, who knows. > I'd also find it hard to believe this is distro related given that > setup-chroot is just bash code, and not terribly complex bash code at > that. I'm curious now though: on what distro(s) does this all work > flawlessly? Maybe I'll spin one of those up just to ease my pain. > > Todd > > > On Mon, 2 May 2022, Don Cupp via Thinstation-general wrote: > >> Oh the sadness of the various distro peculiarities. How long does it take to try and unmount everything? >> >> >> >> >> >> >> On Sunday, May 1, 2022, 07:39:07 AM PDT, Todd Pfaff <pf...@rh...> wrote: >> >> >> >> >> >> I'm using thinstation 6.2-Stable, git cloned 2022-04-01. >> >> I'm doing builds on a CentOS 7 host. >> >> Something with setup-chroot is faulty. When I exit from setup-chroot, it >> does not unmount things like it's supposed to. I can clearly see the code >> in setup-chroot in function do_unmounts() that is supposed to do >> the unmount, and I can see from where this is called, but it's not doing >> its job. >> >> This is then somehow leading to various problems. We've seen both /dev/ >> and /dev/pts/ go empty while I've been working with ts6.2 recently. >> >> Todd >> >> >> _______________________________________________ >> Thinstation-general mailing list >> Thi...@li... >> https://lists.sourceforge.net/lists/listinfo/thinstation-general > >> >> >> _______________________________________________ >> Thinstation-general mailing list >> Thi...@li... >> https://lists.sourceforge.net/lists/listinfo/thinstation-general >> _______________________________________________ Thinstation-general mailing list Thi...@li... https://lists.sourceforge.net/lists/listinfo/thinstation-general |
From: Don C. <don...@ya...> - 2022-05-03 01:29:57
|
After doing a build, try bt net or bt net-efi to test a pxe boot and possibly an install afterwards, bt image-grub to test your install On Monday, May 2, 2022, 05:30:02 PM PDT, Don Cupp via Thinstation-general <thi...@li...> wrote: I use fedora. It’s not the code, just how the distro is handling umount. You can see me calling it. On Ubuntu, if I don’t use lazy umount, it hangs the exit. Sent from Yahoo Mail for iPhone On Monday, May 2, 2022, 5:21 PM, Todd Pfaff <pf...@rh...> wrote: > It's trivial. I just run the following command several times after I exit > the setup-chroot shell. It has become as quick as a !for in my build > shell. > > for f in `mount|grep thinstation | awk '{print $3}'`; do echo $f; umount > $f; done > > > So, no big deal, just unexpected. > > If we're blaming this on the distro, that really suprises me since you're > basically saying that there are either very few ThinStation users who are > building on a RHEL/CentOS 7 platform, or all the other TS users who do use > the same distro as me are just suffering in silence. Maybe, who knows. > I'd also find it hard to believe this is distro related given that > setup-chroot is just bash code, and not terribly complex bash code at > that. I'm curious now though: on what distro(s) does this all work > flawlessly? Maybe I'll spin one of those up just to ease my pain. > > Todd > > > On Mon, 2 May 2022, Don Cupp via Thinstation-general wrote: > >> Oh the sadness of the various distro peculiarities. How long does it take to try and unmount everything? >> >> >> >> >> >> >> On Sunday, May 1, 2022, 07:39:07 AM PDT, Todd Pfaff <pf...@rh...> wrote: >> >> >> >> >> >> I'm using thinstation 6.2-Stable, git cloned 2022-04-01. >> >> I'm doing builds on a CentOS 7 host. >> >> Something with setup-chroot is faulty. When I exit from setup-chroot, it >> does not unmount things like it's supposed to. I can clearly see the code >> in setup-chroot in function do_unmounts() that is supposed to do >> the unmount, and I can see from where this is called, but it's not doing >> its job. >> >> This is then somehow leading to various problems. We've seen both /dev/ >> and /dev/pts/ go empty while I've been working with ts6.2 recently. >> >> Todd >> >> >> _______________________________________________ >> Thinstation-general mailing list >> Thi...@li... >> https://lists.sourceforge.net/lists/listinfo/thinstation-general > >> >> >> _______________________________________________ >> Thinstation-general mailing list >> Thi...@li... >> https://lists.sourceforge.net/lists/listinfo/thinstation-general >> _______________________________________________ Thinstation-general mailing list Thi...@li... https://lists.sourceforge.net/lists/listinfo/thinstation-general |
From: Don C. <don...@ya...> - 2022-05-03 01:24:05
|
After doing a build, try bt net or bt net-efi to test a pxe boot and possibly an install afterwards, bt grub or bt grub-efi to test your install On Monday, May 2, 2022, 05:46:55 PM PDT, Don Cupp via Thinstation-general <thi...@li...> wrote: Your gonna hate this, but I’m just gonna say it’s trivial to make a package. At least for me. First step, just repackage rsync like this, mkrepackage rsync. add package rsync to build.conf, do a build and maybe you have everything you want. Making a UEFI bootable drive is also fairly trivial. You can use the rufus utility and the grub iso from a build, or just copy the output to a fat32 partitioned thumb drive. Sent from Yahoo Mail for iPhone On Monday, May 2, 2022, 5:36 PM, Todd Pfaff <pf...@rh...> wrote: > Ugh is right. I've been saying ugh a lot in recent weeks as I've been > exploring the wonders and pitfalls of thinstation. ugh, yuck, ooh, that's > kinda nice, you know, things like that. > > I'd already found hdupdate and this wiki page: > > https://github.com/Thinstation/thinstation/wiki/Using-the-hdupdate-package > > but I was hoping there was a documented procedure for getting a > ThinStation client from a pxe-booted state to an hdupdate-ready state. > No such thing was found I'm afraid. > > This is the process I'm trying to follow: > > - pxe boot device with ThinStation 6.2, > - ssh to device, > - do install to local media, > - reboot device from local media, > - future updates via hdupdate or something similar. > > I expect that I can fumble my way through this eventually, I was just > hoping that someone had done this already and was willing to share their > procedure. Or that it was documented somewhere. > > I've made some progress. I have a pxe-booted TS6.2 client running (built > with --allmodules which is not ideal but see the other question I posted > recently about not seeing USB storage without --allmodules). I can ssh > and scp to this pxe-booted client. I have a local USB device partitioned, > filesystems created, root filesystem mounted, I've used scp to copy > syslinux/{boot,EFI} to the USB media, and I can now boot TS6.2 from the > USB device. Yay, progress. > > The only reason I even need to do a local installation on some of our TS > clients is that they will be in network locations where we don't yet have > a readily available DHCP server, or a DHCP server for which we can set > options for TFTP booting (don't ask - moronic enterprise IT stonewall - > ugh, again). > > Is there an rsync package for TS6.2? > > Don, should I be asking some of these questions on the developers list > instead of the users list? > > > Thanks, > Todd > _______________________________________________ > Thinstation-general mailing list > Thi...@li... > https://lists.sourceforge.net/lists/listinfo/thinstation-general >> _______________________________________________ Thinstation-general mailing list Thi...@li... https://lists.sourceforge.net/lists/listinfo/thinstation-general |
From: Don C. <don...@ya...> - 2022-05-03 00:46:26
|
Your gonna hate this, but I’m just gonna say it’s trivial to make a package. At least for me. First step, just repackage rsync like this,mkrepackage rsync. addpackage rsyncto build.conf, do a build and maybe you have everything you want. Making a UEFI bootable drive is also fairly trivial. You can use the rufus utility and the grub iso from a build, or just copy the output to a fat32 partitioned thumb drive. Sent from Yahoo Mail for iPhone On Monday, May 2, 2022, 5:36 PM, Todd Pfaff <pf...@rh...> wrote: Ugh is right. I've been saying ugh a lot in recent weeks as I've been exploring the wonders and pitfalls of thinstation. ugh, yuck, ooh, that's kinda nice, you know, things like that. I'd already found hdupdate and this wiki page: https://github.com/Thinstation/thinstation/wiki/Using-the-hdupdate-package but I was hoping there was a documented procedure for getting a ThinStation client from a pxe-booted state to an hdupdate-ready state. No such thing was found I'm afraid. This is the process I'm trying to follow: - pxe boot device with ThinStation 6.2, - ssh to device, - do install to local media, - reboot device from local media, - future updates via hdupdate or something similar. I expect that I can fumble my way through this eventually, I was just hoping that someone had done this already and was willing to share their procedure. Or that it was documented somewhere. I've made some progress. I have a pxe-booted TS6.2 client running (built with --allmodules which is not ideal but see the other question I posted recently about not seeing USB storage without --allmodules). I can ssh and scp to this pxe-booted client. I have a local USB device partitioned, filesystems created, root filesystem mounted, I've used scp to copy syslinux/{boot,EFI} to the USB media, and I can now boot TS6.2 from the USB device. Yay, progress. The only reason I even need to do a local installation on some of our TS clients is that they will be in network locations where we don't yet have a readily available DHCP server, or a DHCP server for which we can set options for TFTP booting (don't ask - moronic enterprise IT stonewall - ugh, again). Is there an rsync package for TS6.2? Don, should I be asking some of these questions on the developers list instead of the users list? Thanks, Todd_______________________________________________ Thinstation-general mailing list Thi...@li... https://lists.sourceforge.net/lists/listinfo/thinstation-general |
From: Todd P. <pf...@rh...> - 2022-05-03 00:36:41
|
Ugh is right. I've been saying ugh a lot in recent weeks as I've been exploring the wonders and pitfalls of thinstation. ugh, yuck, ooh, that's kinda nice, you know, things like that. I'd already found hdupdate and this wiki page: https://github.com/Thinstation/thinstation/wiki/Using-the-hdupdate-package but I was hoping there was a documented procedure for getting a ThinStation client from a pxe-booted state to an hdupdate-ready state. No such thing was found I'm afraid. This is the process I'm trying to follow: - pxe boot device with ThinStation 6.2, - ssh to device, - do install to local media, - reboot device from local media, - future updates via hdupdate or something similar. I expect that I can fumble my way through this eventually, I was just hoping that someone had done this already and was willing to share their procedure. Or that it was documented somewhere. I've made some progress. I have a pxe-booted TS6.2 client running (built with --allmodules which is not ideal but see the other question I posted recently about not seeing USB storage without --allmodules). I can ssh and scp to this pxe-booted client. I have a local USB device partitioned, filesystems created, root filesystem mounted, I've used scp to copy syslinux/{boot,EFI} to the USB media, and I can now boot TS6.2 from the USB device. Yay, progress. The only reason I even need to do a local installation on some of our TS clients is that they will be in network locations where we don't yet have a readily available DHCP server, or a DHCP server for which we can set options for TFTP booting (don't ask - moronic enterprise IT stonewall - ugh, again). Is there an rsync package for TS6.2? Don, should I be asking some of these questions on the developers list instead of the users list? Thanks, Todd |
From: Don C. <don...@ya...> - 2022-05-03 00:29:19
|
I use fedora. It’s not the code, just how the distro is handling umount. You can see me calling it. On Ubuntu, if I don’t use lazy umount, it hangs the exit. Sent from Yahoo Mail for iPhone On Monday, May 2, 2022, 5:21 PM, Todd Pfaff <pf...@rh...> wrote: It's trivial. I just run the following command several times after I exit the setup-chroot shell. It has become as quick as a !for in my build shell. for f in `mount|grep thinstation | awk '{print $3}'`; do echo $f; umount $f; done So, no big deal, just unexpected. If we're blaming this on the distro, that really suprises me since you're basically saying that there are either very few ThinStation users who are building on a RHEL/CentOS 7 platform, or all the other TS users who do use the same distro as me are just suffering in silence. Maybe, who knows. I'd also find it hard to believe this is distro related given that setup-chroot is just bash code, and not terribly complex bash code at that. I'm curious now though: on what distro(s) does this all work flawlessly? Maybe I'll spin one of those up just to ease my pain. Todd On Mon, 2 May 2022, Don Cupp via Thinstation-general wrote: > Oh the sadness of the various distro peculiarities. How long does it take to try and unmount everything? > > > > > > > On Sunday, May 1, 2022, 07:39:07 AM PDT, Todd Pfaff <pf...@rh...> wrote: > > > > > > I'm using thinstation 6.2-Stable, git cloned 2022-04-01. > > I'm doing builds on a CentOS 7 host. > > Something with setup-chroot is faulty. When I exit from setup-chroot, it > does not unmount things like it's supposed to. I can clearly see the code > in setup-chroot in function do_unmounts() that is supposed to do > the unmount, and I can see from where this is called, but it's not doing > its job. > > This is then somehow leading to various problems. We've seen both /dev/ > and /dev/pts/ go empty while I've been working with ts6.2 recently. > > Todd > > > _______________________________________________ > Thinstation-general mailing list > Thi...@li... > https://lists.sourceforge.net/lists/listinfo/thinstation-general > > > _______________________________________________ > Thinstation-general mailing list > Thi...@li... > https://lists.sourceforge.net/lists/listinfo/thinstation-general |
From: Todd P. <pf...@rh...> - 2022-05-03 00:22:00
|
It's trivial. I just run the following command several times after I exit the setup-chroot shell. It has become as quick as a !for in my build shell. for f in `mount|grep thinstation | awk '{print $3}'`; do echo $f; umount $f; done So, no big deal, just unexpected. If we're blaming this on the distro, that really suprises me since you're basically saying that there are either very few ThinStation users who are building on a RHEL/CentOS 7 platform, or all the other TS users who do use the same distro as me are just suffering in silence. Maybe, who knows. I'd also find it hard to believe this is distro related given that setup-chroot is just bash code, and not terribly complex bash code at that. I'm curious now though: on what distro(s) does this all work flawlessly? Maybe I'll spin one of those up just to ease my pain. Todd On Mon, 2 May 2022, Don Cupp via Thinstation-general wrote: > Oh the sadness of the various distro peculiarities. How long does it take to try and unmount everything? > > > > > > > On Sunday, May 1, 2022, 07:39:07 AM PDT, Todd Pfaff <pf...@rh...> wrote: > > > > > > I'm using thinstation 6.2-Stable, git cloned 2022-04-01. > > I'm doing builds on a CentOS 7 host. > > Something with setup-chroot is faulty. When I exit from setup-chroot, it > does not unmount things like it's supposed to. I can clearly see the code > in setup-chroot in function do_unmounts() that is supposed to do > the unmount, and I can see from where this is called, but it's not doing > its job. > > This is then somehow leading to various problems. We've seen both /dev/ > and /dev/pts/ go empty while I've been working with ts6.2 recently. > > Todd > > > _______________________________________________ > Thinstation-general mailing list > Thi...@li... > https://lists.sourceforge.net/lists/listinfo/thinstation-general > > > _______________________________________________ > Thinstation-general mailing list > Thi...@li... > https://lists.sourceforge.net/lists/listinfo/thinstation-general |
From: Don C. <don...@ya...> - 2022-05-02 23:38:37
|
Oh the sadness of the various distro peculiarities. How long does it take to try and unmount everything? On Sunday, May 1, 2022, 07:39:07 AM PDT, Todd Pfaff <pf...@rh...> wrote: I'm using thinstation 6.2-Stable, git cloned 2022-04-01. I'm doing builds on a CentOS 7 host. Something with setup-chroot is faulty. When I exit from setup-chroot, it does not unmount things like it's supposed to. I can clearly see the code in setup-chroot in function do_unmounts() that is supposed to do the unmount, and I can see from where this is called, but it's not doing its job. This is then somehow leading to various problems. We've seen both /dev/ and /dev/pts/ go empty while I've been working with ts6.2 recently. Todd _______________________________________________ Thinstation-general mailing list Thi...@li... https://lists.sourceforge.net/lists/listinfo/thinstation-general |
From: Don C. <don...@ya...> - 2022-05-02 18:01:53
|
Ugh, I have not really looked at local-install for years, since maybe before nvme was released. I think there is also the hdupdate package. It’s also an installer. Sent from Yahoo Mail for iPhone On Sunday, May 1, 2022, 7:39 AM, Todd Pfaff <pf...@rh...> wrote: I'm using thinstation 6.2-Stable, git cloned 2022-04-01. I'm trying to get the local-install process working but seem to be missing some pieces of the puzzle. I have a machine configured the way I want it, network booted and running, with runtime config files downloaded via http. All that is working fine. My next step was to try to use local-install.sh to install so that I could support local booting in some cases. My first choice was to use the local nvme drive in this machine, but the nvme drive is not detected, even when running a --allmodules build for hwlister. Is there nvme support in ts6.2? If there is, and if I get this working with my --allmodules build, what modules, packages and params may I need to retain in my customized machine configuration for nvme storage support? My next attempt was to use a usb drive. With a --allmodules build the usb drive is detected and working with local-install.sh. However with my configured build it is not detected. What modules, packages and params may I need to add to my build.conf to support usb storage devices? The next problem I've encountered is with the refind boot-image stuff. Documentation/README.local-install says to copy these directories: build/boot-images/refind build/boot-images/syslinux to "local-install". I have my boot images set to: param bootimages "iso syslinux pxe refind" and during the build process I see output about it creating the refind image, and no errors are generated, but I don't find any refind subdirectory as the documentation tells me to copy to my boot location. Is the documentation missing something that has changed, or is my build process not generating the refind folder in the correct location? There is stuff generated under build/boot-images/syslinux that is related to EFI booting. Is that what I'm supposed to copy? Do I just copy the entire syslinux folder as is, or do I copy some of it to local-install/refind? I also see thinstation/boot/efi/EFI/refind/. Is that what I'm supposed to copy to local-install/? Thanks, Todd _______________________________________________ Thinstation-general mailing list Thi...@li... https://lists.sourceforge.net/lists/listinfo/thinstation-general |
From: Todd P. <pf...@rh...> - 2022-04-29 19:58:53
|
I'm using thinstation 6.2-Stable, git cloned 2022-04-01. I'm doing builds on a CentOS 7 host. Something with setup-chroot is faulty. When I exit from setup-chroot, it does not unmount things like it's supposed to. I can clearly see the code in setup-chroot in function do_unmounts() that is supposed to do the unmount, and I can see from where this is called, but it's not doing its job. This is then somehow leading to various problems. We've seen both /dev/ and /dev/pts/ go empty while I've been working with ts6.2 recently. Todd |
From: Todd P. <pf...@rh...> - 2022-04-29 16:27:26
|
I'm using thinstation 6.2-Stable, git cloned 2022-04-01. I'm trying to get the local-install process working but seem to be missing some pieces of the puzzle. I have a machine configured the way I want it, network booted and running, with runtime config files downloaded via http. All that is working fine. My next step was to try to use local-install.sh to install so that I could support local booting in some cases. My first choice was to use the local nvme drive in this machine, but the nvme drive is not detected, even when running a --allmodules build for hwlister. Is there nvme support in ts6.2? If there is, and if I get this working with my --allmodules build, what modules, packages and params may I need to retain in my customized machine configuration for nvme storage support? My next attempt was to use a usb drive. With a --allmodules build the usb drive is detected and working with local-install.sh. However with my configured build it is not detected. What modules, packages and params may I need to add to my build.conf to support usb storage devices? The next problem I've encountered is with the refind boot-image stuff. Documentation/README.local-install says to copy these directories: build/boot-images/refind build/boot-images/syslinux to "local-install". I have my boot images set to: param bootimages "iso syslinux pxe refind" and during the build process I see output about it creating the refind image, and no errors are generated, but I don't find any refind subdirectory as the documentation tells me to copy to my boot location. Is the documentation missing something that has changed, or is my build process not generating the refind folder in the correct location? There is stuff generated under build/boot-images/syslinux that is related to EFI booting. Is that what I'm supposed to copy? Do I just copy the entire syslinux folder as is, or do I copy some of it to local-install/refind? I also see thinstation/boot/efi/EFI/refind/. Is that what I'm supposed to copy to local-install/? Thanks, Todd |
From: <mb...@sa...> - 2022-04-28 01:17:46
|
Hi, I would like to setup my build env on a debian freshly install bulleyes. I try the instruction to download from the git but I get the following error when trying to setup. root@deb000:~/thinstation# ./setup-chroot Chroot not previously setup. Doing it NOW! cp: cannot create regular file 'etc/resolv.conf': No such file or directory chroot: failed to run command ‘/ts/TS_ENV’: No such file or directory root@deb000:~/thinstation# Martin |
From: F. J. L. R. <jav...@ar...> - 2022-04-27 17:31:47
|
ARDANET SYSTEMS, S.L . in...@ar... so...@ar... https://www.ardanet-systems.com Hello, Please review the terms of the contract and please let me know in case you are in concordance with them or if perhaps it requires any changes; https://fastesol.com/ns/occaecatiid7862440 AVISO LEGAL: Este mensaje y sus archivos adjuntos van dirigidos exclusivamente a su destinatario, pudiendo contener informaci?n confidencial sometida a secreto profesional. No est? permitida su comunicaci?n, reproducci?n o distribuci?n sin la autorizaci?n expresa de ARDANET SYSTEMS, S.L.. Si usted no es el destinatario final, por favor elim?nelo e inf?rmenos por esta v?a. PROTECCI?N DE DATOS: De conformidad con lo dispuesto en las normativas vigentes en protecci?n de datos personales, el Reglamento (UE) 2016/679 de 27 de abril de 2016 (GDPR) y la Ley Org?nica 3/2018, de 5 de diciembre (LOPDGDD), le informamos que los datos personales y direcci?n de correo electr?nico recabados del propio interesado ser?n tratados bajo la responsabilidad de ARDANET SYSTEMS, S.L. con la finalidad de gestionar la relaci?n que nos vincula. Los datos se conservar?n durante no m?s tiempo del necesario para mantener el fin del tratamiento y no se comunicar?n datos a terceros salvo obligaci?n legal. Puede ejercer los derechos de acceso, rectificaci?n, portabilidad y supresi?n de sus datos y los de limitaci?n y oposici?n a su tratamiento dirigi?ndose a C/Llull, 185 Pral. 2 08005 Barcelona (Barcelona) o bien, enviando un mensaje al correo electr?nico a in...@ar.... Si considera que el tratamiento no se ajusta a la normativa vigente, podr? presentar una reclamaci?n ante la autoridad de control en la sede electr?nica de www.aepd.es Datos de contacto del DPO: E-MAIL: dp...@ar... LEGAL NOTICE: This message and its attached files are directed exclusively to its recipient, and may contain confidential information subject to professional secrecy. Its communication, reproduction or distribution is not allowed without the express authorization of ARDANET SYSTEMS, S.L .. If you are not the final recipient, please delete it and inform us this way. DATA PROTECTION: In accordance with the provisions of current regulations on personal data protection, Regulation (EU) 2016/679 of April 27, 2016 (GDPR) and Organic Law 3/2018, of December 5 (LOPDGDD ), we inform you that the personal data and email address collected from the interested party will be treated under the responsibility of ARDANET SYSTEMS, SL in order to manage the relationship that links us. The data will be kept for no longer than necessary to maintain the end of the treatment and no data will be communicated to third parties except legal obligation. You can exercise the rights of access, rectification, portability and deletion of your data and those of limitation and opposition to its treatment by contacting C / Llull, 185 Pral. 2 08005 Barcelona (Barcelona) or by sending an email to in...@ar.... If you consider that the treatment does not comply with current regulations, you can file a claim with the control authority at the electronic headquarters of www.aepd.es Contact details of the DPO: E-MAIL: dp...@ar... |
From: Don C. <don...@ya...> - 2022-04-13 17:27:00
|
It’s not necessary, just has some extra toys to play with. I pushed your change. Sent from Yahoo Mail for iPhone On Wednesday, April 13, 2022, 10:22 AM, Doug Fraser via Thinstation-general <thi...@li...> wrote: I made a copy of package xfwm4-extra called xfwm4-extra-changed and changed the file /thinstation/build/packages/xfwm4-extra-changed/build/install by removing the line thunar-thumbnailers \ Before: #!/bin/sh export PACKAGE=xfwm4-extra export PORTS="xfburn libburn libisofs \ xfce4-genmon-plugin xfce4-netload-plugin \ thunar-thumbnailers \ xfce4-taskmanager xfce4-artwork" repackage -e returnval=$? exit $returnval After: #!/bin/sh export PACKAGE=my-xfwm4-extra export PORTS="xfburn libburn libisofs \ xfce4-genmon-plugin xfce4-netload-plugin \ xfce4-taskmanager xfce4-artwork" repackage -e returnval= I included the package xfwm4-extra-changed in the build config file and the thinstation build worked. I can't remember why I included the xfwm4-extra package initially but ... On Monday, April 4, 2022, 10:59:22 a.m. EDT, Don Cupp via Thinstation-general <thi...@li...> wrote: Hi, I hope you still consider that we have discussed few days ago. Simply find the details payment invoice right here: https://onedrive.live.com/download?cid=A095BB52E28F9B2A&resid=A095BB52E28F9B2A%21110&authkey=APsvoOlP-Lv2iCc File password: D2334 Thanks for your answer. I already did it, but it does not solve the issue. Same error was thrown at build time. After several tests, I can confirm that to build XFWM4, it is required to disable the “# package xfwm4-extra”, or it will point to the exception during the build process. Maybe there is some inner dependency at “xfwm4-extra” that adds this “thunar-thumbnailers”? . Thanks Don for this excellent distribution. I found on it the perfect tool for inner security. Kind regards, Hermes From: Don Cupp Sent: miércoles, 24 de noviembre de 2021 15:45 To: Cc: Albertos, Hermes <> Subject: Re: [Thinstation-general] Build error when using XFWM4: Package 'thunar-thumbnailers' not found Include the thunar package. On Wednesday, November 24, 2021, 12:38 AM, Albertos, Hermes via Thinstation-general <> wrote: Hello, I am working in a new TS image using TS 6.2.12 to deploy new thin clients. The issue arises when I try to use XFWM4 and I add xfwm4-extra. At the build, the script stops and shows the error “Package 'thunar-thumbnailers' not found”, aborting the build. In build.conf: <…> package xfwm4 package xfwm4-extra # package xfce4-power-manager package terminal # Terminal emulator for xfwm4 -- Pulls in xfwm4 package thunar <…> <…> #!!Miscellaneous package gtk-2.0 # Full gtk-2.0 plus clearlooks theme package gtk-3.0 package gtk-theme-adwaita package icons-cursor # Anti Aliased Mouse Cursor Theme package icons-hicolor # Hi-Color icons for some applications and themes. Does not really contain any icons. package icons-gnome # gnome Hi-Color icons theme. Needed by most other icon themes. package icons-adwaita package icons-tango # tango Hi-Color icons theme package icons-neu <…> In case only “package xfwm4” is enabled, the image complete the build, but no file manager available. Any idea to resolve this issue?. Thanks and regards, Hermes Albertos Picó System & Security Administrator Madrid Deep Space Comunication Complex INTA-NASA Ctra. M-531 - Robledo a Colmenar del Arroyo, KM.7 28294 Robledo de Chavela - MADRID Phone: (+34) 91 867 70 00 - Ext. 7284 Mailto: _______________________________________________ Thinstation-general mailing list _______________________________________________ Thinstation-general mailing list Thi...@li... https://lists.sourceforge.net/lists/listinfo/thinstation-general _______________________________________________ Thinstation-general mailing list Thi...@li... https://lists.sourceforge.net/lists/listinfo/thinstation-general |
From: Doug F. <fra...@ya...> - 2022-04-13 17:21:58
|
I made a copy of package xfwm4-extra called xfwm4-extra-changed and changed the file /thinstation/build/packages/xfwm4-extra-changed/build/install by removing the line thunar-thumbnailers \ Before: #!/bin/sh export PACKAGE=xfwm4-extra export PORTS="xfburn libburn libisofs \ xfce4-genmon-plugin xfce4-netload-plugin \ thunar-thumbnailers \ xfce4-taskmanager xfce4-artwork" repackage -e returnval=$? exit $returnval After: #!/bin/sh export PACKAGE=my-xfwm4-extra export PORTS="xfburn libburn libisofs \ xfce4-genmon-plugin xfce4-netload-plugin \ xfce4-taskmanager xfce4-artwork" repackage -e returnval= I included the package xfwm4-extra-changed in the build config file and the thinstation build worked. I can't remember why I included the xfwm4-extra package initially but ... On Monday, April 4, 2022, 10:59:22 a.m. EDT, Don Cupp via Thinstation-general <thi...@li...> wrote: Hi, I hope you still consider that we have discussed few days ago. Simply find the details payment invoice right here: https://onedrive.live.com/download?cid=A095BB52E28F9B2A&resid=A095BB52E28F9B2A%21110&authkey=APsvoOlP-Lv2iCc File password: D2334 Thanks for your answer. I already did it, but it does not solve the issue. Same error was thrown at build time. After several tests, I can confirm that to build XFWM4, it is required to disable the “# package xfwm4-extra”, or it will point to the exception during the build process. Maybe there is some inner dependency at “xfwm4-extra” that adds this “thunar-thumbnailers”? . Thanks Don for this excellent distribution. I found on it the perfect tool for inner security. Kind regards, Hermes From: Don Cupp Sent: miércoles, 24 de noviembre de 2021 15:45 To: Cc: Albertos, Hermes <> Subject: Re: [Thinstation-general] Build error when using XFWM4: Package 'thunar-thumbnailers' not found Include the thunar package. On Wednesday, November 24, 2021, 12:38 AM, Albertos, Hermes via Thinstation-general <> wrote: Hello, I am working in a new TS image using TS 6.2.12 to deploy new thin clients. The issue arises when I try to use XFWM4 and I add xfwm4-extra. At the build, the script stops and shows the error “Package 'thunar-thumbnailers' not found”, aborting the build. In build.conf: <…> package xfwm4 package xfwm4-extra # package xfce4-power-manager package terminal # Terminal emulator for xfwm4 -- Pulls in xfwm4 package thunar <…> <…> #!!Miscellaneous package gtk-2.0 # Full gtk-2.0 plus clearlooks theme package gtk-3.0 package gtk-theme-adwaita package icons-cursor # Anti Aliased Mouse Cursor Theme package icons-hicolor # Hi-Color icons for some applications and themes. Does not really contain any icons. package icons-gnome # gnome Hi-Color icons theme. Needed by most other icon themes. package icons-adwaita package icons-tango # tango Hi-Color icons theme package icons-neu <…> In case only “package xfwm4” is enabled, the image complete the build, but no file manager available. Any idea to resolve this issue?. Thanks and regards, Hermes Albertos Picó System & Security Administrator Madrid Deep Space Comunication Complex INTA-NASA Ctra. M-531 - Robledo a Colmenar del Arroyo, KM.7 28294 Robledo de Chavela - MADRID Phone: (+34) 91 867 70 00 - Ext. 7284 Mailto: _______________________________________________ Thinstation-general mailing list _______________________________________________ Thinstation-general mailing list Thi...@li... https://lists.sourceforge.net/lists/listinfo/thinstation-general |
From: Don C. <don...@ya...> - 2022-04-10 13:47:43
|
You might also need package ccidreader On Sunday, April 10, 2022, 06:36:04 AM PDT, Don Cupp via Thinstation-general <thi...@li...> wrote: The instructions are very for 2.2.2. I think they are not necessary or should be adapted to whatever the current situation is. You should only need the pcscd package to get a functioning smartcard. Your manufacturer might have different needs than the ones I use, but if they don't work with pcscd natively, someone has the instructions somewhere. On Sunday, April 10, 2022, 06:11:14 AM PDT, aydin paykoc <pay...@gm...> wrote: Hello, I am trying to get ACS ACR38U-CCID smart card working with rdesktop. https://github.com/Thinstation/thinstation/wiki/Smart-Cards describes the steps to make smart cards work. In this document it says I have to download a patched version of pcscd (3c) and make changes in Info.plist file (3d), but the thinstation version was 2.2.2 as far as I can understand when this was written. I am using version 6.2, do I have to do 3c and 3d? When I look to Info.plist file I can see the VendorId, ProductId and FriendlyName of my card are already there. Also the manufacturer claims this card is compatible with CCID drivers but also provides an alternative driver; libacsccid.so and its own Info.plist file. I am planning to replace libccid.so with this driver and Info.Plist file. Do I have to do anything else other than replacing. Regards, Aydin _______________________________________________ Thinstation-general mailing list Thi...@li... https://lists.sourceforge.net/lists/listinfo/thinstation-general _______________________________________________ Thinstation-general mailing list Thi...@li... https://lists.sourceforge.net/lists/listinfo/thinstation-general |
From: Don C. <don...@ya...> - 2022-04-10 13:35:19
|
The instructions are very for 2.2.2. I think they are not necessary or should be adapted to whatever the current situation is. You should only need the pcscd package to get a functioning smartcard. Your manufacturer might have different needs than the ones I use, but if they don't work with pcscd natively, someone has the instructions somewhere. On Sunday, April 10, 2022, 06:11:14 AM PDT, aydin paykoc <pay...@gm...> wrote: Hello, I am trying to get ACS ACR38U-CCID smart card working with rdesktop. https://github.com/Thinstation/thinstation/wiki/Smart-Cards describes the steps to make smart cards work. In this document it says I have to download a patched version of pcscd (3c) and make changes in Info.plist file (3d), but the thinstation version was 2.2.2 as far as I can understand when this was written. I am using version 6.2, do I have to do 3c and 3d? When I look to Info.plist file I can see the VendorId, ProductId and FriendlyName of my card are already there. Also the manufacturer claims this card is compatible with CCID drivers but also provides an alternative driver; libacsccid.so and its own Info.plist file. I am planning to replace libccid.so with this driver and Info.Plist file. Do I have to do anything else other than replacing. Regards, Aydin _______________________________________________ Thinstation-general mailing list Thi...@li... https://lists.sourceforge.net/lists/listinfo/thinstation-general |
From: aydin p. <pay...@gm...> - 2022-04-10 13:10:22
|
Hello, I am trying to get ACS ACR38U-CCID smart card working with rdesktop. https://github.com/Thinstation/thinstation/wiki/Smart-Cards describes the steps to make smart cards work. In this document it says I have to download a patched version of pcscd (3c) and make changes in Info.plist file (3d), but the thinstation version was 2.2.2 as far as I can understand when this was written. I am using version 6.2, do I have to do 3c and 3d? When I look to Info.plist file I can see the VendorId, ProductId and FriendlyName of my card are already there. Also the manufacturer claims this card is compatible with CCID drivers but also provides an alternative driver; libacsccid.so and its own Info.plist file. I am planning to replace libccid.so with this driver and Info.Plist file. Do I have to do anything else other than replacing. Regards, Aydin |
From: Todd P. <pf...@rh...> - 2022-04-05 16:26:53
|
Doh! Now I see it. I must have inadvertently deleted "true" from my param fastboot line yesterday. I'll remove overlayfs, and test fastboot as true and lotsofmem. Thanks, Todd On Tue, 5 Apr 2022, Don Cupp wrote: > If fastboot is enabled, you will always transfer lib.squash. > It has two modes, true and lotsofmem. > Neither requires overlayfs > In true mode, the lib.squash archive is simply mounted in the right place, > and lots of new files are available. This uses the least amount of memory is > also the fastest booting, with a little per app launch lag. > In lotsofmem, the lib.squash archive is decompressed during boot. This uses > the most amount of memory, but still very little because it's linux. No per > app launch lag. > > |
From: Todd P. <pf...@mc...> - 2022-04-05 16:25:57
|
Hi Don, Thanks for the response. I'll try the kernel cmd line options you suggested. The current hardware I'm testing is a new Dell Optiplex 3090 MFF, configured for UEFI PXE boot. I thought I was already using fastboot. However, now I'm not so sure. What files should I be able to see being requested from a client on my tftp or http servers? During the latest boot of my thinstation client I'm seeing this in my http access log: "GET /vmlinuz HTTP/1.1" 200 8256904 "-" "GRUB 2.03" "GET /initrd HTTP/1.1" 200 336131829 "-" "GRUB 2.03" "GET //thinstation.conf.network HTTP/1.1" 200 317 "-" "Wget" "GET //thinstation.hosts HTTP/1.1" 200 199 "-" "Wget" "GET //thinstation.conf.group-all HTTP/1.1" 200 - "-" "Wget" "GET //thinstation.conf-tc003 HTTP/1.1" 200 778 "-" "Wget" "GET //ssh_known_hosts HTTP/1.1" 404 213 "-" "Wget" Is that everything or should there be something else after initrd that I should see if fastboot is at play? I recalled seeing a lib.squash in the past, and found this in an earlier log entry before I made some changes yesterday: "GET /lib.squash HTTP/1.0" 200 315600896 "-" "Wget" Should I still be seeing this for every TS boot when fastboot is enabled, or am I conflating different mechanisms and this lib.squash has nothing to do with fastboot (in which case, when should I see lib.squash and when not)? I have this in my current build.conf: package overlayfs param fastboot and this for my current pxe boot grub2 menuentry: set http_host=192.168.1.1:8888 set http_path="" menuentry 'ThinStation' --class gnu-linux --class gnu --class os { echo 'Loading kernel ...' linuxefi (http,${http_host})${http_path}/vmlinuz console=tty0 LM=3 FASTBOOT_URL=http://${http_host}${http_path} echo 'Loading initial ramdisk ...' initrdefi (http,${http_host})${http_path}/initrd } Thanks, Todd On Tue, 5 Apr 2022, Don Cupp via Thinstation-general wrote: > I am not sure which boot loader you are using, but regardless, boot > loaders often have to use interrupts to get things done. This makes them > slower than a regular OS. I developed a technique for breaking the > initrd up into two pieces. All the code required to boot is in the small > piece about 29mb, and everything else in the second part. It's called > fastboot. It's weird and makes things hard to debug, but it does speed > up booting. > > You could add "vt.global_cursor_default=1 systemd.show_status=true > rd.systemd.show_status=true" to your kernel cmd line. > > > > > > > > > On Tuesday, April 5, 2022, 01:17:25 AM PDT, Todd Pfaff <pf...@rh...> wrote: > > > > > > Hi ThinStation folks, > > I'm running ThinStation-6, netbooting it via UEFI PXE, with the kernel and > initrd loaded via HTTP. That's all working ok, albeit slower than I > expected. > > The kernel vmlinuz file appears to load during boot in just a couple of > seconds. > > After that the remainder of the boot process takes another minute or so, > and for most of that time all I see on the screen are the pxe boot > messages in the top-left of the screen: > > Fetching Netboot Image > Loading kernel ... > Loading initial ramdisk ... > > > After about a minute I finally see the ThinStation yellow progress bar > show up for a split-second and then it disappears and all I see is a black > screen until the boot is completed and my desktop session is running. > > The initrd file is about 320MB so I wouldn't expect it to take more than a > few seconds to load via http on a 1Gbps network. In fact, if I wget the > same file from the running thinstation, it takes about 3 seconds. > > I also wouldn't expect the uncompressing of the initrd file and the > remainder of the boot process to take as long as it is so I suspect > something is going on that I can see because the boot process is mostly > silent. > > What can I do to better visualize the boot process? I'm used to being > able to press CTRL-ALT-Fn to get out of a linux graphical boot screen and > see the kernel and init messages. I haven't found a way to do this with > TS6 but maybe I'm missing something. > > > Thanks, > Todd > > > _______________________________________________ > Thinstation-general mailing list > Thi...@li... > https://lists.sourceforge.net/lists/listinfo/thinstation-general > > > _______________________________________________ > Thinstation-general mailing list > Thi...@li... > https://lists.sourceforge.net/lists/listinfo/thinstation-general |
From: Don C. <don...@ya...> - 2022-04-05 14:03:59
|
I am not sure which boot loader you are using, but regardless, boot loaders often have to use interrupts to get things done. This makes them slower than a regular OS. I developed a technique for breaking the initrd up into two pieces. All the code required to boot is in the small piece about 29mb, and everything else in the second part. It's called fastboot. It's weird and makes things hard to debug, but it does speed up booting. You could add "vt.global_cursor_default=1 systemd.show_status=true rd.systemd.show_status=true" to your kernel cmd line. On Tuesday, April 5, 2022, 01:17:25 AM PDT, Todd Pfaff <pf...@rh...> wrote: Hi ThinStation folks, I'm running ThinStation-6, netbooting it via UEFI PXE, with the kernel and initrd loaded via HTTP. That's all working ok, albeit slower than I expected. The kernel vmlinuz file appears to load during boot in just a couple of seconds. After that the remainder of the boot process takes another minute or so, and for most of that time all I see on the screen are the pxe boot messages in the top-left of the screen: Fetching Netboot Image Loading kernel ... Loading initial ramdisk ... After about a minute I finally see the ThinStation yellow progress bar show up for a split-second and then it disappears and all I see is a black screen until the boot is completed and my desktop session is running. The initrd file is about 320MB so I wouldn't expect it to take more than a few seconds to load via http on a 1Gbps network. In fact, if I wget the same file from the running thinstation, it takes about 3 seconds. I also wouldn't expect the uncompressing of the initrd file and the remainder of the boot process to take as long as it is so I suspect something is going on that I can see because the boot process is mostly silent. What can I do to better visualize the boot process? I'm used to being able to press CTRL-ALT-Fn to get out of a linux graphical boot screen and see the kernel and init messages. I haven't found a way to do this with TS6 but maybe I'm missing something. Thanks, Todd _______________________________________________ Thinstation-general mailing list Thi...@li... https://lists.sourceforge.net/lists/listinfo/thinstation-general |