time away, explanation

[donkey42]

well, i'm now back online after about a month of irate & pointless phone calls to virgin, they've finally sorted it, apparently (unknown to me at the time) i was disconnected from virgins old network when i requested my BB account / connection be moved addresses to where i am now as i have had to be moved out while the council upgrade my property, i did know they where going to do this but tbh i didn't ever believe it would happen due to my past experience with the council, anyway enough moaning

during my time offline i've being playing with Debian & i have to admit i like it, but i now have the difficult job of informing an offline installed version of lenny B2 with HWF kernel (which i'm unsure if i've configured correctly)

anyway, now i'm back online i can search net for some kind of kernel config checker if such a thing exist

Edit: BTW: i'm thinking of sticking with Debian

 

[Big B]

Hey, welcome back. Yeah, things happen to us all, so no biggie.

 

[Pimp]

Yeah Welcome back, you have been missed :)

 

[donkey42]

Yeah Welcome back, you have been missed :)

thankies AAaaWWww :love:[ot]in a very non gay way[/ot]

 

[Sniper]

lol

welcome donkey42

 

[megamaced]

I thought this place was quiet... now I know why!

I am back too..full time now. I've finished my studies, got my MCSE and can once again be considered a regular.. :beer:

 

[donkey42]

I thought this place was quiet... now I know why!

bo11ocks mega, one day we'll be able to stop jon benge (aka Mega) slating VIA because as we all know he actually uses VIA successfully[ot]theres no getting away from it Mega, we all know your sordid little secret[/ot]

Edit: welcome back too Mega

 

[Anti-Trend]

...i now have the difficult job of informing an offline installed version of lenny B2 with HWF kernel (which i'm unsure if i've configured correctly)...

I wouldn't if I was you... at least until I can get around to building a fresh batch. The ones in the repo are pretty outdated. Reason being, the kernel-package suite in deb/ubuntu was bugged for later kernels, meaning source packages built that way need some manual tweaking to get them working. That kinda defeats the purpose of having somebody rolling kernels for you. Of course, you could always learn to roll your own... :D

 

[donkey42]

I wouldn't if I was you... at least until I can get around to building a fresh batch.

when do you suppose you would be until you get around to it ?

The ones in the repo are pretty outdated. Reason being, the kernel-package suite in deb/ubuntu was bugged for later kernels, meaning source packages built that way need some manual tweaking to get them working. That kinda defeats the purpose of having somebody rolling kernels for you. Of course, you could always learn to roll your own... :D

that sounds like a challenge & i'm not someone who usually backs down from a challenge, so, if i'm going to do it, better start now

fear the unknown[ot]bo11ocks to the unknown, lets get rolling[/ot]

BTW: i'd still like to know when you think you will get around to rolling the kernels, in case i :swear: it up

 

[Anti-Trend]

when do you suppose you would be until you get around to it ?that sounds like a challenge & i'm not someone who usually backs down from a challenge, so, if i'm going to do it, better start now

To be honest, I've been working on quite a lot of involved projects at work -- for example, consolidating a bunch of disparate servers into guest domains on a big Xen box -- so my free time has been split pretty evenly between work and family. :O

As for the kernel-package bug, it's supposedly fixed. Last I checked though, the kernel bug was still manifesting for x86 builds, so I may have to reopen it. I can revisit the issue this weekend, I suppose.

BTW: i'd still like to know when you think you will get around to rolling the kernels, in case i :swear: it up

I'll try a few test builds and see how it works out. If kernel-package doesn't work as expected, I'll be holding off for now. Maybe I should be distributing the config files and the build scripts instead, and simply letting users roll their own for now?

 

[donkey42]

To be honest, I've been working on quite a lot of involved projects at work -- for example, consolidating a bunch of disparate servers into guest domains on a big Xen box -- so my free time has been split pretty evenly between work and family. :O

i thought Xen was a VM app, although i've never used Xen, i couldn't get it to work successfully, so i gave up cos i got bored with it

what kernel-package bug on x86

I'll try a few test builds and see how it works out. If kernel-package doesn't work as expected, I'll be holding off for now. Maybe I should be distributing the config files and the build scripts instead, and simply letting users roll their own for now?

can i help ?

i realize that i'm nowhere near as good as you[ot]but i'm willing to try[/ot]

BTW: if i can sort HWF custom kernel, it'd be something less for you to do, i'm on debian now

 

[Anti-Trend]

i thought Xen was a VM app, although i've never used Xen, i couldn't get it to work successfully, so i gave up cos i got bored with it

Xen is a paravirtualization suite which runs on Linux at the kernel level to run guest operating systems at near bare metal speeds. The idea in our case is that one fairly high-end 2U server with Xen can run the OSes from 8 scattered 1U servers which are eating up power and putting out lots of heat. It's more cost-effective, and in theory, easier to backup and manage.

what kernel-package bug on x86

#468839 - linux-source-2.6.24: A make-kpkg build of Linux 2.6.24 generates an unusable headers package (i.e. : not suitable for m-a). - Debian Bug report logs

can i help ? i realize that i'm nowhere near as good as you but i'm willing to try

Well, it's not as much about being "good" as about:

1. First and foremost, being very experienced with Linux, compilation, Debian-specific tools, and especially advanced kernel options across multiple x86 platforms
2. Having a secure build environment so that the kernels are built in a very trustworthy way
3. Owning a rig fast enough to build the kernels punctually
4. Possessing enough bandwidth to upload all the kernels in a timely manner once they're built
5. Having user-level access to the HWF server

BTW: if i can sort HWF custom kernel, it'd be something less for you to do, i'm on debian now

Thanks, I do appreciate the offer, but I don't think it's feasible.