* Bruno Lustosa <[EMAIL PROTECTED]> [06-02-2003 20:42]: > Yesterday night, I was using linux, all was fine. I did a emerge sync > and a emerge -up world, and it said it would be upgrading a few > packages, including gcc among others. > I also did an emerge glibc, to recompile it from scratch. All went well, > no problems at all. Today, I shutdown the machine, and later when I > tried to boot, it wouldn't. > Just when it starts init, it spits lots of messages about not being able > to write to some files (read-only fs), and lots of them about grsec > sending signal 11 to some applications. > > (...)
Well, just for all of you to know what happened. I just fixed it, so I'd want to let everyone know.. nobody can tell how many people will go through what I passed in the future. It seemed that devfsd wasn't running, though there was a /dev/.devfsd (got it from /sbin/rc). Tried to rm it, but it wouldn't allow me. So, devfs was running, but devfsd wasn't. If I would run devfsd manually, things would start to work better. So, a flash of light came to my mind, and I decided to look at /etc, as only thinggs I changed were in my last upgrade, and as I went to bed because it would take too long, I haven't really seed what happened. To my surprise, I found out /etc/._cfg_inittab and /etc/._cfg_rc.conf, because of config_protect. After diff'ing these files with the old ones, I saw that there were lots of changes on inittab. Just as I copied it over and rebooted, it started normally again. Bingo! So, for all of you.. if things start to work weirdly (or simply not work) after an upgrade of some sort through emerge, have a look at unchanged files due to config_protect. Could happen to anyone, specially to people new to gentoo's unique features (there's nothing like this in slackware or debian, the systems I used before). -- Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] Network Administrator/Web Programmer | ICQ UIN: 1406477 Rio de Janeiro - Brazil |
msg00703/pgp00000.pgp
Description: PGP signature
