Hi all, still in Progress of the Kernel Install Guide, which will hopefully make all these others obsolete and up to date with Linux 2.6.11.X from 5 to 7. then maybe Iwill have to revise it as the later Linux 2.3.0 comes around. I think by then all the Depereciated items will be finally removed and everything will be stabler for all fo us.

Oh how I love Linux, Dounloading the Slackware Latest ISO's and listening to Rockfun24 on Gxine and replying ot forum posts and all without too manny issues if any. Linux makes windows a Childs toy for the ones who just want to play, this is a serious OS that can not be topped.

yes and they were somewhat rhetoricle (sp?) I know that Ihave to change all that.

The correct spelling is rhetorical

Cheers

It's all ones and zeroes after all..

what is " linux 2.3.0 " ? i think you mean another ( newer ) version.
the next will be 2.6.12 etc........
...and it might contain other depricated functions that will give such warnings.

btw.: i don't hope you'll write a paragraph about your " bug " in that guide.....

egag

It's an "Install guide" so it wil mention it, but not go extensively into it. Just mention thta the word "Depreciated" means just that, it is not used anymore, and the code is being revised, but other than that it works without a problem. Will also add an edit for the install.sh for properly setting the VmLinuz and System.map ffiles in the right place and not in / but actually in /boot with the proper naming to make sure they are setup with a version name so they can be easily identified. and also the ls -sf System.map-2.6.11.7 will be set, and the config-2.6.11.7 will also be set, and then the config-ide-2.4.29 will also be set, then the config will set up with the proper boot version with a config.back so that any problems they can revert back to the old Kernel and System config and Maps.


As for Linux 2.3.0, yes that is a future date release, and I understand that 2.6.12 is the next stage. There will probably be 3 more revisoons then 2.3.0 will come. At least that is my own personal predictions.

Is there a bash.org for forums?

One found on google http://techpatterns.com/forums/index.php it is more a generic forum, but there is one thread or forum area devoted to Linux and Bash

Well, it was a good prediction, but this site seems to indicate that you are off by about six years.

http://kernel.org/pub/linux/kernel/v2.3/

The value of the prediction has certainly depreciated, and is therefore deprecated.

oh....it's a bug.



egag

A bug, it's predicting the next Generation, and I don't mean startrek, TNG Anyway Kernels updated soon, and each one should have the depreciated files removed. I am still awaiting the Revisions from Piete on my Install guide. Be well and If my sweetie really does come through, I will be moving, but then who knows for sure.

I'm trying. Dear the seven bearded buttocks of Zeus, I'm trying ... but not as trying as some I know =/

Is there someone I can contact to lock a thread? Possibly locking Shilo's 2.6 compile guide with a more formatted FAQ (I'll happily sift through all 25 pages and assemble the blasted thing, if only to stop this sort of thing happening again ...) would solve a lot of problems and also stop so many people loosing valuable hours of their lives reading posts ...

- Piete.
-He-lpm-ehe-lp-meh-el-pme-

Takes the time to say Haa haa haa. Very funny. Yes once this is all said and done, maybe the Threads can all be shut down and one ALL DEfining Guide with a NO Replies could be set. With a READ it and DO NOT PASS THIS UP or you will have problems.

Easy enough:
1. download kernel source
2. extract sources, set correct permissions, add any symlinks you need.
3. backup existing data
4. make mrproper
5. cp /foo/existingconfig ./.config
6. make menuconfig
7. make
8. make modules_install
9. set up lilo/grub

Go through each step. If a step finishes successfully, continue to the next step UNLESS:
A. You are one of the Linux kernel maintainers
B. You know what you're doing well enough to write a diff/patch and forward it to one of the Linux kernel maintainers.
C. You're a glutton for punishment, with a primal desire to look like a fool on the internet.

hmm....don't know why, but i'll give my thoughts.....
( for the brave that read this thread from the top to here.... )

1 ok
2 no need to set permissions or make any symlinks.
( if you advise such a thing , than also say what perm. or links. )
3 ? ( what data )
4 no need to....it's new ( and proper )
5 well...ok
6 ok
7 ok
8 ok
-----< copy bzImage & System.map & config-file to /boot >
9 ok
-----< run lilo and watch the output >
-----<reboot>

btw.: maybe this thread is becoming too long ?

egag

depends on where and how you copy it.
You may need a symlink from /usr/src/2.6.11-foo to /usr/src/linux
You may have downloaded a custom patched kernel with permissions set to a uid you don't have. Or you may have extracted to /home/foo as root and need to chown to yourself. User HAS to decide a few things for him(her)self.

Example - you downloaded 2.6.11-2 and already have /usr/src/linux-2.6.11-2 which contains kernel headers. You also already have kernel modules for 2.6.11-2 in lib. Back this up for quick and easy revert to old kernel.
see above. if /usr/src/foo already existed and you extracted source to it also, mrproper is in order. Also it's suggested by kernel maintainers to run before each compile after data has been backed up.
Copying binaries and map files -
1. it's part of setting up bootloader.
2. why insist on copying to boot? many ways to set up lilo (for example) image = /boot/tamu/mylinux where mylinux is symlink to /usr/kernels/linux_2.6.11-2_custom_no_USB. Far fetched, but possible
3. Once again, User HAS to decide a few things for him(her)self.

Yes, I was only trying to be humorous with my above post, but you did ask legitimated questions, so I thought I'd respond with the reasons