I have a few linux questions. As u can see i am still a newbie to linux :)
[*]I just installed kernel 2.6.1 on my RH9 system ( kernel 2.4.20). I see that the /boot folder contains a link to System.Map & vmlinuz which currently point to version 2.4.20 of the kernel. Now , i want to keep both the kernels on my machine right now so that i can switch in case of any trouble with the new kernel ( which i am having a lot ;) ), so to which version of the kernel do i make these links point to ( 2.6.1 or 2.4.20 ) ? Also what is the use of these links?
[*] When starting up with the latest kernel (2.6.1) the system shows error msgs when loading modules. Even when i try to do a modprobe it gives me the same errors. I cant remember the error right now, as i am on a windows system. How do i correct this?
I am not able to use my cd rom drive or mount windows partitions although i compiled the support vfat in my kernel as a module. How do i load the module for these?
Is there any way i can get to know the name of all the modules on my box. What is the command for this?
[*] In all the linux HOWTOs on the web i have seen people ocmpiling their kernel in the /usr/src/linux directory but the readme in the kernel sources specifically mentions not to extract the contents of the tarball in that directory. And now that th kernel is made i still cant see any /usr/src/linux directory? Why is this? I am all confused about the /usr/src/lunx stuff? Why is it needed in the first place? Can someone explain it please?
vmlinuz is your kernel image
system.map contains the location of symbols in your compiled kernel
so both need to change if you have a new kernel and your system uses system.map
system.map contains the location of symbols in your compiled kernel
so both need to change if you have a new kernel and your system uses system.map
I have placed the new versions of vmlinuz and system.map in /boot but i am confused as to which version to point the links to?
well the links should point to the versions that you wish to use
but if you placed the new versions directly in /boot then you don't need the links anymore. AFAIK (I'm not that familiar with RH systems)
but if you placed the new versions directly in /boot then you don't need the links anymore. AFAIK (I'm not that familiar with RH systems)
what boot loader are you useing ?( most likely lilo read the man ,info,/usr/doc/lilo to find out how to edit your /etc/lilo.conf file BACK IT UP FIRST)
you load modules with modprobe
or in the case of a file format with the -t option for mount
ie mount /dev/hda1 -t vfat /mnt/hda
the best place to untar the source files to would be /usr/src/linux(verison number )
ie /usr/src/linux-2.6.1
the /usr/src/linux should be a link to the files that your system libarays were linked to
even thought this is a good place to ask for help there are better places try this forum for linux help
/http://linuxcult.com
poeple like f0dder get banned on there first post
you load modules with modprobe
or in the case of a file format with the -t option for mount
ie mount /dev/hda1 -t vfat /mnt/hda
the best place to untar the source files to would be /usr/src/linux(verison number )
ie /usr/src/linux-2.6.1
the /usr/src/linux should be a link to the files that your system libarays were linked to
even thought this is a good place to ask for help there are better places try this forum for linux help
/http://linuxcult.com
poeple like f0dder get banned on there first post
goes to show how little you know him, he can probably manage his linux systems better than you do :p
Old linux kernel tree tarballs used to extract to "linux" instead of a version-named folder like "linux-2.4.22" - pretty retarded, you could mess up things bigtime. Thus, I'd extract the kernel source to a temp location, rename the folder if it was just named "linux", move it to /usr/src, remove old "linux" folder symlink and point it to the new kernel tree. That's a safe way of doing stuff.
I do "make bzImage" when building the kernel, and when 'installing' a freshly compiled kernel, I move bzImage to /boot/linux-version. I have a bunch lying around there for various reasons, like linux-2.4.{21,22,23}.
When you've moved the new kernel in place (and not overwritten your old kernel, for whatever_deity's sake), time to configure your bootloader. I use lilo, so time to edit /etc/lilo.conf and run "lilo" afterwards. I believe newer versions of RedHat use grub by default?, and I haven't any experience with that one - small old lilo works for me.
I'm personally not touching kernel 2.6 before distros arrive using it. With stuff written by amateurs, I'd rather have other people burn their fingers first ;). Besides, there's a lot of changes in the kernel, so you'll probably need to upgrade a lot of system tools etc... I don't feel like figuring out all the necessary changes, especially when my system works fine.
I probably *will* play around with kernel2.6 sometime... but not on a live system :).
As for loading modules - insmod. With a "correctly set up" system, the modules should be loaded transparently though. Good luck figuring out how to do a "correctly set up system" if it's not done for you automatically.
<3 linux - because I have time to muck around manually with stuff windows does automatically for me, and has done automatically for me for the last 5+ years <3
linuxcult.com, eh? Suitable name ;)
I do "make bzImage" when building the kernel, and when 'installing' a freshly compiled kernel, I move bzImage to /boot/linux-version. I have a bunch lying around there for various reasons, like linux-2.4.{21,22,23}.
When you've moved the new kernel in place (and not overwritten your old kernel, for whatever_deity's sake), time to configure your bootloader. I use lilo, so time to edit /etc/lilo.conf and run "lilo" afterwards. I believe newer versions of RedHat use grub by default?, and I haven't any experience with that one - small old lilo works for me.
I'm personally not touching kernel 2.6 before distros arrive using it. With stuff written by amateurs, I'd rather have other people burn their fingers first ;). Besides, there's a lot of changes in the kernel, so you'll probably need to upgrade a lot of system tools etc... I don't feel like figuring out all the necessary changes, especially when my system works fine.
I probably *will* play around with kernel2.6 sometime... but not on a live system :).
As for loading modules - insmod. With a "correctly set up" system, the modules should be loaded transparently though. Good luck figuring out how to do a "correctly set up system" if it's not done for you automatically.
<3 linux - because I have time to muck around manually with stuff windows does automatically for me, and has done automatically for me for the last 5+ years <3
linuxcult.com, eh? Suitable name ;)
BUT you have to have it windows way NOT your way
hay Hero
I doubt it from what he has sed about linux being eletest
he dosen't even know how to ask for help
hay Hero
I doubt it from what he has sed about linux being eletest
he dosen't even know how to ask for help
trust me, after you've used linux for a few years, you can work with it ;) (so f0dder can too, reluctantly maybe but he can :grin: )
Oh, rob must be right - I don't know how to work with linux.
I wonder how that router/firewall/fully encrypted fileserver/dnscache/squid proxy/DHCPD/HTTPD/FTPD/IDENTD server box set up itself automagically.
I wonder how that router/firewall/fully encrypted fileserver/dnscache/squid proxy/DHCPD/HTTPD/FTPD/IDENTD server box set up itself automagically.
Oh, rob must be right - I don't know how to work with linux.
I wonder how that router/firewall/fully encrypted fileserver/dnscache/squid proxy/DHCPD/HTTPD/FTPD/IDENTD server box set up itself automagically.
lets not start another fight F0dder
hay clippy read the man or info pages for both insmod and modprobe then decide witch one to use to load modules
Who started? ;)
If i link the system.map & vmlinuz files to the latest kernel versions(2.6.1) then how will i run linux using the previous version (2.4.20) ?
clippy, keep an entry in lilo.conf (or whatever bootloader you use) for the old kernel too. In case of lilo, you can hold down shift while booting, which gets you to a bootmenu where you can select your kernel.
I have something like
(I boot from a initially-loaded ramdisk, so yours will most definitely look different :))
I have something like
image = /boot/linux-2.4.24
root = /dev/ram1
initrd = /boot/initrd.gz
label = linux
image = /boot/linux-2.4.22
root = /dev/ram1
initrd = /boot/initrd.gz
label = linux-working
(I boot from a initially-loaded ramdisk, so yours will most definitely look different :))
I use grub. I have put both my kernels in its startup menu but the problem is that how will i tell the bootloader to change the link of system.map and vmlinuz to to the appropriate kernel which i select.
sorry, don't have any experience with grub - try finding the documentation :)
f0dder, don't be cruel, you know that is impossible :)
try reading this
http://www.redhat.com/docs/manuals/linux/RHL-7.3-Manual/ref-guide/ch-grub.html
there are 10 pages for " grub " at http://google.com/linux
http://www.redhat.com/docs/manuals/linux/RHL-7.3-Manual/ref-guide/ch-grub.html
there are 10 pages for " grub " at http://google.com/linux
Funny how there aren't really any pages for the 9x/NT bootloaders? ^_^
Funny how there aren't really any pages for the 9x/NT bootloaders? ^_^
could it be that thay olny boot one system from olny one place the MBR ?