FatdogArm Beta1/2/3/4- 16 April 2016

[jamesbond]

the method BerryBoot uses is copied on page 14 of this thread,
http://www.murga-linux.com/puppy/viewto ... 158#864158

That initscript does not use aufs and is meant for full install. FatdogArm is frugal install.

[mories]

Yes, beta3 and beta4 has changed in the way it gets the IP address. I tried to make it more resistant and able to handle roaming, but apparently there are race issues. The issue seems familiar to Fatdog64 - but your dmesg output is a bit different. Which board is this, raspi2?

The board is Raspi2, and the wireless:
Bus 001 Device 004: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
what use 8192cu kernel module.

That initscript does not use aufs and is meant for full install. FatdogArm is frugal install.

The init script of berryboot use aufs, you can see it at lines

Code: Select all

   for initfile in sbin/init usr/lib/systemd/systemd lib/systemd/systemd init
   do
      if [ -e $initfile ]; then
         echo Mounting RW data directory on top
         mount -t aufs -o br:${DATADIR}:${SHAREDDIR}:/squashfs none /aufs
         cd /aufs
         mount -o move /dev dev
         mount -o move /sys sys
         mount -o move /proc proc
         echo Setting CPU governor to $GOVERNOR
         echo "$GOVERNOR" > sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
         echo Starting operating system ${IMAGE}...
         exec switch_root . $initfile
      fi
   done

DATADIR=save directory
SHAREDDIR=/lib/modules
/squashfs=base sfs

[Ted Dog]

Yep.. BerryBoot does install kinda, but with FatDogs more advanced layering methods, we shouldn't have to 'install' BerryBoot makes an example that with a shared kernel and basic layering then almost all Raspberry Pis Distros can be switched 'AFTER BOOTING' and AFTER a GUI is on screen.
So leverage all the tools ( hopefully add kpartx ) we should be able to duplicate BerryBoot idea into a BETTER no install ( copy only method to Fat32-type generic SDcard ) and download/modify and ~boot~ into new Distro as a layer 'OVER/NEXT/???' FatDogArm.

Also could not get expand to work, and multisession save dialog still has FatDog64 and DVD full messages here is my cmdline.txt

Code: Select all

smsc95xx.turbo_mode=N elevator=deadline loglevel=3 basesfs=local savefile=direct:multi:sda3 base2ram=expand

[Ted Dog]

oh reread the copy to RAM post above/before this and you did not say expand <I read that into it> did get me all excited to see what bare-metal RaspPi2B could do... oh well I'll just move file to usb harddrive.
Is save to folder in this version??

[Ted Dog]

not wanting to dominate this thread.. FatBERRYboot thread
http://www.murga-linux.com/puppy/viewto ... 694#897694

[Ted Dog]

sound does work but playback not fast enough with most basic videos I could locate

[don570]

I'm researching making images of a sdcard in Windows XP.

Here are two references:

The windows version of testdisk program
http://www.cgsecurity.org/wiki/Image_Creation


Windows version of dd
http://www.chrysocome.net/dd

____________________________________________________

[don570]

don570 wrote:
Would it be possible to use a sdcard entirely formatted as fat32.
Then boot up entirely in RAM like most users of BarryK 's Puppy linux.

If this was possible then the fatdog arm distro could be easier to install.
Possible. I have not tested it (XU4 chugging along doing something now), but you can use base2ram=yes just like Fatdog64.

I worked on this project today and I can report that it can be done!!

Here's how I did it.
Step 1: I installed fatdog arm the usual way using berryboot and then dragging
the 3 files. ---> initrd.rpi2 vmlinuz.rpi2 fd-arm.sfs
Make a save file on partition 1.
Partition 1 is only about 150 mb which is not big enough to be useful.

Step 2: move over to a linux computer and use the program pmirror
to make a storage folder of partition 1 files.

Step3: Now that these files are safe on my linux computer I can proceed to
re-format the sdcard as I wish with gparted. I made a 500mb fat32 partition and the
rest of my card was unformatted.

