> I was thinking... I have a cable modem, so I'm constantly on the
> internet. Plus, the shared bandwidth is a concern because of skript
> kiddies. When I'm making world, I'm logged in as root for the entire
> build.
> Would it make sense to kill inetd in this case? Of course, I can always
> use newsreaders and other stuff. But, I don't have any other server
> daemons running other than inetd. Should I kill this when doing a make
> world? Is it wise to kill all network services when making world?
It shouldn't be worth worrying about. Running as root *routinely* is a
bad idea because it's easy to make a mistake, but this isn't like removing
files or browsing the web with Netscape running as root or anything that
obviously unwise. Just close your root shell when you're done.
If you want to be paranoid, the thing to be paranoid about is trying to
overwrite system components in use; for this reason, a lot of people play
it safe by doing "make world" in single-user mode. A lot more run "make
buildworld" in a regular running system and drop to single-user mode for
actually installing everything. [For actual details, see the handbook,
and Nik Clayton's great tutorial referenced there.]
I'm sorry if I was confusing when I suggested, a while back, that you
shouldn't run as root. What I was trying to say was that you should
*only* run as root when *necessary*, not that logging in as root was an
inherent danger in itself. root *is* necessary for installing new system
binaries.
Be well.
by