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 Wed 17 Sep 2014, 13:51
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Projects
Aboriginal Linux as a Puppy Pet and Puppy
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 2 [30 Posts]   Goto page: 1, 2 Next
Author Message
scsijon

Joined: 23 May 2007
Posts: 1042
Location: the australian mallee

PostPosted: Wed 12 Jun 2013, 19:02    Post subject:  Aboriginal Linux as a Puppy Pet and Puppy  

I have created a pet that allows you to play with a busybox based aboriginal linux under puppy.

It was built with the i486 in mind and should have it's dev 'bits' already there.

It uses chroot so you don't need qemu, etc.

It installs in it's own directory under /root and starts with a script so you can play with it and see it's workings and have access to anything you build in it.

It should be found at www.lamiaworks.com.au/puppy/aboriginal/aboriginal-i486-130612.pet and is about 31meg in size and a hash of 2a21a278d28618199036dd47c70636f9.

To use it:-

drop out of your desktop to a # prompt (using a console is not suitable as you can have serious corruption);
type on on the # prompt> ./aboriginal
and you should be in it
to exit it press <ctrl>d
and you should see the word exit and a new # prompt, you should be able to start your desktop again.

Have fun.

Last edited by scsijon on Sun 30 Jun 2013, 22:46; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
goingnuts

Joined: 07 Dec 2008
Posts: 780

PostPosted: Sun 16 Jun 2013, 05:46    Post subject:  

This is HOT! Very Happy Just played a little with it:
After chroot I
* compiled & installed libz
* compiled & installed tinyXlib
* compiled & installed tiny-Xvesa
* compiled & installed m4-1.4.12
* compiled & installed dvd+rw-tools-7.0 (to check c+ build)

Then exited from the chroot.

Then populated aboriginal-filesystem-i486/dev and run the below before another chroot:
Code:
if [ ! -c aboriginal-filesystem-i486/dev/null ]; then
   mknod -m 666 aboriginal-filesystem-i486/dev/null c 1 3
fi

#getting net access
cd aboriginal-filesystem-i486
mount -t proc proc proc/
cd ..

cp -af /etc/resolv.conf aboriginal-filesystem-i486/etc/resolv.conf

#shell...
[ ! -f aboriginal-filesystem-i486/etc/profile ] && cp -af /etc/profile aboriginal-filesystem-i486/etc/profile
[ ! -f aboriginal-filesystem-i486/root/.bashrc ] && cp -af /root/.bashrc aboriginal-filesystem-i486/root/.bashrc

mount -t devpts devpts aboriginal-filesystem-i486/dev/pts
mount -t tmpfs shm aboriginal-filesystem-i486/dev/shm
mount -t proc proc aboriginal-filesystem-i486/proc
mount -t sysfs sysfs aboriginal-filesystem-i486/sys


After chroot I was able to start Xvesa. Will do further testing to get jwm & rxvt running too.

Is it possible for you to post a "recipe" for your build of the pet?
Anyway thanks a lot for doing this pet!
Back to top
View user's profile Send private message Visit poster's website 
PANZERKOPF

Joined: 16 Dec 2009
Posts: 280
Location: Earth

PostPosted: Tue 18 Jun 2013, 15:18    Post subject:  

goingnuts wrote:
This is HOT!

Yes, this is really HOT Smile
They have images for many targets: x86, arm, PowerPC etc.
http://landley.net/aboriginal/downloads/

Thanks scsijon!

_________________
SUUM CUIQUE.
Back to top
View user's profile Send private message 
scsijon

Joined: 23 May 2007
Posts: 1042
Location: the australian mallee

PostPosted: Wed 19 Jun 2013, 21:14    Post subject: building aboriginal  

All I did was download their build script http://landley.net/aboriginal/downloads/aboriginal-1.2.3.tar.bz2, followed their instructions on how to build, created my 'aboriginal' starting script and put it all together into a pet using my version of Petmaker (2.2).

