Posted: Wed 28 Dec 2011, 19:43
I dont ever use finnish special characters in filenames but now I was curious to test what I can find from keyboard in dpup exprimo. So these characters should work.
READ-ONLY Archive
https://oldforum.puppylinux.com/
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
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.
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.
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
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.
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.
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.
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
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
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
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
værsgo udråbsordEDIT: Oh, I see it's corrected in 1.7.1 in Racy, Barry must have corrected this. Thanks Karl.
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 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