EasyOS Scarthgap-series version 6.6.3

[BarryK]

Version 6.6.3 released:

https://bkhome.org/news/202502/easyos-s ... eased.html

[tammi806]

I did the update / upgrade to 6.6.3 and everything I've used works without complaints.

Thanks @BarryK.

[TerryH]

Twice today when running an Easy Daedalus 6.5.1.1 container within Easy Scarthgap 6.6.3, I've been unable to flip out of the container. I have the flip icon in the tray. I clicked the flip icon and nothing happened. To check I navigated to the /usr/local/easy_containers directory, opened a terminal then ran ./flip-out-of-container, which also had no effect. On the first occasion, I left my laptop on and checked again a short while later and was able to flip out using the tray icon.

On the second occasion I went out for an hour, on return I was still unable to flip out of the container. There was nothing running at the time. I had to do a hard shutdown to get out.

On reboot I have since re-checked the Daedalus container and also the other containers without issue.

[measter]

I've installed 6.6.3 to an 8G USB on a legacy bios desktop and booted. Besides its usb sticks, it has a usb attached external hdd spinner just for storage, no booting, a bootable ntfs Win7 internal hdd spinner, an ext4 internal SATA SSD w/ a LM Cinnamon install with plenty of room left and an optical I actually use as a plop boot manager (his newest PBM6) because of some trouble booting the LM trying to use the desktop's bios boot manager, which story I don't want to get into here. I usually boot various linux distro/s on a Ventoy stick, and one of those is a current MX which I've configured for frugal persistence which it saves to a linux formatted dir on the Win7's hdd, resembling the old Puppy days, occasionally the Win7 for something.

I was expecting to be able to easily do a save as a frugal install persistence from the Easy into a folder on the ext4 SSD LM single partition because it is already ext4, but I'm not yet reading how to do it as simply as I was expecting from the collection of Easy docs about installing to hdd. My preference would be to do it like I used to do w/ Puppy; to boot Puppy (now Easy) from a *USB*, not the hdd, but then go/save into the frugal persistence dir on the SSD, but I don't seem to be finding those specific instructions.

Could someone give me some guidance for that please? Thanks; great distro. The only foreign 'app' I've installed so far is an xkbset.deb so I can have sticky keys, which works just fine.

[n00b]

I've installed 6.6.3 to an 8G USB on a legacy bios desktop and booted. Besides its usb sticks, it has a usb attached external hdd spinner just for storage, no booting, a bootable ntfs Win7 internal hdd spinner, an ext4 internal SATA SSD w/ a LM Cinnamon install with plenty of room left and an optical I actually use as a plop boot manager (his newest PBM6) because of some trouble booting the LM trying to use the desktop's bios boot manager, which story I don't want to get into here. I usually boot various linux distro/s on a Ventoy stick, and one of those is a current MX which I've configured for frugal persistence which it saves to a linux formatted dir on the Win7's hdd, resembling the old Puppy days, occasionally the Win7 for something.

I was expecting to be able to easily do a save as a frugal install persistence from the Easy into a folder on the ext4 SSD LM single partition because it is already ext4, but I'm not yet reading how to do it as simply as I was expecting from the collection of Easy docs about installing to hdd. My preference would be to do it like I used to do w/ Puppy; to boot Puppy (now Easy) from a *USB*, not the hdd, but then go/save into the frugal persistence dir on the SSD, but I don't seem to be finding those specific instructions.

Could someone give me some guidance for that please? Thanks; great distro. The only foreign 'app' I've installed so far is an xkbset.deb so I can have sticky keys, which works just fine.

Install EasyOS on the SSD and create a grub menu entry for it on the Ventoy stick.

https://www.ventoy.net/en/plugin_grubmenu.html

[measter]

Install EasyOS on the SSD and create a grub menu entry for it on the Ventoy stick.

https://www.ventoy.net/en/plugin_grubmenu.html

Thanks for your help. My experience w/ the Ventoy plugins in the past are the plugson and persistence. i'm struggling w/ trying to learn how to make the grub2.cfg file; I don't really find the ventoy example above particularly useful.

i've read the Arch wiki about grub2.cfg, but i still don't really get it.

What i've done so far is to create a Easy66 dir on the / of the ext4 LM Cinnamon install and put the 3 files from the Easy .img into it. if I were creating a path to a file in that dir, which would it be? Because I don't really understand Easy's layered filesystem properly i'm not clear on why i take the files out of their .img package.

