smplayer/smtube,vcl,kodi,firfox,and a few more.
It's working well.
It's an older version of Kodi,15.4 I think,latest Firefox I think.
Anyway,
It's very cool

http://bkhome.org/news/201811/xenialpup ... asyos.htmlbelham2 wrote:Is Xenialpup as an OS running in Virtualbox (inside Easy) and then that Virtualbox itself is inside a Container?
The CD boots up and runs in ram, there should not be any error about missing boot drive.belham2 wrote:Hi Barry & everyone,
Thanks, Barry, for this latest release. Made the mistake of burning the ISO immediately after download, and then wondering why it wouldn't boot on any machine of mine (laptop and/or desktop, kept throwing "Finding Drives....Creating compressed zram.....sda sr0 written 20 times)...then..ERROR:Boot drive not found...Have now dropped into a shell in the initramfs." Then it hit me, I needed to cpio the initrd, fix the boot_specs and then all was fine booting up the ISO. Thought maybe the ISO got past this BOOT_SPEC messing around and/or having the restriction of having to be in a booted Easy install to manipulate it. I think a lot of other who run "frugal" are going to fall victim to this, and then, once again, turn away because of the restrictions (not me, I don't mind it, but others will...).
A thought just occurred to me. The BOOT_SPECS file in the CD looks for BOOT_DISKID='0xf95ae985', which can confirm is correct:BarryK wrote:The CD boots up and runs in ram, there should not be any error about missing boot drive.belham2 wrote:Hi Barry & everyone,
Thanks, Barry, for this latest release. Made the mistake of burning the ISO immediately after download, and then wondering why it wouldn't boot on any machine of mine (laptop and/or desktop, kept throwing "Finding Drives....Creating compressed zram.....sda sr0 written 20 times)...then..ERROR:Boot drive not found...Have now dropped into a shell in the initramfs." Then it hit me, I needed to cpio the initrd, fix the boot_specs and then all was fine booting up the ISO. Thought maybe the ISO got past this BOOT_SPEC messing around and/or having the restriction of having to be in a booted Easy install to manipulate it. I think a lot of other who run "frugal" are going to fall victim to this, and then, once again, turn away because of the restrictions (not me, I don't mind it, but others will...).
In other words, you downloaded the iso, burnt it to CD, booted, and it should work. It defaults to looking for /dev/sr* with iso9660 filesystem and that is the boot drive.
You had me worried for a moment there. Just checked on the Compaq Presario, booted the CD, it found sr0 as the boot-drive and zram0 as working-partition.
It is a bit slow at first bootup, as copies easy.sfs off the CD to zram, but gets to desktop OK. Reminds me just how incredibly slow data transfer is from CDs.
Code: Select all
# fdisk -l /dev/sr0
Disk /dev/sr0: 425.3 MiB, 445952000 bytes, 217750 sectors
Units: sectors of 1 * 2048 = 2048 bytes
Sector size (logical/physical): 2048 bytes / 2048 bytes
I/O size (minimum/optimal): 2048 bytes / 2048 bytes
Disklabel type: dos
Disk identifier: 0xf95ae985
Device Boot Start End Sectors Size Id Type
/dev/sr0p1 * 0 870399 870400 1.7G 0 Empty
/dev/sr0p2 224 24799 24576 48M ef EFI (FAT-12/16/32)
Code: Select all
Disk /dev/sr0: 425 MiB, 445644800 bytes, 217600 sectors
Units: sectors of 1 * 2048 = 2048 bytes
Sector size (logical/physical): 2048 bytes / 2048 bytes
I/O size (minimum/optimal): 2048 bytes / 2048 bytes
Disklabel type: dos
Disk identifier: 0xf95ae985
Device Boot Start End Sectors Size Id Type
/dev/sr0p1 * 0 870399 870400 1.7G 0 Empty
/dev/sr0p2 224 24799 24576 48M ef EFI (FAT-12/16/32)
#
Code: Select all
Disk /dev/sr0: 425 MiB, 445644800 bytes, 217600 sectors
Units: sectors of 1 * 2048 = 2048 bytes
Sector size (logical/physical): 2048 bytes / 2048 bytes
I/O size (minimum/optimal): 2048 bytes / 2048 bytes
Disklabel type: dos
Disk identifier: 0xf95ae985
Device Boot Start End Sectors Size Id Type
/dev/sr0p1 * 0 870399 870400 1.7G 0 Empty
/dev/sr0p2 224 24799 24576 48M ef EFI (FAT-12/16/32)
#
Code: Select all
a062d7cb25163c404bb2ba9528a83683 boot.cat
bf5d542ecc91a7148681b20c8302b9fe boot.msg
a4cab410601141a4d593e8850b4d7706 easy.sfs
189b1b39a15fced246310ce684602488 efiboot.img
e1a8baf0ec0dd106e5bc7dfc42361e2e help.msg
3cf726926145fa51d7054aba79f95104 initrd
8a35222196ca8ae9c26a98e355d82ad4 isolinux.bin
7350c35d8b68933e76a49f0a53862c95 isolinux.cfg
92b12a15eb2a2ac9ef561c0cdb8aa616 ldlinux.c32
37b0732672d89069cdf8426af6c0c25c logo.16
b5194a3d8533ceb605f67982bc3db7d9 vmlinuz
I mean, compared with after you create a usb working-partition. easy.sfs gets copied onto that, then copied from usb to ram at every bootup.Sage wrote:Not much difference between first run USB, which has to form part2, and CD which is always first run.Reminds me just how incredibly slow data transfer is from CDs
Yes, I also tested a burn to DVD-RW this morning, works fine.FeodorF wrote:DVD burn boots well over here. Posting of the live-DVD right now.
Putting Easy to the usb stick works too.
Mostly working with older kit, retired (or semi-) folk, ditto PCs, time is illusory! Sometimes USB is less reliable between differing HW (esp. video cards and wifi) when the stored material seems to be adjusting itself? With CD .iso always know and can see what's happening, pick up any quirks as the boot ploughs through its detection steps, etc., and leaves NO record at shutdown. Other CD attributes as discussed...I mean, compared with after you create a usb working-partition. easy.sfs gets copied onto that, then copied from usb to ram at every bootup.
With a good usb stick, that is very fast.