On Monday 18 March 2002 09:49, you wrote:
> On Mon, 2002-03-18 at 09:30, David Walser wrote:
> > Well, given the decision that's been made, couldn't
> > you just cut your own CD with 8.2 and the new kernel?
>
> I don't have the time, much less the willingness, to roll my own distro
> CDs, and I'd reckon neither do the majority of overworked admins (let
> alone whether they have the competence to do so). Mandrake will *NEVER*
> be taken seriously in business circles with this kind of release snafu.
It's not that hard would maybe take an hour tops and thats including doing a
little reading. What do admins do these days if they are this unable to do
basic system admin stuff. Some people in the past had to down load the kernel
source, apply patches and do the work of compiling the thing themselves.
If you ask me there are way to many point and click windows admins out there.
point and click does not an admin make.
>
> The whole idea of a point release is a *stable* point release. Oopsing
> kernels ain't it.
This however I agree with.
>
> I know about and understand release schedules and commitments. Believe
> me. With that said, if the release schedule was so almighty important,
> then why didn't the kernel maintainers respond and interact with those
> of us who were reporting this with plenty of time left to test fixes? I
> was so concerned about the time that I *directly* contacted Juan when it
> became obvious that not a single Mdk person was going to respond, and
> still got no response at all. Now the reason the fix isn't in final is
> that there's "no time left". WTF? There was plenty of time left if we
> could have just gotten someone on the kernel team to take us seriously.
> This doesn't exactly fall into the "gee, it would be nice if xcdroast
> works (it doesn't)..." category - we're talking about frying the kernel
> by using smbfs, for goodness' sake.
>
> I guess that's really the bee in my bonnet - that it was more important
> to get the release out than it was to get it out working. It's really
> easy to just say "update afterwards". Great, that's cool for the
> home/hobby crowd, but for those of us who have to maintain and support
> hundreds of boxen, it's not fun, and it's not funny. It's real time and
> real money that could be better spent on, say, MandrakeClub and
> MandrakeStore.
Thats why I mentioned earlier the way I do this. Wait a month add all the
updates and delete the old rpm's then run the mkcd's script. It will make the
iso's for you couldn't actually be easier.
It's to late to complain about it now but at least a month from now you can
add the updates and have something you can use without destroying your
network. I'm not saying I agree with the way it was done but I can do
something about it thats constructive.
I also understand you frustation. I have set up mail servers for the city
here were I live and after they managed to crash mandrake they installed
redhat on it. I also recommended mandrake to another person who installed
mandrake on the univercity servers here and gues what afer it crashed they
went back to windows I believe. I want mandrake to be so much more. They are
a decent desktop os and I use at least 80% of the time. But for serious
server stuff I keep getting the door slammed in my face. Thats why I slowed
down wated for updatesd and started making my distro with the exact packages
I want.
--
-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-
Brook Humphrey
Mobile PC Medic, 420 1st, Cheney, WA 99004, 509-235-9107
http://www.webmedic.net, [EMAIL PROTECTED], [EMAIL PROTECTED]
Holiness unto the Lord
-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-
