From jdmulloy at gmail.com Tue Aug 5 01:56:38 2008 From: jdmulloy at gmail.com (Joseph Mulloy) Date: Tue, 5 Aug 2008 01:56:38 -0400 Subject: [Poly-p-ux] Hi all just installed poly-p-ux on a 586 Message-ID: <5b530dbd0808042256v1ab82f81x3657405b2a2aaff2@mail.gmail.com> Hi all I've just installed poly-p-ux on the oldest working machine I have. It's a Gateway G5-233. Here are the specs. 233 MHz Pentium-MMX 32 MB 66 MHz SD-RAM 2564 MB Quantum Fireball HD I know it's at the upper end of what poly-p-ux is supposed to be for but it runs nice. You may have seen me on the Gentoo Forums as jdmulloy. I thought I'd give this thing a try on real hardware. I've attached some edited init scripts to this email. I made the swap script use /etc/fstab to configure swap instaed of hard coding it into the script. All I needed there was the -a flag for swapon which actually does the work. I also made the modules script loop through a list of modules in /etc/modules.autoload to load kernel modules on boot. Hope you like it. Is there anything that needs to be worked on? Any thing you need tested on i586? Can I get a copy of the build environment? Thanks. It's nice to have this old box doing something useful again. At some point I'm going to see if I can get links to run on it, unless anyone knows of an even smaller browser. I wrote this email on my Pentium box running poly-p-ux on links running on my server which I'm accessing over ssh. -- Joseph Mulloy jdmulloy at gmail.com -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: S10swap Url: http://lists.ibiblio.org/pipermail/poly-p-ux/attachments/20080805/da29faf1/attachment.pl -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: S15modules Url: http://lists.ibiblio.org/pipermail/poly-p-ux/attachments/20080805/da29faf1/attachment-0001.pl From polypolyman at ibiblio.org Tue Aug 5 05:55:37 2008 From: polypolyman at ibiblio.org (Poly-p man) Date: Tue, 5 Aug 2008 05:55:37 -0400 Subject: [Poly-p-ux] Hi all just installed poly-p-ux on a 586 In-Reply-To: <5b530dbd0808042256v1ab82f81x3657405b2a2aaff2@mail.gmail.com> References: <5b530dbd0808042256v1ab82f81x3657405b2a2aaff2@mail.gmail.com> Message-ID: <200808050555.38094.polypolyman@ibiblio.org> On Tuesday 05 August 2008 01:56:38 am Joseph Mulloy wrote: > Hi all I've just installed poly-p-ux on the oldest working machine I > have. It's a Gateway G5-233. Here are the specs. > > 233 MHz Pentium-MMX > 32 MB 66 MHz SD-RAM > 2564 MB Quantum Fireball HD nice specs... too bad there's no actual MMX support in poly-p-ux :D > I know it's at the upper end of what poly-p-ux is supposed to be for > but it runs nice. This time around, even though it's excruciatingly difficult to get releases going (because I have 3 - no, 4 systems I need to build twice each, then manually compile and configure everything...), I'm building an i686 version to support all the people who think their Pentium 2 box is "old" 1.0 is delayed, but only because it's hard to release... I'll put more effort into it probably today and over the next week. > You may have seen me on the Gentoo Forums as jdmulloy. I thought I'd > give this thing a try on real hardware. I've attached some edited init > scripts to this email. I made the swap script use /etc/fstab to > configure swap instaed of hard coding it into the script. All I needed > there was the -a flag for swapon which actually does the work. I also > made the modules script loop through a list of modules in > /etc/modules.autoload to load kernel modules on boot. Hope you like > it. For swap, I think I tried that on one of my older incarnations, with an older busybox version - I think swaponoff -a has been added - I'll have to check the mailing list. For modules... that is awesome! I was working on a modules.autoload system a while back... never got it to work. The most important part is options... for example, for my 486's network card, I need to load ne with the options io=0x280 irq=3. looking at your script, will that work? Also... with my new, improved init, stop actually gets called... not that it matters with modules anyway... :D > Is there anything that needs to be worked on? Any thing you need > tested on i586? Can I get a copy of the build environment? Thanks. Testing would be nice after release... currently I have nothing to test! The build environment is Buildroot... I'll upload all my config files at some point. If you want to be a huge help, get my builds of LILO going - I'm dropping grub because it's slow :D . Currently, my 486 box (upgraded to it's 850mb hard drive) is a complete development environment, so building LILO there wasn't an issue... if you could try building for all the archs (or at least static for 386), that would help me tons! > It's nice to have this old box doing something useful again. At some > point I'm going to see if I can get links to run on it, unless anyone > knows of an even smaller browser. That was one of the packages I was trying to get compiled on the old versions... links, lynk, elinks, anything... I had MAJOR trouble with that... At the release of 1.0, I'll upload tarballs of the development environment (chroot into it to have fun) for people who care. > I wrote this email on my Pentium box running poly-p-ux on links > running on my server which I'm accessing over ssh. That's great! Honestly, just having a usable old system (even if it means using dropbear to connect to a server) means so much for this project... I have my 486 set up such that it's much more comfortable to use it... can't wait until I get kdrive and friends up - the system WILL be a beast... I know it :D Thanks for showing an interest, poly-p man From jdmulloy at gmail.com Tue Aug 5 11:48:46 2008 From: jdmulloy at gmail.com (Joseph Mulloy) Date: Tue, 5 Aug 2008 11:48:46 -0400 Subject: [Poly-p-ux] Hi all just installed poly-p-ux on a 586 In-Reply-To: <200808050555.38094.polypolyman@ibiblio.org> References: <5b530dbd0808042256v1ab82f81x3657405b2a2aaff2@mail.gmail.com> <200808050555.38094.polypolyman@ibiblio.org> Message-ID: <5b530dbd0808050848k705fbbdj361ce6da938a7142@mail.gmail.com> Joseph Mulloy jdmulloy at gmail.com On Tue, Aug 5, 2008 at 5:55 AM, Poly-p man wrote: > On Tuesday 05 August 2008 01:56:38 am Joseph Mulloy wrote: > > Hi all I've just installed poly-p-ux on the oldest working machine I > > have. It's a Gateway G5-233. Here are the specs. > > > > 233 MHz Pentium-MMX > > 32 MB 66 MHz SD-RAM > > 2564 MB Quantum Fireball HD > > nice specs... too bad there's no actual MMX support in poly-p-ux :D > I don't really care too much about not having MMX > > > I know it's at the upper end of what poly-p-ux is supposed to be for > > but it runs nice. > > This time around, even though it's excruciatingly difficult to get releases > going (because I have 3 - no, 4 systems I need to build twice each, then > manually compile and configure everything...), I'm building an i686 version > to support all the people who think their Pentium 2 box is "old" > Why bother with i686? Debian or even Gentoo would work fine on an i686 class machine, heck the machine I'm using for poly-p-ux could handle debian just fine, especially since I have more ram lying around that I could use. I've got two nearly identical i686 class machines if you want testing done. If you want at some point I could setup ssh access to the machines for you. > > 1.0 is delayed, but only because it's hard to release... I'll put more > effort > into it probably today and over the next week. > > > You may have seen me on the Gentoo Forums as jdmulloy. I thought I'd > > give this thing a try on real hardware. I've attached some edited init > > scripts to this email. I made the swap script use /etc/fstab to > > configure swap instaed of hard coding it into the script. All I needed > > there was the -a flag for swapon which actually does the work. I also > > made the modules script loop through a list of modules in > > /etc/modules.autoload to load kernel modules on boot. Hope you like > > it. > > For swap, I think I tried that on one of my older incarnations, with an > older > busybox version - I think swaponoff -a has been added - I'll have to check > the mailing list. > > For modules... that is awesome! I was working on a modules.autoload system > a > while back... never got it to work. The most important part is options... > for > example, for my 486's network card, I need to load ne with the options > io=0x280 irq=3. looking at your script, will that work? > Try it out, it Should work, it just calls modprobe and then appends whatever is on the current line of the file. I haven't made it too smart yet, so you can't do commments, (well it probably won't hurt anything but it will try to modeporbe your comments). Just put "ne io=0x280 irq=3" into the file /etc/modules.autoload and it should work. > > Also... with my new, improved init, stop actually gets called... not that > it > matters with modules anyway... :D > > > Is there anything that needs to be worked on? Any thing you need > > tested on i586? Can I get a copy of the build environment? Thanks. > > Testing would be nice after release... currently I have nothing to test! > > The build environment is Buildroot... I'll upload all my config files at > some > point. > > If you want to be a huge help, get my builds of LILO going - I'm dropping > grub > because it's slow :D . Currently, my 486 box (upgraded to it's 850mb hard > drive) is a complete development environment, so building LILO there wasn't > an issue... if you could try building for all the archs (or at least static > for 386), that would help me tons! > I could try building for 386 but I don't have any to test on. Is grub really that slow on older machines? > > > It's nice to have this old box doing something useful again. At some > > point I'm going to see if I can get links to run on it, unless anyone > > knows of an even smaller browser. > > That was one of the packages I was trying to get compiled on the old > versions... links, lynk, elinks, anything... I had MAJOR trouble with > that... > I tried to compile it statically on my Gentoo laptop and it wouldn't complie. When I removed the static flag I ran ldd on the binary and it had a large list of dependencies. It can probably be made to work hardware wise, but it may need a lot of disk space for all the dependencies. What's the target disk usage? > > At the release of 1.0, I'll upload tarballs of the development environment > (chroot into it to have fun) for people who care. > > > I wrote this email on my Pentium box running poly-p-ux on links > > running on my server which I'm accessing over ssh. > > That's great! Honestly, just having a usable old system (even if it means > using dropbear to connect to a server) means so much for this project... I > have my 486 set up such that it's much more comfortable to use it... can't > wait until I get kdrive and friends up - the system WILL be a beast... I > know > it :D > > Thanks for showing an interest, > poly-p man > _______________________________________________ > Poly-p-ux mailing list > Poly-p-ux at lists.ibiblio.org > http://lists.ibiblio.org/mailman/listinfo/poly-p-ux > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.ibiblio.org/pipermail/poly-p-ux/attachments/20080805/30b93d1d/attachment.html From jdmulloy at gmail.com Tue Aug 5 19:04:18 2008 From: jdmulloy at gmail.com (Joseph Mulloy) Date: Tue, 5 Aug 2008 19:04:18 -0400 Subject: [Poly-p-ux] Hi all just installed poly-p-ux on a 586 In-Reply-To: <5b530dbd0808050848k705fbbdj361ce6da938a7142@mail.gmail.com> References: <5b530dbd0808042256v1ab82f81x3657405b2a2aaff2@mail.gmail.com> <200808050555.38094.polypolyman@ibiblio.org> <5b530dbd0808050848k705fbbdj361ce6da938a7142@mail.gmail.com> Message-ID: <5b530dbd0808051604n2ecbb664t4f2e71f6c90c4cfe@mail.gmail.com> Is it possible to get gcc onto my poly-p-ux installation? I'm going to try using build root to cross compile things on my Gentoo laptop and see if I can get the to run on the Pentium box. I'm going to start with links, I've managed to get it's dependencies down to glibc, obviously I'm going to have to get it compiled statically or against uClibc which would be preferred since we want to minimize our memory footprint. What version of build root did you use for i586 0.01? I will try with the latest svn version but If I can download the same version you have then it will be more compatible. It may help the project if we could get a build system bundled up into a tarball for people to download. It will also help if people want to build applications for the system, then they can make them available and they can be packaged. As for lilo do you have anything in progress that you can make available or should I just grab sources from the lilo site? If you could make your build root config files available that would be immensely helpful. Thanks. Joseph Mulloy jdmulloy at gmail.com On Tue, Aug 5, 2008 at 11:48 AM, Joseph Mulloy wrote: > > Joseph Mulloy > > jdmulloy at gmail.com > > > On Tue, Aug 5, 2008 at 5:55 AM, Poly-p man wrote: > >> On Tuesday 05 August 2008 01:56:38 am Joseph Mulloy wrote: >> > Hi all I've just installed poly-p-ux on the oldest working machine I >> > have. It's a Gateway G5-233. Here are the specs. >> > >> > 233 MHz Pentium-MMX >> > 32 MB 66 MHz SD-RAM >> > 2564 MB Quantum Fireball HD >> >> nice specs... too bad there's no actual MMX support in poly-p-ux :D >> > > I don't really care too much about not having MMX > > >> >> > I know it's at the upper end of what poly-p-ux is supposed to be for >> > but it runs nice. >> >> This time around, even though it's excruciatingly difficult to get >> releases >> going (because I have 3 - no, 4 systems I need to build twice each, then >> manually compile and configure everything...), I'm building an i686 >> version >> to support all the people who think their Pentium 2 box is "old" >> > > Why bother with i686? Debian or even Gentoo would work fine on an i686 > class machine, heck the machine I'm using for poly-p-ux could handle debian > just fine, especially since I have more ram lying around that I could use. > I've got two nearly identical i686 class machines if you want testing done. > If you want at some point I could setup ssh access to the machines for you. > > >> >> 1.0 is delayed, but only because it's hard to release... I'll put more >> effort >> into it probably today and over the next week. >> >> > You may have seen me on the Gentoo Forums as jdmulloy. I thought I'd >> > give this thing a try on real hardware. I've attached some edited init >> > scripts to this email. I made the swap script use /etc/fstab to >> > configure swap instaed of hard coding it into the script. All I needed >> > there was the -a flag for swapon which actually does the work. I also >> > made the modules script loop through a list of modules in >> > /etc/modules.autoload to load kernel modules on boot. Hope you like >> > it. >> >> For swap, I think I tried that on one of my older incarnations, with an >> older >> busybox version - I think swaponoff -a has been added - I'll have to check >> the mailing list. >> >> For modules... that is awesome! I was working on a modules.autoload system >> a >> while back... never got it to work. The most important part is options... >> for >> example, for my 486's network card, I need to load ne with the options >> io=0x280 irq=3. looking at your script, will that work? >> > > Try it out, it Should work, it just calls modprobe and then appends > whatever is on the current line of the file. I haven't made it too smart > yet, so you can't do commments, (well it probably won't hurt anything but it > will try to modeporbe your comments). > > Just put "ne io=0x280 irq=3" into the file /etc/modules.autoload and it > should work. > > >> >> Also... with my new, improved init, stop actually gets called... not that >> it >> matters with modules anyway... :D >> >> > Is there anything that needs to be worked on? Any thing you need >> > tested on i586? Can I get a copy of the build environment? Thanks. >> >> Testing would be nice after release... currently I have nothing to test! >> >> The build environment is Buildroot... I'll upload all my config files at >> some >> point. >> >> If you want to be a huge help, get my builds of LILO going - I'm dropping >> grub >> because it's slow :D . Currently, my 486 box (upgraded to it's 850mb hard >> drive) is a complete development environment, so building LILO there >> wasn't >> an issue... if you could try building for all the archs (or at least >> static >> for 386), that would help me tons! >> > > I could try building for 386 but I don't have any to test on. Is grub > really that slow on older machines? > > >> >> > It's nice to have this old box doing something useful again. At some >> > point I'm going to see if I can get links to run on it, unless anyone >> > knows of an even smaller browser. >> >> That was one of the packages I was trying to get compiled on the old >> versions... links, lynk, elinks, anything... I had MAJOR trouble with >> that... >> > > I tried to compile it statically on my Gentoo laptop and it wouldn't > complie. When I removed the static flag I ran ldd on the binary and it had a > large list of dependencies. It can probably be made to work hardware wise, > but it may need a lot of disk space for all the dependencies. What's the > target disk usage? > > >> >> At the release of 1.0, I'll upload tarballs of the development environment >> (chroot into it to have fun) for people who care. >> >> > I wrote this email on my Pentium box running poly-p-ux on links >> > running on my server which I'm accessing over ssh. >> >> That's great! Honestly, just having a usable old system (even if it means >> using dropbear to connect to a server) means so much for this project... I >> have my 486 set up such that it's much more comfortable to use it... can't >> wait until I get kdrive and friends up - the system WILL be a beast... I >> know >> it :D >> >> Thanks for showing an interest, >> poly-p man >> _______________________________________________ >> Poly-p-ux mailing list >> Poly-p-ux at lists.ibiblio.org >> http://lists.ibiblio.org/mailman/listinfo/poly-p-ux >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.ibiblio.org/pipermail/poly-p-ux/attachments/20080805/8fce0751/attachment.html From polypolyman at ibiblio.org Tue Aug 5 22:39:54 2008 From: polypolyman at ibiblio.org (Poly-p man) Date: Tue, 5 Aug 2008 22:39:54 -0400 Subject: [Poly-p-ux] Hi all just installed poly-p-ux on a 586 In-Reply-To: <5b530dbd0808051604n2ecbb664t4f2e71f6c90c4cfe@mail.gmail.com> References: <5b530dbd0808042256v1ab82f81x3657405b2a2aaff2@mail.gmail.com> <5b530dbd0808050848k705fbbdj361ce6da938a7142@mail.gmail.com> <5b530dbd0808051604n2ecbb664t4f2e71f6c90c4cfe@mail.gmail.com> Message-ID: <200808052239.54586.polypolyman@ibiblio.org> On Tuesday 05 August 2008 07:04:18 pm Joseph Mulloy wrote: > Is it possible to get gcc onto my poly-p-ux installation? I'm going to try > using build root to cross compile things on my Gentoo laptop and see if I > can get the to run on the Pentium box. I'm going to start with links, I've > managed to get it's dependencies down to glibc, obviously I'm going to have > to get it compiled statically or against uClibc which would be preferred > since we want to minimize our memory footprint. What version of build root > did you use for i586 0.01? I will try with the latest svn version but If I > can download the same version you have then it will be more compatible. It > may help the project if we could get a build system bundled up into a > tarball for people to download. It will also help if people want to build > applications for the system, then they can make them available and they can > be packaged. As for lilo do you have anything in progress that you can make > available or should I just grab sources from the lilo site? If you could > make your build root config files available that would be immensely > helpful. Thanks. > > Joseph Mulloy > > jdmulloy at gmail.com shouldn't matter - stuff's binary compatible for the most part (uclibc hasn't bumped versions... Anyway, except for my vacation this weekend, I'll be working on 1.0... It's pretty much done, and it could DEFINITELY be sped along if someone (you :P ) could compile me LILO binaries - this is what's holding me back right now. As for your other message - I finally was bullied into 686 by all the people in OTW complaining about how old their pentium 2 boxen are... and as no one ever says - give the people what they want! I'll give the modules.autoload a shot on my 486... I seem to remember I had major trouble with IFS being wrong last time - I think modprobe needs all the options as seperate argv's... I might as well throw the modules.autoload code into the c part anyway (snailit is VERY nice, I might add!) One of my biggest issues in the past has been text-mode browsers being mean to me - If you could work on that (after getting LILO to work, of course :D ), that would be lovely. Oh, and yes, grub DOES run slowly on my 486 - not to mention my 386 :P poly-p man From jdmulloy at gmail.com Tue Aug 5 23:26:43 2008 From: jdmulloy at gmail.com (Joseph Mulloy) Date: Tue, 5 Aug 2008 23:26:43 -0400 Subject: [Poly-p-ux] Hi all just installed poly-p-ux on a 586 In-Reply-To: <200808052239.54586.polypolyman@ibiblio.org> References: <5b530dbd0808042256v1ab82f81x3657405b2a2aaff2@mail.gmail.com> <5b530dbd0808050848k705fbbdj361ce6da938a7142@mail.gmail.com> <5b530dbd0808051604n2ecbb664t4f2e71f6c90c4cfe@mail.gmail.com> <200808052239.54586.polypolyman@ibiblio.org> Message-ID: <5b530dbd0808052026w1730861eide209f2885d832b8@mail.gmail.com> I have managed to get a very basic version of links running on my box. It was actually an option in build root, I just copied over the binary and it works, I compiled it for 386, can't test it obviously but I believe it should work. Do you want me to send you a copy? Also ifup usually segfaults, but if I run it a few times I eventually get an IP address and can access my network and the Internet. I'll try working on LILO, but it would be helpful if I had a toolchain and compiler on the box. Joseph Mulloy jdmulloy at gmail.com On Tue, Aug 5, 2008 at 10:39 PM, Poly-p man wrote: > On Tuesday 05 August 2008 07:04:18 pm Joseph Mulloy wrote: > > Is it possible to get gcc onto my poly-p-ux installation? I'm going to > try > > using build root to cross compile things on my Gentoo laptop and see if I > > can get the to run on the Pentium box. I'm going to start with links, > I've > > managed to get it's dependencies down to glibc, obviously I'm going to > have > > to get it compiled statically or against uClibc which would be preferred > > since we want to minimize our memory footprint. What version of build > root > > did you use for i586 0.01? I will try with the latest svn version but If > I > > can download the same version you have then it will be more compatible. > It > > may help the project if we could get a build system bundled up into a > > tarball for people to download. It will also help if people want to build > > applications for the system, then they can make them available and they > can > > be packaged. As for lilo do you have anything in progress that you can > make > > available or should I just grab sources from the lilo site? If you could > > make your build root config files available that would be immensely > > helpful. Thanks. > > > > Joseph Mulloy > > > > jdmulloy at gmail.com > > shouldn't matter - stuff's binary compatible for the most part (uclibc > hasn't > bumped versions... > > Anyway, except for my vacation this weekend, I'll be working on 1.0... It's > pretty much done, and it could DEFINITELY be sped along if someone (you :P > ) > could compile me LILO binaries - this is what's holding me back right now. > > As for your other message - I finally was bullied into 686 by all the > people > in OTW complaining about how old their pentium 2 boxen are... and as no one > ever says - give the people what they want! > > I'll give the modules.autoload a shot on my 486... I seem to remember I had > major trouble with IFS being wrong last time - I think modprobe needs all > the > options as seperate argv's... I might as well throw the modules.autoload > code > into the c part anyway (snailit is VERY nice, I might add!) > > One of my biggest issues in the past has been text-mode browsers being mean > to > me - If you could work on that (after getting LILO to work, of course :D ), > that would be lovely. > > Oh, and yes, grub DOES run slowly on my 486 - not to mention my 386 :P > > poly-p man > _______________________________________________ > Poly-p-ux mailing list > Poly-p-ux at lists.ibiblio.org > http://lists.ibiblio.org/mailman/listinfo/poly-p-ux > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.ibiblio.org/pipermail/poly-p-ux/attachments/20080805/699f15ea/attachment.html From polypolyman at ibiblio.org Wed Aug 6 00:21:33 2008 From: polypolyman at ibiblio.org (Poly-p man) Date: Wed, 6 Aug 2008 00:21:33 -0400 Subject: [Poly-p-ux] Hi all just installed poly-p-ux on a 586 Message-ID: <200808060021.33383.polypolyman@ibiblio.org> On Tuesday 05 August 2008 11:26:43 pm Joseph Mulloy wrote: > I have managed to get a very basic version of links running on my box. It > was actually an option in build root, I just copied over the binary and it > works, I compiled it for 386, can't test it obviously but I believe it > should work. 386 binaries should work on all systems... right? > Do you want me to send you a copy? why not? :D > Also ifup usually > segfaults, Known issue - it's bash's fault, actually. First off, stop using ifup (use ifconfig, udhcpc for dhcp), and secondly, 1.0 will use busybox ash entirely. Seems bash + uclibc + kernel > 2.6.24 segfaults randomly. That's why I started writing my init, before realizing it was a bash issue :D > I'll try working on LILO, but it > would be helpful if I had a toolchain and compiler on the box. True... currently I have my 486 with a full compiler - makes lilo nicely - of course, this will make 486 binaries, so no dice. If you want to build everything with full compiler support, I'll upload the config files, and you can save me about 2/3s of the compile time for release :P poly-p man From jdmulloy at gmail.com Wed Aug 6 01:18:52 2008 From: jdmulloy at gmail.com (Joseph Mulloy) Date: Wed, 6 Aug 2008 01:18:52 -0400 Subject: [Poly-p-ux] Hi all just installed poly-p-ux on a 586 In-Reply-To: <200808060021.33383.polypolyman@ibiblio.org> References: <200808060021.33383.polypolyman@ibiblio.org> Message-ID: <5b530dbd0808052218i1c256416pda9d23efe9c1ad5f@mail.gmail.com> As you probably already know, you can build an i386 version and load it on any system that supports at least the same instruction set. You can use the 486 or any other machine as a build machine and then load the finished product onto the 386. I know there were a lot of features added from i386 up through i686 but if you want to get a release out the door, how about concentrating on just i386. An i386 build will run on any system, that way everyone can get something, then we can optimize. Config files would be good. I'm trying to get gcc to by coping it from an i386 build root image available from the uClibc website (the link is in the FAQ, Is a pre-compiled uClibc development system available?). I'll try to make a gcc package to make this easier. Joseph Mulloy jdmulloy at gmail.com On Wed, Aug 6, 2008 at 12:21 AM, Poly-p man wrote: > On Tuesday 05 August 2008 11:26:43 pm Joseph Mulloy wrote: > > I have managed to get a very basic version of links running on my box. It > > was actually an option in build root, I just copied over the binary and > it > > works, I compiled it for 386, can't test it obviously but I believe it > > should work. > 386 binaries should work on all systems... right? > > Do you want me to send you a copy? > why not? :D > > Also ifup usually > > segfaults, > Known issue - it's bash's fault, actually. First off, stop using ifup (use > ifconfig, udhcpc for dhcp), and secondly, 1.0 will use busybox ash > entirely. > > Seems bash + uclibc + kernel > 2.6.24 segfaults randomly. That's why I > started > writing my init, before realizing it was a bash issue :D > > > I'll try working on LILO, but it > > would be helpful if I had a toolchain and compiler on the box. > > True... currently I have my 486 with a full compiler - makes lilo nicely - > of > course, this will make 486 binaries, so no dice. > > If you want to build everything with full compiler support, I'll upload the > config files, and you can save me about 2/3s of the compile time for > release :P > > poly-p man > _______________________________________________ > Poly-p-ux mailing list > Poly-p-ux at lists.ibiblio.org > http://lists.ibiblio.org/mailman/listinfo/poly-p-ux > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.ibiblio.org/pipermail/poly-p-ux/attachments/20080806/5332f7b4/attachment.html From polypolyman at ibiblio.org Wed Aug 6 01:31:25 2008 From: polypolyman at ibiblio.org (Poly-p man) Date: Wed, 6 Aug 2008 01:31:25 -0400 Subject: [Poly-p-ux] Hi all just installed poly-p-ux on a 586 In-Reply-To: <5b530dbd0808052218i1c256416pda9d23efe9c1ad5f@mail.gmail.com> References: <200808060021.33383.polypolyman@ibiblio.org> <5b530dbd0808052218i1c256416pda9d23efe9c1ad5f@mail.gmail.com> Message-ID: <200808060131.25767.polypolyman@ibiblio.org> On Wednesday 06 August 2008 01:18:52 am Joseph Mulloy wrote: > As you probably already know, you can build an i386 version and load it on > any system that supports at least the same instruction set. You can use the > 486 or any other machine as a build machine and then load the finished > product onto the 386. I know there were a lot of features added from i386 > up through i686 but if you want to get a release out the door, how about > concentrating on just i386. An i386 build will run on any system, that way > everyone can get something, then we can optimize. Config files would be > good. basically, config files are the only difference... I already have those :D > I'm trying to get gcc to by coping it from an i386 build root image > available from the uClibc website (the link is in the FAQ, Is a > pre-compiled uClibc development system available?). I'll try to make a gcc > package to make this easier. meh... too hard... just use a buildroot (or anything else - lilo is mostly bin86 code, if not entirely static anyway)... It's not too hard to add arches, it's mostly hard to do the few packages that are annoying... lilo, for example. Tomorrow (I'll go to sleep soon - if motion detecting on the sixaxis doesn't kill me first :D) I'll work on the release... ...btw, so far, 386 has given me troubles every time... back in the 0.20 days, it actually killed my host system slowly to chroot into the system! This time, I'm having a bit of trouble - I've been too lazy to try much, tho. poly-p man From polypolyman at ibiblio.org Wed Aug 6 15:04:56 2008 From: polypolyman at ibiblio.org (Poly-p man) Date: Wed, 6 Aug 2008 15:04:56 -0400 Subject: [Poly-p-ux] config files Message-ID: <200808061504.57106.polypolyman@ibiblio.org> The config files for everything except buildroot and 686's kernel (still working on that) are now on the ftp site. I'm adding module support to the c portion of init, and I'll throw it up on the site as soon as that's done. poly-p man From jdmulloy at gmail.com Thu Aug 7 02:39:53 2008 From: jdmulloy at gmail.com (Joseph Mulloy) Date: Thu, 7 Aug 2008 02:39:53 -0400 Subject: [Poly-p-ux] Hi all just installed poly-p-ux on a 586 In-Reply-To: <5b530dbd0808052312ifb4cb5elfa7432072f35ca1a@mail.gmail.com> References: <200808060021.33383.polypolyman@ibiblio.org> <5b530dbd0808052218i1c256416pda9d23efe9c1ad5f@mail.gmail.com> <200808060131.25767.polypolyman@ibiblio.org> <5b530dbd0808052312ifb4cb5elfa7432072f35ca1a@mail.gmail.com> Message-ID: <5b530dbd0808062339r3b78096bj5af8da45729964f2@mail.gmail.com> Hi again. I haven't made much progress with gcc or lilo. I did dig another old machine out of a closet. It's a 200MHz Pentium MMX. I took everything out of it before I put it away in the closet so I had to scrounge up a fan, memory, and a hard drive. I also upgraded the ram in a PIII system recently which freed up a 128MB stick, so now I have a PII class system with a 333MHz Celeron, 256MB of RAM (128MB + 64MB + 64MB), a 20 GB drive that came with the system that had it's ram upgraded and an AGP nVidia card from another machine that got a video card upgrade. I'm installing debian on it now, but I'm leaving room of the drive for other things, like poly-p-ux if needed. I've got plenty of hardware to work with, now all I need is that buidlroot .config file and working gcc on poly-p-ux. I also need to find more NICs, I know I have more, I just can't seem to find them. Joseph Mulloy jdmulloy at gmail.com On Wed, Aug 6, 2008 at 2:12 AM, Joseph Mulloy wrote: > Send your config file when you can. As soon as I get gcc working I'll > trying getting lilo to work. > > Joseph Mulloy > > jdmulloy at gmail.com > > > On Wed, Aug 6, 2008 at 1:31 AM, Poly-p man wrote: > >> On Wednesday 06 August 2008 01:18:52 am Joseph Mulloy wrote: >> > As you probably already know, you can build an i386 version and load it >> on >> > any system that supports at least the same instruction set. You can use >> the >> > 486 or any other machine as a build machine and then load the finished >> > product onto the 386. I know there were a lot of features added from >> i386 >> > up through i686 but if you want to get a release out the door, how about >> > concentrating on just i386. An i386 build will run on any system, that >> way >> > everyone can get something, then we can optimize. Config files would be >> > good. >> basically, config files are the only difference... I already have those :D >> > I'm trying to get gcc to by coping it from an i386 build root image >> > available from the uClibc website (the link is in the FAQ, Is a >> > pre-compiled uClibc development system available?). I'll try to make a >> gcc >> > package to make this easier. >> meh... too hard... just use a buildroot (or anything else - lilo is mostly >> bin86 code, if not entirely static anyway)... >> >> It's not too hard to add arches, it's mostly hard to do the few packages >> that >> are annoying... lilo, for example. >> >> Tomorrow (I'll go to sleep soon - if motion detecting on the sixaxis >> doesn't >> kill me first :D) I'll work on the release... >> >> ...btw, so far, 386 has given me troubles every time... back in the 0.20 >> days, >> it actually killed my host system slowly to chroot into the system! This >> time, I'm having a bit of trouble - I've been too lazy to try much, tho. >> >> poly-p man >> _______________________________________________ >> Poly-p-ux mailing list >> Poly-p-ux at lists.ibiblio.org >> http://lists.ibiblio.org/mailman/listinfo/poly-p-ux >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.ibiblio.org/pipermail/poly-p-ux/attachments/20080807/440e7a29/attachment.html From jdmulloy at gmail.com Tue Aug 12 02:04:59 2008 From: jdmulloy at gmail.com (Joseph Mulloy) Date: Tue, 12 Aug 2008 02:04:59 -0400 Subject: [Poly-p-ux] Hi all just installed poly-p-ux on a 586 In-Reply-To: <5b530dbd0808062339r3b78096bj5af8da45729964f2@mail.gmail.com> References: <200808060021.33383.polypolyman@ibiblio.org> <5b530dbd0808052218i1c256416pda9d23efe9c1ad5f@mail.gmail.com> <200808060131.25767.polypolyman@ibiblio.org> <5b530dbd0808052312ifb4cb5elfa7432072f35ca1a@mail.gmail.com> <5b530dbd0808062339r3b78096bj5af8da45729964f2@mail.gmail.com> Message-ID: <5b530dbd0808112304w63f1352eif40f2dc84174ee6e@mail.gmail.com> Hi Poly-p-man Can you post the build root config file? I'm still having issues getting gcc to run. I get the following error messgae. gcc: symbol '__ctypr_b': can't resolve symbol in lib 'gcc'. I need all the configs to make sure everything is exactly the same. I need to get gcc working on this system. Joseph Mulloy jdmulloy at gmail.com On Thu, Aug 7, 2008 at 2:39 AM, Joseph Mulloy wrote: > Hi again. I haven't made much progress with gcc or lilo. I did dig another > old machine out of a closet. It's a 200MHz Pentium MMX. I took everything > out of it before I put it away in the closet so I had to scrounge up a fan, > memory, and a hard drive. I also upgraded the ram in a PIII system recently > which freed up a 128MB stick, so now I have a PII class system with a 333MHz > Celeron, 256MB of RAM (128MB + 64MB + 64MB), a 20 GB drive that came with > the system that had it's ram upgraded and an AGP nVidia card from another > machine that got a video card upgrade. I'm installing debian on it now, but > I'm leaving room of the drive for other things, like poly-p-ux if needed. > I've got plenty of hardware to work with, now all I need is that buidlroot > .config file and working gcc on poly-p-ux. I also need to find more NICs, I > know I have more, I just can't seem to find them. > > Joseph Mulloy > > jdmulloy at gmail.com > > > On Wed, Aug 6, 2008 at 2:12 AM, Joseph Mulloy wrote: > >> Send your config file when you can. As soon as I get gcc working I'll >> trying getting lilo to work. >> >> Joseph Mulloy >> >> jdmulloy at gmail.com >> >> >> On Wed, Aug 6, 2008 at 1:31 AM, Poly-p man wrote: >> >>> On Wednesday 06 August 2008 01:18:52 am Joseph Mulloy wrote: >>> > As you probably already know, you can build an i386 version and load it >>> on >>> > any system that supports at least the same instruction set. You can use >>> the >>> > 486 or any other machine as a build machine and then load the finished >>> > product onto the 386. I know there were a lot of features added from >>> i386 >>> > up through i686 but if you want to get a release out the door, how >>> about >>> > concentrating on just i386. An i386 build will run on any system, that >>> way >>> > everyone can get something, then we can optimize. Config files would be >>> > good. >>> basically, config files are the only difference... I already have those >>> :D >>> > I'm trying to get gcc to by coping it from an i386 build root image >>> > available from the uClibc website (the link is in the FAQ, Is a >>> > pre-compiled uClibc development system available?). I'll try to make a >>> gcc >>> > package to make this easier. >>> meh... too hard... just use a buildroot (or anything else - lilo is >>> mostly >>> bin86 code, if not entirely static anyway)... >>> >>> It's not too hard to add arches, it's mostly hard to do the few packages >>> that >>> are annoying... lilo, for example. >>> >>> Tomorrow (I'll go to sleep soon - if motion detecting on the sixaxis >>> doesn't >>> kill me first :D) I'll work on the release... >>> >>> ...btw, so far, 386 has given me troubles every time... back in the 0.20 >>> days, >>> it actually killed my host system slowly to chroot into the system! This >>> time, I'm having a bit of trouble - I've been too lazy to try much, tho. >>> >>> poly-p man >>> _______________________________________________ >>> Poly-p-ux mailing list >>> Poly-p-ux at lists.ibiblio.org >>> http://lists.ibiblio.org/mailman/listinfo/poly-p-ux >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.ibiblio.org/pipermail/poly-p-ux/attachments/20080812/6047ad4f/attachment.html From polypolyman at ibiblio.org Sun Aug 17 11:07:39 2008 From: polypolyman at ibiblio.org (Poly-p man) Date: Sun, 17 Aug 2008 11:07:39 -0400 Subject: [Poly-p-ux] stuff is on the server Message-ID: <200808171107.41143.polypolyman@ibiblio.org> rconfs (buildroot) are in the same directory as everything else... they are subject to change and may or may not be the version that has the full toolchain. Note: don't build in a gentoo multilib system! start a 32-bit chroot if you have to. Also, added bonus: devone.patch (courtesy of Marcin, cleaned up for recent kernels) is in projects/. have fun poly-p man