Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sat 20 Jul 2019, 22:31
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
WeeDog Linux
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 2 [28 Posts]   Goto page: 1, 2 Next
Author Message
wiak

Joined: 11 Dec 2007
Posts: 1486
Location: not Bulgaria

PostPosted: Sat 04 May 2019, 23:55    Post subject:  WeeDog Linux  

Model 01 of WeeDog Linux (C) bootable distribution is available in the form of a FirstRib root_filesystem/initramfs, MIT licensed, buildscript system here, along with creation/boot details:

http://www.murga-linux.com/puppy/viewtopic.php?p=1031022#1031022

Best is to read the two very simple creation scripts which each contain less than 40 lines of actual shell code plus documentation/explanations in the forms of comments.

If anyone later runs into firmware/modules missing issues, also see here:

http://www.murga-linux.com/puppy/viewtopic.php?p=1031078#1031078

On first build, WeeDog is a commandline system, but users can add X functionality via its package manager (or specially configured/written firstrib00.plug).

Note that the FirstRib firstrib_rootfs can, as an alternative to independent booting, be used on its own via a chroot mechanism on any existing Linux host per the description at the first post of that FirstRib thread. WeeDog is the bootable version that has its own independent initramgs.gz/init to provide its functionality.

Various models of WeeDog are likely to be constructed, and based also on various FirstRIb flavours. This first flavour uses Void Linux package manager (xbps) and its associated package repositories.

