Date: Tue, 29 Apr 1997 09:00:19 -0700 (PDT) From: Simon Shapiro <Shimon@i-Connect.Net> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: freebsd-hackers@FreeBSD.org, Julian Elischer <julian@whistle.com> Subject: Re: A Desparate Plea for Help... Message-ID: <XFMail.970429174652.Shimon@i-Connect.Net> In-Reply-To: <5304.862292870@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Jordan K. Hubbard; On 29-Apr-97 you wrote: > > BTW, I have disabled ALL LKM's in the system and it appears to hold > > together! > > <USUAL-OBLIGATORY-POINT TRIGGERED-BY="LKM-KEYWORD"> > If your installed LKMs are not in sync with your kernel, e.g. you're > actively using LKMs and you haven't gone into /usr/src/lkm and done a > "make depend all install" to correspond to the kernel you just > config'd, built and installed, well, then you're taking your life into > your own hands and you should, at the minimum, probably be spanked. Agreed. I'll have my 4 years old do it. > Various schemes, ranging from the semi-sane to the outright crackpot, > have been advanced for adding LKM versioning and fancy dependency > checking but nothing workable (and inoffensive to the smell) has been > implemented yet, so, for now this is what you have to do. Again: > MAKE SURE YOUR LKMS ARE IN SYNC WITH YOUR KERNEL! So building a kernel should be: cd /usr/src/sys/compile/WHATEVER && make && make install && cd /usr/src/lkm... How does one then maintain several kernel versions without going mad? In Linux (sorry), one has /lib/modules/X.y.z.... and a current symlink that actualy gets created at boot time by some clever awking of /proc/version. > > Thank you. > </USUAL-OBLIGATORY-POINT> > > In this particular case, however, I think I blame the OSS LKM > specifically and if the linux & screen saver lkms are sure to be in > sync with their kernel then they can probably be brought back safely. They will, once my upload (2GB +) is done. > I should also point out that if this turns out to be an instance of > someone using a driver which is *openly acknowledged to be BETA > software* on a production machine, and crashing that machine from said > use, then I shall most definitely recommend that this particular > someone do at least 10 hours of penance in recompense, perhaps by > helping out at the local homeless shelter or giving blood. > Foolishness of such magnitude demands some form of restitution. ;-) I take fool (!) responsibility here. I cannot donate blood as I had Malaria many years ago. I already pay 10% of my income in contributions. I promise, instead to donate 100 hours of community service to the FreeBSD project. My activity? Create noise about threads. My server engineer tells me they are broken. how is that? Simon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.970429174652.Shimon>