jaeger changed the topic of #crux to: CRUX 3.6 | Homepage: https://crux.nu/ | Ports: https://crux.nu/portdb/ https://crux.ninja/portdb/ | Logs: https://libera.irclog.whitequark.org/crux/
SiFuh has joined #crux
SiFuh_ has quit [Ping timeout: 255 seconds]
jaeger- has joined #crux
jaeger has quit [*.net *.split]
plow has quit [*.net *.split]
leah2 has quit [*.net *.split]
plow has joined #crux
leah2 has joined #crux
ppetrov^ has joined #crux
ty3r0x_ has joined #crux
ty3r0x_ has quit [Ping timeout: 268 seconds]
ty3r0x_ has joined #crux
ardo has quit [Read error: Connection reset by peer]
ardo has joined #crux
genpaku has quit [Remote host closed the connection]
genpaku has joined #crux
Guest62 has joined #crux
Guest62 has quit [Client Quit]
<SiFuh> farkuhar: What did you do?
<SiFuh> You alone have demonstrated exactly the confusion I said would happen in your handbook. :-)
<SiFuh> %fn%/boot/efi%% <-- This is what I said is fine. But others are wanting %fn%/boot/efi/efi%% which to be honest is just the existance of a non needed extra directory.
<SiFuh> 67, 68, 78, 193 and 194 you have /boot/efi/BOOT and 113, 153 and 155 /boot/efi/EFI/BOOT/. Would it not just be easier to choose one specific way, but then explain that it can be mounted anywhere?
<SiFuh> Such as the less evil way is this way and for the sake of the manual we will do it this way. But it can be done this way which is more common?
<SiFuh> It's super complicating things $INSTALLDIR is now going to need to have the kernel installed. If the kernel is in another location then syslinux.cfg is going to need to be changed. It's like dominoes falling ;-)
ppetrov^^ has joined #crux
ppetrov^ has quit [Ping timeout: 255 seconds]
<farkuhar> SiFuh: thanks for the careful proofreading. I'll go back and put into agreement all the references to subdirectories of the EFI partition.
<SiFuh> It's good, just getting a bit to complex. Maybe it is the format I am reading it as. But yeah, I think the best way is to do the entire thing one way, but create a small section explaining that it can be anywhere kind of almost like what you have done. Ultimately it isn't up to me anyway. I am just throwing in my 2 cents worth
<farkuhar> As for a remark about UEFI not caring about the fstab mountpoint for the EFI partition, I think such a remark should appear in *both* the GRUB section and the SYSLINUX appendix, or just relegated to the separate Wiki page on UEFI.
<SiFuh> But as I was saying, if you are going to to start changing paths then you are probably going to have to start covering more stuff like vmlinuz and ../vmlinuz or /EFI/BOOT/vmlinuz
<SiFuh> Yeah, probably easier to add a tiny section for UEFI
<SiFuh> In fact, it might involve clicking an extra link but to be honest UEFI is not grub or SYSLINUX so maybe deserving it's own little subsection.
<farkuhar> The way navigation works in the current draft of the handbook, readers are only directed to the separate Wiki page on UEFI if they proceed through the GRUB installation. If they skip to the Appendix, then they won't see that link, so I should probably add it there too.
<SiFuh> I think the CRUX handbook is very well written. It is very simplistic in its approach.
<SiFuh> Don't go the Arch Linux wiki path. You can read, and re-read SYSLINUX or even LUKS(2) Encryption and just get lost.
<SiFuh> farkuhar: https://wiki.archlinux.org/title/Dm-crypt/Encrypting_an_entire_system This is the one that I was studying from a few years back.
<farkuhar> I actually referred to handwritten notes copied from the Slackware syslinux howto, when explaining the relative paths that syslinux will search for a kernel.
<SiFuh> Yeah, I got most of mine from the SYSLINUX wiki/howto and some from Slackware and Arch
<farkuhar> But in my latest edits I might have introduced some of the inconsistencies that you pointed out above (lines 193 and 194 in conflict with 153 and 155)
<SiFuh> But these days, geetverything SYSLINUX from SYSLINUX wiki because I understand it much better than when I started. I actualy learned it under Slackware and thought, this is really cool
<SiFuh> I liked your lit bit of shell codes though. :-P
ty3r0x_ has quit [Ping timeout: 268 seconds]
<farkuhar> Thanks again for the feedback. I have a few work-related obligations to take care of first, and then I'll revisit the handbook in a few hours.
<SiFuh> But the moment you stoped at line 121 I was thinking, errrr, what now? I am just coying and pasting and where do I put my kernel?
<SiFuh> Take you time, no hurry
<SiFuh> I am sure the Mona Lisa wasn't painted over night.
ppetrov^^ has quit [Quit: Leaving]
<cruxbot> [contrib.git/3.6]: yt-dlp: 2022.08.08
ppetrov^ has joined #crux
<SiFuh> farkuhar: Do you mind to put the configuration back in capital letters as well? Such as LABEL, KERNEL, PROMPT.. and so on. Nothing serious though.
<SiFuh> Sorry for being a bit pedantic :-P
<farkuhar> Happy to oblige you, SiFuh. But all these changes have to be approved by the core team anyway; my draft is just a starting point (and not a particularly well-formatted one, given my inexperience with pmwiki)
<SiFuh> Understood, but still, even SYSLINUX writes their labels in capitals so as to define a clear syntax between that which is theirs and that which a user has added
<SiFuh> I am waiting for the influx of users complaing why doesn't 'label = Linux' work? :-) It ain't LILO hahah
<SiFuh> https://crux.nu/gitweb/?p=system/iso.git;a=blob;f=iso/isolinux/isolinux.cfg;h=9c746ff0fd14e185efd5a6086d3a8fea7c6793bc;hb=614c77fb70760ce711faea6c2234f2e8487ff186
ardo has quit [Read error: Connection reset by peer]
ardo has joined #crux
<farkuhar> That blob from the gitweb confirms the precedent of using uppercase for SYSLINUX keywords, so the core team will probably approve your suggested change. I've already made the revisions to the draft.
<SiFuh> farkuhar: have you ever built a CRUX ISO?
<SiFuh> Sorry off-topic
<farkuhar> SiFuh: no, i haven't had the opportunity yet.
<SiFuh> Maybe jaeger- knows
<SiFuh> I have noticed that there is syslinux/isolinux and grub and then isohybrid (Which is from syslinux)
<SiFuh> Curious to why grub exists when isohybrid should do similar
<jaeger-> grub was the only working choice for a hybrid UEFI image at the time
<SiFuh> isohybrid -u <- Build EFI bootable image
<SiFuh> So why why keep it? Maybe can knock a few bytes off the disk
<SiFuh> I did notice that on a non UEFI system I got ISOLINUX and on a UEFI system it was grub
<SiFuh> jaeger-: sorry I was thinking about it today at work, and had to look again.
<jaeger-> At the time it was THE ONLY way that worked :) I'm not being hyperbolic, that was literal truth
<jaeger-> It's entirely possible that it's not the case now, a lot of time has passed
<jaeger-> Would just need to research it more
jaeger- is now known as jaeger
<SiFuh> The same thing came to mind for me
<SiFuh> Should grub be able to boot in non-UEFI mode as well?
<jaeger> I imagine so, but syslinux was already there and working for it so I didn't try to replace it
<SiFuh> I understand
<farkuhar> SiFuh, you find cause to celebrate in some very obscure places ... shaving 256 bytes here and there, reducing by 1 the number of bootloaders on the installation media
<SiFuh> I just found it odd that we have a bootloader that can do things, and one that could do 2 things but was doing one thing that the other could already do ;-)
<SiFuh> Need stenur here to try to make heads or tails of that ;
<SiFuh> farkuhar: actually I was suprised that by addind two extra features to the kernel caused it to become smaller.
<SiFuh> I remember when I selected LPSS that the one in menu config switched from module to built into the kernel. Yet, still ended up being smaller
<SiFuh> That made no sense
<SiFuh> When I selected LPSS the Intel SoC IOSF became built in. But it was built in already. It jsut stopped the option to allow it to module. That is why the { } disappeared.
<SiFuh> So nothing special.
ardo has quit [Read error: Connection reset by peer]
ardo has joined #crux
<SiFuh> jaeger: Apart from changing the CD boot kernel to support LPSS and exfat, the rest of the system is doing well. I don't see anything serious as of yet.
<SiFuh> A mini PC and the one with 1GB of RAM is running fine.
<jaeger> good deal
<SiFuh> Not sure if it was a good deal, had to make my own ISO for the mini PC. I deserve a refund :-P
<SiFuh> To be honest, the only reason I did the new ISO is that I wanted to test the CD kernel, Kernel modifications so that it would make your life a bit easier
<farkuhar> refund from MoreFine? What was the current kernel version at the time you bought that mini PC? There's no way they could have anticipated all the kernel changes since then. :-P
<SiFuh> Maintaining distros can be annoying especially with my nagging ;-)
<SiFuh> farkuhar: Sorry but both Morfine +S500 run OpenBSD
<SiFuh> CRUX 3.7 are on the Beelink BT3 PRO and some ancient 1GB RAM HP thing
<SiFuh> 3.6 is on the Metabox
<farkuhar> Oh, it must have been an older mini PC that needed the custom ISO. Even less likely you'll get a refund from that manufacturer.
<SiFuh> 3.5 is on some super ancient laptop
<SiFuh> I may have upgraded that to 3.6 :-P
<SiFuh> I think jaeger needs to slap farkuhar around with the Zotac ;-)
<SiFuh> farkuhar: by enabling LPSS has opened a new doorway for CRUX to be easily installed certain MINI PCs that do not use standard disks. SUch as, and we have mentioned it before MMC drives.
<SiFuh> Might take them 12 hours to compile a kernel though. :-D
<SiFuh> The Beelink took about 11 hours
<SiFuh> I actually did a make bootstrap twice and make ISO and produced 2 ISO images before the Beelink was done
ty3r0x_ has joined #crux
<jaeger> yeah, compiling on my zotac box is a chore, definitely
<jaeger> It has a fairly anemic dual-core atom CPU and 2GB RAM
<SiFuh> They are reasonable for what they do but they are not good at much else
<SiFuh> This particular one came with Clear Linux and it was horrible. I think in the end it was running Linux Mint. I can't verify that as I killed it. It would crash 1 hour in to any movie being played with mpv or 'cellaloid'? .
<SiFuh> Celluloid
fishe has joined #crux
<fishe> hello!
<fishe> are there any good examples of ports that install packages via pip?
<SiFuh> If ther eare, I have never seen any
<fishe> ah
<SiFuh> I myself usually install pip or pip3 ports for my specific user
<SiFuh> -ports
<SiFuh> Ports are system wide, and I am unaware if any ports exist that use pip to unstall system wode
<SiFuh> wide*
<fishe> im not entirely sure how pip works so i didn't know if it would be a better idea to write it as a port lol
<SiFuh> Seriously something wrong with my fingers. I type so poorly
<fishe> trying to get woeusb installed to throw vista on the old pc, just for fun
<SiFuh> fishe it is usually done at the user level. So for example I want 'subliminal'. There are no ports. I install 'pip(whatever version)' and then do 'pip(what ever version) install subliminal'
<fishe> ah, that makes sense
<fishe> i'll try that
<SiFuh> Just imagine pip is like a user local version of a not so CRUX port ;-)
<fishe> fair lol
<SiFuh> I use subliminal for mpv to auto download subtitles. I find it difficult to hear things very close to me.
<SiFuh> It gets installed in my home directory and is not available anywhere else
ty3r0x_ has quit [Quit: Konversation terminated!]
fishe has quit [Quit: Connection closed for inactivity]
ppetrov^ has quit [Quit: Leaving]
_0bitcount has joined #crux
_0bitcount has quit [Quit: Leaving]
tilman has quit [Ping timeout: 268 seconds]
tilman has joined #crux