My Slackware 12.1 install hangs as it boots. It hangs at the udev-trigger --retry-failed (Topic about this I read about here: http://www.linuxquestions.org/questi...t=udev+trigger) but only for about 10 seconds or so, it's still annoying.
But the biggest hang is at the very end, about 30 - 45 seconds, I would say. It gets to the end, the part where it says loading the gpm mouse support, and then after about 30 seconds it gives me the log in. I tried disabling the mouse line, but then it just hangs at a line about alsa. I don't know what it is doing at this time because it doesn't seem to be doing anything.
My dmesg is about 600 lines long right now, next time I reboot I'll include it, I can't reboot right now. Are there any other files I should give that would give me some clues?

this is most likely dhcpd trying to get an IP from eth0 when it's unplugged
I don't know why but my system incests that eth0 needs to get an IP address from dhcp
you could put some
echo "starting this "
echo "configuring that "
lines in your /etc/rc.d scripts
to track this down
delete your log files then use touch to make empty log files
much much faster than deleting lines in an editor
this way you know what boot the log file is about

Huh, that would make sense, I have always had terrible problems with my internet.
I use atheros madwifi drivers, I don't use eth0, but ath0. Got the drivers off of Alien's wiki, there used to be a pause when the bootup procedure reached the internet connection point. Here is the code from /etc/rc.d/rc.inet1
I thin it reads ${1} as eth0, and it doesn't see a carrier because it should be looking for ath0. It used to be that DHCP_TIMEOUT was 10, but it took too long, so I changed it. There seems to be about a 30%-ish chance that my internet works when I log in, if it doesn't, I typically have to run a script as root that I made.
I know I could put an conditional in there so that it would automatically run if the computer failed to initially start the internet, but I never bothered. Could I edit the boot sequence to replace simply running /etc/rc.d/rc.inet1 with /etc/rc.d/rc.inet1 ath0_start?

If you arent' connected to the internet on the system startup, then there might be very long pause when sendmail daemon starts (until connection is timed out, which is more than 30 sconds).

To be more specific, if a box is not assigned to a domain, then sendmail takes forever to load. Add a domain name (for example, localdomain) to the box name in /etc/hosts and this will solve sendmail loading issues. A quick check if sendmail is the cause of the delay is simply disabling the executable bit on /etc/rc.d/rc.sendmail.