(old)Puppy Linux Discussion Forum

Latest version: 12.12.2 http://www.murga-linux.com/puppy/viewtopic.php?t=83064
--------------------------------------------------
Here I will add my To-do list, changes compared to stable version and other future plans related to ArchPup development:
29 Jan
Just to add some more information regarding /etc/rc.conf. Following line is new:
# LOCALIZATION
LOCALE="C"
That means changing system language requires only to change one line in one file, but off course only after
you enable desired locale in /etc/locale.gen. Now, that's simple and easy
Second - important information: With this major version change creating new save file is required.
Here is my advice: First backup your /root folder to some location outside your save file, then rename save file
to archpup.2fs.bak (just in case ), reboot and make new savefile. Then finally you can move original /root folder
back in its place. This way you settings will be saved and you can continue to use them in new version.

21 Jan
In attempt to centralize system configuration in one file like in good old Arch Linux , here is
list of current variables inside /etc/rc.conf
X_AUTOLOGIN="yes"
AUTOMOUNT_VOLUMES="no"
SAVEFILE_DIALOG_FORCE="no"
DAEMONS="metalog alsa cups messagebus dhcpcd rc.pcmcia rsync Pwireless2_service"
MODULES="" Add modules you want to run on startup. After this change /etc/MODULESCONFIG is removed.
------------------
spacefm replaces thunar as default file manager
It is much more customizable than thunar, has image preview, right click create and extract archive..
Problems with mounting are now fixed!
--------------------------
use latest kernel from 3.4 series
split and simplify build script

I was thinking what is the best way to distribute next version, so here is final decision for version 132, that will be based on
packages from 1st February 2013:
- First there will be archpup-132-alpha, iso with only archpup.sfs and adrv.sfs size around 80 Mb.
- After some period of testing and probably fixing this alpha version, next iso will be archpup.sfs+adrv.sfs+archapps.sfs
and around 150 Mb size. I will no longer make this minimal 80 MB iso, because everyone can remove archapps.sfs and still
OS would be functional.
- In archapps will be included pacmanxg4, but not yaourt. Instead for managing packages from AUR there will be packer in
another sfs - archdev. Reason is simple, you need development sfs to compile packages from AUR, so packer is moved to
that module.
- Evince will be removed, and as new pdf viewer there will be qpdfview
- Under system menu new entry is added "Update package databases", easier for beginners no need for manual pacman -Sy.
----------------------------------------------------

You should add that a more stable and well-compiled kernel.

those plans for the new ArchPup are sounding GREAT!!

with PACMAN the complete package manager? even 'better' than apt-get?? this is AMAZING!! now those hard to install apps that puppy has so much trouble with, will be a BREEZE. easily install KDE, Mate, Unity, Compiz etc...just by typing the command 'pacman -S mate'....absolutely amazing.

i think the ydrv idea and keeping the wm.sfs separate is also a good idea.

simargl,
good start.

Would you mind clarifying your goals on:
kernel,
aufs-utils,
udev,
Wireless connectivity,
Arch version (12.12 again?)
Maximum size of the iso
Possibility of 3 SFSs (base - X drivers/video libs, DM, WM - Apps).
The answers might avoid useless discussions and save us some time.

Regarding Qt devel files in apps/adrv SFS, is it an sfs-building issue or a functionality issue that can not be moved to archdev?

bark_bark_bark:
Could you explain what you mean with 'more stable' 'well-compiled kernel'. This kernel ( 3.6.8 ) for me
is perfectly stable, I think you meant older kernel that better supports your hardware. And , for compiling
kernel there are rules - list of commands that everyone is following, I did not add some crazy patch that would
make it unstable, so what is well-compiled kernel and why is this bad-compiled kernel?

mavrothal:
Thanks, this topic is just for (mostly useless ) talk. I'm not against adding 3 SFSs but this is important problem -
Qt or any devel files from adrv sfs must stay there, otherwise if someone replaces adrv, gcc would still see qt as
installed, and pacman -S qt would refuse to overwrite those files.

Great to hear the next version is being developed. Is it going to be possible to add Puppy style apps, for example startmount or pburn. Most of them just need gtkdialog and a few scripts. It would also be good to improve the USB drive support.

