bhoggett wrote:
mikeymike wrote:
Then ask a locale question and configure it like that. And Linux isn't maintained by Mandrake either, so "they cannot be responsible for that either", nor is X, OpenOffice, Mozilla, etc, etc.
That's not the same thing. While the various applications aren't maintained by Mandrake they are packaged, tested and released by them or though them as far as the mdk rpms are concerned. So Mandrake have some control.
The mirrors are completely independent and can disappear any time and without warning or notification to Mandrake. If they were pre-configured, then Mandrake would have to field all the irate users' complaints when mirror X turns out not to work straight after they install their system.
As opposed to "all the irate users' complaints" that the system doesn't work in the first place? Mandrake's own software update system can take care of maintaining the independent update source list.
Ok, how did you ask it nicely to install vlc? :-)
I opened up a shell. I typed "su -" then followed it with my root password when prompted, then I typed "urpmi vlc". It came back giving me a whole list of front end packages to choose from. I chose kvlc. Then it gave me a list of packages that it needed to install to satisfy the dependencies, and asked me if that was OK. I said "y".
Hmm, I tried that, but the usual "dependency, dependency, sod off" occurred. Next time I boot into Linux I'll paste the exact errors.
Alternatively, you can start the software installer, search for vlc, select all the packages that have vlc 0.7.2 in them (the dependancies will be selected automatically) and install. This will install all the front-ends and plug-ins too.
If you mean the Mandrake Control Centre, VLC isn't listed in the search IIRC.
It could be that you are missing a repository from your urpmi config, or it could be that something is conflicting. However, it's hard for me to diagnose the problem from the information you've given me.
I'll paste the urpmi config command I use next time, and try a few different options.
Reminds me of NT4 and having to slip it the NT4 SP4 IDE driver to get it to recognise large IDE disks :-)
Except that in this case it must be something specific to your hardware, as I've never come across it. With NT4, it was not a surprising thing really when you consider the amount of time between NT4 being released and SP4 coming out.
No, it wasn't, but the business of allowing the APIC to work after the install is just over-complicating the process. The installer should support everything possible and provide the resulting OS installation with the same capabilities.
AmigaOS wasn't exactly devoid of hard disk size problems either as hardware advanced and the OS became more and more obsolete. Suddenly you'd need to install all sort of patches and third party filing systems just to make your hardware usable.
It would have been the same for x86 had it lingered in computer limbo for the amount of time the Amiga has, but it hasn't. APICs are pretty standard nowadays, my motherboard is over two years old.