You could of used their pre-built versions if you wanted and add all sorts of things but different kernels=different results.

it's built for kernel 3.8.x.

Go herehttp://landley.net/aboriginal/screenshots/ to see the best descriptions of their versions and bases. Don't use the links on this page as most don't work properly as they were the old ones, http://landley.net/aboriginal/downloads/ do.

Have fun

Last edited by scsijon on Mon 24 Jun 2013, 20:30; edited 4 times in total
Back to top
View user's profile Send private message Visit poster's website 
scsijon

Joined: 23 May 2007
Posts: 1042
Location: the australian mallee

PostPosted: Sun 23 Jun 2013, 21:51    Post subject:  

@goingnuts, ?do you want to build a single package with those you built and maybe well start a puppy aboriginal for those that want a minimalist system to play with.
Back to top
View user's profile Send private message Visit poster's website 
goingnuts

Joined: 07 Dec 2008
Posts: 780

PostPosted: Mon 24 Jun 2013, 01:44    Post subject:  

I was thinking about something like that but ran into problems with jwm & rxvt. They wont compile (some pthread error) and I am kind of stuck for the moment...
Back to top
View user's profile Send private message Visit poster's website 
scsijon

Joined: 23 May 2007
Posts: 1042
Location: the australian mallee

PostPosted: Mon 24 Jun 2013, 19:48    Post subject:  

goingnuts wrote:
I was thinking about something like that but ran into problems with jwm & rxvt. They wont compile (some pthread error) and I am kind of stuck for the moment...


You were using a 3.8.x kernel, wern't you.

?which errors with jwm, it may be a missing package or switch.

If you can build a package of what you already have added to the basic pet, I'll see if I or joewing can sort it out.

The current building package is attached, it does almost everything you need. EDIT: I've just found it builds with kernel 3.9.

I just modified it for a puppy environment.
aboriginal-84bd3248fad8.tar.bz2
Description 
bz2

 Download 
Filename  aboriginal-84bd3248fad8.tar.bz2 
Filesize  193.78 KB 
Downloaded  181 Time(s) 

Last edited by scsijon on Tue 25 Jun 2013, 19:31; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
goingnuts

Joined: 07 Dec 2008
Posts: 780

PostPosted: Tue 25 Jun 2013, 14:42    Post subject:  

I could make a package of buildscripts + sources that would compile and install zlib + tinyx11 + tinyxvesa.

I did have to eliminate the toybox and replace it with a busybox 1.20.2 as toybox-cp wont do "cp -L -rf X11 /usr/include" (correctly) which is needed for tinyxlib. Alternative the aboriginal should be rebuild without toybox and a "full" busybox.

After that a package for populating /dev should be installed. And before Xvesa can run it needs fonts and other auxiliary files.

Then you can run Xvesa...

I could include a build script for rxvt (which works in other toolchains with musl/uclibc) and you could view the build errors.

But that is a huge package to make...so before doing so I have attached the build log for rxvt. It might give some ideas...my other uclibc toolchain configure with pty/tty type: GLIBC and my musl toolchain configures with pty/tty type: OPENPTY...
This toolchain configures with pty/tty type: STREAMS which seems to be a sort of last resort...
No idea why or if this is the problem - but I think it should be solved before creating a lot of packages.
rxvt_build_log.txt.gz
Description 
gz

 Download 
Filename  rxvt_build_log.txt.gz 
Filesize  15.83 KB 
Downloaded  177 Time(s) 
Back to top
View user's profile Send private message Visit poster's website 
scsijon

Joined: 23 May 2007
Posts: 1042
Location: the australian mallee

PostPosted: Tue 25 Jun 2013, 19:52    Post subject:  

downloaded your log, will have a look and see if anything obvious, but you may get a few 'odd' questions back.

and no' we want toybox in it as it has a lot of the switches missing from busybox commands that otherwise are requiring full commands to be included, I shall pass on your comment about 'cp' as this is the sort of thing they want to know to fix. It's also needed for the cross-compile versions.-DONE

