On Sunday 04 March 2001 22:29, Philipp Thomas wrote:

* Steven T. Hatton [Sun, 4 Mar 2001 17:35:29 -0500]:

...

Ok, so this *should* be a newbie question, but I don't know the answer! How do I install the pre-built 2.4.2 kernel? Should I simply rpm -i k_deflt_24-2.4.2-4.i386.rpm?

Not quite :-) Use 'rpm -Uvh k_deflt_24-2.4.2-4.i386.rpm'.

Philipp, That didn't work for me. I did this and I still get 'uname -r' == 2.4.0-4GB, but now I don't have any modules to go along with it. No network on my print server {:-(>. Perhaps it's 'cause I had changed something in the configuration along the way. This is fairly unlikely in as much as this box was upgraded to 7.1 about an hour ago. The only way my changes could be the cause of the problem is if the stuff carried over from the previous configuration. Oh well, I may actually have time to read some of the modutils stuff. Perhaps I'll be able to play a bit more by the rules if I learn what they are. Steve

On Monday 05 March 2001 03:19, Konstantin (Kastus) Shchuka wrote:

On Mon, Mar 05, 2001 at 12:30:32AM -0500, Steven T. Hatton wrote:

...

Philipp,

That didn't work for me. I did this and I still get 'uname -r' == 2.4.0-4GB, but now I don't have any modules to go along with it. No network on my print server {:-(>. Perhaps it's 'cause I had changed something in the configuration along the way. This is fairly unlikely in as much as this box was upgraded to 7.1 about an hour ago. The only way my changes could be the cause of the problem is if the stuff carried over from the previous configuration.

I think you need to run lilo after installing new kernel. rpm doesn't do it for you.

Kastus, Indeed. I'm sitting here with the SuSE book opened to chapter 4. But now, guess what don't work? Perhaps it's my fault for buying such an unusual piece of hardware as a SoundBlaster 16. Sure OSS would work, but not with 2.4.2. Do you happen to know exactly what LILO has changed? I may learn this form the chapter, but a different perspective never (rarely) hurts.

-Kastus

PS I am very disappointed with 7.1. This is my worst experience in my 5+ years Linux history.

I'm mixed on it. Back when we had XF86Setup, I had my video pretty much mastered. XFree86-4.x seems to have destabilized the whole X configuration thing. Sound has always been a disappointment to me. It's just too much effort to keep it working. I really hate the way 4-Front does the licensing. Their product has always work for me, but as soon as I upgrade the kernel, I need to go through at least an hour's work to figure out where the stupid license code is (I have no idea right now where it is) and then figure out how to update the product to the new kernel version. Then I have to remember to have the correct selections in the kernel so that OSS can detect it. On top of that, I've had times where that selection (i think it's something like 'load version information') caused problems with other things. I was extremely happy about my upgrade from 7.0 to 7.1 on the second box. That is, until I started to mess with the display. Of course, If I use Windows, the vendor has written a driver which integrates into MS's mono-platform OS. The vendor has also probably provided a generous suite of tools to configure and enhance the product. I do believe SuSE 7.1 has many fundamental changes in concept which are in the right direction. I could name a bunch of things I don't like about YaST 2, and probably will as soon as I feel I have control over the systems again. I think part of the reason 7.1 may seem disappointing is that our expectations have grown. I have know idea what it takes to put together a Linux distribution every 4 to 6 months, but I have the feeling it is not easy. Heck, SuSE what putting the CDs out and intercepting them at the other end with a new Kernel, and a new KDE. Both of which seem very promissing. I know the KDE2.1 from betas, so I'm not oowwing and aahhing over that, but they did a sharp job of integrating with it. The kernel has changed drastically from my perspective. That is, there are a lot of new files and structures in the /boot and /lib/modules directories. someone at SuSE had to adapt to all of this. Hopefully these changes will may future growth less painful I call trying to work around the edges of SuSE juggling knives. I would hate to be the person who has to maintain compatability with all these moving parts as they constantly change. I believe this integration process will continue to mature, and standard procedures with evolve to prevent or at least mitigate the unfortunate conflicts that we currently meet. I do believe there are certain redundancies which probably make the distribution overly complex. This is a difficult matter. The features or applications I may not care about might be the whole reason others buy the product. there are also, certainly things in the distribution I haven't even thought about yet. These might be the answer to some, as yet, unasked question. I do have to wonder how many different windowing environments we need, or how much of a distraction they represent. We all know Germans can get a little carried away with this at times {;-)>, but the thing SuSE need to work on is imposing and maintaining order. I'm not saying they don't do a good job of this in comparison to what others may do. I have no standard by which to measure. I am saying that the problems that I meet at this end seem to often arise out of a lack of coordination. OTOH, a bit of chaos is essential for creativity and happiness. There's no perfect ballance. One reason I am loath to criticize too harshly is that we are asking for a very high standard of performance in a field where the only constant is change. I am not great at organization nor self-discipline. It's hard for me to be harsh about other's shotcomings when mine are so great. What I do is simply say 'this seems broke, and it's really important that it works.' I can only imagine that it is very discouraging to put out a product with so many amazing capabilities, only to have all of its faults constantly and sometimes viciously recounted. Thanks SuSE, we're gonna win in the end, because we're doing the right thing. Steve