After I had placed those 3 files, I tho't I might try the F4 option in Ventoy's default menu, but that didn't seem to give me the navigation I needed to get to the Easy66 dir in the SSD.

[measter]

What i've done so far is to create a Easy66 dir on the / of the ext4 LM Cinnamon install and put the 3 files from the Easy .img into it.

Now i've found something else to wonder about. Right now I'm in Easy and I'm noticing that its menu has a "Limine bootloader installer", so I'm wondering if there isn't some .cfg type file I could modify to boot from the Easy in the SSD instead of the Easy on the USB stick.

That is, instead of employing Ventoy to get to the SSD Easy66, I would employ the Easy USB to do it.

[pp4mnklinux]

Just updated from 5.5.4

Testing, but till now it works nice.

Thanks a lot for your work.

[FeodorF]

Hello @measter

What i've done so far is to create a Easy66 dir on the / of the ext4 LM Cinnamon install and put the 3 files from the Easy .img into it.

Now i've found something else to wonder about. Right now I'm in Easy and I'm noticing that its menu has a "Limine bootloader installer", so I'm wondering if there isn't some .cfg type file I could modify to boot from the Easy in the SSD instead of the Easy on the USB stick.

That is, instead of employing Ventoy to get to the SSD Easy66, I would employ the Easy USB to do it.

The reason you'll find the Limine 7.12.0 boot loader is that it has the ability to boot straight into an ext4 partition as well as being able to boot old PC systems with BIOS (pre 2012) and new PC systems (>2012).

In order to boot into your SSD drive you'll have to add a new entry to the limine.cfg file. Make sure you add the uuid of your SSD drive there. And as well change the '-6-6-x' to the version number that you are using on your system.

Code: Select all

:EasyOS Scarthgap-6-6-x
    COMMENT=EasyOS Scarthgap-6.6.x bootup
    RESOLUTION=800x600
    PROTOCOL=linux
    KERNEL_PATH=uuid://7920b1e6-ddf4-11ef-9ab3-a4ae11162368/Easy66/vmlinuz
    MODULE_PATH=uuid://7920b1e6-ddf4-11ef-9ab3-a4ae11162368/Easy66/initrd
    KERNEL_CMDLINE=rw wkg_uuid=7920b1e6-ddf4-11ef-9ab3-a4ae11162368 wkg_dir=Easy66/easyos/ intel_iommu=igfx_off

[measter]

In order to boot into your SSD drive you'll have to add a new entry to the limine.cfg file. Make sure you add the uuid of your SSD drive there. And as well change the '-6-6-x' to the version number that you are using on your system.

Code: Select all

:EasyOS Scarthgap-6-6-x
    COMMENT=EasyOS Scarthgap-6.6.x bootup
    RESOLUTION=800x600
    PROTOCOL=linux
    KERNEL_PATH=uuid://7920b1e6-ddf4-11ef-9ab3-a4ae11162368/Easy66/vmlinuz
    MODULE_PATH=uuid://7920b1e6-ddf4-11ef-9ab3-a4ae11162368/Easy66/initrd
    KERNEL_CMDLINE=rw wkg_uuid=7920b1e6-ddf4-11ef-9ab3-a4ae11162368 wkg_dir=easyos/ intel_iommu=igfx_off

Thank you for your input. I'm on unfamiliar ground here, so I could use some more help.

I'm able to find some limine 'stuff' in user/bin and usr/share but not a limine.cfg. I don't know how to do it.

[measter]

I'm able to find some limine 'stuff' in user/bin and usr/share but not a limine.cfg. I don't know how to do it.

And my boot dir is empty; I don't understand that.

[measter]

I'm able to find some limine 'stuff' in user/bin and usr/share but not a limine.cfg. I don't know how to do it.

And my boot dir is empty; I don't understand that.

[n00b]

Install EasyOS on the SSD and create a grub menu entry for it on the Ventoy stick.

https://www.ventoy.net/en/plugin_grubmenu.html

Thanks for your help. My experience w/ the Ventoy plugins in the past are the plugson and persistence. i'm struggling w/ trying to learn how to make the grub2.cfg file; I don't really find the ventoy example above particularly useful.

i've read the Arch wiki about grub2.cfg, but i still don't really get it.

