13:08:13 <nsITobin> good morning zedmatrix 
13:14:27 <nsITobin> i been looking to see if there is a per file size limit and all i can find is the total size of 10gbs for free accounts
13:15:55 <nsITobin> zedmatrix: I have server space I could offer but should the federal government take a crap that and I would vanish but if you wanna hope for the best i gots some space to share
13:18:23 <nsITobin> ima gonna try and boot bare metal the iso you sent
13:18:28 <nsITobin> see how that goes
13:23:29 <nsITobin> couldn't mount device /dev/sr0
13:24:04 <nsITobin> i used fedora media writer which I believe is just dd stuff everyone but me seems to be able to remember lol
13:26:05 <nsITobin> first scsi cdrom in the system eh
13:27:10 <nsITobin> wha
13:27:34 <nsITobin> why in gods name did fedora media writer creatte a 1.1gb hfs+ partition
13:28:03 <nsITobin> ... right looking up the commands .. likely in that repo
13:46:22 <nsITobin> what's with all the macintosh stuff in the iso?
13:47:59 <nsITobin> *reads init closer*
13:48:09 <nsITobin> i see
13:48:52 <zedmatrix> ahh who know what, i made it for a cd/dvd media, i am gonna have change the initramfs to look for that .boot-uuid identifier
13:49:08 <nsITobin> zedmatrix: yeah I figured that out
13:49:10 <nsITobin> uhh
13:49:12 <nsITobin> hmm
13:49:34 <zedmatrix> the grub mk cmd installs that into the iso
13:49:59 <nsITobin> well PARTLABEL= is very nice but you still have to handle an actual cdrom case .. seems like everything else is trivial.. and even cdrom should respond to a search by partlabel
13:50:31 <nsITobin> i have basically made PARTLABEL my lowest common denominator cause who can remember guids
13:50:47 <nsITobin> because it works EVERYWHERE except grub its self
13:51:01 <nsITobin> but kernel can deal.. system can deal
13:52:08 <nsITobin> nvme0n1p1 sounds like this year's flu
13:52:11 <nsITobin> for example
13:52:56 <nsITobin> man I hope I don
13:53:08 <zedmatrix> nah its just a couple lines in the initramfs
13:53:14 <nsITobin> i don't catch x86-64v3
13:53:16 <nsITobin> :P
13:54:03 <nsITobin> your example has answered a CRAP ton of questions about initramfs for me
13:54:47 <nsITobin> also you expand the squashfs into the ram drive? that's it?
13:56:31 <nsITobin> lower mounts it str8 so attempted streaming.. and high means ramdisk?
13:59:00 <zedmatrix> grub (cmd line mode) will show these parts... (cd0) (cd0,apple1) (cd0,gpt1)
13:59:05 <nsITobin> and once the overlay is establshed and the switchroot is done.. it is more or less eq to any other booted system save space restrictions
14:00:35 <zedmatrix> yea the is from the kernel overlayfs. https://docs.kernel.org/filesystems/overlayfs.html
14:00:44 <zedmatrix> i just had chatgpt refine it
14:01:35 <nsITobin> also examining the initrd contents only a few libs and tools it seems answers more questions on how libs and crap work in such a concrete way so thanks for doing this and I am sure it will help lots of people.. I haven't even done anything yet and it has helped my understanding.
14:02:11 <nsITobin> gotta watch those bots tho.. they like to override my formatting and intentions on unrelated stuff
14:02:54 <nsITobin> it is like this should be part of linux 101 but it is like.. forbidden to know it especially if it isn't distro specific
14:04:30 <zedmatrix> the initamfs i used the script to parse the bin/sbin using ldd
14:05:02 <zedmatrix> the info is in linux 101
14:05:16 <zedmatrix> but the advanced linux 101
14:06:15 <zedmatrix> you can examine what grub inserted using > xorriso -indev lfslive.iso -find /
14:08:47 <nsITobin> i guess part of what dracut does is sit there and interrogate every device until it finds its crap
14:09:20 <nsITobin> tried to understand it but another py3 mess and py2 stuff is too rotted to recollect it these days
14:10:13 <nsITobin> if i had started a decade ago on this instead of mozmoon junk it would all be on tauthon 
14:17:18 <zedmatrix> hmm could be When such an ISO is written to USB via dd or Fedora Media Writer (which wraps dd), the USB stick ends up with: An MBR + GPT partition scheme
14:24:45 <nsITobin> zedmatrix: the burdon of not specializing too much can be heavy but can be effectively countermanaged with careful selection so special cases don't grow beyond being able to deal with em
14:25:02 <zedmatrix> yea the mkinitramfs from LFS site uses udevadm 
14:25:19 <nsITobin> now that I have seen how this works without all the $distro garbage on top I have IDEAS!
15:22:34 <zedmatrix> nsITobin:  ok i think i have it
15:45:08 <zedmatrix> nsITobin: i cleaned up the files so they are in archives... https://gitlab.com/zed-linuxfromscratch/live-iso
15:47:56 <zedmatrix> ok a new little archive for you https://ln5.sync.com/4.0/dl/5b74a8660#j6pfufvs-t9nbcgh4-b9vnzn7e-9ej72737
15:48:15 <zedmatrix> just haveto remember the dd command now
15:50:57 <zedmatrix> oh good i got the right device , the usb is flashing :)
15:56:16 <zedmatrix> hmm i guess i shouldof made a label instead of ISOIMAGE :)
15:59:49 <nsITobin> zedmatrix: put the dd commands in the repo
15:59:50 <nsITobin> lol
16:00:02 <nsITobin> or rather
16:00:22 <nsITobin> zedmatrix: When you get a moment could you please put the commands somewhere like your repo.
16:00:46 <nsITobin> i am issuing orders to the COMputer.. sorry if i get all demand-y sounding
16:01:23 <zedmatrix> you mean the dd?
16:01:37 <zedmatrix> >> dd if=lfslive.iso of=/dev/sdX bs=4M status=progress oflag=sync
16:11:25 <zedmatrix> hmm interesting
16:23:50 <zedmatrix> nsITobin:  ahh its not checking the partitions, just the device
16:42:13 <zedmatrix> ok just writing to usb to test 2nd pass
16:58:57 <nsITobin> cool
16:59:05 <nsITobin> gonna walk a bag of trash out be back shortly
17:06:23 <zedmatrix> i think i am also missing the dev/tty{0,1,2} nods
17:15:19 <zedmatrix> i think its cause i am not using udevd
17:21:01 <nsITobin> PARTLABEL doesn't need udev or anything
17:21:14 <nsITobin> PARTLABEL != LABEL
17:21:20 <nsITobin> LABEL needs more stuff
17:32:06 <zedmatrix> i think its cause i am missing the /dev nodes like /dev/sd{a,b,c}{1,2,3}
17:33:27 <zedmatrix> ok third usb burn 
17:40:50 <zedmatrix> hmm found another missing program "mountpoint"
20:48:06 <zedmatrix> oh cool you can copy and paste in a vm
20:48:11 <zedmatrix> *qemu
20:53:41 <zedmatrix> nsITobin: hmm using the udevd i ended up with 1000 0000:00:03.0 ens3: renamed from eth0
20:59:31 <nsITobin> ffs lol
21:00:25 <nsITobin> but it is your livecd if I want eth0 i can change it
21:00:27 <Moody> check net.ifnames=0 on the kernel cmdline
21:01:04 <nsITobin> eth0 is the best interface name
21:01:14 <nsITobin> second only to wlan0
21:01:20 <nsITobin> :)
21:01:35 <nsITobin> but I do have an alternative
21:01:46 <nsITobin> "Local Area Connection" and "Wireless Connection"
21:01:47 <nsITobin> ;)
21:03:30 <nsITobin> zedmatrix: the ONE reason I'd opt into the qt ecosystem is a Qt Program Manager and Qt File Manager that isn't junk.
21:06:09 <zedmatrix> that is what sys-v/udevd made
21:07:09 <nsITobin> well let's stick close to "default" where possible.. if some nut like my self wants to reconfigure it to eth0 i uhh can ;) less overhead
21:09:39 <nsITobin> zedmatrix: you know.. i need to rebuild my kernel ... which sucks cause it means i have to try bash vmware into accepting the new order
21:09:51 <nsITobin> i don't HAVE squashfs support built in
21:12:55 <nsITobin> see i wanna try and experiment
21:13:05 <zedmatrix> yea thats y i made a new config-6.14.10 
21:13:30 <zedmatrix> also thats y i like qemu :)
21:13:31 <nsITobin> I am still on 6.10.x
21:13:41 <nsITobin> i need to look into some security backports
21:14:56 <nsITobin> i like 6.10.x
21:15:01 <nsITobin> it functions well
21:15:07 <nsITobin> unlike some 6.x versions
21:16:06 <nsITobin> *I* don't need to care about such things on my own workstation but of course for others I'd be using latest or some lts
21:18:56 <nsITobin> zedmatrix: do you intend on making a graphical livecd eventually.. cause I certainly am.. theoretically once you have the boot with a rw root figured out what is on the root is arbitrary
21:19:08 <zedmatrix> yea maybe 
21:20:03 <zedmatrix> the problem with a graphical, is probably would haveto make it not read from ram
21:20:27 <zedmatrix> that would make the ramdisk too large
21:22:22 <nsITobin> well there are small alternatives one could use
21:39:06 <zedmatrix> hmm i think the usb is taking too long to power up
21:51:53 <zedmatrix> hmm found another option i missed CONFIG_HFS_FS=m CONFIG_HFSPLUS_FS=m
21:56:19 <nsITobin> zedmatrix: yeah why is it hfs+?
22:02:14 <zedmatrix> its something with the isofs
22:03:19 <zedmatrix> its probably something to do with having both bios and uefi 
22:07:40 <nsITobin> perhaps