Wary/Racy 5.3RC2 (5.2.91)

[L18L]

Setting of hostname is in QuickSetup now.

But should not be in Change Resolution

---------

PPM: wrong path for langpacks

Spider mode enabled. Check if remote file exists.
--2012-03-12 18:41:40-- http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-noarch/langpack_fr-20120307.pet
Resolving distro.ibiblio.org (distro.ibiblio.org)... 152.19.134.43
Connecting to distro.ibiblio.org (distro.ibiblio.org)|152.19.134.43|:80... connected.
HTTP request sent, awaiting response...
HTTP/1.0 404 Not Found
Content-type: text/html
Connection: keep-alive
Date: Mon, 12 Mar 2012 17:40:24 GMT
Server: lighttpd/1.4.26
Remote file does not exist -- broken link!!!

http://distro.ibiblio.org/quirky/pet_packages-noarch/langpack_fr-20120307.pet

_________

Changes we had made in
/usr/share/sss/initrd_strings/initrd_strings.de (early boot messages)
are NOT automatically used.
edited: OK, I have changed them manually using "lang2initrd de"
_______

[Billtoo]

.

[Billtoo]

I made an sfs file which contains the newest
smplayer-0.7.1,smtube-1.0, and qt-4.8.0
If you load smtube you can search youtube for any videos that you
would like to play/record and it will call smplayer to play the video.
The F11 function key in smplayer also calls smtube.

The download link for smplayer-0.7.1-i686-racy.sfs is:





http://www.datafilehost.com/download-3cbea789.html

[esmourguit]

Bonjour à tous,

First test of Racy 5.2.2.9

Frugal install on ext3 partition : I copied files initrd.gz, vmlinuz and puppy_racy_5.2.2.9.sfs in directory Racy5229 and modified menu.lst of Grub4dos. No pupsave file.
I run new Racy 5.2.2.9 from grub4dos.

The boot was normal, but when the desktop is displayed, the proposed resolution was 1280x1024 for my old 17" RTC monitor whereas usually all previous versions offered me 1080x768.

In the window Quicksetup start, I changed the resolution to be 1024x768, chosen locale, keyboard and time zone.
I validated (it takes a relatively long time after validation and before displaying the popup listing the changes and to click on it, which may suggest that the machine no longer works),and unfortunately the resolution change has not turned out as expected.

I restarted X, without success.

So I launched the Xorg Wizard to return to the prompt, launched Xorgwizard, test equipment and I finally have the desired resolution. But the display is shifted to the right.

Cordialement

[peebee]

Hi Barry

Could you check the download links for Wary 5.2.2.7 please?

The links in your blog give 404 errors....

and if you go to Ibiblio then the devx in quirky/test is showing as just 100K big....

Thanks
PeeBee

[npierce]

Barry, thanks for adding recent fixes to Woof and web pages.

By the way, when I opened the April issue of Linux Format, I was pleased to see who was "top dog" in their review of distros for older hardware.

[vicmz]

quicksetup and xdelta spanish locales updated

[BarryK]

Setting of hostname is in QuickSetup now.

But should not be in Change Resolution

---------

PPM: wrong path for langpacks

Spider mode enabled. Check if remote file exists.
--2012-03-12 18:41:40-- http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-noarch/langpack_fr-20120307.pet
Resolving distro.ibiblio.org (distro.ibiblio.org)... 152.19.134.43
Connecting to distro.ibiblio.org (distro.ibiblio.org)|152.19.134.43|:80... connected.
HTTP request sent, awaiting response...
HTTP/1.0 404 Not Found
Content-type: text/html
Connection: keep-alive
Date: Mon, 12 Mar 2012 17:40:24 GMT
Server: lighttpd/1.4.26
Remote file does not exist -- broken link!!!

http://distro.ibiblio.org/quirky/pet_packages-noarch/langpack_fr-20120307.pet

_________

Changes we had made in
/usr/share/sss/initrd_strings/initrd_strings.de (early boot messages)
are NOT automatically used.
edited: OK, I have changed them manually using "lang2initrd de"
_______

Thanks, fixed. I will announce on my blog.

[BarryK]

Changes we had made in
/usr/share/sss/initrd_strings/initrd_strings.de (early boot messages)
are NOT automatically used.
edited: OK, I have changed them manually using "lang2initrd de"
_______

After you have changed the locale in QuickSetup, a window pops up asking if you want to translate initrd.gz. If you accepted the offer, it should have run lang2initrd.

However, you won't get that offer if booted from CD, as initrd.gz on CD can't be changed.

[BarryK]

As MoManager seems to include in the langpack only .mo files made through MoManager, the langpacks I make have the 44 files I made with MoManager so far but exclude the 50 .mo files of existing translations, some of them for applications not included in the list of .mo files (HomeBank, ePDFView, AbiWord etc.), that's why the created langpack is less than 200k. I also checked the generated folder langpack_es-xxxxx to find out why my new langpack doesn't install my translations in 'applications' and 'desktop-directories', these folders appear with a '.in' suffix, for example appliactions.in, so when I install my langpack I get an 'applications.in' folder outside the 'applications' directory. I modified the generated folder langpack_es-xxxxx (removed '.in' folder suffix and added existing translations to what has been done so far) and used don570's Right-Click to produce a langpack (over 1MB), then tested without pupsave and it worked, I could see the desktop, the menu and great part of the applications in Spanish. I also tried including the Spanish dictionary for AbiWord, the langpack installs the dictionary but for now I don't know how to set it as default. I attach that langpack to this post so that you can check it and let me know how I'm doing.

If you look in 'pinstall.sh' in the PET langpack, you will see how those .in suffix directories are processed.

The reason for having them in .in folders is so that when someone installs a langpack, they don't get menu entries for applications that are not installed.

[vicmz]

Actually I don't understand anything about programming, and (just in case) I wasn't being critical either, I just told about my experience using MoManager. I should've guessed those .in extensions served for a particular purpose

By the way, these mini-translations are too long for your blog comment form, so I put them here and commented the post link in the blog post:

Portuguese:

Code: Select all

AVAILMSG="Há um pacote \Zb${AVAILPACK}\ZB apropriado no respositório de PETs \Zbnoarch\ZB, na categoria \ZbConfiguração\ZB. Após ter uma conexão a Internet, clique o ícone \Zbinstalar\ZB da

[OscarTalks]

This may be something that is not unique to Racy (though it is happening for me on 5.2.2.9 right now) but perhaps someone can shed some light.

I like to run 2 sound cards in my computers so I can route audio from different applications to different places.

So I have "Soundcard A" (which is integrated on the motherboard) and "Soundcard B" (which is a PCI card).

My problem is that the process of establishing the default soundcard appears to be random.

At first I thought that the Multiple Sound Card Wizard just wasn't working, but I see that there is a file at /etc/asound.conf which appears to define the default soundcard.

But it only specifies a card and device NUMBER eg:

defaults.pcm.card 1
defaults.pcm.device 0

Am I looking at the correct file for this?
Note that the cards are not named.

The big problem arises from the fact that at each boot-up the process of allocating the card numbers seems totally random. Sometimes Soundcard A will be given the number 0 and Soundcard B will be given the number 1 and on another boot-up they can be allocated the other way round.

Would it be possible to have the file set the default card by specifying it by name?

Alternatively (and probably the ideal solution), is there a way to ensure that the allocation of number to name remains the same at every boot-up?

UPDATE - Think I may have solved it. Running the ALSA Wizard (despite my reluctance because of the scary dialog that pops up) seems to have enabled me to lock down the allocation of "Card 0" to the integrated soundcard on the motherboard.

I see that lines have been added to the file /etc/modprobe.d/alsa.conf thus:-

# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF version 1.0.21 ---
alias snd-card-0 snd-intel8x0
alias sound-slot-0 snd-intel8x0
# --- END: Generated by ALSACONF, do not edit. ---

The other soundcard does disappear from the options displayed in Multiple Sound Card Wizard when you do this, so I was worried that I may have lost my internal connection to it, but on re-boot they were both there again and on a couple of re-boots the order was staying the same.
I then had to use Multiple Sound Card Wizard (again) to change the default back from "Card 1" to "Card 0". This creates a new file at /etc/asound.conf leaving the previous one there with the suffix "old".

[Billtoo]

I did a manual frugal install of 5.2.2.9 to a 4gb flash drive.
I found some wallpaper that suits racy I think
No problems so far, working well.

[BarryK]

This may be something that is not unique to Racy (though it is happening for me on 5.2.2.9 right now) but perhaps someone can shed some light.

I like to run 2 sound cards in my computers so I can route audio from different applications to different places.

So I have "Soundcard A" (which is integrated on the motherboard) and "Soundcard B" (which is a PCI card).

My problem is that the process of establishing the default soundcard appears to be random.

At first I thought that the Multiple Sound Card Wizard just wasn't working, but I see that there is a file at /etc/asound.conf which appears to define the default soundcard.

But it only specifies a card and device NUMBER eg:

defaults.pcm.card 1
defaults.pcm.device 0

Am I looking at the correct file for this?
Note that the cards are not named.

The big problem arises from the fact that at each boot-up the process of allocating the card numbers seems totally random. Sometimes Soundcard A will be given the number 0 and Soundcard B will be given the number 1 and on another boot-up they can be allocated the other way round.

Would it be possible to have the file set the default card by specifying it by name?

Alternatively (and probably the ideal solution), is there a way to ensure that the allocation of number to name remains the same at every boot-up?

UPDATE - Think I may have solved it. Running the ALSA Wizard (despite my reluctance because of the scary dialog that pops up) seems to have enabled me to lock down the allocation of "Card 0" to the integrated soundcard on the motherboard.

I see that lines have been added to the file /etc/modprobe.d/alsa.conf thus:-

# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF version 1.0.21 ---
alias snd-card-0 snd-intel8x0
alias sound-slot-0 snd-intel8x0
# --- END: Generated by ALSACONF, do not edit. ---

The other soundcard does disappear from the options displayed in Multiple Sound Card Wizard when you do this, so I was worried that I may have lost my internal connection to it, but on re-boot they were both there again and on a couple of re-boots the order was staying the same.
I then had to use Multiple Sound Card Wizard (again) to change the default back from "Card 1" to "Card 0". This creates a new file at /etc/asound.conf leaving the previous one there with the suffix "old".

Yes, that does seem a bit roundabout to fix your problem, but I don't really know any simple fix, other than perhaps adding some documentation.

[antiloquax]

.

[Karl Godt]

Yes, that does seem a bit roundabout to fix your problem, but I don't really know any simple fix, other than perhaps adding some documentation.

My one "onboard's soundcards" use mostly two drivers , especially the snd-intel8x0 + snd-mpu401 or snd-wavefront , sometimes three and there are snd-pcsp and pcspkr kernel modules possible to enable .

This random detection of the modaliases in rc.sysinit probably could get sorted by sort command .

But my experience is that the many triggerings to modprobe drivers queue up before the CPU and get processed by the CPU in a unordered mode even filtering with the sort binary . I observed this especially with one core intel cpus .

a wait function for pup_event_backend_modprobe would look something like

Code: Select all

ALSACONFFILES="/etc/modprobe.d/alsa-base.conf /etc/modprobe.d/alsa.conf"
snd_order_func(){
if [ "`echo "$MODULE" |grep -E '^snd'`" ] ;then
listed_soundcards=`grep -e '^alias snd\-card\-[0-9]*' $ALSACONFFILES | awk '{print $2" "$3}' |sort -u`
[ "$listed_soundcards" ] || return 0
snd_card_nrs=`echo "$listed_soundcards" |awk '{print $1}' |cut -f3 -d'-'`
current_nr=`echo "$listed_soundcards" | grep "${MODULE//_/-}" |awk '{print $1}' |cut -f3 -d'-'`
already_loaded=`lsmod |grep '^snd_' |awk '{print $1}'`

for n in $snd_card_nrs;do
soundcard=`echo "$listed_soundcards" | grep -o "\-$n .*" |awk '{print $2}' |head -n 1`
if [ "${soundcard//-/_}" = "$MODULE" -a "$n" = '0' ];then return 0;fi #first module
c=$((n-1));h=$((h+1))
for zzz in `seq 1 1 $n`;do
temp_soundcard=`echo "$listed_soundcards" | grep -o "\-$zzz .*" |awk '{print $2}' |head -n 1`
until [ "`lsmod | grep "${temp_soundcard//-/_}"`" ];do sleep 1s;done
pattern=`echo "$listed_soundcards" |head -n $h`
included=`echo "$pattern" | grep "${MODULE//_/-}"`
[ "$included" ] && return
done
done
fi
}

Another idea would be a bootparameter pfix=nosound
with code for rc.sysinit like

Code: Select all

pfix=`cat /proc/cmdline |grep -o 'pfix=.* |cut -f 1 -d ' '`
params=`echo "$pfix" |sed 's/pfix=//' |tr ',' ' '`
for param in $params;do
case $param in
nosound)echo "NOSOUND='yes'" >>/etc/rc.d/PUPSTATE ;;
novideo)echo "NOVIVEO='yes'" >>/etc/rc.d/PUPSTATE ;;
esac