What i've done so far is to create a Easy66 dir on the / of the ext4 LM Cinnamon install and put the 3 files from the Easy .img into it. if I were creating a path to a file in that dir, which would it be? Because I don't really understand Easy's layered filesystem properly i'm not clear on why i take the files out of their .img package.

After I had placed those 3 files, I tho't I might try the F4 option in Ventoy's default menu, but that didn't seem to give me the navigation I needed to get to the Easy66 dir in the SSD.

Write your menu and grub2 commands in a cfg file ventoy_grub.cfg under ventoy directory in the first partition, that is /ventoy/ventoy_grub.cfg and that's all.
Press F6 to load the customized menu when in Ventoy's boot menu.

https://easyos.org/install/easy-frugal- ... ation.html

menuentry "EasyOS" {
insmod ext2
insmod search_fs_uuid
search --no-floppy --fs-uuid --set=root 054a04b8-0f00-11ed-aeb9-287fcfeb4376
linux /Easy66/vmlinuz rw wkg_uuid=054a04b8-0f00-11ed-aeb9-287fcfeb4376 wkg_dir=Easy66
initrd /Easy66/initrd
}

That UUID value can be found by running the 'blkid' utility, for the example of EasyOS installed in partition /dev/sda3, with partition-label "easy2":

# blkid /dev/sda3
/dev/sda3: LABEL="easy2" UUID="054a04b8-0f00-11ed-aeb9-287fcfeb4376" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="a3976784-02"

Or Limine menu entry for EasyOS stick:

limine.cfg is on the first partition of the stick (boot partition)

:EasyOS Scarthgap-6-6-x
COMMENT=EasyOS Scarthgap-6.6.x bootup
RESOLUTION=800x600
PROTOCOL=linux
KERNEL_PATH=uuid://7920b1e6-ddf4-11ef-9ab3-a4ae11162368/Easy66/vmlinuz
MODULE_PATH=uuid://7920b1e6-ddf4-11ef-9ab3-a4ae11162368/Easy66/initrd
KERNEL_CMDLINE=rw wkg_uuid=7920b1e6-ddf4-11ef-9ab3-a4ae11162368 wkg_dir=Easy66/ intel_iommu=igfx_off

[measter]

Write your menu and grub2 commands in a cfg file ventoy_grub.cfg under ventoy directory in the first partition, that is /ventoy/ventoy_grub.cfg and that's all.
Press F6 to load the customized menu when in Ventoy's boot menu.

https://easyos.org/install/easy-frugal- ... ation.html

menuentry "EasyOS" {
insmod ext2
insmod search_fs_uuid
search --no-floppy --fs-uuid --set=root 054a04b8-0f00-11ed-aeb9-287fcfeb4376
linux /Easy66/vmlinuz rw wkg_uuid=054a04b8-0f00-11ed-aeb9-287fcfeb4376 wkg_dir=Easy66
initrd /Easy66/initrd
}

That UUID value can be found by running the 'blkid' utility, for the example of EasyOS installed in partition /dev/sda3, with partition-label "easy2":

# blkid /dev/sda3
/dev/sda3: LABEL="easy2" UUID="054a04b8-0f00-11ed-aeb9-287fcfeb4376" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="a3976784-02"

Thank you for your detailed and helpful instructions. What I've done: booted into usb easy to write the file. Previously I had written the 3 Easy files to Easy66 on the LMcinn ext4 part of the sata ssd. Next I used your instructions about blkid, uuid, and the example ventoy_grub.cfg to put that into the ventoy dir on a ventoy stick. That particular ventoy had not had a ventoy dir before, but I did have a ventoy dir on some previous ventoy project stick.

Unfortunately, the F6 from the basic Ventoy menu did not contain the Easy OS entry. However, I was able to use the Ventoy F2 browse function and see lots of disks incl what was the LMcinn, and when selected the Easy66 dir was visible, but selection and entry made some progress, but it didn't boot.

After I submit this from another system than Easy, I'll go back to that and paste in my ventoy_grub.cfg. I have some concerns about whether or not some lines end w/ return/newline.

[measter]

After I submit this from another system than Easy, I'll go back to that and paste in my ventoy_grub.cfg. I have some concerns about whether or not some lines end w/ return/newline.