Make sure you use the vmlinuz/initramfs.gz/firstrib_firmware_modules.sfs combination for the appropriate 32bit or 64bit scenario. The boot_partition must be a Linux formatted partition at this stage (but it's a frugal install so can share partition with other Pups/Dogs/etc). Also remember to delete any old upper_changes and work directories in <boot_partition>/firstrib/ when using a new build for the first time.

These are early WeeDog/FIrstRib development days so it should be considered experimental/draft for now, though it may well work reliably. Aside from using Void Linux package manager/repos (and optionally vmlinuz/firmware/modules from other distributions), FIrstRib-based WeeDog is an independent distribution. However, unlike many/most other even small independent distribution-build systems, FirstRib/WeeDog is purposively simple by design (to encourage active learning and system development by 'anyone' interested). It has its own independent initramfs/init boot script(s) and will always be developed along the lines of simple/short/easy-to-read-and-modify build scripts plus extra sfs and/or plugins.

This early model 01 uses overlayfs followed by a chroot mechanism inside a 'huge model' initramfs. Later model will employ a small initial initramfs followed by a switch_root to actual root filesystem.

wiak

_________________
Tiny Linux Blog: http://www.tinylinux.info/
Check Firmware: www.murga-linux.com/puppy/viewtopic.php?p=1022797
tinycore/slitaz: http://www.murga-linux.com/puppy/viewtopic.php?p=990130#990130

Last edited by wiak on Thu 27 Jun 2019, 22:34; edited 9 times in total
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1486
Location: not Bulgaria

PostPosted: Sat 04 May 2019, 23:55    Post subject:  

Reserved
_________________
Tiny Linux Blog: http://www.tinylinux.info/
Check Firmware: www.murga-linux.com/puppy/viewtopic.php?p=1022797
tinycore/slitaz: http://www.murga-linux.com/puppy/viewtopic.php?p=990130#990130
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1486
Location: not Bulgaria

PostPosted: Sat 04 May 2019, 23:56    Post subject:  

Reserved
_________________
Tiny Linux Blog: http://www.tinylinux.info/
Check Firmware: www.murga-linux.com/puppy/viewtopic.php?p=1022797
tinycore/slitaz: http://www.murga-linux.com/puppy/viewtopic.php?p=990130#990130
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1486
Location: not Bulgaria

PostPosted: Sat 04 May 2019, 23:56    Post subject:  

Reserved
_________________
Tiny Linux Blog: http://www.tinylinux.info/
Check Firmware: www.murga-linux.com/puppy/viewtopic.php?p=1022797
tinycore/slitaz: http://www.murga-linux.com/puppy/viewtopic.php?p=990130#990130
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1486
Location: not Bulgaria

PostPosted: Sat 04 May 2019, 23:56    Post subject:  

Reserved
_________________
Tiny Linux Blog: http://www.tinylinux.info/
Check Firmware: www.murga-linux.com/puppy/viewtopic.php?p=1022797
tinycore/slitaz: http://www.murga-linux.com/puppy/viewtopic.php?p=990130#990130
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1486
Location: not Bulgaria

PostPosted: Wed 26 Jun 2019, 23:29    Post subject:  

Model 01 of WeeDog Linux (C) bootable distribution is available in the form of a FirstRib root_filesystem/initramfs, MIT licensed, buildscript system here, along with creation/boot details:

http://www.murga-linux.com/puppy/viewtopic.php?p=1031022#1031022

Best is to read the two very simple creation scripts which each contain less than 40 lines of actual shell code plus documentation/explanations in the forms of comments.

On first build, WeeDog is a commandline system, but users can add X functionality via its package manager (or specially configured/written firstrib00.plug).

Note that the FirstRib firstrib_rootfs can, as an alternative to independent booting, be used on its own via a chroot mechanism on any existing Linux host per the description at the first post of that FirstRib thread. WeeDog is the bootable version that has its own independent initramgs.gz/init to provide its functionality.

Various models of WeeDog are likely to be constructed, and based also on various FirstRIb flavours. This first flavour uses Void Linux package manager (xbps) and its associated package repositories.

Make sure you use the vmlinuz/initramfs.gz/firstrib_firmware_modules.sfs combination for the appropriate 32bit or 64bit scenario. The boot_partition must be a Linux formatted partition at this stage (but it's a frugal install so can share partition with other Pups/Dogs/etc). Also remember to delete any old upper_changes and work directories in <boot_partition>/firstrib/ when using a new build for the first time.

These are early WeeDog/FIrstRib development days so it should be considered experimental/draft for now, though it may well work reliably. Aside from using Void Linux package manager/repos (and optionally vmlinuz/firmware/modules from other distributions), FIrstRib-based WeeDog is an independent distribution. However, unlike many/most other even small independent distribution-build systems, FirstRib/WeeDog is purposively simple by design (to encourage active learning and system development by 'anyone' interested). It has its own independent initramfs/init boot script(s) and will always be developed along the lines of simple/short/easy-to-read-and-modify build scripts plus extra sfs and/or plugins.

This early model 01 uses overlayfs followed by a chroot mechanism inside a 'huge model' initramfs. Later model will employ a small initial initramfs followed by a switch_root to actual root filesystem.

wiak

_________________
Tiny Linux Blog: http://www.tinylinux.info/
Check Firmware: www.murga-linux.com/puppy/viewtopic.php?p=1022797
tinycore/slitaz: http://www.murga-linux.com/puppy/viewtopic.php?p=990130#990130
Back to top
View user's profile Send private message 
fredx181


Joined: 11 Dec 2013
Posts: 3987
Location: holland

PostPosted: Thu 27 Jun 2019, 11:22    Post subject:  

Hi wiak, tested on 32-bit, not sure if I did things right, but trying to boot with grub4dos according to your instructions I get something like:
"chroot: failed to run setsid, no such file or directory"

I ran first : build_firstrib_rootfs_i686ver006.sh and worked fine, also installed: coreutils file mc and bash.
And then ran: "build_firstrib_initramfs01_ver006.sh sda5" and it went without errors.
and put the vmlinuz from bionicpup 32-bit and the created initramfs.gz in sda5/firstrib.
Grub4dos menu.lst entry:
Code:
title FirstRib (Void Linux Flavour) on sda5/firstrib
root (hd0,4)
kernel /firstrib/vmlinuz
initrd /firstrib/initramfs.gz


EDIT: Perhaps better to keep just one main thread, 3 threads containing links to each other may be a bit confusing for some (well, at least for me)

Fred

_________________
Dog Linux website
Tinylinux blog by wiak
Back to top
View user's profile Send private message 
rockedge


Joined: 11 Apr 2012
Posts: 1129
Location: Connecticut, United States

PostPosted: Thu 27 Jun 2019, 11:52    Post subject:  

Quote:
"chroot: failed to run setsid, no such file or directory"


I am seeing this since I have been messing with FirstRib and now when boot
an endless loop occurs until I ctrl-alt-del displaying the error
Back to top
View user's profile Send private message Visit poster's website 
fredx181


Joined: 11 Dec 2013
Posts: 3987
Location: holland

PostPosted: Thu 27 Jun 2019, 15:39    Post subject:  

Quote:
"chroot: failed to run setsid, no such file or directory"


Found out what was the problem, I had zdrv from older Bionicpup loaded, now works ok with zdrv and vmlinuz from newest Bionicpup: bionicpup32-8.0+7-uefi.iso (zdrv_upupbb_19.03.sfs renamed to firstrib_firmware_modules.sfs in firstrib folder).
Probably the loading of the correct firstrib_firmware_modules.sfs is essential to make overlayfs work properly Question

Next step is trying to get X working (and install a window-manager).

EDIT: Got ethernet working now, for me "modprobe tg3" was required to do first and then did "ifconfig eth0 up" and "udhcpc -i eth0"

Fred

_________________
Dog Linux website
Tinylinux blog by wiak
Back to top
View user's profile Send private message 
Keef


Joined: 20 Dec 2007
Posts: 966
Location: Staffordshire

PostPosted: Thu 27 Jun 2019, 16:16    Post subject:  

Code:
"chroot: failed to run setsid, no such file or directory"


I got the same error, but it was because I hadn't amended the script for my boot partition:

Code:
boot_partition="sda1"  # partition (sda1, sda2, sdb1 ... etc) where firstrib boot directory to be


Firstrib is on sda2.

Booted ok to prompt. Just a quick test to see if it worked.
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1486
Location: not Bulgaria

PostPosted: Thu 27 Jun 2019, 16:45    Post subject:  

fredx181 wrote:
Quote:
"chroot: failed to run setsid, no such file or directory"


Probably the loading of the correct firstrib_firmware_modules.sfs is essential to make overlayfs work properly Question


Yes, that is correct (unless you've purposively put overlay.ko module in correct kernel_related directory structure in firstrib_rootfs; much easier to rely on firstrib_firmware_modules.sfs to include it!). The overlay.ko module is in the firmware_modules.sfs, so if FirstRib can't find that (such as specifying wrong partition or not providing appropriate firstrib_firmware_modules.sfs then you'll get above error message.

Also, yes, three threads may be a problem. Reason I made three is that WeeDog is not FirstRib per se. And firstrib_rootfs can also be used via chroot on any host linux system without needing to be independently bootable. I also didn't want to confuse myself with development discussions about the initramfs, which is a separate matter to the building of a root filesystem, but I will reconsider how best to discuss the three things. I will certainly need separate thread for FirstRib build scripts and for WeeDog, which is an actual bootable distribution that involves FirstRib but may become different via added complexity. Think of WeeDog as releases of independently bootable distros (of various flavours and levels of polish, whereas FirstRib is simple build scripts for either or both rootfs and initramfs.

wiak

Last edited by wiak on Thu 27 Jun 2019, 17:37; edited 2 times in total
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1486
Location: not Bulgaria

PostPosted: Thu 27 Jun 2019, 16:56    Post subject:  

Keef wrote:
Code:
"chroot: failed to run setsid, no such file or directory"


I got the same error, but it was because I hadn't amended the script for my boot partition:

Code:
boot_partition="sda1"  # partition (sda1, sda2, sdb1 ... etc) where firstrib boot directory to be


Firstrib is on sda2.

Booted ok to prompt. Just a quick test to see if it worked.


Yes, right again. You must specify the correct partition, where you intend placing the vmlinuz, initramfs.gz and firstrib_firmware_modules.sfs otherwise you will end up with above error. Being simple code, FirstRib does not search for the firstrib directory, so needs it in /mnt/selected_boot_partition/firstrib (i.e. directory MUST BE named 'firstrib'). For example sda1 or sda2 of sda3 or sdb1 or sdb2 etc when making the initramfs.gz with:

./build_firstrib_initramfs01_ver006.sh <partition>

which will result in an initramfs.gz that must be copied to /mnt/<partition>/firstrib directory. Then the simple firstrib init script inside the initramfs will correctly find the firstrib_firmware_modules.sfs

Of course the build_script is simple on purpose so easy to modify to specify other boot directory name when wished/required.

Though it is possible to add code to the build script to make it search for firstrib dir of any name or any partition, that is not something I wish to do since this is as much about keeping the scripts basis, simple, easy to follow/understand. But also therefore easy to fork to provide all singing/dancing search version. Let's keep it simple... Wink

NOTE WELL: you don't need to amend the build script though, Keef. You just must have missed providing the first argument on running it. That is, for sda2, you should have run build script as:

Code:
./build_firstrib_initramfs01_ver006.sh  sda2


and then placed the resultant initramfs.gz, the vmlinuz, and the prepared firstrib_firmware_modules.sfs into directory /mnt/sda2/firstrib, prior to amending menu.lst and booting.

Only if you want to use different boot directory name would you need to actually amend the script (could even make $2 specify directory name easily or just do a search/replace of name 'firstrib' where used in the script as /mnt/$boot_partition/firstrib). At this testing phase best, I suggest, to just use script as provided though (and therefore use boot directory name /mnt/boot_partition_name/firstrib as the location). If you want various firstrib versions stored on same partition, you can just rename the directory you are storing things in to 'firstrib' just prior to booting.

wiak

_________________
Tiny Linux Blog: http://www.tinylinux.info/
Check Firmware: www.murga-linux.com/puppy/viewtopic.php?p=1022797
tinycore/slitaz: http://www.murga-linux.com/puppy/viewtopic.php?p=990130#990130
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 1486
Location: not Bulgaria

PostPosted: Thu 27 Jun 2019, 17:13    Post subject:  

rockedge wrote:
Quote:
"chroot: failed to run setsid, no such file or directory"


I am seeing this since I have been messing with FirstRib and now when boot
an endless loop occurs until I ctrl-alt-del displaying the error


See my post to Keef immediately above rockedge. That endless loop error occurs if you have either not specified the boot partition during the build initramfs part, or if you have not provided the appropriate (32bit or 64bit) firstrib_firmware_modules.sfs

If FirstRib doesn't find firstrib_firmware_modules.sfs where it expects it, then overlayfs can't work (since overlay.ko module is in the firmware sfs), and then the error you see occurs. I have also seen that error, which always turned out to be my error in forgetting to specify destination partition that will be used for the boot components.

This is a simple init without searching for its needed boot component parts. You can't build an initramfs destined, for example, for /mnt/sda5/firstrib and then expect it to work at /mnt/sda1/firstrib or /mnt/sda5/othername. If built for sda5, per that example, it must be installed at /mnt/sda5/firstrib exactly.

Note that, by default, if partition not specified, firstrib expects location to be /mnt/sda1/firstrib. The examples I gave for menu.lst were for the case where sda5 had been specified as alternative.

wiak

_________________
Tiny Linux Blog: http://www.tinylinux.info/
Check Firmware: www.murga-linux.com/puppy/viewtopic.php?p=1022797
tinycore/slitaz: http://www.murga-linux.com/puppy/viewtopic.php?p=990130#990130
Back to top
View user's profile Send private message 
rockedge


Joined: 11 Apr 2012
Posts: 1129
Location: Connecticut, United States

PostPosted: Thu 27 Jun 2019, 17:33    Post subject:  

what I thought were matching isn't

I am using on the 64 bit version overlayfs_module_i686.tar.gz which appears to be for the kernel 4.19.23 and the firmware.sfs and vmlinuz from kernel 4.19.25...seems to be the root of my problem here....I corrected it and I am able to boot successfully with a Bionic64-v8 kernel 4.19.23

I have established a network connection and xbps-install is functioning.
Back to top
View user's profile Send private message Visit poster's website 
wiak

Joined: 11 Dec 2007
Posts: 1486
Location: not Bulgaria

PostPosted: Thu 27 Jun 2019, 17:42    Post subject:  

rockedge wrote:
what I thought were matching isn't

I am using on the 64 bit version overlayfs_module_i686.tar.gz which appears to be for the kernel 4.19.23 and the firmware.sfs and vmlinuz from kernel 4.19.25...seems to be the root of my problem here....I corrected iand I am able to boot successfully with a Bionic64-v8 kernel 4.19.23


Actually, the newest (version 006) build_firstrib_rootfs script no longer needs or uses overlayfs_module_XXX.tar.gz, which contained overlay.ko module. Rather, the overlay.ko module is now expected to be included in the appropriate firstrib_firmware_modules.sfs, which it certainly is for BionicPup renamed zdrv used. Very important to remember to use all 32-bit parts for 32bit FirstRib-based WeeDog system of course (or all 64bit for 64bit version)

Network connection of course also relies on firstrib_firmware_modules.sfs being in correct location (and for correct kernel version).

wiak

_________________
Tiny Linux Blog: http://www.tinylinux.info/
Check Firmware: www.murga-linux.com/puppy/viewtopic.php?p=1022797
tinycore/slitaz: http://www.murga-linux.com/puppy/viewtopic.php?p=990130#990130
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 2 [28 Posts]   Goto page: 1, 2 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Projects
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0983s ][ Queries: 12 (0.0045s) ][ GZIP on ]