(old)Puppy Linux Discussion Forum

Could it still be uploading Igu?
Only md5sums.txt in that directory . . .

Yes, still uploading, as I said - it's 248 MB.

EDIT: done uploading!

EDIT 2: started working on a nice experiment. It's pretty stable and snappy, so I think it's time for fun experiments!

I'm trying to build a minimal Puppy-like skeleton which contains the JWM and ROX-Filer configuration files - sort of an add-on that can be put on top of Subito to make it feel like Puppy. If it works nicely, I might add a menu generator and some graphical applications.

I attached a screeny of what I have so far - it works pretty well!

Thanks, I wonder, what if one have Subito 0.9 in a subdir
I guess that maybe the script find that one? How can I hide it?
Does it look inside if I rename it to subito-09

I have to find my old grub4dos code that booted the 0.9
and see if it boot this one too.

Edit using Subito and Links browser
Testing to write from within Subito 1.0.0
using Links browser so have no practice on Links.
Now I only have to find the submit button.

Rebooted back in Lupu
Edit using Lupu. Jay it worked. MHHP taught me to write dhcpcp
or whatever it was now I've already forgotten but it worked.
And then more by accident I got Links going
I guess that MHHP has told me how to use the file manager
but I don't get how to. And I maybe need to do mount of the NTFS hd too
or even to install nfs-3g something before I can boot it?

I feel like back in 1986 when I used Ms DOS and other DOS varieties.
And did not Xerox have some named CM/L whatever. I fail to remember
but one used the command line a lot.

Anyway fun to test even if I have no idea how to get ROX or Thunar going
or how to get Firefox going either. I guess one have to get terminal or use the command line and apt-get or something.
Yes there exist some FAQ or Wiki but I usually fail to understand such text. Drowning in details and not knowing where to look

Thanks for providing Subito. I have to wait until I know how to read such things.

oops I used this code to boot frugal install.
title subito rootnoverify (hd0,1)
find --set-root --ignore-floppies --ignore-cd /subito/initrd.gz
kernel /subito/vmlinuz boot_mode=live sleep=5
initrd /subito/initrd.gz

I guess it would have worked using this one too?

title subito rootnoverify (hd0,1)
rootnoverify (hd0,1)
kernel /subito/vmlinuz boot_mode=live sleep=5
initrd /subito/initrd.gz

What is the feature or good effect of adding boot_mode=live ?
I used Subito 0.9 without boot_mode=live

I built a new homepage for Subito GNU/Linux, with full instructions for building it.

The "boot_mode" boot code is removed - now there's only way to make Subito persistent (the "home" boot code, which accepts a partition name or UUID). If you want to test Subito, the easiest way is creating a bootable flash drive.

Regarding package management - Subito has a package managed called "hpm", which is a simple shell script. It has its own package format (called "RXZ") and that's the only format supported by hpm.

By the way - I got JWM and ROX-Filer working pretty well, but there are no graphical applications, so it still doesn't look and feel like Puppy.

ISO: subito-0.9.5.iso

This link to the ISO is an dead link .....any other links???

Things has changed. It is in git now.
http://www.dimakrasner.com/roar-ng/download.php

Hi Iguleder,

When you will do one for a 32bit that is all that I have and would like to try this and build one myself.

This all sounds great!!

Full instructions are located here.

However, in order to make a 32-bit, you'll have to do one extra step: run 4buildpackage for each package mentioned here. Before you do this, you'll have to change the architecture (under conf/distrorc) to "i486" and remove all Subito packages from the package list. Once all packages are built, you can rebuild the whole thing with those packages included.

Thanks

Will give this a try. On the site it says to run 4buildpackages after 3builddistro.

Do I still do it that way even though there will be no list for Subito since I will be taking that packages off the list to build for 32-bit?

This is a pretty hacky situation. You'll need some hacks to get this to work: /bin/dash should be a symlink to /bin/bash - create this under sandbox/rootfs/bin.

If you notice any build failures, it's because of things like this.

Once all packages are built, run 3builddistro again, this time with the packages included - you can generate a package list manually, so roar-ng finds the packages you just built.

Ok will keep that in mind;

will likely try this next week and will post my work here if that is ok?

May need help

Thanks

This thread has been quiet for some time, but roar-ng is alive and kickin'!

Since its initial post here, it went through many improvements:
- It is able to build many packages automatically (around 100).
- It supports more distributions: Slackware, Arch, Debian, Ubuntu, Raspbian and packages in roar-ng's dedicated format. Debian Wheezy and the upcoming Slackware 14.0 are supported, too.
- It's much faster and has a simpler design.
- The result distributions boot much faster (in the case of Subito GNU/Linux, the flagship distro built using roar-ng, it's 7-8 seconds on a netbook).
- Support for multiple kinds of bootable media was added.
- Initial Raspberry Pi support; the only missing part is construction of the bootable image.
- Better enforcing of compiler flags, so packages are more optimized.
- The /run directory was added and contains a tmpfs file system; /tmp is linked to it to make stuff faster and simpler.
- A third-generation, recursive optimization script, which makes packages way smaller.
- The boot sequence has changed - the main SFS is now placed on a partition, as in Puppy.

At the moment, roar-ng's development goes in two directions:
- A Slackware 14.0-based, improved version of Subito GNU/Linux. It worked great in all testing builds; now I'm doing a clean, untouched build using the vanilla roar-ng so I can declare it as release-quality.
- An unnamed distribution for the Raspberry Pi. Everything is already in place, except the SD card image generation; I'm waiting for my Pi to arrive, so I can run an alpha-quality build.

hi iguleder

i'm getting an error with ldownload

Yep, that's because the package was not added to the repository yet.

I'm currently building all x86_64 packages on a Slackware 14.0 based build of Subito GNU/Linux - if it goes on well, I'll upload everything.

I thought I would give it a try, no go.

# ./0setup
Processing arch-core
Downloading the package list
--2012-08-18 22:50:21-- http://mirror.csclub.uwaterloo.ca/archl ... .db.tar.gz
Resolving mirror.csclub.uwaterloo.ca (mirror.csclub.uwaterloo.ca)... 129.97.134.71
Connecting to mirror.csclub.uwaterloo.ca (mirror.csclub.uwaterloo.ca)|129.97.134.71|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2012-08-18 22:50:22 ERROR 404: Not Found.

Error: failed to download http://mirror.csclub.uwaterloo.ca/archl ... .db.tar.gz.
#


I'm obviously confused by your instructions.

You configuration is invalid; you have supplied an invalid architecture: it should be either i686 or x86_64 for Arch.

EDIT: see the configuration here if you need an example.

EDIT 2: it seems mplayer2 is screwed up. Since it depends on Python 3, it cannot be built using Slackware's Python. Also, syslinux fails to build for some reason - I'm still investigating this.

smokey,

the arch is missing in your url e.g. i686 ...

EDIT: ah iguleder you been faster (and you know more about that ...)

aragon

Forgot to mention - make sure you work against the latest version (here).

Currently, there is a development branch called "raspberry-pi", which has many improvements. I'm going to merge it back to the master branch soon.

I progressed a lot further this time but encountered a lot of command not found errors.

Never got to build an image.

See attached output from Terminal window.

Regards

Well, that makes lots of sense - take a look at the package list you used - it's pretty much empty. You don't even have a C library or a kernel.

But yes, you used roar-ng right - kudos for that. Now, get a real package list (as the one here) and run 1download, 2createpackages and 3builddistro again.