Printable View
And with all these people demanding features all the time, i am sure a system won't age quickly....Quote:
Originally Posted by TheLlama
come on.... a GUI??? who uses that?? navigation? i got two [not so] good eyes and a map. Music? HAH! I like listening to my engine... And anyway, who has time for all that while driving and compiling a new kernel?
steve
Hmm... Ok, I'll bite. You're being sarcastic because eitherQuote:
Originally Posted by khemical
Either way, chill out, steve.
- you enjoy spewing venom from the cozy shelter of the Windows garden, or
- you misinterpreted thellama's comment re:an install becoming "frozen." I'm pretty sure that (s)he meant an individual install will become frozen, not development for the carpc toward which we're all working, in our sometimes strange ways.
- Bill S. Preston, Esq.
Correct. I meant that the individual's installation will come to a point where no more maintanence needs to occur (except for adding features). At this point it makes little sense to upgrade packages if everything works fine and meets specification.Quote:
Originally Posted by rubicon
BTW. I'm a he. As in, I'm a male.
Actually, I am 100% against using windows -- I am a mac/linux user. I was being sarcastic because, of all places, this forum seems to be filled with people who want to be on the bleeding edge.
Lets say that there exists a project for a frontend that becomes fairly popular, fairly quickly. It follows the development model of most linux apps, having a stable release, and a development release/cvs/subversion. And, for instance, if 60% of the people are happy with the stable release, the other 40% are wanting to try out the new features. Unless the developer is insane, ala RMS, and writes a lot of their own modules, this won't be a problem. But as with most projects, the cvs release creates a need for new dependancies that can always be changing. I don't blame developers for this, but using these apps on a bare LFS system gets to be a pain.
I have been using a bleeding edge LFS compile for the last 2 years or so. I update my system about every 2 months (automatically, overnight -- i don't have THAT much free time) to the current CVS/Testing release of LFS. I don't need time added to that to update dependancies that are used by only 1 program! I only use 1, MAYBE 2, programs that use GNOME. 1!! That is one f'n huge dependancy. And most of the frontends i see now use Qt. Thats even worse!!!
You can't please everybody. The only person I care to please is myself, so that is why I write my own software. Works the way I want it to, but never when I want it too ;)
steve
nice save
I'm using Fedora Core 3 on my laptop but am looking in to linux from scratch and will hopefully soon when I get some time use this on my car pc. Have had a good look around and it seems to be the best way to go to get the system as minmal as possible.
Here is my distro for pycar. Works on EPIA-Ms only.
http://indashpc.org/downloads/software/pycar-1.3.iso ( 10MB )
upon boot PyCar can be started by: /etc/init.d/rc.pycar
It is not yet official release, still have to clean up something. Hope this helps.
We're an LFS shop, but we used Slackware to help us learn some of the Linux intricacies before we made the jump to LFS.
LFS is not easy, though. We've used Redhat 6.x and 7.1 (the one without the glibc 3.0 nightmare). We've used Slackware 8,9,10; and we're now running LFS with a 2.6.7 kernel (which we've hacked the hell out of).
New users should stick with Fedora/Redhat (same thing), possibly Mandrake or Gentoo.
For really small installations, look at Peanut Linux or ZipSlack.
Intermediate users will probably all find Slackware or Debian to be the consensus.
Beyond that, LFS + custom kernel is the only option.
gentoo on an amd64 (sucks up lots of power) regularly updated via wireless through my home's adsl.
LFS!! I am actually in the final steps of customizing my LFS system for my EPIS MS board...
A little off topic...Is anybody using the linuxbios for their epia boards...they dont have one for mine yet, but as soon as they do im gonna be all over it...