(old)Puppy Linux Discussion Forum

Iguleder wrote:In fact, you can build for another architecture, but in order to compile packages using roar-ng, you'll need to run it on that architecture, through any distro..

Many thanks
Will run through Debian and as displaying on HDMI TV, graphic card probs should be circumnavigated..
Just managed to order a B board RPi (at last) - 58 days to delivery
- in Internet time I think that is aprox 3 years

Hope to have an A board sooner - thanks to Ed (another Puppy in US) for his help with the Rpi Foundation

Upon fsck:ing my roar-ng-build's save-file (ext2), there are many FS_errors ...

Right, there is a sequential mounting of file-systems, which are unioned by aufs at / - then if load_sfs is run for e.g. devx.sfs, there is another mountpoint remounted ro in the aufs-tree at / .

How to disentangle this mess, for to cleanly unmount /mnt/save and /mnt/home_partition, by unmounting/remounting backwards? Is it possible? The woof-builds unmount save-files and home-partitions cleaner, irrespective of any fsck run at re-boot, than my roar-ng builds.

Can a cleaner unmount of save-file and home-partition be achieved by a remount,ro of the aufs-tree, or even tricked by a blunt, non-remounted ro, sync;umount -l?

I did read the aufs and aufs-utils documentation and, I must admit, I ended up non-the wiser ...


Roar-ng is fun (and somewhat addictive )

Grateful for any input / MHHP

Yep, there is some issue with ext2 errors.

However, I don't think it's possible to cleanly unmount the Aufs file system because it's the file system root. I'll take a look at this on this weekend.

I've been thinking - maybe we should revert back to the old behavior - make create_save_file manual and put it in the main file system, so the user can create a save file with any file system (since the required tools are there).

G'day Iguleder, Please eXplain this dd...

This ISO is hybrid, which means you can make a live USB easily, just dd it to the device.

Cheers

The ISO and DEVX links in the OP is broken.

Also, as I may remember, there is a Manual/Guide floating around somewhere; is there a link to it (I may have missed that in the OP)

Here to help

There's a guide, next to the code, in the "doc" directory.

And yes, now I found out everything to deleted. I just rebuilt the package repository completely this Saturday and synced it using LFTP, which removed all other files

Regarding "live USB" - do this to your device - and there you have a bootable stick. In my case, I used this: Use this with care! You can easily lose all your data this way - don't do this unless you're completely aware of all parameters and what they mean.

so i am a little confused; using woof you are given the option to choose a base distro

does roar-ng do this?

maybe i should just run it and find out...

The "base distro" in Woof means which distro to take all non-PET packages from.

In roar-ng, you can choose for each package, from which distro to take it. This way, you can use packages of more than one distro - way more flexible and generic!

oh!

well in that case ( this is what i aim to end up with you see) how would just asking roar to download pacman + dependencies work?

when i have the time (soon! so soooooon lol) i intend to make and maintain a puplet that is rolling-release via a pacman (arch package manager) wrapper that uses arch packages as much as possible and also looks for most up-to-date puppy packages

how far would putting pacman in the list go?


BTW

i attached a dash.pet as i couldnt find one when using roar

Hi @Iguleder

In telling a colleague about your distro, they gave up without ever starting. They were turned off by the opening post where you "target" the location of the ISO as well as the DEVX files. Its near the bottom of the post under the tit "Subito GNU/Linux Alpha 1".

I know you moved them to GIT, but they didn't figure that out.

FYI

gcmartin wrote:Hi @Iguleder

In telling a colleague about your distro, they gave up without ever starting. They were turned off by the opening post where you "target" the location of the ISO as well as the DEVX files. Its near the bottom of the post under the tit "Subito GNU/Linux Alpha 1".

I know you moved them to GIT, but they didn't figure that out.

FYI

Sorry if I interupt. Why would that make them hesitate?
I guess my poor English fails to get the way they think about it.

One more n00bish question from me... well, actually two.

(1) Does roar-ng build what could still be considered Puppy Linux, or is it its own brand of something new...? (Yes, I read the part about it being forked from Woof.)

(2) Could I build on ARM devices with roar-ng...? I'm thinking (if I can scrape together some money AND sell a bunch of stuff that's not going anywhere right now anyways) of getting a BeagleBoard-xM and somehow putting Puppy on that just seems like the right thing to do

1) Not at all. It's a distro similar to Puppy here and there, though - it shares no code with it.
2) Yes - any architecture. However, you'll need to be able to compile packages for it.

So, if I wanted to use roar-ng with ARM, I'd start with, for example, Debian-armel... would I have to run roar-ng on the intended target device itself (that might be difficult for me to figure out)...? or could I make the OS on, say, an x86 system and just copy bootable files to an SD card (much easier)?

You can run build a distro with roar-ng on any architecture, for any architecture. However, to build packages, you'll have to run it on the target architecture.

In order to port my distro to x86_64 I ran roar-ng on a 64-bit distro, built all the packages, then built the ISO on Puppy.

OK, I think I understand... I'll give it a whirl if/when I get my beagleboard.

Haha Iguleder you have humor.
http://www.dimakrasner.com/roar-ng/

You write

Be Smart

roar-ng is simple

Yes I know I am a very confused guy with a twisted? brain.
But "simple". Embarrassingly I fail to use even simple OS now.

Okay I download and give it another try. Anyway I love that you provide
such innovative products. Keep it coming. Always interesting to follow you
even when I don't get a thing of what you are doing due to my lack of know how.

Ooops too late one need to use GIT

I have no wishes to learn such is it mirrored somewhere
so I can download the iso like one use to do?

Currently, there is no ready ISO available. If you run roar-ng with Subito's configuration, you'll end up with a polished and working image identical to the one I use.

However, I rewrote ncsplash (the boot splash tool of roar-ng, written in C) and fixed many bugs. Boot times are better than ever (partially because ncsplash is now much more efficient) and stability is superb.

I might upload an ISO of Subito GNU/Linux 1.0 soon. Seems ready for general consumption :p

Happy Smile Icon

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:
It's about the same size as an equivalent Puppy, with some minor additions, such as Mesa and SDL.

Also, it has much more drivers, since Puppy's kernels usually have slightly reduced functionality to save size. I believe it's wrong - the kernel package of this build is 14 MB (smaller than Puppy's!) and provides much better hardware support.

I tested it only on two machines - my Asus Eee PC 1001PX (N450, 1 GB RAM, Atheros WiFi, Intel GMA 3150, Intel HDA) and a desktop machine (Core 2 Duo E6320, 2 GB RAM, no WiFi, GeForce 7300GS, Intel HDA). Worked flawlessly on both - Nouveau is included, so the latter had an accelerated framebuffer console, KMS goodness and good performance.