menuentry "EasyOS"
insmod ext2 ext4
insmod search_fs_uuid search --nofloppy --fs-uuid --set=root 13dc283d-9553-482e-bb6c-477baa1fd54e
linux /Easy66/vmlinux rw wkg_uuid=13dc283d-9553-482e-bb6c-477baa1fd54e wkgdir=Easy66
initrd /Easy66/initrd

[measter]

menuentry "EasyOS"
insmod ext2 ext4
insmod search_fs_uuid search --nofloppy --fs-uuid --set=root 13dc283d-9553-482e-bb6c-477baa1fd54e
linux /Easy66/vmlinux rw wkg_uuid=13dc283d-9553-482e-bb6c-477baa1fd54e wkgdir=Easy66
initrd /Easy66/initrd

I fixed the condition of not starting the search line on a new line and tried again, but F6 still didn't show the Easy.

search --nofloppy --fs-uuid --set=root 13dc283d-9553-482e-bb6c-477baa1fd54e

[n00b]

menuentry "EasyOS"
insmod ext2 ext4
insmod search_fs_uuid search --nofloppy --fs-uuid --set=root 13dc283d-9553-482e-bb6c-477baa1fd54e
linux /Easy66/vmlinux rw wkg_uuid=13dc283d-9553-482e-bb6c-477baa1fd54e wkgdir=Easy66
initrd /Easy66/initrd

I fixed the condition of not starting the search line on a new line and tried again, but F6 still didn't show the Easy.

search --nofloppy --fs-uuid --set=root 13dc283d-9553-482e-bb6c-477baa1fd54e

Grub menu entry doesn't work without curly braces.

Code: Select all

menuentry "EasyOS" {
insmod ext2
insmod search_fs_uuid
search --no-floppy --fs-uuid --set=root 13dc283d-9553-482e-bb6c-477baa1fd54e
linux /Easy66/vmlinuz rw wkg_uuid=13dc283d-9553-482e-bb6c-477baa1fd54e wkg_dir=Easy66
initrd /Easy66/initrd
}

[measter]

Or Limine menu entry for EasyOS stick:

limine.cfg is on the first partition of the stick (boot partition)

:EasyOS Scarthgap-6-6-x
COMMENT=EasyOS Scarthgap-6.6.x bootup
RESOLUTION=800x600
PROTOCOL=linux
KERNEL_PATH=uuid://7920b1e6-ddf4-11ef-9ab3-a4ae11162368/Easy66/vmlinuz
MODULE_PATH=uuid://7920b1e6-ddf4-11ef-9ab3-a4ae11162368/Easy66/initrd
KERNEL_CMDLINE=rw wkg_uuid=7920b1e6-ddf4-11ef-9ab3-a4ae11162368 wkg_dir=Easy66/ intel_iommu=igfx_off

When I look at the Easy usb from another dev, it does not have the dir structure I see when I boot in Easy.

Booting from another dev, the Easy stick has two part/s, a 7 meg fat16 and the rest of the usb is ext4. The first little part has the boot flag and an esp flag for EFI. When I'm examining that stick from another dev, I cannot access the little part w/ the boot flag, which on the current config is called /dev/sde2 whereas the boot part is /dev/sde1 and is not accessible by my tools.

When I boot in Easy, the dir structure shows me a Boot *directory* (not partition) and that is where I put the above limine.cfg file.

That does not give me access to booting Easy on the LMcinn sata ssd, but the boot manager just gives me the usb Easy.

[measter]

Grub menu entry doesn't work without curly braces.

Doh! Fixed.

Now I get Ventoy 'transition' to the EasyOS menu item, but then errors:

error: no such device --nofloppy
error: file '/Eas66/vmlinux' not found
error: you need to load the kernel first

And no boot

[measter]

Now I get Ventoy 'transition' to the EasyOS menu item, but then errors:

error: no such device --nofloppy
error: file '/Eas66/vmlinux' not found
error: you need to load the kernel first

And no boot

Oops. vmlinux above corrected to vmlinuz, but now the same errors w/ vmlinux>vmlinz.

[measter]

And no boot

Progress. More corrections of the ventoy grub cfg file and an advance in the progress of the boot before it failed. It was working toward the Easy of the sata ssd, but it didn't work out/ find it properly.

It got to: working partition sdb1, but it wasn't finding what it wanted; it was looking for paths that 'didn't exist':
stat: can't stat '/mnt/sdb1/releases/easy-6.6.3/easy.sfs'

... whereas to my way of thinking, it should be looking in /sdb1/Easy66

[n00b]

And no boot

Progress. More corrections of the ventoy grub cfg file and an advance in the progress of the boot before it failed. It was working toward the Easy of the sata ssd, but it didn't work out/ find it properly.

It got to: working partition sdb1, but it wasn't finding what it wanted; it was looking for paths that 'didn't exist':
stat: can't stat '/mnt/sdb1/releases/easy-6.6.3/easy.sfs'

... whereas to my way of thinking, it should be looking in /sdb1/Easy66

Delete the Easy66 folder and recreate it (with the files easy.sfs vmlinuz and initrd). Use exactly this menu entry:

Code: Select all

menuentry "EasyOS" {
insmod ext2
insmod search_fs_uuid
search --no-floppy --fs-uuid --set=root 13dc283d-9553-482e-bb6c-477baa1fd54e
linux /Easy66/vmlinuz rw wkg_uuid=13dc283d-9553-482e-bb6c-477baa1fd54e wkg_dir=Easy66
initrd /Easy66/initrd
}

[measter]

Delete the Easy66 folder and recreate it (with the files easy.sfs vmlinuz and initrd). Use exactly this menu entry:

Code: Select all

menuentry "EasyOS" {
insmod ext2
insmod search_fs_uuid
search --no-floppy --fs-uuid --set=root 13dc283d-9553-482e-bb6c-477baa1fd54e
linux /Easy66/vmlinuz rw wkg_uuid=13dc283d-9553-482e-bb6c-477baa1fd54e wkg_dir=Easy66
initrd /Easy66/initrd
}

Thank you for your extraordinary patience.

The short form is: Done and done and successful boot of Easy on the ssd. There is a longer form about my confusion that I hesitate to express, but I will as part of my trying to understand this system better. Basically I have two problems, not fully properly grasping how Easy is put together, which I can continue to work out on my own by experiencing, and some kind of trouble I have w/ the accessibility of the sata ssd. I'll try to not drag this thread into anything that doesn't have anything to do w/ Easy, except to mention confusion overlapping Easy.

That sata ssd doesn't behave for me like a normal drive. When I access it from say a USB, I can't delete or copy files or dir/s there w/o elevating my privleges. When I handle the Easy .img file to 'open' it to copy its contents, I actually *mount* it, and then it looks like a dir structure of easy os containing the 3 files. If I open that dir and copy the files and paste them into the Easy66 dir, they may 'show up' as the .img depending on how I'm viewing

[measter]

The short form is: Done and done and successful boot of Easy on the ssd.

That sata ssd doesn't behave for me like a normal drive.

This departs from Easy, except to say that Easy doesn't perform as I would expect on the ssd. The quick start settings aren't saved; the only thing that is saved is what is saved in the files dir.

I'll add some non-Easy things to add to some ssd things I said before. My bios has a boot menu, it does not handle the ssd properly, which cannot be selected for a boot by the bios boot manager; instead I have to use a Plop boot manager to be able to boot from the LMcinn I installed there recently.

Now the LMcinn install isn't performing properly. When I get to the boot login (via the Plop cdrom bm) now (not previously) my pw seems to be accepted, but the manager just 'loops' back to requiring pw. It does not announce bad pw,. it just doesn't boot, requesting pw for that user again. And again.

I realize that this isn't really about Easy, except for how the ssd problem manifests itself in easy, causing it to perform as if it were NOT an ssd, but like an unwritable usb, which is the way it acts on the usb.

[measter]

I realize that this isn't really about Easy, except for how the ssd problem manifests itself in easy, causing it to perform as if it were NOT an ssd, but like a mostly unwritable usb, which is the way it acts on the usb.

I should take this discussion somewhere else because except for the Easy part, the problem which is hardware related is broader than the Easy part of the issue. The HP Compaq 6005 Pro SFF 'legacy bios' desktop's mobo has 4 sata connections 0-3. As I recall (I'm going to recheck this soon), conventional hdd to 0, ssd to 1, optical to 2, and 3 is empty. I was able to check via the bios w/o having to open the case; the preceding is incorrect: Win7 install conventional hdd #0, cdrom #1, LMcinn install #2, #3 empty (manual advises #3 can be eSATA.)

Also, most recently, my install of LMcinn on that sata ssd isn't behaving normally; when I boot up and get to the graphical login, the pw seems to be accepted, but the login just loops back to requesting the pw and I haven't logged in, Previously it worked fine for a few days.

The bios boot menu does not show any hdd except Win, the older Plop bm can't find a boot on any non-USB devices except the Win, the newer Plop PBM6 on optical can boot from the LMcinn as well as the Win and bootable USBs.

[measter]

my install of LMcinn on that sata ssd isn't behaving normally;

I have a degree of progress wlith some reconfiguration of the ssd.

To reiterate, my desktop legacy bios boot menu cannot display the ssd in the boot menu, altho' the bios can see everything about the ssd in its setup 'dash', but its boot order control can NOT independently 'handle' the ssd, it is 'lumped' w/ the ssd in that part of the bios. Consequently I use a Plop PBM6 optical boot manager to be able to boot from the ssd. I have now partitioned the ssd and resinstalled LM to the 1st partition. I'm working on getting a frugal install of Easy with the 2nd partition. In the past when I put the Easy files on the same partition with LM that caused boot problems - too long an unexplained story.

There is an 'anomaly' about booting the LM using the PBM6, namely it doesn't 'naturally' go thru' a grub menu, straight from PBM6 to the LM desktop. I have modified the grub.d/40_custom menu of LM as suggested in BK's frugal install and have installed the 3 easy files to a easyos dir on the non-LM ssd part.

Since I don't /get/ a grub2 menu booting the LM, I use the escape key during the boot to get a 'different looking' grub which has the Easy OS entry to try to boot into the frugal, BUT... something goes 'whacky' w/ the graphic during that boot; I'm thinking the boot parameter needs some mod such as for at least 800x600 gfx because the boot can't 'make it' w/ a graphic disruption and seems to crash back to a hard restart/reboot which precedes even the PBM6 boot.

Currently I'm working on graphic boot parameter experiments.

[measter]

Since I don't /get/ a grub2 menu booting the LM, I use the escape key during the boot to get a 'different looking' grub which has the Easy OS entry to try to boot into the frugal, BUT... something goes 'whacky' w/ the graphic during that boot; I'm thinking the boot parameter needs some mod such as for at least 800x600 gfx because the boot can't 'make it' w/ a graphic disruption and seems to crash back to a hard restart/reboot which precedes even the PBM6 boot.

Currently I'm working on graphic boot parameter experiments.

Nope. Eliminated the whacky graphics w/ 800x600, but the booting crashed the same anyway. I guess the easyos dir isn't working out, or maybe it/grub can't even find it because the ssd's accessibility is funky.

My earliest plan was to install Ventoy to the ssd; it won't install on a part, but it allegedly can install on the whole disk and then the disk can be parted, but my first attempts to do that couldn't get Ventoy on the ssd to boot; sticks at blinking cursor.

[measter]

Back to a previous attempt via Ventoy. Corrected the changes from the ventoy grub cfg, different uuid, different dir name.

Boot failed w/ a lot of errors which scrolled off-screen. The last developer one was:
Line 2112:Failed to mount easy.sfs

I suspect that is because some conditions change the accessibility to the ssd, apparently in 'mid-operation' going from accessible to inaccessible.

[measter]

Back to a previous attempt via Ventoy. Corrected the changes from the ventoy grub cfg, different uuid, different dir name.

Boot failed w/ a lot of errors which scrolled off-screen. The last developer one was:
Line 2112:Failed to mount easy.sfs

The string of errors was all about 'cp can't preserve ownership .... ' related to the .sfs.

I have tried to fix an ownership/permissions condition of the easyos dir which contains the 3 files by using a chmod -R 777 on the dir w/ the files in it, but that still results in a condition of the files belonging to some kind of group mike, which I don't know about. I tho't 777 was supposed to be 'everyone'; I don't know how to do that.

[measter]

The string of errors was all about 'cp can't preserve ownership .... ' related to the .sfs.

Code: Select all

mike@Compaq:/media/mike/F7FF-FDC2$ sudo chown -R nobody easyos
[sudo] password for mike:      
chown: changing ownership of 'easyos/vmlinuz': Operation not permitted
chown: changing ownership of 'easyos/initrd': Operation not permitted
chown: changing ownership of 'easyos/easy.sfs': Operation not permitted
chown: changing ownership of 'easyos': Operation not permitted