Buildscripts, source (referances rather than the source itself) would be appreciated;

and agree, want to fix problems before a major building of packages run.

comment1:Building a new one for 3.9 in the background, no problems so far. They also seem to have a control on cpu useage somewhere, so that they are not overloading a working system, which is nice.

comment2:I want to have a look at their packaging script next to see if I can 'call' another pre-named script to add others into its build. It would make sense and I think I will sugest it to them.

regards
Back to top
View user's profile Send private message Visit poster's website 
goingnuts

Joined: 07 Dec 2008
Posts: 780

PostPosted: Thu 27 Jun 2013, 01:37    Post subject:  

adding "UCLIBC_HAS_GETPT=y" to sources/baseconfig-uClibc solve the rxvt build... Smile
Back to top
View user's profile Send private message Visit poster's website 
scsijon

Joined: 23 May 2007
Posts: 1042
Location: the australian mallee

PostPosted: Fri 28 Jun 2013, 20:47    Post subject:  

@goingnuts: it also seems there are a few expected include '.h' files missing, I have asked them what gives as we will need some of them such as a libc.h if we are going to build anything decent.

It's also nice to see you've progressed with your problem.

against "comment 2" in a previous post (above), I got a reply that they do have a way, it's called 'control-images, which seems like we do when we add an extra .sfs to the system, except they do it as drive attachments on the starting command line. I prefer our way, especially now we can load/unload on the fly. It's also nice that they are all squashfs so with a little renaming I can see what's inside. The static tools may be of interest to you as it has dropbear, strace and zlib in it, the latter two I thought would be in their basic system, I have no comment on dropbear as I haven't investigated it yet.

regards
Back to top
View user's profile Send private message Visit poster's website 
Ibidem

Joined: 25 May 2010
Posts: 489
Location: State of Jefferson

PostPosted: Sat 29 Jun 2013, 01:09    Post subject:  

scsijon wrote:

against "comment 2" in a previous post (above), I got a reply that they do have a way, it's called 'control-images, which seems like we do when we add an extra .sfs to the system, except they do it as drive attachments on the starting command line. I prefer our way, especially now we can load/unload on the fly. It's also nice that they are all squashfs so with a little renaming I can see what's inside. The static tools may be of interest to you as it has dropbear, strace and zlib in it, the latter two I thought would be in their basic system, I have no comment on dropbear as I haven't investigated it yet.

regards

dropbear is a small ssh mcb (server and client in one).

The command line part is because Aboriginal targets qemu, since it's a cross-compiling environment.
The sfs must be a drive or be on a drive for qemu to access it.
Also, Aboriginal is intended to be a minimal system (just enough to cross-compile), so clever scripts that don't serve that end aren't included.

OT, I may investigate the modinfo usage in eudev; I've sent modinfo patches adding multiple module support, plus -b and -k options.
toybox has lsmod, insmod, and modinfo, but not:
-compressed module support (especially in modinfo, which mmaps the module)
The theory as far as compressed ... support goes is that we have bzcat and xzcat (pending) and may have gzip sometime, so we'll use a function that detects the type of compression, spawns the decompressor, and reads the output of that.
-modprobe
I thought about the logic for this, but don't have anything more than vaguely C-ish pseudocode for the most important function, which is a recursive module loader...
Code:
- modprobe
recursive insmod.
**char recursive_depload(char * modname, char ** options, dryrun) {
   if !dryrun && isloaded(modname) return NULL;
   if !dryrun (if check_blacklist(modname) return NULL;);
   array=recursive_depload(modname);
   if (array)
      orig_array=array;
      for mod in orig_array
         append(array,recursive_depload(mod));
   if !dryrun  {
      if (insmod(modname, options)) abort;
   } else
      return array;
}
OPTIONS:
-a Loop through list, instead of treating rest of args as options.
-b Get blacklist (and options) from modprobe.conf / modprobe.d
-D dryrun
? depmod
-Needed for alias support, unless every modprobe reads all the aliases in every module.
Back to top
View user's profile Send private message 
goingnuts