simargl wrote: I'm not against adding 3 SFSs but this is important problem -
Qt or any devel files from adrv sfs must stay there, otherwise if someone replaces adrv, gcc would still see qt as
installed, and pacman -S qt would refuse to overwrite those files.

I guess this is one of the Arch/pacman limitations. Not distinct devel packages (as fedora/debian have).
May not be perfect after all

I guess the major problem devel-package-size wise is Qt and X.
X is OK but for Qt one solution is to drop Qt apps.
If on the other hand you consider Qt apps "mandatory" then you could move Qt with X and DM/WM to adrv and put their devel files in archdev.
Then use ydrv as an apps sfs.
This would keep the main iso size reasonable and allow compiling without confusing pacman or have missing level libs.

mavrothal
I forgot to answer about kernel version for next release. First I thought to use latest kernel from
3.7 series or eventually 3.6.11. But at http://www.kernel.org/ 3.6.11 is labeled as end of
life (EOL), so maybe I will use 3.4.25 or latest from that series, it was updated 2013-01-1.
I made rc.conf with this content It's pretty obvious what will these variables do.

darkcity
startmount http://www.murga-linux.com/puppy/viewtopic.php?t=50845 is program that
automount drives on every boot, and that gave me idea to maybe add option in rc.conf .
It would be set to no by default, change it to yes and every partition will be mounted
automatically on next reboot.

Also I'm thinking to replace thunar + pup-volume-monitor with spacefm. If you want to test spacefm
is in Arch repo : install with pacman -S spacefm.

simargl wrote:mavrothal
I forgot to answer about kernel version for next release. First I thought to use latest kernel from
3.7 series or eventually 3.6.11. But at http://www.kernel.org/ 3.6.11 is labeled as end of
life (EOL), so maybe I will use 3.4.25 or latest from that series, it was updated 2013-01-1.

I would highly appreciate a kernel 3.4.25. That would solve my hardware-incompatibilitiy-problems with kernels > 3.5 / xserver-xorg-video-intel driver / G45 (Eaglelake G+) chipset. Please, see my previous posts in the other ARCHPUP-threads.

simargl wrote:bark_bark_bark:
Could you explain what you mean with 'more stable' 'well-compiled kernel'. This kernel ( 3.6.8 ) for me
is perfectly stable, I think you meant older kernel that better supports your hardware. And , for compiling
kernel there are rules - list of commands that everyone is following, I did not add some crazy patch that would
make it unstable, so what is well-compiled kernel and why is this bad-compiled kernel?

Well someone pointed out that the 3.6.8 kernel you had was a bit buggy and problemetic. The one problem I only had was the broadcom device would never work no matter what (that was a kernel related problem). Also when adding modules, it rejects the new modules (also a sign of a bad kernel).

EDIT: I would keep the kernel version used by ArchLinux (to keep things consistent and Arch compatible). I also would just use arch's kernel as it has SquashFS support (and you won't have to worry about compile errors as well has device compatibility problems).

bark_bark_bark wrote:I would keep the kernel version used by ArchLinux (to keep things consistent and Arch compatible). I also would just use arch's kernel as it has SquashFS support (and you won't have to worry about compile errors as well has device compatibility problems).

Standard-Arch-kernel has no aufs-support. You would have to use an aufs-supporting kernel from AUR,
say a liquorix-kernel:

https://aur.archlinux.org/packages/linu ... mments=all

http://liquorix.net/sources/

or an older kernel (3.4.xy) of calimero:

https://aur.archlinux.org/packages/linux-aufs_friendly/

Here's the media player nightingale (fork of the media player songbird) running on ArchPup:


I simply compiled it from the AUR which is easily accomplished using ArchPup. Still trying to decide if i like it more than clementine, but here it is if anyone wants to check it out:

Download:
nightingale-git-20130116-1-i686.pkg.tar.xz

easily install the package using: offtopic kinda, but indirectly still applies:
Take a look at this website it's like one i've never seen before. It's a massive list, so massive you could get lost, of linux users, favorite apps. this bad boy has been bookmarked by me.

http://www.techsupportalert.com/content ... page=0%2C0

cinclus_cinclus wrote:

bark_bark_bark wrote:I would keep the kernel version used by ArchLinux (to keep things consistent and Arch compatible). I also would just use arch's kernel as it has SquashFS support (and you won't have to worry about compile errors as well has device compatibility problems).

