On every other Puplet I've used, jwm config is in /etc/xdg (and I don't recall where the default-app settings are)... but I can't find 'em in pUPnGO!
Code: Select all
#sc0ttman start
check_sfs_size () {
# assume it's all gonna work
TOO_BIG=false
# $1 is the SFS FILE
echo $1
SFSFILE="${1}"
# get the PUPMODE
. /etc/rc.d/PUPSTATE
# note, these vars are used from PUPSTATE
PUPMODE=$PUPMODE
SAVE_LAYER=$SAVE_LAYER
# check if save file is being used
if [ $PUPMODE -eq 12 ] || [ $PUPMODE -eq 13 ];then
# get save space in bytes
PUPSAVESPACE=`df -B 1 | grep $SAVE_LAYER | awk '{print $4}'`
# keep only the numbers, if needed
#PUPSAVESPACE=$(echo "$PUPSAVESPACE" | sed "s/[^0-9]//g")
# get size of sfs file in bytes
SFSSIZE=$(stat -c %s "$SFSFILE")
# get required free space (around 3x the size of sfs file)
REQUIREDSPACE=$(($SFSSIZE * 3))
# if free space is less than required space
if [ $PUPSAVESPACE -lt $REQUIREDSPACE ];then
# cannot load sfs file
TOO_BIG=true
else
# loading sfs will be ok
TOO_BIG=false
fi
fi # end if save file is being used
}
# sc0ttman endCode: Select all
# sc0ttman start - check save file space before loading
check_sfs_size "$REPLY_CHAR"
if [ "$TOO_BIG" = true ];then
TEXT="Warning: The SFS file '$(basename $SFSFILE)' may be too big for your save file.\nAre you sure you want to load it?"
yesno_fc
if [ "$REPLY_CHAR" = "No" ];then
TEXT="You can make your save file bigger here:\n\nMenu->Utility->Resize personal storage file\n\n"
message_fc
break
fi
fi
REPLY_CHAR="${1}"
# sc0ttman endCode: Select all
else #silent run
REPLY_CHAR="${1}"
FILENAME=$(basename $REPLY_CHAR)
fiYou could start with the zdrv from Puplite 4.0 - it is a standard 4.2 zdrv, but I added most, if not all, of the extra drivers I could find for 2.6.25.16 (and I will add the one posted above, too!)goingnuts wrote:Would like to include as many drivers as possible in the next build...
Code: Select all
#replace: "cp -u $1 $2" with:
[ "$1" -nt "$2"] && cp -f $1 $2 || cp $1 $2
#force cp if $1 is newer
#rely on cp failure if $2 is newer
#but still cp in case $2 does not exist
Then tried to follow code from jemimah´s pwireless2 using a static build of wpa_cli and wpa_supplicant - but still not working (always)...Would be nice to have in pUPnGo someday... 
But is that the old 2.6 something I don't remember which version it was but it was not one of the later version when I tried to use it some week ago.080211: Special build with TC as GUI.
if you still have your wireless tools package, there is a multicall binary build (like busybox) that will save some space (however this will also make it an easy port to busybox next time I have an hour or so and a decent internet connection) The wireless tools source is pretty easy to follow IIRC, so it shouldn't be too hard to track down the source of "unknown"... maybe even make some shell parsability improvements to the output.goingnuts wrote:Getting closer to wireless in pupngo although not quite there yet. Managed to compile iwconfig, iwlist and wpa_supplicant static. Created a script that succesfully connect my zd1211 usb wireless interface to WPA and WPA_PSK wireless in org. P412.
In pupngo drivers load but was unable to do a ifconfig wlan0 up. Response was the cryptic "SIOCSIFFLAGS: No such file or directory"
Solution was to manually install zd1211 firmware archive from /lib/modules/all-firmware.
Anyone know which part of Puppy is responsible for installing the firmware-packets? Is it udevd, kernel or something else?
Next problem now is that iwlist do not report found network types correctly in pupngo - and that breaks my connect-script - as the reported types are "unknow". Strange the iwlist works in org. P412 but not in pupngo...
I did try to use org. modprobe but did no difference...