(old)Puppy Linux Discussion Forum

Yes, already doing that now.

It's not so clear to us old chaps.

Thanks

That's why you have this.

Iguleder wrote:That's why you have this.

I read the readme.

What would be easier to understand is if you had a fully configured conf directory so following the ./1 ./2 ./3 & ./4 would have produced something.

You are much cleverer than the average bear.

Great news! I got both Syslinux and mplayer2 to build.

The former had an issue with LDFLAGS - for some reason, it reads it from the environment but fails to build with my custom flags.

The latter required Python 3, so I got Python 3.1 from Debian to work (extremely hacky!).

I'm currently uploading all packages - you'll have to run 0setup, 1download and 2createpackages again. Make sure you clean processed-packages from remains of the previous .rxz packages.

EDIT: smokey01 - I improved the README and added details documentation of the configuration. Packages are still uploading, shouldn't take very long.

Iguleder wrote:
EDIT: smokey01 - I improved the README and added details documentation of the configuration. Packages are still uploading, shouldn't take very long.

Thanks mate.

It's generating a lot of "command not found errors" during the ./2createpackages stage. Is this normal?

Anyway, after 02:00 better go to bed.

Thanks for your help and advice.

Yes, it's normal. That happens because you don't have AdvanceCOMP or OptiPNG installed.

The result is a larger, less optimized distro.

Iguleder wrote:Yes, it's normal. That happens because you don't have AdvanceCOMP or OptiPNG installed.

The result is a larger, less optimized distro.

With AdvanceCOMP and/or OptiPNG installed, is it larger?
Is it better with or without?

It's slowly starting to make sense but just when I think it's safe to go back in the water, another bugger bites me.

During the ./2createpackages:
squashfs-tools (subito)
Error: squashfs-tools-4.2.rxz does not exist under packages.

It appears squashfs-tools-4.2.rxz has not been downloaded. I guess it's pretty important as it's required to build the iso.

I re-ran ./1download but it still did not find the package. Is it missing or is something wrong with the script?

I guess you wouldn't notice as it would already be in your packages directory from previous ./1downloads.

Should I comment all lines out in the conf/package_list or are these files required when building slackware?

###################################
# Subito GNU/Linux-specific stuff #
###################################
subito|subito-desktop|subito-desktop|exe,dev,doc,nls
subito|locale-gen|locale-gen|exe,dev,doc,nls
subito|advancecomp|advancecomp|exe>dev,dev,doc,nls
in the conf/package_list or are these files required when building slackware?
.
.
.


I don't fully understand what packages are required. It would be nice to have a default list of bare minimum for each distro, or is this list it?

I also read in the manual: ./3builddistro
"It is recommended to edit the script before its execution, in order to tweak various parameters, such as the default desktop background."

In sandbox/rootfs there doesn't appear to be a backgrounds directory where I would expect it /usr/share/backgrounds. Do I need to manually create this directory and populate it with backgrounds?

Thanks

It's better with AdvanceCOMP and OptiPNG - they're used to shrink the ISO. Get them installed on your distro.

And no, you can't build "slackware", but you can build a distro which contains packages taken from Slackware. If you don't have any other AdvanceCOMP package, use the one in the example I gave you.

By the way - the manual was removed from recent versions of roar-ng. It's totally irrelevant - if you still have it, get a newer version.

Iguleder wrote:Uploading the 1.0.0 stable release to this directory. It's 248 MB, since the ISO contains the devx.

Here's the list of the ISO contents: ...

Hi @Iguleder.

I saw this post to this thread, but, I cannot find the ISO you present. Has it been moved or placed somewhere else?

Thanks in advance. ... Also see PM

I guess you need what is referred to as "git"

I know nothing about it but I failed to download
due to me have no "git"

Here is a link to the ReadMe of latest version 2013?
https://github.com/iguleder/roar-ng-ii/ ... ter/README

So what lies in the future for this then? Any prediction?
I find it interesting but I am not on the level needed to get any of it.

https://github.com/iguleder/roar-ng-ii/ ... ter/README

The future's so bright, you gotta wear shades. ©

Maybe it's too early to ask questions about roar-ng-ii:

After successfully running:
# sh roar-ng setup

I'm now stuck at:
# sh roar-ng download
busybox (subito 3 x86_64)
Error: failed to locate the package "busybox".
Error: failed to locate busybox.

Yep, I'm aware of this problem. I'm currently trying to solve it - it's a problem with my domain, which prevents download tools from downloading package lists.

EDIT: I think it works now.

EDIT 2: I'm currently working on a new distro using roar-ng-ii. It's a console-only, live distro similar to Puppy, with heaps of console applications. I also have a Raspberry Pi (btw, the reason why you had issues with roar-ng-ii is the fact I moved all my stuff from hosting in the US to my Raspberry Pi, at home ) and I want to port this distro to ARM later.

Thanks, Iguleder, downloading now! Just a minor problem:
Error: failed to download terminus-font-4.36-1.rxz.

And I'm really, REALLY looking forward to your ARM port! But take all the time you need.
*currently building a retro-Acorn BBC Microcomputer round my Pi*

Problem solved, it was a missing directory

By the way - I'm currently generating the first ISO of my new distro; all packages were built successfuly. It's for x86_64 and uses Ubuntu 12.04 packages, so it's possible to build a 32-bit flavor compatible with Precise Puppy once the 64-bit one is good enough.

cool you wrote

I'm currently working on a new distro using roar-ng-ii. It's a console-only, live distro similar to Puppy, with heaps of console applications.

So it never start an X then. It is like old Unix
that one write commands on the CLI?

so if I want to start Firefox instead of clicking on an icon
on a board window I call firefox to start by writing its name?

In such a system how does one know which program
it has when it have no menu at all? Sorry me so naive.

Way back in time MsDOS had a free? program
named Directory Control DC and later it turned into NC?

Or one was a rip of the other not sure. There one had some kind of
table list one had a system that looks like a Menu.

is that possible to get on your latest version too. How.

Ihave 64 bit now so would be cool to test it
but take your time. No hurry.

Yep, just like it used to be. It's sort of a tribute to the late DOS days - there were many text applications that actually have a user interface, like Ytree and cmus.

I got the distro to boot and fixed a few bugs in the build system - now it works flawlessly and most applications seem to work well. RAM usage is 32 MB

Now I'm trying to solve the last problem, which is Syslinux 5.00. For some reason, roar-ng II outputs defective ISO images that won't boot. I tried this boot loader on a flash drive and my machine reboots immediately - I guess something is wrong with it if other distributions skip this version. At the moment, I'm building a new image, with Syslinux 4.06. If it works fine, I'll upload everything tomorrow

yes that would be cool

I had this boot code for grub4dos for subito

title subito rootnoverify (hd0,0)
find --set-root --ignore-floppies --ignore-cd /subito/initrd.gz
kernel /subito/vmlinuz
initrd /subito/initrd.gz

Maybe your new one does not have any NTFS ability
built in so it only boots on ext2 and such linux partitions?

It should be able to boot from anything, as long as both the boot loader and the kernel support the file system you use.

By the way, good news - this configuration can produce a bootable, beta-quality image of the new distro. A fresh git checkout of roar-ng II (and a small change: remove Irssi, gotta fix this) is required, as you can see in the changelog

The result image can be written to a flash drive using dd (or burnt, up to you). It performs quick, automatic detection of the boot device/partition - no need for crappy boot codes and no noticeable delay as in Puppy. Works well here