slacko-6.0 beta 2

[partsman]

When installing supertux2 from PPM It wouldn't run still needed to install openal even though PPM showed openal-soft was installed !
I chose to install openal-1.13.pet to solve this however a symlink to openal-soft may be a better approach

[technosaurus]

Close but it only has 256-color drawing, not enough colours:)
ttuuxxx

You can always add more layers to get more colors. That is what I did with mtpaint anyhow. Any more than 256 makes it difficult to get to the colors anyhow.

[MochiMoppel]

X crashes when using Gnumeric

Slacko 5.7 and 5.9.3 use the same Gnumeric version (1.10.17), so the problem must be with the new Slacko. Can somebody confirm?

To reproduce:
1) Type anything into a cell and press Enter
2) Select this cell and press Ctrl+C (to copy)
3) Select another cell and press Crl+V (to paste)

This may already crash X, latest when selecting another cell X crashes. Typing xwin will restart X, but changes made in Gnumeric are lost.

Copy & Paste via context menu works normal.

[LazY Puppy]

Hi.

I'm currently examining the Slacko 5.9.3 and found some issues.

1.) using pkeys as boot parameter and boot is failing (puppy sfs not found)
2.) using plang as boot parameter and boot is failing (puppy sfs not found)
3.) can't connect to the internet using my GPRS Mobile USB-Modem (it is detected and ready for use - as the messages say; menus are updated but nothing else happens after this; no menu entries, no option to connect - works always in Lucid and Precise)

RSH

P.S.

Booting pkeys and plang tested in combination and as single used options - failed all the way. Failed also using 'fr' (french). Other languages not tested.

[mavrothal]

1.) using pkeys as boot parameter and boot is failing (puppy sfs not found)
2.) using plang as boot parameter and boot is failing (puppy sfs not found)
<snip>
Booting pkeys and plang tested in combination and as single used options - failed all the way. Failed also using 'fr' (french). Other languages not tested.

Looks fine here, alone or in combination. Few lang tested (including french - pic).

Anything special in your setup? The only relevant change I can find is this relating to VFAT booting devices, but this is also in slacko-5.7

[SFR]

1.) using pkeys as boot parameter and boot is failing (puppy sfs not found)

The use of pkeys while booting off USB drive is causing such problems due to absence of some modules (which usually were in initrd.gz) that should be compiled into vmlinuz.
http://www.murga-linux.com/puppy/viewto ... 977#789977
http://www.murga-linux.com/puppy/viewto ... 324#790324
Does it also happens while booting off USB, in your case?

2.) using plang as boot parameter and boot is failing (puppy sfs not found)

Can't recreate - works for me (USB & CD)...

3.) can't connect to the internet using my GPRS Mobile USB-Modem (it is detected and ready for use - as the messages say; menus are updated but nothing else happens after this; no menu entries, no option to connect - works always in Lucid and Precise)

PGPRS' files have been lost in action.
https://github.com/puppylinux-woof-CE/w ... issues/498
___________

Can somebody confirm?

Just checked in VBox & QEmu and can not recreate this behaviour...
Anything relevant in the output?

Code: Select all

gnumeric > /tmp/gnumeric.log 2>&1

Greetings!

[MochiMoppel]

Just checked in VBox & QEmu and can not recreate this behaviour...
Anything relevant in the output?

Code: Select all

gnumeric > /tmp/gnumeric.log 2>&1

Looks relevant, but not pleasant:

Code: Select all

gnumeric: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

Thanks for checking.

[mavrothal]

1.) using pkeys as boot parameter and boot is failing (puppy sfs not found)

The use of pkeys while booting off USB drive is causing such problems due to absence of some modules (which usually were in initrd.gz) that should be compiled into vmlinuz.
http://www.murga-linux.com/puppy/viewto ... 977#789977
http://www.murga-linux.com/puppy/viewto ... 324#790324
Does it also happens while booting off USB, in your case?

Makes sense. With the new kernel setup (no modules in initrd.gz) booting from a vfat usb drive with non-english will fail since it can not read the filesystem and find the files.
It needs a new kernel with CONFIG_NLS_CODEPAGE_{850,852} and CONFIG_NLS_ISO8859_2 set to"y" instead of "m".
Maybe when/if Mick appears.

[LazY Puppy]

relating to VFAT

Does it also happens while booting off USB, in your case?

Yes, I'm booting generally from a VFAT Partition. Also generally from USB. This time External 500GB USB HDD.

As I was running into this I did use my modified version of the initrd.gz.

Had immediately tested with the original one after running into this.

Equal Results.

As soon as I enter pkeys or plang, it won't find the puppy sfs.

I can set DE keyboard later by using setxkbmap de, but need to do it each time after restarting X.

Just for your interest.
My modifications on initrd.gz to make me able to configure Slacko 5.9.3 at boot up and auto-start by an external .cfg File

Thanks,

RSH

[mavrothal]

Yes, I'm booting generally from a VFAT Partition. Also generally from USB. This time External 500GB USB HDD.

As I was running into this I did use my modified version of the initrd.gz.

Since you are playing with the initrd then it should be easy to use the tahpup kernel (3.14.20) that has the modules built in and should be OK. Is fairly easy to exchange them

[lolox]

Hello !
I am a happy puppy Linux user since v. 4.2.1. I switched to slacko 5.4 in 2012 and I am now running 5.7.

I installed the 5.9.3 test release found at ibiblio on my old laptop (a 2007 hp/compaq nc6120) hdd. Everything worked fine (I noticed that a bug modifying time & date at boot was fixed. Good job : a firewall does not authorize me to use ntpdate at work ; I compiled htpdate to synchronize time & date at start) until I tried to upgrade from slacko 5.7 by copying my slackosave.sfs file in the 5.9.3 directory (I used to do this successfully to upgrade to 5.5, 5.6 and 5.7) and to reboot. When X started, I got a black screen showing only the bottom menu bar. The menu is there with all my software, but only a few SDL apps like Dosbox seem to work. I cannot even open a terminal, so it is difficult to tell what is going wrong.

My slackosave is large, 4.5Gb, too large to boot from a USB stick formatted with fat16 or fat32, but works fine with ext2 or ext3+grub and slacko 5.7. Maybe is it the source of my problem ? Have I to reinstall all my software in slacko 5.9.3 ? Should I try to install 5.9.1 and upgrade to 5.9.3 from 5.9.1 ?

[LazY Puppy]

Maybe this is of some kind of interest.

http://murga-linux.com/puppy/viewtopic.php?t=96571

I have reached my current goals so far.

Btw: booting from ext2 and it goes straight into DE desktop and DE keyboard layout.

When will the lost PGPRS files be included or are they ready for download somewhere?

[LazY Puppy]

PGPRS' files have been lost in action.
https://github.com/puppylinux-woof-CE/w ... issues/498

Since the PGPRS Files have been lost in action may I suggest a small tweak to its GUI for next release of Slacko (5.9.4?, 6.0?).

Instead of using a entry widget to enter the modem device manually and to enter the APN manually also, just using a comboboxentry to give the user option to choose the modem device from a list as well as to choose the APN from a list.

For one of the main providers in Germany it would be: internet.t-d1.de

[LazY Puppy]

http://murga-linux.com/puppy/viewtopic. ... 542#814542

Hi.

While doing some work on this I have found a issue in precise 5.7.1.

The file /etc/DISTRO_SPECS in main sfs is different to the file /DISTRO_SPECS in initrd.gz. The one in initrd.gz is missing this:

Code: Select all

#multiarch distros, such as Ubuntu, will have this. ex: /usr/lib/i386-linux-gnu, so DISTRO_ARCHDIR=i386-linux-gnu
DISTRO_ARCHDIR='i386-linux-gnu'

Hi.

Since you are already changing things in WoofCE may I add another suggestion to the one posted above, to avoid the above quoted issue in precise 5.7.1 happening in Slacko or any future WoofCE Puppy.

Just remove /etc/DISTRO_SPECS from inside of the main sfs and copying the one from inside of the initrd.gz to /pup_new/etc/ right before performing the switch_root.

[mavrothal]

Since you are already changing things in WoofCE may I add another suggestion to the one posted above,

The idea of CE (community edition) is not that the community suggests and one or 2 persons are materializing the suggestions, but rather that the suggestions are implemented by the community and contributed to the project in a form of a patch(set) in a pull request.
This way more work gets done and every one is properly credited for their contribution (in the git log)

So please, if you or anybody else wants to implement this (I know you -plural- can do it), patches are welcome

[MochiMoppel]

suggestions are implemented by the community

but how and who exactly is "the community"? I understand the idea of patch contribution, but I don't understand the authorization process. If 10 people come with patches, who sorts this out? Who does the quality control? And who has the final say on what's in and what's out? Sorry for my naive questions, but I'm used to a company environment with quite different decision processes

[LazY Puppy]

Since you are already changing things in WoofCE may I add another suggestion to the one posted above,

