Re:DAMN! Am compiling 2.4.16 on a 486 as I write t
on
Kernel 2.4.17 Out
·
· Score: 1
eeek! this is off-topic, sort of, but you really need to start rethinking your firewall... over here I do the same thing but DO NOT have gcc or anything remotely "code-powerful" (would kill mount if I could) installed on my firewall box... as such, yes I HAVE to take advantage of my protected computers increased performance for compiling the kernel and the modules I see fit (VERY few), then ship them over via scp (just for practice) to restart the new "test" config with......has anyone heard of patches btw?!!?
also, why would you "upload" the source instead of the.tgz?!?!?
also, having the kernel source on your firewall box is probably not the best thing to do.... especially since gcc appears to be there as well (and I didn't even have to crack your box to find out!)
I appreciate your "pain" but please consider that this is a large community and "somebody's already thought of that"... instead of suffering, please do a little checking and spare yourself... the kernel will help you:)
if you do insist on keeping the source on your firewall, then patches will certainly benefit you!
but DON'T...
kernel source+ gcc+ floppy disk=serious fun!
kernel source+ gcc+ root+ lilo=serious problem...
of course, the reasoning behind this is that my "protected computer(s?)" all run firewalls and "suspect" my firewall... hehe....
just a thought...
Slashdot Mirror
eeek! this is off-topic, sort of, but you really need to start rethinking your firewall... over here I do the same thing but DO NOT have gcc or anything remotely "code-powerful" (would kill mount if I could) installed on my firewall box... as such, yes I HAVE to take advantage of my protected computers increased performance for compiling the kernel and the modules I see fit (VERY few), then ship them over via scp (just for practice) to restart the new "test" config with... ...has anyone heard of patches btw?!!?
also, why would you "upload" the source instead of the .tgz?!?!?
also, having the kernel source on your firewall box is probably not the best thing to do.... especially since gcc appears to be there as well (and I didn't even have to crack your box to find out!)
I appreciate your "pain" but please consider that this is a large community and "somebody's already thought of that"... instead of suffering, please do a little checking and spare yourself... the kernel will help you :)
if you do insist on keeping the source on your firewall, then patches will certainly benefit you!
but DON'T...
kernel source+ gcc+ floppy disk=serious fun!
kernel source+ gcc+ root+ lilo=serious problem...
of course, the reasoning behind this is that my "protected computer(s?)" all run firewalls and "suspect" my firewall... hehe....
just a thought...