Step4: I used pmirror to copy the files back to the fat32 partition.

Step5: I made the appropriate change to the cmdline.txt file
so the SFS files would be recognized on the first partition.

Step 6 : booted up raspberry pi computer and I now had about 130mb
space left to store documents.


i am now working on making an image of the 500 mb fat32 partition
to see if it is worth posting for others users.
However Barry Kauler's pudd program doesn't seem to like the
unallocated space on my 16 gig sd card.
so I may have to partition the whole card as fat32.

In that case i will have to be careful to zero out the sdcard when I
fourmat it as 16gig fat32 so it will compress nicely.

______________________________________________________
_______________________________________________________

[Ted Dog]

Can I make a point DON.. you prove it could be done & so have I and even move various RaspberryPi Distros into subdirectory to keep rewrites down, I currently have 5 other Distros ( 1 FatDog64 with EFI boot, 2 FatDogArm versions for Mele1000, RaspBerry Mate, Kodi, and this ) on one Fat32 that is 2Gs, then you go BACKWARDS into image file methods. Just copy those files to a zip or into a different harddrive and that is all anyone needs.
Maybe you are already there and do not trust it can be SO easy, why does the rest of linux world love disk image files? they are a pain.
I have been doing this almost a year, with same SDcard & its Adapter

[jamesbond]

beta4 sfs re-uploaded.
1. Add ntfs-3g, wireless-tools (iwconfig etc), mdadm and dosfstools to basesfs as per mories' request.
2. (hopefully) fix the network dhcp issue.

[mories]

beta4 sfs re-uploaded.
1. Add ntfs-3g, wireless-tools (iwconfig etc), mdadm and dosfstools to basesfs as per mories' request.
2. (hopefully) fix the network dhcp issue.

1. Thanks for the effort to make basesfs more autonomous. That result in a easier integration with tools like Berryboot.
Still I miss dropbear.
It would also be necessary some minor modifications in rc.sysinit:
- Create /dev/pts and /dev/shm (if no exist)
- Create /etc/BOOTSTATE (if no exist) only with the information of AUFS_ROOT_ID

2. Unfortunately dhcp issue continues to fail several times on my RPi2.

[don570]

To Ted Dog..

Maybe you are already there and do not trust it can be SO easy, why does the rest of linux world love disk image files? they are a pain.

Yes .. I realised late night that the ideal way to distribute fatdog arm
is the same way the berryboot OS is distributed i.e.

instruct people to format the SD card as fat32 and then drag the files to
the card from a mounted archive. As long as there is no links fat32 is the ideal solution.
.... and all the linux links are inside the SFS files so they are safe.

_____________________________________________________

[jamesbond]

1. Thanks for the effort to make basesfs more autonomous. That result in a easier integration with tools like Berryboot.
Still I miss dropbear.

Does it have to be dropbear? The full openssh is already inside basesfs.

It would also be necessary some minor modifications in rc.sysinit:
- Create /dev/pts and /dev/shm (if no exist)

I'll make the changes.

- Create /etc/BOOTSTATE (if no exist) only with the information of AUFS_ROOT_ID

This information can only be reliably given by initrd. You can do this after the fact too if you know that the system does in fact use stackable filesystem, but this is installation-specific; so you should do it in rc.local instead. Here is the code:

Code: Select all

AUFS_ROOT_ID=$(
awk '{ if ($2 == "/" && $3 == "aufs") { match($4,/si=[0-9a-f]*/); print "si_" substr($4,RSTART+3,RLENGTH-3) } }' /proc/mounts
)

EDIT: I'll add this line in rc.local, commented out, you can uncomment it as needed.

EDIT: beta4 re-uploaded with the above two changes.

2. Unfortunately dhcp issue continues to fail several times on my RPi2.

You need to remove the existing "ip address configuration" and re-create it again.

[mories]

You need to remove the existing "ip address configuration" and re-create it again.

