Quoting Orlando Andico <[EMAIL PROTECTED]>: > By making your own distro, instead of deriving from say RedHat, you add > very little value. Anybody can type > > ./configure > make > make install
I am sorry to disagree here, but making your own distro involves more than just typing these three lines. (1) There are many design decisions: where do you put files? (FSSTND, FHS, Linuxbase). Which sysvinit system do you use (debian-style, redhat style, etc). Do you use devfs or not? Do you use PAM or not? How do you handle NIS-related security issues, or do you just NOT include NIS in your distro. (2) Do you rewrite code when the build breaks? For example, linux-2.4.21 does not build cleanly with gcc-3.3, and you have to rewrite some code. Or do you just wait for the developer to rewrite his code? In my case, I can not wait and must do something right away. (3) Do you copy kudzu, or do you write your own hardware probing scripts? Would you feel tainted if you do so? (4) How do you handle installation issues? Do you use syslinux, loadlin, lilo, grub, etc? How do you fit all the binaries and libs needed for the install in a mere 2.88 boot disk image? Ian Sison is right in saying that it is not easy to make and maintain your own distro. For one person, this can be a lifetime of work. P~Manalastas -- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
