<DIV>Hi,</DIV>
<DIV> </DIV>
<DIV>This is in reply to Ben's post on my original post. BTW, sorry about my replies not appearing under the appropriate thread on the trilug web site. I use digest to get messages, and I haven't figured out how to put the right subject line in yet. I am also sorry that the original post is not indented correctly on the web, my second one is right.</DIV>
<DIV> </DIV>
<DIV>Are you the Ben I met at Perl meetings and the Trilug installfest ? I will assume you are, sorry I don't remember your last name so I can't be sure. If so, your recommendation is one of the reasons I decided to try Debian. Thanks alot.</DIV>
<DIV> </DIV>
<DIV>You are right about the hardware detection, but once I got my video info right it did work. It's actually kind of like the older installation process. In the mid-90's, I usually had to generate the XF86config myself, but the tools (running xf86config command) usually made the process much easier. I wasn't aware of the Xandros distribution, but I did try Knoppix and posted my comments about it. </DIV>
<DIV> </DIV>
<DIV>Thanks for the praise on the post. Especially if you are the Ben I think you are. It's nice to hear that a Debian expert like yourself thought the post was basically accurate and well-written. You are welcome to share the post with anyone you like, Debian people, new users or whatever. If you like, I could try to rewrite the post to be suitable for posting on a web site. Right now, the post just reads as a personal narrative. I am not sure that this is a bad thing. I also thought I did suggest that people use the network install and only download one cd, maybe it just needs more emphasis. I hang out in the chat room, so if you would like to talk about it that would be fine. The only other thing I would like to do if it were posted on a website is to use DocBook. However, I have never used it before so it may take a couple days to learn it. </DIV>
<DIV> </DIV>
<DIV>You are also right about the buzz on the Debian install being worse than the bite. I find this has more to do with how Debian people think and are. They are mostly technical people not marketers. They are willing to share all of the information with you even (and sometimes especially) the pitfalls. That's the way many competent technical people act. They post the bugs if there are problems and give you an honest report. They tell you the whole story, if you are patient enough to listen. Unfortunately, most other people don't think this way. By contrast, take the microsoft approach. They rarely if ever list bugs or problems. People then just assume that because they don't list problems the problems don't exist. And since Debian lists them, Debian must be full of problems. I have always wondered that if that were literally true why there are any patches given on the ms websites. I guess they would say they are only adding new features to improve customer service (or whatever). Or maybe changing some "features" that are counter-intuitive (what I would call a bug).</DIV>
<DIV> </DIV>
<DIV>On the sources.list issue, I saw this mentioned by Mike in his suggestion about using Knoppix. He is right, if you use Knoppix there are many more entries in the sources.list file. This is because Knoppix is really a mixed distribution (i.e. it takes some packages from stable, some from testing, and maybe some from unstable). The apt.conf file actually shows the default distribution as testing. It probably needs the extra entries to update correctly. When you install Debian using the normal install procedure, it only gives entries for the stable distribution. So the confusion on the complexity of the sources.list is really a product of using Knoppix. I didn't mention this in my Knoppix post.</DIV>
<DIV> </DIV>
<DIV>Hopefully we'll talk later,</DIV>
<DIV> </DIV>
<DIV>Bill Gooding</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>// Ben's original post</DIV>
<DIV> </DIV>
<DIV>Folks,<BR><BR>No, Debian's hardware detection leaves something to be desired, but it's<BR>something that they're working on. They're also working on a graphical<BR>installer that is a very high priority for the new Debian project leader<BR>Martin Michlmayr. Keep an eye out on the Debian Weekly News<BR>(<A href="http://www.debian.org/News/weekly/">http://www.debian.org/News/weekly/</A>) for updates on things like that. It<BR>also gives a very good accounting of new packages, orphaned packages (ones<BR>that no longer have an official Debian maintainer), and packages with<BR>security issues and updates.<BR><BR>Back to the point. While the Debian installer does not do very good<BR>hardware detection, it is also true that Debian expects users to know a bit<BR>more about their hardware than your average Red Hat install does.<BR>Personally, I consider this a good thing, but it's difficult when you get<BR>down into the realms of non-standard hardware, and specialty stuff.<BR>Debian's USB support is there, but not as intuitive as other distros. It<BR>does require you to know a little bit more about the software doing the USB<BR>work than do other distros. That being said, it's still not an overly<BR>difficult process, to my mind, and most folks will learn alot about their<BR>systems in the process of making all of this stuff work. If that's not your<BR>cup of tea, you probably want to go with a Debian distro like Xandros, which<BR>has better support for that kind of thing at present. I'm sure the Debian<BR>project will claim a great deal of that technology over time, the way they<BR>did with the Progeny and Corel Debian distros.<BR><BR>Bill, that is an EXCELLENT document on the installation of Debian. I'd like<BR>to see that put into a document that we can have up on our website for users<BR>who may be interested in trying Debian, but who may want to know more about<BR>the install process before trying it. The buzz on the process is typically<BR>MUCH worse than the install process itself, and so many users don't even try<BR>it, or wait a long time to do so, largely due to the intimidation factor.<BR>This might help to alleviate alot of that. Thanks for putting it together.<BR>You did an excellent job. It actually pointed out in a better way than I<BR>might have described the process, and looked at it from a much more<BR>realistic point of view. I never really thought of the install process as<BR>being in 2 stages, but you're quite right in saying that it is. You might<BR>want to emphasize that Debian is quite easy to install over a high speed<BR>Internet connection, and that those with that facility may wish to avoid<BR>downloading the CDs altogether, or at most, only download the first CD.<BR>Only folks doing a standalone system with no connectivity need all three<BR>CDs.<BR><BR>One person mentioned that the sources.list file was a bit intimidating. I<BR>thought so at first as well, but maybe we can change that. The file is<BR>fairly straight forward in that it simply defines protocols (http, ftp),<BR>server URLs, distro versions (woody, sarge, sid, or stable, testing,<BR>unstable, either way), etc. for downloading packages through apt, and<BR>updating your system with security and bug fixes. Once you get a good<BR>sources.list file, it's easy to just port that too other machines via a<BR>floppy, and use it elsewhere. In fact, it is not even architecture<BR>dependent, as I ported one from an Intel box, and it worked flawlessly on a<BR>Sparc machine without ever needing to edit it. Also, by just changing<BR>stable to testing, or woody to sarge, whatever, you can then just run<BR>'apt-get update' and 'apt-get dist-upgrade' and easily go from one Debian<BR>distro to the next. I've never been able to do that with Red Hat. I've<BR>ALWAYS had problems trying to upgrade those, whereas Debian's dist-upgrade<BR>process has been an absolute joy. YMMV.<BR><BR>That's my tupence. Thanks again, Bill.<BR><BR>Regards,<BR>Ben Pitzer<BR></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://us.rd.yahoo.com/search/mailsig/*http://search.yahoo.com">The New Yahoo! Search</a> - Faster. Easier. Bingo.