On Monday 10 December 2001 14:31, Justin Bengtson wrote: > > -----Original Message----- > > From: Mark Bigler [mailto:[EMAIL PROTECTED]] > > Sent: Monday, December 10, 2001 2:05 PM > > To: [EMAIL PROTECTED] > > Subject: [EUG-LUG:493] Re: naive distro questions > > > > > > A good list. I like it. > > thanks. i made it myself. :)
<snip> > > Often, assuming that you're using a Debian kernel with a standard > > config, such problems may be due to apt-get only handling app > > dependancies and something apt-get did would have worked better if > > it had also handled "recommends" and/or "replaces" properly. But, > > even with a standard Debian kernel in place, there a still apps > > (like those > > dependent on lm-sensors) that require you to modify the kernel, but > > never mention it. > > > > I know, just more of why Debian isn't your first choice. > > debian isn't my first choice (anymore) because they're still "stuck > in the 60's". for christ's (or whoever else you give props too...) > sake, use a newer f**king kernel! i'm sure there's a reason for it, > but i can't find it. 2.4.5 worked just fine on my firewall (P166) so > i can't exactly see why age of system would be a problem. With Debian, the problem is usually finding out how to bring it to the point you want. I don't know of a single Debian book that actually let's you in on how to use Debian. Very sad, almost everything is there waiting and ready to go, but... <snip> > > Again, I've found Debian source dependencies to work well. > > Clearly, Your Millage Has Varied. > > heh! > > debian source dependencies work fine. until you set apt to use the > testing sources. Possibly some of the hard to find magic was missed when you tried to use the testing sources. Hopefully you moved your whole system up to testing prior to trying to compile testing sources. Although I can't recommend dselect as an example of how to code a UI, for Debian, it's almost a must to learn how to use it when doing distribution upgrades (it's sort of a tradeoff in pain). > then everything goes to hell. unfortunately, as > said before, i am not "stuck in the 60's" and would like to use > newer-edge programs than those from last year. I know there are huge delays with some packages (Mozilla, StarOffice, etc.), but I'm generally up to date here (at the very least a long way from the '60s -- hey I liked the '60s). I'm certainly within a month or so of the latest of everything I'm using. > maybe that's why i am having such a problem. but redhat was just > fine with these newer versions. what's with debian? Many hands make light work. It's all volunteer. > > > 6. above all, the distro's installer should actually work. it > > > shouldn't forget important things like apt-utils (for debian) > > > > Wow. You got Debian to install without it including apt-utils!? > > kept happening with 2.2.4. i finally figured that one out and just > alt-f2'd during install and apt-got it before continuing with the > rest of the package install. little "fixes" like that really hack me > off. Weird. Not that it hacked you off, but that it happened ;) > > > that's what i want out of a distro. > > > > As I said, a good list, just what a user should expect. Ignoring > > the FHS and Linux kernel requirements, BeOS came close, OS/2 and > > Geos tried, and Windows doesn't really (people just tend to think > > anything that goes wrong in Windows was their own fault). > > > > Keeping plugging and we'll get there. > > i suppose what i really need is a distro for the soul. one that > let's you hack it to your heart's content, but doesn't require you to > hack it just to get it WORKING... redhat ALMOST fit the bill. but i > really just don't like the RPM system. and redhat had it's own > problems. Again, I'm not sure any system you install from scratch (no matter who ships it) ever "just works" all the time (yet).
