Messages in this thread | | | Date | Wed, 5 May 1999 20:02:09 +0100 | From | Steve Dodd <> | Subject | Re: Invalid inode->i_sb in clear_inode()? (was Re: Kernel Oops, 2.2.7) |
| |
On Wed, May 05, 1999 at 02:37:57PM -0400, Michael B. Trausch wrote:
> I know vaguely what you're talking about, but since I know almost nothing > about programming, I'll trust that you know what you're talking about.
Most unwise!
> One thing that I can do is mail the binary kernel image and its friends > the modules if that would help any -- i know that every built kernel is > different in some little way.
I don't think we need to be that drastic, yet :)
> Usually, I upgrade within 48 hours of the kernel release. The thing is > that my system is SO slow (486 dx/4) that it takes between two and three > hours to build a kernel. I learned that the first time I built one. So, > I do everything using cron, basically.
Hmm.. It only used to take my 486dx2-66 30-40 minutes max, but that was for 1.2/2.0. I don't think 2.2 is _that_ much bigger. You not compiling from floppies or tape or anything? <g>
> BTW... should I reboot my system, or is it stable? It seems like it's > stable to me... only thing is that syslog is printing everything to the > console unless tail -f /var/log/messages is run, but that's fine by me.
Hmm.. It depends what it's used for; it might not be such a bad idea to reboot if you can spare the downtime.
-- A neutron walks into a bar. "I'd like a beer" he says. The bartender promptly serves up a beer. "How much will that be?" asks the neutron. "For you?" replies the bartender, "no charge"
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |