Slacko Puppy 5.3.1
viewnoir and no ascii chars
Tried on Slacko + lang_pack_ja-1.4.sfs and has no problem.zigbert wrote:There seems to be an issue with viewnoir......
Works fine for filenames containing only english chars
So, it is not the issue of the vewnoir itself.
I have not tried the lang_pack_all yet.
- Attachments
-
- viewnior.png
- Japanese file name
- (25.01 KiB) Downloaded 1628 times
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Re: viewnoir and no ascii chars
But fails under en_US locale. en_US.UTF-8 is OK.shinobar wrote:Tried on Slacko + lang_pack_ja-1.4.sfs and has no problem.
- Attachments
-
- viewnior_en_US.png
- Fails under en_US (no UTF-8).
- (7.77 KiB) Downloaded 1592 times
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Re: viewnoir and no ascii chars
en_US.UTF-8 is OK except the title bar.
- Attachments
-
- viewnior_en_US_utf8.png
- Under en_US.UTF-8. OK except the title bar.
- (14.2 KiB) Downloaded 1572 times
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Re: viewnoir and no ascii chars
Confirmed on the native(without lang_pack) Slacko 5.3.1 MAIN with RAM mode.shinobar wrote:en_US.UTF-8 is OK except the title bar.
Of course the Japanese filename is unreadable because of lacking the font, but no problem in showing the image.
To set the locale with UTF-8, choose 'en (English)' or any language on the Country wizard. Tick on 'UTF-8' checkbox appears on the next window.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
- Iguleder
- Posts: 2026
- Joined: Tue 11 Aug 2009, 09:36
- Location: Israel, somewhere in the beautiful desert
- Contact:
01micko, here's the fix for the Slackware libpng, which is a 'lil bit smaller:
I added this to the libpng FIXUPHACK and now stuff seem to compile just fine!
Code: Select all
ln -s libpng14.pc ./usr/lib/pkgconfig/libpng.pc
ln -s libpng14 ./usr/include/libpng
ln -s libpng/png.h ./usr/include
ln -s libpng/pngconf.h ./usr/include
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
Re: viewnoir and no ascii chars
Ok, so this is the trickshinobar wrote:To set the locale with UTF-8, choose 'en (English)' or any language on the Country wizard. Tick on 'UTF-8' checkbox appears on the next window.

I meant that this option was available in the main window earlier ? Maybe I wrong....
If I set it to nb_NO I don't get a second window.
Sigmund
Re: viewnoir and no ascii chars
Wow! it is the bug of the 'Country wizard' i have to fix.zigbert wrote:If I set it to nb_NO I don't get a second window.
Use the 'Choose locale' instead

EDIT: Updated firstrun-1.9.6.pet (1 Jan 2012)
http://www.murga-linux.com/puppy/viewtopic.php?t=58312
Last edited by shinobar on Sun 01 Jan 2012, 05:54, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Sorry if this comment is late...
Sadly, I don't have a working Dell server with Fusion MPT interfaces to test
Aitch
Yes, actually Adaptec AIC-7892A U160/m....and I'm not booting from harddrive mbr/grub, as I'm using noryb's win installer version, though boot is finding the savefile/s and sfs, so I presumed it would, as I had an earlier Dell server working OK with a previous scsi booting puppy that Barry didtempestuous wrote:I'm unfamiliar with Woof, but that's interesting. It appears that a basic set of SCSI drivers (as specified by Barry) is then included in the initrd.01micko wrote:Barry has an option in Woof.. Boot scsi, I accepted this for k2.6.29.4 and in this release k2,6,37.6
Obviously the 3 new Fusion SCSI drivers are not included, so if desired these would need to be manually inserted (and modules.dep updated) ...
or maybe the Woof script could be modified to automatically include these new modules?
But anyway, no one has specifically asked for boot support from a Fusion SCSI interface at this stage.
Yes, it appears that booting from SCSI works, that's great ...01micko wrote:Aitch has reported success on an old server box of his a few pages back.
but of course Aitch's SCSI hardware uses the aic7xxx SCSI driver, nothing to do with the 3 new drivers.
Sadly, I don't have a working Dell server with Fusion MPT interfaces to test
Aitch

Are your eyes painted on? Or is there paint in your eyes? (yes, pathetic art humour!zigbert wrote:GrubConfig is not found in the menu. If this is intentional (to only offer Grub4Dos), there is a message in the universal installer mentioning GrubConfig.
Sigmund


I knew it was there as I did test for Sage, it's in the announcement thread.
- Attachments
-
- legacygrub.png
- (43.7 KiB) Downloaded 1250 times
Puppy Linux Blog - contact me for access

Truly, my eyes are covered by dark oil painting.
But why is Grub4Dos placed in 2 dfferent menus, while Legacy Grub only in System menu? Please give me a logic answer

- Attachments
-
- forum.png
- (152.25 KiB) Downloaded 1190 times
Hi zigbert,
I assume that the placement of Grub4Dos in 2 different menus was a trivial oversight but, now you have pointed this out, I have used Pmenu to hide both entries. I can temporarily unhide them if I want to make any changes.
As regards the "green" I seem to recall 01micko commented "you'll love it or hate it". Personally, I love it.
My regards and thanks for all your Puppy programs.
I assume that the placement of Grub4Dos in 2 different menus was a trivial oversight but, now you have pointed this out, I have used Pmenu to hide both entries. I can temporarily unhide them if I want to make any changes.
As regards the "green" I seem to recall 01micko commented "you'll love it or hate it". Personally, I love it.
My regards and thanks for all your Puppy programs.
Puppy is confusing as always ...But why is Grub4Dos placed in 2 dfferent menus, while Legacy Grub only in System menu? Please give me a logic answer Twisted Evil
Slacko-5.3.1 /usr/share/applications/Grub4DosConfig.desktop
has got two entries for the /etc/xdg/menus/hierarchy :
Categories=X-SystemMemory;X-SetupUtility
/usr/share/applications/Grub-bootloader-config.desktop
Categories=X-SystemMemory
while Racy-5.2.2 Grub4DosConfig.desktop for example
has only one entry :
Categories=X-SystemMemory
(version 1.7.1)
Grub-bootloader-config.desktop
Categories=X-SystemMemory
Applying this code to change the submenu entries to show up with 1 entry already by the argument 1 ( $1= 1 )
Code: Select all
#!/bin/sh
N="$1"
[ ! "$N" ] && N=5
[ "`echo "$N" | grep '[^0-9]'`" ] && exit 106
cd /etc/xdg/menus
#for i in * ; do echo $i; sed -i 's#inline_limit="[0-9]*"#inline_limit="5"#g' $i; done
SED1='inline_limit="[0-9]*"'
SED2='inline_limit="'$N'"'
for i in * ; do echo $i;
if [ -f "$i" ];then
if [ -w "$i" ];then
sed -i "s#${SED1}#${SED2}#g" "$i"
[ "$?" != '0' ] && exit 107
fi;fi
done
fixmenus
#[ "$?" != '0' ] && exit 108
jwm -restart
[ "$?" != '0' ] && exit 109
exit 0
At both Puppies the /etc/xdg/menus/hierarchy are same :
Code: Select all
#the menu hierarchy used in official Puppy v2.14
#'X-' categories are unofficial, Puppy-specific.
#w482 changed top-level name 'Calculate' to 'Business'.
System :Memory X-SystemMemory
Setup :Utility X-SetupUtility
Hmm.. the technical answer is that there are 2 category entries in the Grub4DosConfig.desktop file:zigbert wrote:![]()
Truly, my eyes are covered by dark oil painting.
But why is Grub4Dos placed in 2 dfferent menus, while Legacy Grub only in System menu? Please give me a logic answer
Code: Select all
Categories=X-SystemMemory;X-SetupUtility

EDIT: Oh, I see it's corrected in 1.7.1 in Racy, Barry must have corrected this. Thanks Karl.
Puppy Linux Blog - contact me for access
værsgo udråbsordEDIT: Oh, I see it's corrected in 1.7.1 in Racy, Barry must have corrected this. Thanks Karl.
også i formerne: værsågod, værs'god, værsgo'
Here you go
Poohæ posting such in bug section


Happens , that the many usability bug posts colored onto me once or twice too .


I think it is meant good to put several categories into the .desktop files because the SUB MENU NAMING X-SystemMemory would probably fit to snapmergepuppy but not to a bootloader installer . P-SystemBoot category still to introduce

-
- Posts: 452
- Joined: Thu 20 Mar 2008, 01:48
syslinux
is it just me or when i try to install slacko into 4gb flashdishk formatted as FAT, syslinux didnt run... so i have run sys linux from lucid 528 ???
error code :
possibly unsafe /tmp/ permissions
EDIT : slacko 5.3
EDIT 2 : this solve the problem
#chmod 1777 /tmp
error code :
possibly unsafe /tmp/ permissions
EDIT : slacko 5.3
EDIT 2 : this solve the problem
#chmod 1777 /tmp
Last edited by Master_wrong on Mon 02 Jan 2012, 13:54, edited 1 time in total.
Cluster-Pup v.2-Puppy Beowulf Cluster
[url]http://www.murga-linux.com/puppy/viewtopic.php?p=499199#499199[/url]
[url]http://www.murga-linux.com/puppy/viewtopic.php?p=499199#499199[/url]
Grub4Dos menu
My intentionzigbert wrote:But why is Grub4Dos placed in 2 dfferent menus, while Legacy Grub only in System menu? Please give me a logic answer

I would like the Grub4Dos menu at the same place of the installers that is 'Setup' for convenience.
But also need at 'System' where the legacy grub is.
But i think purging the legacy grub is better solution because it makes confuse for the users.
Nowadays Grub4Dos covers most of all the function what the legacy grub does.
I know some linux power users love the legacy. In that case, they can get it from the PPM.
Other case is he already has the legacy grub installed as the boot loader and want to rewrite only the menu.lst. In this case, he can do it manually using a text editor. Anyway he must do so even if the legacy grub config is available, isn't it?
(I have ever tried adding a function for the Grub4Dos config to generate legacy compatible menu.lst. But i found it is difficult to do it automatically. The user must correct the number of (hd0,0) or something manually.)
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
I have done it in two ways >(I have ever tried adding a function for the Grub4Dos config to generate legacy compatible menu.lst. But i found it is difficult to do it automatically. The user must correct the number of (hd0,0) or something manually.)
Code: Select all
echo "Enter the rootdrive ie '/dev/sda1' :
"
read ROOTPART
PARTNUMBER=`echo $ROOTPART | grep -o -e '[0-9]*$'`
echo ROOTPART=$ROOTPART PARTNUMBER=$PARTNUMBER
GRUBPART=$((PARTNUMBER-1))
echo GRUBPART=$GRUBPART
PARTCHAR=`echo $ROOTPART | sed 's#[0-9]##g' | rev | cut -c 1 |rev`
echo PARTCHAR=$PARTCHAR
case $PARTCHAR in
a)GRUBDRIVE=0;;
b)GRUBDRIVE=1;;
c)GRUBDRIVE=2;;
d)GRUBDRIVE=3;;
e)GRUBDRIVE=4;;
f)GRUBDRIVE=5;;
g)GRUBDRIVE=6;;
h)GRUBDRIVE=7;;
i)GRUBDRIVE=8;;
esac
echo GRUBDRIVE=$GRUBDRIVE
Code: Select all
func10(){
if [ "$rootpart" ];then
echo rootpart=$rootpart
#ie sda1
partition=`echo $rootpart | sed 's#[[:alpha:]]##g'`
echo partition=$partition
#ie 1
grubpartition=$((partition-1))
echo grubpartition=$grubpartition
#ie 0
rootdrive=${rootpart:2:1} #first char 0 one char
echo rootdrive=$rootdrive
#ie a
c=0
for i in {a..z};do
if [ "$i" = "$rootdrive" ];then
grubdrive=$c
break
fi
c=$((c+1))
done
return 0
else
echo "WARN : code could not filter the drive"
return 141
fi
}
wd="`pwd`"
if [ "`echo "$wd" |grep '/mnt/'`" ];then
rootpart=`echo "$wd" | grep -o -e '/[shmflr]d.[0-9]/' | tr -d '/'`
func10 || exit 142
else
rootpart=`rdev |grep -o -e '/[shmflr]d.[0-9]' |tr -d '/'`
func10 || exit 143
fi
Code: Select all
for k in $kernels ;do
kernel=${k##*/}
echo $kernel
kernelpattern=`echo "$kernel" |sed 's/\([[:punct:]]\)/\\\\\1/g'`
echo "$kernelpattern"
if [ ! "`grep "$kernelpattern" ./grub/menu.lst`" ];then
echo "
title kernel $kernel on $rootpart
root (hd${grubdrive},${grubpartition})
kernel /boot/$kernel root=/dev/$rootpart ro $kernelline
" >> ./grub/menu.lst
fi
done