Standard-Arch-kernel has no aufs-support.

Aufs is a joke to me. Plus the SFS files used by puppy aren't Aufs, they're SquashFS 4.x format (Puppy 3/4 used v3).

cinclus_cinclus wrote:I would highly appreciate a kernel 3.4.25. That would solve my hardware-incompatibilitiy-problems with kernels > 3.5 / xserver-xorg-video-intel driver / G45 (Eaglelake G+) chipset. Please, see my previous posts in the other ARCHPUP-threads.

You are probably right so I will use latest kernel from 3.4 series. That will support your hardware and still is new
enough to not make problem with arch packages, which are always latest possible . And to report here my
little test with spacefm:
mounting cd-rom, dvd, and usb fat-32 formatted all works
but mounting internal hard disk drive (ntfs or ext4), failed with something like 'specify partition type error'
In devices list in spacefm are shown mount loop files, I couldn't disable that.
Interesting is that usb devices are handled properly with spacefm but they don't show at all in thunar without restarting pup-volume-monitor.
If I am able to fix problems with mounting internal disk and hiding loop devices, this could easily replace thunar and pup-volume-monitor.

simargl wrote:

cinclus_cinclus wrote:I would highly appreciate a kernel 3.4.25. That would solve my hardware-incompatibilitiy-problems with kernels > 3.5 / xserver-xorg-video-intel driver / G45 (Eaglelake G+) chipset. Please, see my previous posts in the other ARCHPUP-threads.

You are probably right so I will use latest kernel from 3.4 series. That will support your hardware and still is new
enough to not make problem with arch packages, which are always latest possible . And to report here my
little test with spacefm:
mounting cd-rom, dvd, and usb fat-32 formatted all works
but mounting internal hard disk drive (ntfs or ext4), failed with something like 'specify partition type error'
In devices list in spacefm are shown mount loop files, I couldn't disable that.
Interesting is that usb devices are handled properly with spacefm but they don't show at all in thunar without restarting pup-volume-monitor.
If I am able to fix problems with mounting internal disk and hiding loop devices, this could easily replace thunar and pup-volume-monitor.

Just don't break the kernel like you did with the 3.6.8 kernel.

EDIT: If you're planning on using the drivers from arch linux be careful when using different kernel versions then what the driver intended to use.

bark_bark_bark wrote:Just don't break the kernel like you did with the 3.6.8 kernel.

Hmm.. wise guy? And very optimistic if you think that, I care about YOUR problems!

This distro needs a thread on the Arch Linux forums as well. because there's 'no way' they won't find it useful.

whoa.. no need to be hostile, bro. I just want to have your puppy become better (as well as stable). I could help by testing the ISO before release though. I don't care which kernel you use (as long as it's from January 2012 or newer). I want to make sure the kernel is fully stable, but I have confidence in the fact that kernel compile errors are less likely to happen for the next version.

i know in pre-ArchPup 12.12.x that broadcom devices worked, but they don't in that version because of kernel-related errors.

Anyways I will be happy to help your Puppy become a success. Don't let that post fool you into thinking it was 100% your fault that the kernel was broken, the kernel sources itself is to blame too. (I know because I've done some test compilations of kernels.)

Remember think proudly about your puplet. I think it's very unique. I would recommend it to anyone who want to switch from arch to Puppy.

Just keep experimenting, it will pay off.

EDIT: You may think you know what my problems are, but you don't and you never will.

simargl wrote:Also I'm thinking to replace thunar + pup-volume-monitor with spacefm.

That may be a ggod idea. Mostly because I _think_ that the patched glib required for pup-volume-monitor gives problems

simargl wrote:so maybe I will use 3.4.25 or latest from that series, it was updated 2013-01-1

Wise.
Also calimero's kernels and ausf-utils suggested by cinclus_cinclus below may be a good idea. Did you check if their config matches yours?
(is always a good idea to follow "upstreams". Less work for you )

bark_bark_bark wrote: Aufs is a joke to me. Plus the SFS files used by puppy aren't Aufs, they're SquashFS 4.x format (Puppy 3/4 used v3).

You do not have a clue what aufs is. Do you?...

I know what Aufs is, I just think it sucks.