Puppy Linux Discussion Forum

mistfire · Joined: 04 Nov 2008 Posts: 1421 Location: PH

@dejan555 yes it is I think because it was very easily to contribute on Puppy Linux development. Biggest changes are already made in woof-ce

musher0 · Posted: Fri 08 Nov 2019, 14:32 Post subject:

rufwoof · Joined: 24 Feb 2014 Posts: 3724

I boot a 11.6MB vmlinuz, a cut down version of Fatdog's Bulldog (initrd cli). That's with the initrd (initramfs/init) built into the kernel, along with all machine specific modules/firmware, so its the only file required in order to boot. Boots in around a second ... a few seconds in total before its also wifi net connected, and includes OpenSSH (so ssh/scp/sftp/sshfs), ccrypt (that I use to encrypt my .ssh folder (ssh keys)), screen (terminal multiplexing), simple-mtpfs (so I can mount my android phone), kexec (to directly boot any other kernel/system), and mc (file manager and text editor). With that I can download any Puppy/distro, and boot (kexec) it. Or kexec any locally stored Puppy (I just tend to boot full Fatdog). Or I can boot it and ssh into hashbang and reattach to a tmux session with multiple windows/sessions for irc, email, w3m ...etc.

mc's F2 "menu" can be user-defined, or you can set up multiple menu's, one menu for each folder. When you're familiar with mc as a file manager/text editor its relatively quick/easy to use. In keeping with that I created a ncurses menu system that works along similar lines/style as mc (see attached image).

Puppy looks to be widely usable, functional when moved from machine to machine. There's little in the way of Puppy to be refined to be single machine specific. Trying to downsize Puppy to be single machine specific, removing firmware/modules etc. is awkward. And much of Puppy size is modules/firmware, much of which might never be used, but is loaded every time.

A combination of being able to use one Puppy (devx) to compile a machine specific kernel (localyesconfig) that also included a mc style ncurses menu system could be made relatively easy for novices to build/run. And once you have a basic network connected system running, adding additional functionality via the likes of loading sfs's can be used to expand that small 'setup' system into a full blown desktop gui system. Or just used to boot a local copy of a full system. With the added advantage of being able to sense (scan) for what hardware is actually available after the initial small kernel has been booted, but prior to downloading/booting the main (full) system.

In short, I'd suggest a TUI (text user interface) .. along the lines of mc or the old Turbo Pascal style IDE as the front end to cli actions/scripts. That tui/scripts could even be downloaded from a central server rather than being contained within the vmlinuz.

musher0 · Posted: Fri 08 Nov 2019, 22:38 Post subject:

Nah, I don't like back-ports! Laughing

sc0ttman · Joined: 16 Sep 2009 Posts: 2806 Location: UK

rufwoof · Joined: 24 Feb 2014 Posts: 3724

mistfire · Joined: 04 Nov 2008 Posts: 1421 Location: PH

Some woof-ce accomplishements this 2019
* Improved package management and sfs loading
* Improved PTP and MTP support
* Improved puppy core apps gui
* Improved disk image file mounting
* XDG Desktop compliance
* Improved touchpad support
* Added non-acpi support

rockedge · Posted: Mon 25 Nov 2019, 11:38 Post subject:

At the moment using the kernel-kit to produce a 5.2.21 SMP PREEMPT RT kernel and I am running into this error immediately

mikeslr · Posted: Mon 25 Nov 2019, 14:26 Post subject:

vercmp is not in the Ubuntu repos. Per Arch, it is a version comparison utility. https://www.archlinux.org/pacman/vercmp.8.html, Distros employing it seem to be few and far between. https://pkgs.org/download/vercmp; https://pkgs.org/download/filevercmp. See also, https://github.com/diorahman/vercmp. They do not appear to be either arch or kernel specific.

And perhaps the idea for a work-around, https://unix.stackexchange.com/questions/163702/bash-script-to-verify-that-an-rpm-is-at-least-at-a-given-version

As always, the information I transmit may be entirely misleading. Shocked

rockedge · Posted: Mon 25 Nov 2019, 14:53 Post subject:

hello mikeslr,

I think I know what is happening and why vercmp did not work on one Bionic64 and does on another. Some thing in the save folder is eliminating or while listing it. I was able to compile a kernel 5.2.21 just now successfully and am now looking into the patches needed to build this as a true real time kernel.

The goal is to create a Puppy Linux that can run LinuxCNC in it's full capacity and direct CNC machines. Although so far there are errors still during compiling LinuxCNC, it is getting closer. I am using for that kernel 4.19.27-rt16 SMP PREEMPT RT right now but if successful in building a newer version 5 real time kernel I will use it.

BarryK · Posted: Mon 13 Jan 2020, 04:45 Post subject:

I was very surprised today. Those of you who have been developing with Puppy for many years will probably know about "PuppyHardwareProfile" for /etc/X11/xorg.conf, which, in a nutshell, handles booting a usb-stick on different PCs, with different video chips and monitors.

Yesterday I have enhanced this a bit in woofQ, my fork of Woof2, and then I looked at woof-CE on github, and it seems that PuppyHardwareProfile was removed in 2016.

See my blog post:

https://bkhome.org/news/202001/improved-hardware-profiling-for-xorg.html

Has hardware-profiling for Xorg been moved or implemented in some other way in woof-CE, or is it really gone?

peebee · Posted: Mon 13 Jan 2020, 07:49 Post subject:

BarryK · Posted: Mon 13 Jan 2020, 10:49 Post subject:

s243a · Joined: 02 Sep 2014 Posts: 2621

jamesbond · Joined: 26 Feb 2007 Posts: 3473 Location: The Blue Marble

s243a - you had a wrong closing url tag.
Here is your post, when the closing tag has been fixed.