On Tue, 29 Jun 2004 12:18:51 -0700 (PDT) Shish <[EMAIL PROTECTED]> wrote:
> Also, I'm on dialup, and it works fine. The whole "time to waste" > seems odd too- what does *your* computer do while you sleep? I would > guess that for most people, not something too productive... > When I first attempted to install Gentoo I was on Mandrake 8.2/9.0 or something. I had a winmodem in my laptop which worked fine in Mandrake, but at that time I had no clue as to how I could get the Gentoo installation to load a lt_modem kernel module. For me, at that time I found the attempt to install Gentoo overly frustrating. I'm sure if I had had a real modem the install would have been much more satisfying. Usually when I'm sleeping my computer is taking part in the Great Internet Mersenne Prime Search (GIMPS) http://www.mersenne.org/prime.htm > > compiling everything per someone else's emerge scripts > > So do you use someone else's ./configure && make && make install, or > do you do things your own way? :p Portage is basically C/M/MI, but > with dependancy tracking built in (and some other odd bits) Yes, of course I use the software author's configure scripts, I figure they know how to build their software. But I never simply ./configure && make && make install. What if the program sucks and I want to remove it? What if the default install spreads config files across a dozen directories? At the very minimum, ie. when I'm lazy, I'll ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var (or /var/log). Then I'll make; create a description-pak file; su; checkinstall. If I'm less lazy, I'll also make a doc-pak directory first. Usually I'll skip the checkinstall, make install DESTDIR=/tmp/something; cd /tmp/something; check permissions, gzip man pages, ensure doc files are where I want them, make a slack-desc file, strip binaries if needed, etc. Then makepkg. Then install my newly built package. > Once the Immense Shiny Thing that is E17 is released, and all the > shiny thing collectors flock to it, what are you going to do about the > reputation of E being no more than a shiny toy for n00bs? I hope that day comes soon...I'll deal with the annoyance then. :) > > Runlevels > > Coming from SuSE / Mandrake / RedHat, I'm not sure of how BSD does > boot scripts, but I must say that Gentoo handles them very nicely > (Yeah, I'm looking into BSD to see how that works already...) > > The runlevels are more meta-runlevels, as there's no link to init - > and they're named, so you can do things like "rc offline" to go into > the "offline" runlevel, which figures service dependancies (calculated > dependancies are much nicer than giving each /etc/rc/ link a number > and hoping you got them in the right order) and takes down the > network-dependant things. Then rc-update to add/remove services from > runlevels, and rc-status to show which services are active. The simplicity that is Slackware's init scripts is that there are NO symlinks. No K01Something, S01Something, etc. There are not separate directories for each runlevel. All the init scripts are in /etc/rc.d/ If I want a service to run before or after another service I start it in the appropriate place in rc.M. Here is an excerpt of my rc.M. # Start the ACPI (Advanced Configuration and Power Interface) daemon: if [ -x /etc/rc.d/rc.acpid ]; then . /etc/rc.d/rc.acpid start fi # Load ALSA (sound) defaults: if [ -x /etc/rc.d/rc.alsa ]; then . /etc/rc.d/rc.alsa fi To get ALSA to load before ACPI, I just move it up in the file. If I want to disable a service, I just make /etc/rc.d/rc.servicename non-executable. The rc.servicename scripts have the usual start|stop|restart options. Here is the contents of my /etc/rc.d/ rc.0 rc.4 rc.6 rc.K rc.M rc.S rc.acpid rc.alsa rc.atalk rc.bind rc.cups rc.dnsmasq rc.font rc.gpm rc.hotplug rc.httpd rc.inet1 rc.inet1.conf rc.inet2 rc.inetd rc.ip_forward rc.local rc.lprng rc.modules rc.mysqld rc.nfsd rc.pcmcia rc.portmap rc.samba rc.sendmail rc.serial rc.sshd rc.syslog rc.sysvinit rc.udev rc.wireless rc.wireless.conf rc.yp Brad ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ enlightenment-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
