good morning zedmatrix

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

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

ima gonna try and boot bare metal the iso you sent

see how that goes

couldn't mount device /dev/sr0

i used fedora media writer which I believe is just dd stuff everyone but me seems to be able to remember lol

first scsi cdrom in the system eh

wha

why in gods name did fedora media writer creatte a 1.1gb hfs+ partition

... right looking up the commands .. likely in that repo

what's with all the macintosh stuff in the iso?

*reads init closer*

i see

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

zedmatrix: yeah I figured that out

uhh

hmm

the grub mk cmd installs that into the iso

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

i have basically made PARTLABEL my lowest common denominator cause who can remember guids

because it works EVERYWHERE except grub its self

but kernel can deal.. system can deal

nvme0n1p1 sounds like this year's flu

for example

man I hope I don

nah its just a couple lines in the initramfs

i don't catch x86-64v3

:P

your example has answered a CRAP ton of questions about initramfs for me

also you expand the squashfs into the ram drive? that's it?

lower mounts it str8 so attempted streaming.. and high means ramdisk?

grub (cmd line mode) will show these parts... (cd0) (cd0,apple1) (cd0,gpt1)

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

yea the is from the kernel overlayfs. docs.kernel.org/filesystems/overlayfs.html

i just had chatgpt refine it

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.

gotta watch those bots tho.. they like to override my formatting and intentions on unrelated stuff

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

the initamfs i used the script to parse the bin/sbin using ldd

the info is in linux 101

but the advanced linux 101

you can examine what grub inserted using > xorriso -indev lfslive.iso -find /

i guess part of what dracut does is sit there and interrogate every device until it finds its crap

tried to understand it but another py3 mess and py2 stuff is too rotted to recollect it these days

if i had started a decade ago on this instead of mozmoon junk it would all be on tauthon

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

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

yea the mkinitramfs from LFS site uses udevadm

now that I have seen how this works without all the $distro garbage on top I have IDEAS!

nsITobin: ok i think i have it

nsITobin: i cleaned up the files so they are in archives... gitlab.com/zed-linuxfromscratch/live-iso

ok a new little archive for you ln5.sync.com/4.0/dl/5b74a8660#j6pfufvs-t9nbcgh4-b9vnzn7e-9ej72737

just haveto remember the dd command now

oh good i got the right device , the usb is flashing :)

hmm i guess i shouldof made a label instead of ISOIMAGE :)

zedmatrix: put the dd commands in the repo

lol

or rather

zedmatrix: When you get a moment could you please put the commands somewhere like your repo.

i am issuing orders to the COMputer.. sorry if i get all demand-y sounding

you mean the dd?

>> dd if=lfslive.iso of=/dev/sdX bs=4M status=progress oflag=sync

hmm interesting

nsITobin: ahh its not checking the partitions, just the device

ok just writing to usb to test 2nd pass

cool

gonna walk a bag of trash out be back shortly

i think i am also missing the dev/tty{0,1,2} nods

i think its cause i am not using udevd

PARTLABEL doesn't need udev or anything

PARTLABEL != LABEL

LABEL needs more stuff

i think its cause i am missing the /dev nodes like /dev/sd{a,b,c}{1,2,3}

ok third usb burn

hmm found another missing program "mountpoint"

oh cool you can copy and paste in a vm

*qemu

nsITobin: hmm using the udevd i ended up with 1000 0000:00:03.0 ens3: renamed from eth0

ffs lol

but it is your livecd if I want eth0 i can change it

check net.ifnames=0 on the kernel cmdline

eth0 is the best interface name

second only to wlan0

:)

but I do have an alternative

"Local Area Connection" and "Wireless Connection"

;)

zedmatrix: the ONE reason I'd opt into the qt ecosystem is a Qt Program Manager and Qt File Manager that isn't junk.

that is what sys-v/udevd made

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

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

i don't HAVE squashfs support built in

see i wanna try and experiment

yea thats y i made a new config-6.14.10

also thats y i like qemu :)

I am still on 6.10.x

i need to look into some security backports

i like 6.10.x

it functions well

unlike some 6.x versions

*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

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

yea maybe

the problem with a graphical, is probably would haveto make it not read from ram

that would make the ramdisk too large

well there are small alternatives one could use

hmm i think the usb is taking too long to power up

hmm found another option i missed CONFIG_HFS_FS=m CONFIG_HFSPLUS_FS=m

zedmatrix: yeah why is it hfs+?

its something with the isofs

its probably something to do with having both bios and uefi

perhaps