Joined: 07 Dec 2008
Posts: 780

PostPosted: Sat 29 Jun 2013, 12:28    Post subject:  

Adding
Code:

CONFIG_CP=y
CONFIG_FEATURE_CP_LONG_OPTIONS=y"

to sources/baseconfig-busybox
get BB cp included but still final symlink of cp is to toybox. I cant see how to force BB-cp...so using a static cp from coreutils for now.

Change in download.sh of kernel ex:
Code:

URL=ftp://kernel.org/pub/linux/kernel/v2.6/linux-2.6.25.tar.bz2 \
SHA1=aa6187a1c212dd2d8bd906b023fcefdcf711f35e \
maybe_fork "download || dienow"

to change kernel (linux-2.6.25 wont build kernel but toolchain ok). Remove the kernel specific patches in sources/patches before building.

jwm can be build (jwm-2.0.1 & jwm-686) - although it has never been straight forward configuring and building it static.

The native-compiler-i486.tar.bz2 can after conversion to tar.gz be installed in pupngo and gives a decent starting point for a development environment. Tested build of zlib/tinyX11/rxvt after install and they are ok.

The potential of using Aboriginal Linux to build a puppy-derivative could be that different architectures would be addressed from start...
snap0009.png
 Description   
 Filesize   168.54 KB
 Viewed   503 Time(s)

snap0009.png

Back to top
View user's profile Send private message Visit poster's website 
bark_bark_bark

Joined: 05 Jun 2012
Posts: 804
Location: USA

PostPosted: Sat 29 Jun 2013, 21:33    Post subject:  

I have tested this set of scripts to build a distro for the m68k arch, so i have a lightweight linux to run in ARAnyM.

The end result, these two files:
Code:
./
./hda.sqf
./vmlinux


In the lilo section of my custom aranym config what do i put?

What I currently have:
Code:
[LILO]
Kernel = vmlinux
Args =
Ramdisk =

_________________
Desktop: Intel 945PSN Motherboard, 3.2Ghz P-IV "Prescott 2M", 2GB RAM, 500GB WD HDD, Windows 7
Back to top
View user's profile Send private message 
scsijon

Joined: 23 May 2007
Posts: 1042
Location: the australian mallee

PostPosted: Sun 30 Jun 2013, 22:36    Post subject: 'concept and initial testing working party'  

i've had some quite comprehensive answers from the aboriginal linux group to my questions. If you've already joined their email group you should have seen both. However for the rest, I shall sort the questions and answers out and add them to this thread in the next few days.

Basically it seems it's not that hard to do what we want, we just need to know what to do in their system methodology.

And Rob Landley (barryk's equivalent) and his group seem to be happy for us to do so. I even got a 'yay!' from him.

So I'm going ahead and changing the Thread title slightly and starting to format a 'structural concept statement' for an Aboriginal Puppy that we may (hopefully) be able to have cross-compile without serious problems. I am not planning for it to be an application loaded Puppy as barry creates, with user type applications already included, but more as a 'basis to build on/from' puppy with application building ocurring after the 'core puppy' has been loaded.

I believe that I can call on goingnuts to help as he has shown in the past, as well as his work in the thread, a minimalist system leaning. I have the same!

I clearly admit that am not a programmer, but can work through an existing script and propose a change or help debug.

Do I have any other puppians willing to put up their hand at this stage to be included on at least, the 'concept and initial testing working party'?

I do admit i'd like for it to build within the woof2 framework, at least for now. Whether that can happen, I think, should be a fair part of the working party's initial task! Maybe we will eventually need to propose back to barryk changes that create a woof3.

regards
scsijon
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 1 of 2 [30 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.1031s ][ Queries: 13 (0.0057s) ][ GZIP on ]