Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sun 23 Nov 2014, 21:18
All times are UTC - 4
 Forum index » Advanced Topics » Cutting edge
Saluki, Puppy Remastered
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 4 of 24 [351 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, ..., 22, 23, 24 Next
Author Message
big_bass

Joined: 13 Aug 2007
Posts: 1747

PostPosted: Thu 09 Sep 2010, 10:26    Post subject:  

Iguleder

I just noticed today that you have an interest in package management
you wrote code for a thingy manager interesting

I spent a lot of time writing a GUI front end to slackwares pkgtools
and it is 100% compatible on the official slackware or on TXZ pup
called slaxer_pkg_tools2.2
http://pastebin.com/kYUcMhSx


Joe

_________________
debian wheezy ,linux mint, slackware I use them all and they all have good points
Mint would be best for general users though
Back to top
View user's profile Send private message 
jemimah


Joined: 26 Aug 2009
Posts: 4309
Location: Tampa, FL

PostPosted: Thu 09 Sep 2010, 10:28    Post subject:  

How old of a computer is it reasonable to try to support? At what point do we give up on older hardware?

Back to top
View user's profile Send private message Visit poster's website 
Aitch


Joined: 04 Apr 2007
Posts: 6825
Location: Chatham, Kent, UK

PostPosted: Thu 09 Sep 2010, 11:08    Post subject:  

LOL Good call, jemimah

However it's not the failure rate on a lot of my old hardware that bothers me....it's the electricity bill!

Old scsi server boxes run wonderfully but you can almost cook on 'em, they need loadsa room, and damn, they're noisy Laughing

Anyone know what happened to Ted dog and his T2 cross compile efforts?

Anyone get a VIA 8505/Eken M001 iPad clone running puppy?....Android's running away with it, atm

They'd be a bit more economical, I suppose....and they're less than $100

http://www.alibaba.com/trade/search?SearchText=eken+m001&Country=&CatId=7&IndexArea=product_en&fsb=y

Aitch Smile
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4376

PostPosted: Thu 09 Sep 2010, 11:57    Post subject:  

@bigbass
I compiled busybox to include the config options. Just run
Code:
bbconfig >my_dot_config
The patch to add minimp3 is already attached in my previous post (and I posted the patch to the busybox mail list)

I understand your point about people using full media players, but I think that at least during development, it is a good idea to have a method of testing that all your piece/parts work including sound, especially if we are going to have a minimal base install. (I do have a separate build of minimp3 though and it is only ~31kb) It would suck to be weeks/months into development and figure out that sound was broken. I'm not 100% sure, but I think that the busybox beep applet uses the pc speaker, so it wouldn't be a good test.

Re:pkgtools - do you have a good reference for putting the build info in the proper format ... and does it work with Amigo's src2pkg?

_________________
Web Programming - Pet Packaging 100 & 101
Back to top
View user's profile Send private message 
dejan555


Joined: 30 Nov 2008
Posts: 2715
Location: Montenegro

PostPosted: Thu 09 Sep 2010, 13:33    Post subject:  

Puppy from scratch sounds good. I support that.
If you go that way I will surely join testing. Cool

_________________
Dpup 487 | Puppy Gallery | My photo gallery | mtPaint works
Back to top
View user's profile Send private message Visit poster's website MSN Messenger 
big_bass

Joined: 13 Aug 2007
Posts: 1747

PostPosted: Thu 09 Sep 2010, 13:53    Post subject:  

Quote:
@bigbass
I compiled busybox to include the config options. Just run
Code:
bbconfig >my_dot_config


Thanks for the quick response is there another way to run that code you posted without installing the new busybox ?

if not could you pastebin it please when you have the time ?


Quote:

Re:pkgtools - do you have a good reference for putting the build info in the proper format ... and does it work with Amigo's src2pkg?


any package slackware compatible will work to build with tgz ,txz ,tlz ,tbz

there are also two dragNdrop scipts to make a slack-desc automatically and
and to make TXZ or tgz packages

and yes of course I am compatible with amigo's src2pkg I have had interest in his tools since puppy linux version 3.01 and was the first to get src2pkg running on puppy of course thanks to his help and advice it has become a backbone
to building packages there is also a GUI config tool I wrote for it
its isnt required its just handy add on to have when doing many complies

GUI for the configuration of packages for src2pkg
http://www.murga-linux.com/puppy/viewtopic.php?mode=attach&id=26243

original post
http://www.murga-linux.com/puppy/viewtopic.php?search_id=848235390&t=51197

Joe

_________________
debian wheezy ,linux mint, slackware I use them all and they all have good points
Mint would be best for general users though
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4376

PostPosted: Thu 09 Sep 2010, 14:14    Post subject:  

@BB re:bb - sure... I'll gzip the .config and post it when I get home this evening (it is basically an allyesconfig without pam, selinux, rfkill or debugging and includes the "full" versions of modutils ... basically setup to include as many desktop tool replacements as possible not for the initrd)
ht21_1.gif
 Description   jemimah's bathtub curve translated into kernel driver support
 Filesize   5.23 KB
 Viewed   1339 Time(s)

ht21_1.gif


_________________
Web Programming - Pet Packaging 100 & 101
Back to top
View user's profile Send private message 
raffy

Joined: 25 May 2005
Posts: 4796
Location: Manila

PostPosted: Thu 09 Sep 2010, 18:30    Post subject: how old  

To the question "how old (hardware to support)", one may say "Pentium III", but the challenge is more of supporting alternative low-power configurations. In this regard, we have the xcore86 (edubook, which Barry said is OK with the latest kernel in Wary 070), also the VIA Unichrome and AMD Geode GX/LX, among others.
_________________
Puppy user since Oct 2004. Want FreeOffice? Get the sfs (English only).
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4376

PostPosted: Thu 09 Sep 2010, 19:54    Post subject: Re: how old  

raffy wrote:
To the question "how old (hardware to support)", one may say "Pentium III", but the challenge is more of supporting alternative low-power configurations. In this regard, we have the xcore86 (edubook, which Barry said is OK with the latest kernel in Wary 070), also the VIA Unichrome and AMD Geode GX/LX, among others.

All of those should work with -march=586 - the only 486 platforms readily available and fast enough to comfortable run are the vortex86 and some of those don't even work with the standard puppy 486 build (vortex86sx don't have a fpu - similar to the 486sx) ... the -march=i486