The idea of CE (community edition) is not that the community suggests and one or 2 persons are materializing the suggestions, but rather that the suggestions are implemented by the community and contributed to the project in a form of a patch(set) in a pull request.
This way more work gets done and every one is properly credited for their contribution (in the git log)

So please, if you or anybody else wants to implement this (I know you -plural- can do it), patches are welcome

No, I have stated earlier, I can't do such!

I'm not able to be active on the WoofCE, sourceforge, git or what else is out there, since I'm online by a bandwidth of around 12 KB/S - which is usually enough to be active on this here forum, but it's of course not enough to be active on any else place at the web.

Also I'm neither able to produce patches for WoofCE nor I'm able to read those stuff with pluses (+++) and minuses (---) that seems to be a/the patch. So here is what I am able to offer:

Code: Select all

# Copy the DISTRO_SPECS file to /etc (/pup_new)
cp -af /DISTRO_SPECS /pup_new/etc/

Instruction: insert it above this code (precise571 init example) at the end of init script.
Note: probably you are the more expert than I am and you'll find a more appropriated place where to insert the above code - since I'm not an expert of all the PUPMODE(s) that can be used.

Code: Select all

sync
#killall -USR1 hotplug2 #v423
umount /proc/bus/usb
umount /sys
umount /proc

#now using cpio archive for initramfs 'initial ramdisk'...
#exec switch_root -c /dev/console /pup_new /bin/busybox init 3
exec switch_root /pup_new /sbin/init

###END###

In addition I'm able to present my ideas and some of my work based on these ideas on this here forum.

But obviously the idea of CE as it is performed will never ever make any of my ideas and/or work being able to find a place in a future puppy - unless I would be able to write/read the patches and performing high-speed-flat-rated internet access - the latter doesn't really make sense to me, since I'm usually a heavy offline user.

Might think about just to switch to develop my own OS and keeping stuff local, which would be a pity after I decided lately to give some more time/ideas/work/innovation to Puppy Linux.

[mavrothal]

suggestions are implemented by the community

but how and who exactly is "the community"? I understand the idea of patch contribution, but I don't understand the authorization process. If 10 people come with patches, who sorts this out? Who does the quality control? And who has the final say on what's in and what's out?

Any one with a github account can issue a pull request.
Any of the 7 current members (pic below) of woof-CE can honor (pull in) a pull request.
Any contributor that is willing to participate, as evident by his/her previous contributions, to woof-CE can also become a member (upon approval).
I'm actually disappointed that capable and active community members do not bother to contribute.

@LazY Puppy, the comment is not directed to you specifically but for the record, after the initial cloning of the woof-CE git, further bandwidth need is actually much-much lower than visiting this forum! (Git was developed in the analogue modem era )

[rcrsn51]

suggestions are implemented by the community

but how and who exactly is "the community"? I understand the idea of patch contribution, but I don't understand the authorization process. If 10 people come with patches, who sorts this out? Who does the quality control? And who has the final say on what's in and what's out?

Any one with a github account can issue a pull request.
Any of the 7 current members (pic below) of woof-CE can honor (pull in) a pull request.

Maybe I don't understand git terminology, but that does not appear to answer MochiMoppel's question.

[mavrothal]

but how and who exactly is "the community"? I understand the idea of patch contribution, but I don't understand the authorization process. If 10 people come with patches, who sorts this out? Who does the quality control? And who has the final say on what's in and what's out?

Any one with a github account can issue a pull request.
Any of the 7 current members (pic below) of woof-CE can honor (pull in) a pull request.

Maybe I don't understand git terminology, but that does not appear to answer MochiMoppel's question.

How so?
The current 7 CE member can all authorize (merge) any incoming patch (pull request) if (s)he finds it appropriate for the function/bug. Sometimes may test the code and others just approve by looking at it.
Take a look at the history of the 475 issues/pull request already discussed and settled one way or another to get a better idea.
Also notice discussions that went on before an issue is settled.

Unless we are discussing about 10 different patches about the same line of code/function. I have not seen this in big projects like Fedora or Debian but if it happens I'm sure that guided by use-case and code quality the 10 contributors and the CE members can come to a concrete result.

The same is true if we are discussing about a new feature. Though new features should be thoroughly tested before they make it into woof (savefolder is a good example). It is also important to consider that woof is mostly for puppy building and only some OS functions are in woof. Mostly those that historically BK decided to put there. Everything else in the final pupplet comes from packages and pets and is up to the puppy builder which ones to use.