>> It's really sad to hear this. Red Hat, SuSE, Slackware,
>> TurboLinux, they all have "Everything" or "Almost
>> Everything" options. I'm curious why it's such a big
>> deal for Mandrake.
>
> Have you tried that option?
>
> I used redhat before working for mandrake. Once I tried all. The system
> was completely fucked up.
Have you tried it with 6.0, 6.1, 6.2, 7.0, or 7.1? That's what we've been
using in our classroom setups for two years now, and it works flawlessly
(although Red Hat had some kickstart bugs around 6.1).
I have at least one of all of these distros loaded here at work (it's my job
to make sure we have a test system for each distro, sometimes more than
one). Everything installs work great. I do at least one a week, on varying
distros.
> Honestly I don't understand why "everything" would be so useful. When I
> install a new system, I often do some "urpmi" (which is a really useful
> tool) and voila...
You have to look at it from a different perspective, especially ours, from
the training center. I feel that urpmi is a great tool, and it will soon be
in our curriculum as something to teach, especially for the advanced
classes. But for our beginner classes, our new ILTs, we need a
pre-installed system that has as much as possible to (1.) show what Linux
has, and (2.) give the trainer as much flexibility as possible when it comes
to choosing what he wants to teach in this class.
> The main problem is that it would need special testing to have this
> feature work flawlessly, and we believe it's long work (time of full
> installs...) and dirty (make special cases to remove the package which
> create most problems), and moreover we would need more attention from the
> packagers. It's sad to say, but most packagers at mandrake don't care
> about their packages. Even if I do more by myself, I can't do everything,
> including my other duties!
Okay, then why does Cooker exist? IMPLEMENT AND WE WILL TEST! That's what
we're here for, silly!
As far as the package managers, it's really sad that they don't care about
their packages. I only wish that (1.) I spoke French, (2.) I lived
somewhere near where you guys had offices (I left early.. I moved out of San
Fran 2 years ago..), and (3.) I was better with RPM/package building and
maintainence and stuff so that I could get a job there and help you guys.
> Or use a postinstall script (in the auto_inst), or at first boot, that
> will call "urpmi" with all the needed leaves...
Yes, this is an option. This would probably work better than trying to
solve rpm -Uvh * problems.
> I sure understand your way of thinking. But please consider my arguments.
> We would need a "safe" and "working" Everything install, which is IMO hard
> to achieve. Also, consider all the critics for open net ports, conflicting
> packages that break many things, etc.
I think that if you implemented it, you'd find that the Cooker community
would be happy to help fix the problems, taking a lot of the testing and
such out of your hands.
7.2 had the slider bar that allowed you to choose 100%, is it really that
difficult to put back in? I guess I'm just not seeing how it could be that
hard. Regardless of the difficulty in testing the thing, as I said, that's
what Cooker is for. Don't want the feature advertised yet? Make some
obscure boot prompt option on the boot.img, "linux everything" or something.
That way we can at least try it out and test it for you.
Don Head
SAIR LCA, CIW-P, i-Net+, Network+, A+
Systems Administrator [ [EMAIL PROTECTED] ]
Web Designer [ 1 314 997-7847 ]
[ AIM - Don Wave ] [ ICQ - 18804935 ] [ Yahoo - Don_Wave ]