and code for pup_event_backend_modprobe
like

Code: Select all

[ "$NOSOUND" = 'yes' -a "`echo "$MODULE" |grep -E '^snd|^sound'`" ] && exit $BECAUSE_NOSOUND
videodrivers=`modprobe -l | grep 'drm'` 
videodrivers=`echo "$videodrivers" |cut -f1 -d'.'|rev|cut -f1 -d'/'|rev`
[ "$NOVIDEO" = 'yes' -a "`echo "$videodrivers" |grep "$MODULE"`" ] && exit $BECAUSE_NOVIDEO

That would enable a script in $HOME/Startup to modprobe the drivers in the wanted order like /root/Startup/Sound.sh .

Code: Select all

#!/bin/sh

#Personal Sound script
# ie to unload modules by the rmmod or modprobe -v commands
# or to load modules by the modprobe [-v] command
# see " [p]man modprobe " for more details .
#It is also advised to run /usr/sbin/bootmanager
# from the System Menu , to force the loading/blacklisting of modules .

#Don't forget to add a line with /etc/init.d/[##_]alsa [start|stop].

#In case on no sound modules loaded, 
# the sound applet in the tray (/usr/[local/]bin/retrovol) tends to exit .
#Of course, you can run alsawizard ,too .

[npierce]

If Multiple-Sound-Card-Wizard doesn't find any sound card, it will create a corrupt /etc/asound.conf file if user clicks "OK".

Of course, if it cannot find any sound cards, there is a worse problem somewhere else, so the corrupt asound.conf file doesn't seem as bad by comparison. If the user could fix the initial problem so that a sound card could be found, then run Multiple-Sound-Card-Wizard again to get a good asound.conf file, life would be good.

Unfortunately, Multiple-Sound-Card-Wizard is confused by the bad asound.conf file it created and will not find any sound cards until the bad file is fixed or deleted.

And while asound.conf is bad, aplay, alsamixer, and probably other stuff will fail. So even if the user has fixed the initial problem and perhaps even rebooted, she still will have no sound.

The bad asound.conf file created by Multiple-Sound-Card-Wizard looks like this:

Code: Select all

defaults.pcm.card 
defaults.pcm.device 

Note that the number at the end of each line is missing, so the next time you run Multiple-Sound-Card-Wizard the first line of the error message will to be:

Code: Select all

ALSA lib conf.c:976:(parse_value) card is not a string

(The line number (976 in the example) will be different for different versions of the ALSA library.)
That error message actually comes from aplay -l, which Multiple-Sound-Card-Wizard calls upon to get its list of sound cards.

alsamixer.bin gives the same error message, but the alsamixer wrapper script gives this error:

Code: Select all

alsamixer.bin: option requires an argument -- 'c'

since it could not find the card number in the /etc/asound.conf file.

Of course, most users probably just run Multiple-Sound-Card-Wizard from the menu, and won't see any error messages unless they look at the /etc/xerrs.log file. Users who run Multiple-Sound-Card-Wizard from within alsawizard will never see any error messages, since that script sends them off to /dev/null.

The proposed fix simply places a message in the list window stating that the utility was unable to find any sound card, and it removes the "OK" button from the dialog. No asound.conf file is created or overwritten when the user clicks "Cancel".

There is also a small change to keep /tmp/mscw.tmp from growing each time the utility is used.

The attached patch is based on the current PET at:
http://distro.ibiblio.org/quirky/pet_pa ... mscw-1.pet

[BarryK]

Wary and Racy 5.2.90 (5.3 Release Candidate 1) is available:

http://bkhome.org/blog/?viewDetailed=02759

npierce, your last post missed it, I will look at that tomorrow, thanks for the info.

[BarryK]

I was informed that we have to use gxmessage instead of xmessage for non-English Puppy. So, I have built Wary and Racy 5.2.90 with gxmessage (and xmessage a symlink to gxmessage).

However, disciple has posted to my blog that this in the X resources, I presume in /root/.Xresources, will enable xmessages to display non-English text properly:

Code: Select all

*international: true

Is this true?

Note, Wary and Racy still have xmessage, at /usr/X11R7/bin -- but the /usr/bin/xmessage symlink is found beforehand. So, just delete the symlink and you have the old xmessage back.

[L18L]

...

Code: Select all

*international: true

Is this true?...

I am thinking it is neither true nor false but simply not necessary.
At least not with racy 5.2.2.9 , see image and/or test yourself

Code: Select all

# xmessage Γαζέες καὶ μυ