Do you even need to bother doing this. If you keep them the same name won't the version in the devx file just mask/overide the version in the pup_xxx.sfs if it is loaded.John Doe wrote:If you rename 'make' to 'make-FULL' in the devx file
Dingo Alpha 5 of 11 Jan. Issues (aka Bugs or Problems)
Re: Idea for devx, to help new users
Will
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
Re: Idea for devx, to help new users
didn't test it that way, but did think of that while typing at one point.HairyWill wrote:Do you even need to bother doing this. If you keep them the same name won't the version in the devx file just mask/overide the version in the pup_xxx.sfs if it is loaded.
willing to give you odds that you are correct.
just strip out some of the logic in it and just make sure the echos for the script that is masked work prior to masking.
it's all irrelevant (but might be helpful to new users)
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
RE: PCMCIA
After the core driver is loaded, the device will appear in the output of lspsi/elspci and the correct module loaded like for a pci device (the modules [most of them, at least] are listed in modules.pcimap).
After the core driver is loaded, the device will appear in the output of lspsi/elspci and the correct module loaded like for a pci device (the modules [most of them, at least] are listed in modules.pcimap).
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
That's not my problem. 'modules.pcimap' lists the PCI-to-PCMCIA interface modules, such as yenta-socket, but not the modules for a particular card, like the 'xirc2ps_cs' required by my PCMCIA network card. 'elspci' will not help either.Dougal wrote:RE: PCMCIA
After the core driver is loaded, the device will appear in the output of lspsi/elspci and the correct module loaded like for a pci device (the modules [most of them, at least] are listed in modules.pcimap).
The old 'cardmgr' package has a database that determines what module to load for a particular card. The new 'pcmciautils' does not have that mechanism/database, or at least not that I can see.
[url]https://bkhome.org/news/[/url]
Invalid IF statement in rc.network script
Line 49 of /etc/rc.d/rc.network is an IF statement that tests for file existence. But "-f /etc/eth[0-9]mode" is invalid because it expands internally to "-f /etc/eth0mode /etc/eth1mode", whereas the "-f" primary accepts only a single file name. The message "/etc/rc.d/rc.network: line 49: binary operator expected" (for two NICs) or ". . . [: too many arguments" (for three NICs) is generated and the conditional "sleep 3" does not occur. The message appears in /tmp/bootsysinit.log.
The following substitute statement works with multiple NIC eth?mode files (and should also with "*wireless"):
Richard
The following substitute statement works with multiple NIC eth?mode files (and should also with "*wireless"):
Code: Select all
if [ "`ls /etc | grep 'eth[0-9]mode\|ethernetmodules\|*wireless'`" != "" ];then
Is that a toaster you're poking with a paper clip, AJ?! All my paper clips are worn out - can you send a couple, please.
JD almost got it right. There is no 'EJECT' provided with Pmount. Never had any auto-ejects with the thousands of drives that passed this way.
Come on Jesse! let's have your MUT port and we can all sleep soundly again.....
JD almost got it right. There is no 'EJECT' provided with Pmount. Never had any auto-ejects with the thousands of drives that passed this way.
Come on Jesse! let's have your MUT port and we can all sleep soundly again.....
The gimageview .pet in the repository has an & in gimageview.desktop, which causes an error if you do
It doesn't actually seem to cause any problems, but it can be fixed by using &
Code: Select all
jwm -p
I almost started a poll to ask who has or doesn't have one of those bent paper clips next to them.Sage wrote:Is that a toaster you're poking with a paper clip, AJ?! All my paper clips are worn out - can you send a couple, please.
SHit my empty 4230-01-101-3984 has one of this in it. Much better than worrying about smokes.
I miss mut also. First thing I used to do when hitting the 'desktop' was change that icon to mut.Sage wrote:JD almost got it right. There is no 'EJECT' provided with Pmount. Never had any auto-ejects with the thousands of drives that passed this way.
Come on Jesse! let's have your MUT port and we can all sleep soundly again.....
---
jwm config stuff tomorrow. drank too much again.
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
I was not referring to yenta-socket etc., but to the drivers for the actual devices: most of them are listed in modules.pcimap. I went over it a month or so ago and there were only a few that weren't.BarryK wrote:That's not my problem. 'modules.pcimap' lists the PCI-to-PCMCIA interface modules, such as yenta-socket, but not the modules for a particular card, like the 'xirc2ps_cs' required by my PCMCIA network card. 'elspci' will not help either
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
Jan 17th Alfa 5
Barry,
I downloaded and tested the Jan 17th Alfa 5 (2.6.24-rc8 kernel) on the eeepc. I just copied the needed files to the internal SSD drive and used the current Grub install to boot it. It booted up and shutdown fine. Durring shutdown I saved the pup file to a SD card in the internal SD card reader slot. On reboot it found the correct file and loaded it. As a side note, one thing I noticed was that the default kernel that comes with the eeepc is 2.6.21.4
I downloaded and tested the Jan 17th Alfa 5 (2.6.24-rc8 kernel) on the eeepc. I just copied the needed files to the internal SSD drive and used the current Grub install to boot it. It booted up and shutdown fine. Durring shutdown I saved the pup file to a SD card in the internal SD card reader slot. On reboot it found the correct file and loaded it. As a side note, one thing I noticed was that the default kernel that comes with the eeepc is 2.6.21.4
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Thanks, I fixed it.disciple wrote:The gimageview .pet in the repository has an & in gimageview.desktop, which causes an error if you doIt doesn't actually seem to cause any problems, but it can be fixed by using &Code: Select all
jwm -p
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
None of the PCMCIA network drivers are in modules.pcimap. They are all the modules that end with '_cs'. The same would apply to any other specialist PCMCIA-card drivers, as these have nothing to do with PCI.Dougal wrote:I was not referring to yenta-socket etc., but to the drivers for the actual devices: most of them are listed in modules.pcimap. I went over it a month or so ago and there were only a few that weren't.BarryK wrote:That's not my problem. 'modules.pcimap' lists the PCI-to-PCMCIA interface modules, such as yenta-socket, but not the modules for a particular card, like the 'xirc2ps_cs' required by my PCMCIA network card. 'elspci' will not help either
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: Jan 17th Alfa 5
That's good news.dvw86 wrote:Barry,
I downloaded and tested the Jan 17th Alfa 5 (2.6.24-rc8 kernel) on the eeepc. I just copied the needed files to the internal SSD drive and used the current Grub install to boot it. It booted up and shutdown fine. Durring shutdown I saved the pup file to a SD card in the internal SD card reader slot. On reboot it found the correct file and loaded it. As a side note, one thing I noticed was that the default kernel that comes with the eeepc is 2.6.21.4
My experiences with the 2.6.24-rc4 and -rc8 have been very positive. I intend to wait until it is released before releasing Dingo beta.
[url]https://bkhome.org/news/[/url]
I did a fresh install to a 1 gigabyte USB flash device. I used an external USB CDROM with the iso to boot the Eee PC and do the installation to the USB flash device. Everything when well expect for the dreaded Syslinux unsafe /tmp permissions error. Saved a pup_save.2fs to the device. Rebooted and used Xandros to complete the syslinux process. Booted the USB device and it worked. The Dingo gold screen looks better on the small screen for some reason. The proper screen resolution (800x480) was available in both Xvesa and Xorg. I tried both video servers with no problems. The only thing missing was the network modules for the ETHERNET and WIFI cards. I could not try the networking.
The sound work fine at the start. I got the two "woofs". This version should work nicely once the card modules for networking are available.
The sound work fine at the start. I got the two "woofs". This version should work nicely once the card modules for networking are available.
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
Live Well, Laugh Often, Love Much