starhawk: thx
greengeek: I found that mp (minimal profit) text editor seems to work ok with copy paste between applications without crashing the source application - still a mystery why beaver and other gtk1.2 apps does that. mp has a different way of selecting text (right mouse button and mark outer points of that is to be selected) but normal shift-key and arrows/ctrl-c/ctrl-v works as well.
Attached tar.gz file - use "tar -xzf mp-3.3.18b.tar.gz" to unpack and copy the extracted files to /
pUPnGO 2012
cs423x was carried over from 431 into 432 it looks like. At least, the source tarball isn't around in /lib/modules/all-firmware/ ... however...
http://www.alsa-project.org/main/index. ... ule-cs4236 should be of some significant use
...lifted SNS from Puplite5. The entire set of icons that should be there are not, but everything else ought to be. Obvious dependencies are iwconfig and ifconfig -- I've not included those because I'd be quite surprised if you didn't already have them.
Also not included is a symlink. /usr/sbin/sns should be linked to ../local/simple_network_setup/sns .
Everything else needed should be in there. I've done my usual trick of preserving heirarchy... files are as follows:
../SNS-puplite5/etc/simple_network_setup/
../SNS-puplite5/usr/local/simple_network_setup/help_security
../SNS-puplite5/usr/local/simple_network_setup/rc.network
../SNS-puplite5/usr/local/simple_network_setup/sns
../SNS-puplite5/usr/sbin/ndiswrapper
../SNS-puplite5/usr/sbin/ndiswrapper-buginfo
../SNS-puplite5/usr/sbin/wpa_cli
../SNS-puplite5/usr/sbin/wpa_passphrase
../SNS-puplite5/usr/sbin/wpa_supplicant
I did not include ndiswrapperGUI.sh because it does not work. AFAIK one cannot copy or archive symlinks properly, so that's why I didn't copy the one mentioned above. All of that said, once you backport the scripts all to GTK1 and stick in iwconfig and ifconfig (if not pulling from Puppy 420, you might want to double-check the commands -- also I don't know their deps) it *should* work fine.
You get a proper tarball of this stuff, since Xarchiver (no Pupzip in Puplite5) doesn't want to gz a directory for some reason. I've made the tarball in Windows XP using 7zip and gzip together.
...and last, but not least...
THANK YOU for putting up with my inane never-ending questions
I really do appreciate it, and I am remiss in not saying that sooner.
http://www.alsa-project.org/main/index. ... ule-cs4236 should be of some significant use
...lifted SNS from Puplite5. The entire set of icons that should be there are not, but everything else ought to be. Obvious dependencies are iwconfig and ifconfig -- I've not included those because I'd be quite surprised if you didn't already have them.
Also not included is a symlink. /usr/sbin/sns should be linked to ../local/simple_network_setup/sns .
Everything else needed should be in there. I've done my usual trick of preserving heirarchy... files are as follows:
../SNS-puplite5/etc/simple_network_setup/
../SNS-puplite5/usr/local/simple_network_setup/help_security
../SNS-puplite5/usr/local/simple_network_setup/rc.network
../SNS-puplite5/usr/local/simple_network_setup/sns
../SNS-puplite5/usr/sbin/ndiswrapper
../SNS-puplite5/usr/sbin/ndiswrapper-buginfo
../SNS-puplite5/usr/sbin/wpa_cli
../SNS-puplite5/usr/sbin/wpa_passphrase
../SNS-puplite5/usr/sbin/wpa_supplicant
I did not include ndiswrapperGUI.sh because it does not work. AFAIK one cannot copy or archive symlinks properly, so that's why I didn't copy the one mentioned above. All of that said, once you backport the scripts all to GTK1 and stick in iwconfig and ifconfig (if not pulling from Puppy 420, you might want to double-check the commands -- also I don't know their deps) it *should* work fine.
You get a proper tarball of this stuff, since Xarchiver (no Pupzip in Puplite5) doesn't want to gz a directory for some reason. I've made the tarball in Windows XP using 7zip and gzip together.
...and last, but not least...
THANK YOU for putting up with my inane never-ending questions
I really do appreciate it, and I am remiss in not saying that sooner.- Attachments
-
- sns-puplite5.tar.gz
- Tarball of Simple Network Setup, liberally stolen from Puplite 5.0 (a Puppy 420 derivative).
- (158.4 KiB) Downloaded 391 times
goingnuts / starhawk
Sorry to butt in, but it may help to have a newer version of the sns script, as it supports profiles. Barry's blog
Originally you had to re-enter everything after a reboot.
I've attached the two main files from /usr/local/simple_network_setup/
I did try stripping this down to CLI level once...
but failed miserably!
Sorry to butt in, but it may help to have a newer version of the sns script, as it supports profiles. Barry's blog
Originally you had to re-enter everything after a reboot.
I've attached the two main files from /usr/local/simple_network_setup/
I did try stripping this down to CLI level once...
but failed miserably!
- Attachments
-
- rc.network.gz
- rc.network script with dummy .gz extension
- (12.96 KiB) Downloaded 397 times
-
- sns.gz
- sns script with dummy .gz extension
- (40.24 KiB) Downloaded 375 times
...back again.
Hope this is not too off-topic, but may be of interest. For some time I have been messing with 4M Linux, an odd little distro with an almost amusingly bad website.
Anyway, the full distro has plenty of faults, but I got interested in the 'core' version. 4M boots with just a bzImage and an intrd.gz.
The initrd contains:
The rcS script sets up the filesystem, profile etc. 4M uses 'addons' which are just tar.gz packages of libs and programs etc. They can be included in etc/init.d to be used straight away.
This structure is easy to clone with the vmlinuz and libs from any Puppy - I'm currently using Wary libs/kernel. I did find that it would not boot with 412 files, but I recompiled BusyBox (with everything), and that worked, so might have been a missing applet or two.
I have been using various static apps that have been posted on the pupngo threads, and have got a gui using the files pinched from pupngo 2012. I had managed to get my wifi working (using the static wpa builds), but it's not having it at the moment for some reason. Shame, because I've got Opera-Next working on it now. Oh well...
Because it is so 'barebones' it means you have to really work on finding the dependencies to get things working - the static apps are a great help though. Termcap is needed for a start.
There is no persistence, (no way to save), but it is just for experimenting with.
Might be useful as a test bed, especially for static apps.
I've attached the rcS in case it takes anyones interest.
Hope this is not too off-topic, but may be of interest. For some time I have been messing with 4M Linux, an odd little distro with an almost amusingly bad website.
Anyway, the full distro has plenty of faults, but I got interested in the 'core' version. 4M boots with just a bzImage and an intrd.gz.
The initrd contains:
Code: Select all
init (symlink to BB)
/dev/console null tty1...tty6
/etc/init.d/ inittab
/init.d/rcS
/lib/ld-2.10.1.so
ld-linux.so.2
libc-2.10.1.so
libc.so.6
libm-2.10.1.so
libm.so.6
/sbin/busybox init (symlink to BB)
This structure is easy to clone with the vmlinuz and libs from any Puppy - I'm currently using Wary libs/kernel. I did find that it would not boot with 412 files, but I recompiled BusyBox (with everything), and that worked, so might have been a missing applet or two.
I have been using various static apps that have been posted on the pupngo threads, and have got a gui using the files pinched from pupngo 2012. I had managed to get my wifi working (using the static wpa builds), but it's not having it at the moment for some reason. Shame, because I've got Opera-Next working on it now. Oh well...
Because it is so 'barebones' it means you have to really work on finding the dependencies to get things working - the static apps are a great help though. Termcap is needed for a start.
There is no persistence, (no way to save), but it is just for experimenting with.
Might be useful as a test bed, especially for static apps.
I've attached the rcS in case it takes anyones interest.
- Attachments
-
- rcS.gz
- (13.72 KiB) Downloaded 396 times
Posted a first try of SNS with gtkdialog1 here. Not so much work going to gtk1 but removing xmessage-stuff and enabling ash-only took time. Also had to compile a newer dhcpcd, a static ethtool+ifplugstatus. But seems to work. Used the Puplite version but plan to go for the version Keef pointed at.
Keef: You mentioned you needed Termcap - what exactly are you missing? Is it the termcap.info files?
And the 4M looks worth a closer look - thanks!
starhawk: I was wondering if the sound is a driver missing or the absent of ALSA that gives problems? I do not know if ALSA can be done static at all - but as you are already having some of the shared libs for Xorg you might try adding a std ALSA-system? Anyway I will try to look into ALSA and the cs423x-stuff in 431.
Attached a static build of blinky-0.8...has retro look but with a low resource demand.
Add: Attached static build of alsalib/alsautils but stripped for most bins not needed for running alsaconf. The alsaconf is a slitaz script that runs with ash (original needs bash). I am not able to test this throughly - guess its mostly relevant for configuring ISA soundcards. Maybe worth a try - starhawk?
Keef: You mentioned you needed Termcap - what exactly are you missing? Is it the termcap.info files?
And the 4M looks worth a closer look - thanks!
starhawk: I was wondering if the sound is a driver missing or the absent of ALSA that gives problems? I do not know if ALSA can be done static at all - but as you are already having some of the shared libs for Xorg you might try adding a std ALSA-system? Anyway I will try to look into ALSA and the cs423x-stuff in 431.
Attached a static build of blinky-0.8...has retro look but with a low resource demand.
Add: Attached static build of alsalib/alsautils but stripped for most bins not needed for running alsaconf. The alsaconf is a slitaz script that runs with ash (original needs bash). I am not able to test this throughly - guess its mostly relevant for configuring ISA soundcards. Maybe worth a try - starhawk?
SNS = dead in the water.
Apparently there is no easy way to associate a driver with a physical device unless it is done automatically -- which pUPnGO2012 DOES NOT.
Plugged in a spare Netgear WG111v3 adapter, having installed the SNS pet and the extra-drivers SFS. Nothing showed up in SNS about the adapter, except for a Windows option (I will NOT use ndiswrapper). modprobe was used, and it loaded the correct WiFi module as listed on WikiDevi (very handy site, that). However, ifconfig and iwconfig would not recognize the device. /dev/wlan0 doesn't exist so that may be part of the issue.
Is there an RXVT command that says, "take this effing driver that's loaded and stuff it into a USB port"?
Also, how do I properly get Blinky working? In the /root/Startup directory it displays in the upper-left corner of the screen.
Haven't tried sound yet.
Apparently there is no easy way to associate a driver with a physical device unless it is done automatically -- which pUPnGO2012 DOES NOT.
Plugged in a spare Netgear WG111v3 adapter, having installed the SNS pet and the extra-drivers SFS. Nothing showed up in SNS about the adapter, except for a Windows option (I will NOT use ndiswrapper). modprobe was used, and it loaded the correct WiFi module as listed on WikiDevi (very handy site, that). However, ifconfig and iwconfig would not recognize the device. /dev/wlan0 doesn't exist so that may be part of the issue.
Is there an RXVT command that says, "take this effing driver that's loaded and stuff it into a USB port"?
Also, how do I properly get Blinky working? In the /root/Startup directory it displays in the upper-left corner of the screen.
Haven't tried sound yet.
Do not know about the wifi-driver thing...If driver present and recognized (including firmware drivers) they are normally loaded during boot...If the extra driver are not present at boot but installed after boot they might not be picked up - but unsure how to get you further there. I think if the right drivers are loaded ifconfig/iwconfig will give you some response...
I have the SNS--retro working with pupngo2012 on an asus eeepc900 and on stationary pc with usb-zd1211 wireless-stick. Also the wired network adapters on both machines are recognized and connected.
For blinky add the below to /root/.jwmrc-tray just after the pmfree swallow line
I have the SNS--retro working with pupngo2012 on an asus eeepc900 and on stationary pc with usb-zd1211 wireless-stick. Also the wired network adapters on both machines are recognized and connected.
For blinky add the below to /root/.jwmrc-tray
Code: Select all
<Swallow name="blinky">
blinky -bg "#DCDAD5"
</Swallow>-
technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
if anyone is looking to do a no-rox version, I wrote some C that checks file extension and gives you the MIME-type:
http://murga-linux.com/puppy/viewtopic.php?t=80916
These are the ones that (by default - not necessarily in pet packages) are semicolon separated in .desktop files as
MimeType=application/vnd.ms-asf;application/vnd.rn-realmedia;...
You can just grep `mimetype $filename` /usr/share/applications/*.desktop to find which programs can run it.
http://murga-linux.com/puppy/viewtopic.php?t=80916
These are the ones that (by default - not necessarily in pet packages) are semicolon separated in .desktop files as
MimeType=application/vnd.ms-asf;application/vnd.rn-realmedia;...
You can just grep `mimetype $filename` /usr/share/applications/*.desktop to find which programs can run it.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].
-
technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
All that shows up is lo. No eth0, no wlan0, and no ath0.
...of note, the Dell C600 (it's xvesa friendly ) I used this time has no ethernet connector IIRC. (The CPi doesn't either.)
I think we need a copy of the "wireless module loader/tester" from Classic Network Wizard. I'd say port the whole thing over... but it's a goodly bit bigger, to say the least.
Unfortunately, I have no idea if it's one single script or a collection. I suspect one single script, which will make lifting out the loader-tester portion that much harder. I'd have to go looking to be sure tho.
...of note, the Dell C600 (it's xvesa friendly
) I used this time has no ethernet connector IIRC. (The CPi doesn't either.)I think we need a copy of the "wireless module loader/tester" from Classic Network Wizard. I'd say port the whole thing over... but it's a goodly bit bigger, to say the least.
Unfortunately, I have no idea if it's one single script or a collection. I suspect one single script, which will make lifting out the loader-tester portion that much harder. I'd have to go looking to be sure tho.
What responses do you get to the following commands:starhawk wrote:All that shows up is lo. No eth0, no wlan0, and no ath0.
ifconfig eth0 up
ifconfig eth1 up
ifconfig wlan0 up
and does "ifconfig" show any change after each of those? Also, goingnuts suggested to me to "Try to look in /tmp/interfaces to view what interfaces was found". Does that contain any info? If not, does anything show there after you try to run the wireless manager wizard?
Is the behaviour identical depending on whether you boot with the usb network adapter already installed, compared to if you plug it in after boot?starhawk wrote:ifconfig [device] universally returns:
ifconfig: SIOCGIFFLAGS: No such device
Any chance of plugging in a pcmcia network card to compare results?
Burnt a closed CD, and this laptop does not have a hard drive -- and it has only one USB port, and my experience with pUPnGO is that it does not like hubs. So no savefile.
I could remaster it with Woofy to include the pet so that I could boot with it like that, but I'm getting low on CD-Rs (again) and the local stores do not sell -RW discs
So the in-there-at-boot-time test will have to wait.
As for your other question... I do have an old Prism2 card out of a router that I can try... it's Wifi "b" rather than "g" but I don't think it'll slow the entire network to a crawl if I use it... just the one connection. Let me go see if I can find it, and I will try it. That I *can* install before booting.
EDIT: nada. Although I may have an idea of the issue... the SNS shell script (as carried over into SNS-Retro) references a file I did not know about listed as /etc/simple_network_setup/connections . I will try to hunt down this file and see if adding that in fixes things.
EDIT: looks like /etc/simple_network_setup/connections is /generated/ by SNS. Either way, copying it over from Puplite 5 does not appear to affect anything. My best guess is that there is some module-chaining not going on. Perhaps modules.dep is not being properly altered with the drivers sfs? (I suspect this because I ran into some errors with that while trying to manually load various modules.)
I could remaster it with Woofy to include the pet so that I could boot with it like that, but I'm getting low on CD-Rs (again) and the local stores do not sell -RW discs
So the in-there-at-boot-time test will have to wait.
As for your other question... I do have an old Prism2 card out of a router that I can try... it's Wifi "b" rather than "g" but I don't think it'll slow the entire network to a crawl if I use it... just the one connection. Let me go see if I can find it, and I will try it. That I *can* install before booting.
EDIT: nada. Although I may have an idea of the issue... the SNS shell script (as carried over into SNS-Retro) references a file I did not know about listed as /etc/simple_network_setup/connections . I will try to hunt down this file and see if adding that in fixes things.
EDIT: looks like /etc/simple_network_setup/connections is /generated/ by SNS. Either way, copying it over from Puplite 5 does not appear to affect anything. My best guess is that there is some module-chaining not going on. Perhaps modules.dep is not being properly altered with the drivers sfs? (I suspect this because I ran into some errors with that while trying to manually load various modules.)