Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
In summary for all the replies... 1) Changing the version ID is likely done in version.h 2) I should be using `make bzInstall` or `make bzlilo` and the ramdisk kernel image (initrd) should get created automagically... 3) module path is determined/set in /etc/rc.d/rc.sysinit so I could likely tool that file to my own preferences, but I've I can successfully tweak the version-ID then it won't be neccessary.. > > System: Intel DK440LX MB with single PII 266 (kernel I'm building > > includes SMP) > > OS: RedHat 6.0 > > OK, is there a reason you're using an SMP kernel? Would that be an SMP > board? Yes... I plan on adding the second CPU shortly. > Once you reboot with a new kernel, it should happen automagically :) > Not completely true. There is a `make newversion` which used to bump the compile ID up one and thus linux-2.2.5-4 became linux-2.2.5-5, but that doesn't appear to be working here. - Christoph - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |