| |
| |
| |
|
Page: 1 2
Comments:
<0> Hey guys, trying to build kernel 2.6.15.4 and I'm getting this error on boot:
<0> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0) [17179573.016000]
<0> I am new to this am I missing something simple?
<1> my friend compiled her kernel when i boot it get: can't open /lib/../../modules.dep any idea?
<1> have same machine and i don't got this problem
<2> would anyone a good site for learning how to stick the kernel on an ext3 drive to start making a distro?
<2> *partition
<3> huh?
<2> well I want to create my own distro
<4> Dvalin: obviously non englidh speaking :)
<2> so I'm wondering how I would need to go about moving the kernel over to a partition
<4> arrgh & imnon english typing
<2> I'm british mate it's late......
<4> spanglesontoast: dont get upity with me
<4> spanglesontoast: look at bluewall
<4> its a distribution that allows you too build the kernel first & then build up from there
<3> spanglesontoast: take a look at lfs (linux from scratch)
<4> ie put a kernel onto any partitionnot just ext3
<2> I hate lfs it's ugly and unhelpful
<3> hehe
<4> nah lfs dont cut it for compiling things for a dist
<4> bluewall was built on lfs though if my memory serves me correctly
<2> hmm
<4> but lfs by itself isn't enough unless youhave more then the half a clue it takes too ask the right question :)
<2> hmm
<2> so I'm guessing you do need a linux distro to do it
<2> to actually make one
<4> basically if you have too ask how you probably cant do it, starting with bluewallcuts out some of the hard stuff araujo has done already without asking
<4> but yes you can build a kernel on anything & compile utilities onto your own root /ext3 but get one lib wrong & you're stuffed
<2> ah
<4> as was the case when slackware went from libc5 too glibc as its base libs
<2> oh ok
<2> so in reality
<2> I could just grab a kernel
<2> whack it on a partition
<2> and then point grub to it
<2> if it was a already compiled one
<4> no you cant
<2> hmm
<4> you need the right libraries too
<2> ok
<2> and some bins aswell?
<4> the kernel is only a pointer system & memory management too other programs
<4> its those other programs you need too work out first
<4> & compile the kernel too them
<2> ok
<4> that was the reason for bluewall because more often then not you got stuff you didn't want in your kernel using other dists as your base & compiling fromlfs was painful
<4> if you want too build it from scratch & learn everything without getting misdirected by debian/redhat bigots then lfs is for you
<4> but be warned its not something that happens by itself & you will get bugger all help from anyone in here :)
<4> this channel is merely comic relief
<2> lol
<5> can anyone ***ist me in compiling 2.6.10 + grsecurity, having issues
<4> Can?Probably;Want too?Probably not.
<5> gb: very admirable of you.
<4> troy1: lets face based on the information you've provided, what do you expect somebody too say?
<5> gb usually if anyone is willing to offer their ***istance i'd list the problem :o but usually its a waste of time.
<4> I'm uncertain about everyone else but my crystal ball broke a long time ago
<5> haha :)
<5> basically there is no direct kernel panic however the filesystem is mounted readonly and i get a warning mesage before the OS actually boots
<5> the machine doesnt actually get past the kernel
<4> uhuh
<4> wot filesystem?
<5> ext3
<4> people are less inclined toohelp if you cannot be bothered too provide minimal information about your system, at least you mentioned thekernel
<5> sorry about that
<4> did you compile it in or as a module?
<4> A big issue most face is the inability too rebuild the initrd with all the needed modules
<5> basically what i did was downloaded the 2.6.10 tar file and then patched in grsecurity, did 'make' and then downloaded an existing .config file off a website because i was getting errors with make menucode
<5> right now when i boot i gert warning: unable to open an initial console.
<4> make menuconfig?
<5> yes
<5> (VFS: mounted root readonly, freeing used kernel memory: 548k freed)
<5> CentOS is a bit awkward when it comes to RPMs
<4> ok tip, I say this often as most regs in here can atest too anything required too mount / build into the kernel, this avoids most potential issues related too initrd
<4> ie make menuconfig & select y too ext3 & anything else required by /
<4> my guess is only ext3 is the issue here as it mounts read only
<5> the issue was i couldnt actually run menucode i was getting errors
<4> I dont know what menucode is
<5> the other unusual thing i found was after i did make i didnt end up with an initrd file
<5> make menucode
<4> I use make menuconfig
<5> yes :)
<5> i can still boot into other kernels to diagnose the problem though
<5> hehe
<5> am i required to have an initrd file?
<4> try rebuilding with ext3 builtin, it will more thenlikely fix your issue
<4> if you want too use ext3 as a module yes you do
<5> basically i get errors when i actually do a make menucode thus preventing me from doing that
<5> is there a way i can correct that?
<4> I dont know what menucode is
<4> & without the actual error I cant help
<5> i can give you the error one moment
<5> **** now i cant even run make menucode for some reason
<5> are there instructions on how to build a 2.6.10 kernel + grsec from scratch?
<4> maybe on kernel.org but I dont see why it should be any different too any other kernel
<5> ahh
<4> I usually patch the kernel;make menuconfig;make dep;make bzImage;make modules;make modules_install;cp /boot/bzImage /boot/stable;cp arch/i386/boot/bzImage /boot/bzImage;lilo
<4> of course you dont need too do tyhings like that for 2.6,I just do :)
<5> alright are you around for a few minutes?
<4> nope, I'm a triangle
<5> heh :o
<4> but dont tell anyone or they'll bew wanting too be one too
<5> lol
<5> should i download the 2.6.10.tar.gz file?
<5> http://www.eth0.us/?q=2.6.10_grsecurity&PHPSESSID=a04bc8f05239d9687af698542d79272e
<5> gb?
<4> no
<4> gz, bz2 matters not
<4> so long as you can uncompress it who cares
<5> :)
<5> tar -xzf :P
<4> if the patch didn't work it should have told you with either a warning or an error
<5> i have 93% lets see here
<4> in which case I would look for a tarball already patched if you really need grsec
<5> okay its untarring
<5> okay so i have untarred it im in the dir
<5> now i should proceed to patch the kernel?
<4> thought you had already?
<5> im starting fresh so i dont get mixed up
<5> the manual im going by says i need to edit modules.conf but i dont have that file
<4> well I aint psatched a kernel in ages so you'll have too rtfm re doing that for correct syntax
<5> oh i have it
<5> patch -p0 < grsecurity-2.1.0-2.6.10-200501071049.patch
<4> yeah looks ok too me, but im clueless :)
<5> now its not even patching damn it
<5> i think im going to reinstall the system :(
<4> hehehe
<5> if i reinstall from scratch is it any easier?
<4> nah download a prepatched kernel
<5> :)
<5> is grsec that important?
<4> you're talking like a microsoft luser :)
<5> haha
<4> nup
<5> i just dont want to leave an internet machine exposed to attack :P
<4> but I personally would rebuild a kernel optimised for your hardware - the initrd :)
<4> but thats just me
<5> im more of a unix person so all this bitch work is pissing me off :(
<4> initrd==good for building a dist too runon lots of different hardware==good for hogging ram on production system which has modules loaded all the time that could have been built in too take up only half or a third of the space in ram/swap then they do as modules in initrd
<5> yeah well this machine is a dual 1.6 so its not that slow
<5> its just going to be an asterisk machine :)
<4> slow==nothing too do with it
<4> ram/swap footprint is whatI'm talking about, the vm killing your x because your kernel is hogging it all types of issues
<5> right, well i dont have that much ram to spare on this box :P
<4> caffiene time
<5> :(
<6> what's the correct way to apply this patch? http://***embler.cz/download/ati2_patch ?
<7> good morning
Return to
#kernel
or
Go to some related
logs:
#oe
#lisp
chron.root
#osdev
#web
ubuntu dapper console font
#awk
#gentoo
ufsrestore fc5
#css
|
|