ok, erasing the previous configuration and creating the new (now I see uses udhcpc instead of dhcpcd) now seems to work correctly every time.
Note: with the newest basesfs seems sometimes fail again

Does it have to be dropbear? The full openssh is already inside basesfs.

Ah OK, but nevertheless in Control Panel->System->Manage Servers and Services you use dropbear and no sshd
Should it be changed that element?

Create /etc/BOOTSTATE (if no exist) only with the information of AUFS_ROOT_ID
This information can only be reliably given by initrd. You can do this after the fact too if you know that the system does in fact use stackable filesystem, but this is installation-specific; so you should do it in rc.local instead.

But /etc/BOOTSTATE is needed at the beginning of rc.sysinit, and information in AUFS_ROOT_ID is used by
# Load Extra sfs
/sbin/load_sfs.sh start
So I would propose something like

Code: Select all

echo AUFS_ROOT_ID=$(ls -1 /sys/fs/aufs/) >> /etc/BOOTSTATE

before including /etc/BOOTSTATE in rc.sysinit

[jamesbond]

ok, erasing the previous configuration and creating the new (now I see uses udhcpc instead of dhcpcd) now seems to work correctly every time.
Note: with the newest basesfs seems sometimes fail again

Try this: wpa_cli disconnect; followed by wpa_cli reconnect. Do you get anything?

Ah OK, but nevertheless in Control Panel->System->Manage Servers and Services you use dropbear and no sshd

Because I haven't written the initscript
EDIT: I have now written the initscript.

But /etc/BOOTSTATE is needed at the beginning of rc.sysinit, and information in AUFS_ROOT_ID is used by
# Load Extra sfs
/sbin/load_sfs.sh start
So I would propose something like

Code: Select all

echo AUFS_ROOT_ID=$(ls -1 /sys/fs/aufs/) >> /etc/BOOTSTATE

before including /etc/BOOTSTATE in rc.sysinit

Done.

EDIT: SFS updated.

[mories]

Congratulations, now your basesfs work properly in the 2 modes:
- native (with its own initrd)
- integrated within berryboot (using berryboot's initrd)

The script for the sshd service also works correctly

Now the wlan0 is working properly, if at any moment should occur again the problem will try wpa_cli commands and I will communicate you the result

[jamesbond]

Yay!

[don570]

Success ! I have made an archive that contains all the files needed for
fatdog arm

In Window XP ---> Just drag the files from the archive to a newly formated
SD card (fat32) and stick the card in the Raspberry Pi2 computer.

It's as simple as that
It has to be the world's simplest operating system.

Thanks to James and Kirk.

The size of zip archive is 300mb . I don't have the time to upload it to mydrive.ch.
Maybe next week. I've added lots of right click entries and additional software.

__________________________________________

Two negatives I noticed.

1) the tmp files aren't deleted between boots.
2) Opening html files with default browser is too difficult

_________________________________________________

[jamesbond]

Two negatives I noticed.
1) the tmp files aren't deleted between boots.

Files in /tmp deleted, since it is a tmpfs (memory-based) filesystems. If you're talking about "temporary files" (which can be any where, but usually lives in /var/tmp and /var/log in addition to /tmp), they are not deleted, because of https://en.wikipedia.org/wiki/Filesyste ... y_Standard. I only delete files in /var/lock{,s}, /var/run, and /var/cache. Anything else needs to be cleaned up manually. You can implement a script in rc.local to delete more files if you want to.

As a bonus if something bad happens the log files aren't automatically wiped out at next reboot; so you'll have the chance to examine them and try to figure out what went wrong.

2) Opening html files with default browser is too difficult

Is that because the browser often does not have access to the files you're trying to open? (you'll get blank pages in this case). Probably because of the spot thing. You can edit defaultbrowser and/or edit run-as-spot.

[don570]

You can implement a script in rc.local to delete more files if you want to.

I noticed that pfind temporary files weren't deleted.
I use pfind a lot so /tmp was loaded with them.
A startup script will delete them.

__________________________________________