Edit - Busybox patches added + an additional patch that will alias waitmax to busybox's timeout applet... there are a couple of differences though

    # timeout --help
    BusyBox v1.15.0.svn (2009-07-25 18:23:53 GMT-Cool multi-call binary

    Usage: timeout [-t SECS] [-s SIG] PROG [ARGS]

    Runs PROG. Sends SIG to it if it is not gone in SECS seconds.
    Defaults: SECS: 10, SIG: TERM.

    # waitmax --help
    Usage: waitmax [-s SIGNUM] MAXTIME PROGRAM [ARGS...]

    Execute PROGRAM as a subprocess. If PROGRAM does not exit before MAXTIME
    seconds, it will be killed with SIGTERM or an alternative signal.

    -s, --signal SIGNUM kill with SIGNUM on timeout
    -h, --help this help
    -V, --version show version an exit


It should mean minimal rewrite to the init script... or would it be better for me to just add waitmax to busybox?
I am trying to minimize the number of binaries required in the initrd, preferably down to just busybox for faster boots. Now that I know how to add an applet, its just a matter of condensing the code into one .c file (waitmax already is) and editing about 4 other files. (I wonder if sqlite's amalgamation script could help make the process easier, or if it is sqlite specific?)
busybox-technosaurified.tar.gz
Description 
gz

 Download 
Filename  busybox-technosaurified.tar.gz 
Filesize  47.19 KB 
Downloaded  224 Time(s) 

_________________
Web Programming - Pet Packaging 100 & 101
Back to top
View user's profile Send private message 
mavrothal


Joined: 24 Aug 2009
Posts: 1794

PostPosted: Fri 10 Sep 2010, 08:33    Post subject:  

technosaurus wrote:
I'll gzip the .config and post it when I get home this evening (it is basically an allyesconfig without pam, selinux, rfkill or debugging and includes the "full" versions of modutils


Mobile computing devices are really expanding and rfkill would be nice to include. Also debugging would be useful. At-least at the early stages of the project.

_________________
Kids all over the world go around with an XO laptop. They deserve one puppy (or many) too Very Happy
Back to top
View user's profile Send private message 
jemimah


Joined: 26 Aug 2009
Posts: 4309
Location: Tampa, FL

PostPosted: Fri 10 Sep 2010, 10:39    Post subject:  

I agree about rfkill. I believe the kernel bug that plagued Barry's Acer has been fixed by 2.6.33. I build my kernels with rfkill (even Fluppy) and so far no one's complaining.
Back to top
View user's profile Send private message Visit poster's website 
linuxcbon

Joined: 09 Aug 2007
Posts: 792

PostPosted: Fri 10 Sep 2010, 11:28    Post subject:  

What about removing unused users and groups in /etc/group gshadow etc .
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4376

PostPosted: Fri 10 Sep 2010, 11:40    Post subject:  

jemimah wrote:
I agree about rfkill. I believe the kernel bug that plagued Barry's Acer has been fixed by 2.6.33. I build my kernels with rfkill (even Fluppy) and so far no one's complaining.

I need to upgrade to a different kernel so that rfkill.h is available in order to make it compile.

I will add rfkill when I rebuild it in aboriginal, but for the time being I am busyboxing the other programs that are used in the initrd. So far I got:
guess_fstype working (still needs some busybox code tweaks)
fusermount condensed down to a single C file so it is pretty close
identified timeout as a replacement for waitmax

I am also considering the rest of the binaries in initrd that aren't already available in busybox (those can be replace already with some code modifications borrowed from tinycore/slitaz)

other possible busybox applets:
autologinroot
suggestions?

Note: So far I can get everything to work and compile as an applet, usually with warnings due to duplicated/differing code from busybox. Denys Vlasenko sent me some advice back to reduce the warnings (and thus code size as well) but I can't actually code in C, so it takes me a while to easter egg the correct fixes. If anyone has time to do some C it would help out a lot and your work could end up getting included upstream in busybox proper. I have set up a 4 stage process to accomplish this - kindof a busybox staging area.
Stage 1: gather all of the files that a program needs to build into one folder. such that it will build with gcc *.c -o <applet>
Stage 2: condense all of the files into a single C file (similar to the sqlite amalgamation) that will successfully compile with a simple gcc -o <applet> applet.c
Stage 3: tweak the includes section of the C file to use libbb.h and tweak about 4 *.src files in busybox to try and build it (correcting errors until it builds)
Stage 4: once an applet builds - it goes here for code formatting and fixes (use busybox functions where possible and remove unnecessary code)

I plan to do this a little different than my last tarball - rather than one large patch, I'll split them out by applet and include the <directory>/<applet>.c file and a small patch for the few modifications. This will make it easier to apply to later versions.

_________________
Web Programming - Pet Packaging 100 & 101
Back to top
View user's profile Send private message 
clarf


Joined: 13 Jun 2007
Posts: 612
Location: The old Lone Wolf

PostPosted: Fri 10 Sep 2010, 13:29    Post subject: Re: how old  

technosaurus wrote:
To the question "how old (hardware to support)", one may say "Pentium III", but the challenge is more of supporting alternative low-power configurations. In this regard, we have the xcore86 (edubook, which Barry said is OK with the latest kernel in Wary 070), also the VIA Unichrome and AMD Geode GX/LX, among others.
All of those should work with -march=586 - the only 486 platforms readily available and fast enough to comfortable run are the vortex86 and some of those don't even work with the standard puppy 486 build (vortex86sx don't have a fpu - similar to the 486sx) ... the -march=i486

I know ttuuxxx still compiles software with -march=i386. I don´t want to start another debate for this but I think it should avoided for future Puppy releases, the older platform to point should be 486 as minimum (and even this architecture is too old to be considered, I haven´t seen any functional/active pre-pentium system from long time ago).

technosaurus wrote:

It should mean minimal rewrite to the init script... or would it be better for me to just add waitmax to busybox?
I am trying to minimize the number of binaries required in the initrd, preferably down to just busybox for faster boots. Now that I know how to add an applet, its just a matter of condensing the code into one .c file (waitmax already is) and editing about 4 other files. (I wonder if sqlite's amalgamation script could help make the process easier, or if it is sqlite specific?)

technosaurus, In Puppy 214R, Dougal removed many busybox applets and modified the init script, it´s a good example of size reduction that you should look.

It´s very hard to remove any applet that is not actually used by init script, anyway I think a review for init is necessary.

For example he removed the "expr" applet and replaced the implicated code in favor of the "let" builtin function. That´s seems also a faster function.

clarf
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4376

PostPosted: Fri 10 Sep 2010, 16:18    Post subject: Re: how old  

clarf wrote:
I know ttuuxxx still compiles software with -march=i386.
As do I - when the speed of the program is inconsequential, because it does typically produce smaller code especially if combined with -mpreferred-stack-boundary=2 and some other flags.

It is perfectly acceptable to lower the architecture for a build (because it will still run on all systems that run on the standard higher architecture), but if you go above the standards set as the norm, it should be annotated. Some areas where a higher architecture would be acceptable are encoders/decoders etc... where a drastic improvement is gained or performance on the lower architecture is deemed to be unacceptable (I don't know of any that meet the latter for 586 but for 486 there are many)

_________________
Web Programming - Pet Packaging 100 & 101
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 4 of 24 [351 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, ..., 22, 23, 24 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Cutting edge
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1131s ][ Queries: 12 (0.0113s) ][ GZIP on ]