scarecrow

True, audio CD's have a raw filesystem, and so they can't be mounted regularly. They can only be pseudo-mounted via a virtual filesystem (kio or gvfs).

You can always install the binary edition. Or, you can also use go-openoffice which boasts even greater MS compatibility.

http://go-oo.org/download/

For the record, I'm running 4.4.0 since Tuesday, and had very few issues with the migration (just an annoyance with a broken Soprano, which has been addressed).

Open as root /etc/fstab end remove all cd-rom references completely.

These can do only harm in any modern system (managed either by HAL, or policykit). Only ancient apps need them.

Wine also needed these fstab entries, but not anymore.

As far as I know (not a Gnome user) you must install the assorted MySpell/Aspell language.

You must use VLC package and plugins from Penguin Liberation Front (PLF). VLC from the main repos is compiled with support ONLY for "free" media formats. There's no such issue with VLC from PLF, you can I/O virtually whatever audio/video file you wish.

Installing VLC from PLF will also bring as a dependency ffmpeg from PLF, which supports more formats than the one from main repos.

VLC does the job pretty well.

Sorry, but all linux partitions (incl. swap) can be logical ones. No need to set swap on primary partition.

Windoze do need primary partition for the OS files.

That's triple boot, not dualboot.

The difiicult part is putting XP and Veesta on the same hard drive. Have you managed that already?

# gpasswd -a PenguinPete scanner

(or whatever your username is, if not "PenguinPete")

After doing that (as root), logout, re-login, and try again.

A waste of effort, IMHO.

4.4.0 is very, very close, so why packaging 400+ MB which will be obsolete within ten days?

Have you tried wicd?

Works mightly perfectly for me with the OpenDNS servers.

The Mandriva mcc network manager, and Ubuntu's NetworkManager are both highly problematic.

Good luck with your ATI card. You will definitely need it.

Their closed source driver is absolute crap, and your only chance is the opensource driver with kernel mode-setting (KMS) enabled. This requires AT LEAST kernel 2.6.32 and xorg-server 1.7.2.

Unfortunately the nomenclature of the Linux initscripts is far from being unified. For example, in ArchLinux which I'm using for some six years, it used to be Daniewicz-like ( /etc/modprobe.conf ), which is still what all BSD distros use, but recently it has changed to /etc/modprobe.d/modprobe.conf

Customization at the will of user is surely one of the greatest (if not the greatest) advantage of Linux over windblows, but it would harm no-one if there was a COMMON policy for config files storage.

So- no need for "aagghh" dear daniewicz. It's not just distro-specific, but also release-specific.

It sounds like a simple plan: Shrink the existing NTFS partition to whatever size you wish, and then install Mandriva from USB stick (if you don't have some USB CD-ROM handy).

To shrink the existing XP installation, use Parted Magic

Before shrinking, get sure your XP installation isn't very fragmented, and keep the final size of the partition at least 15% bigger than the total data in it.

Uhhhh... I don't claim that I've used any Linux flavour out there, but NO serious distro overwrites files in /boot without user consent. At least, none of the distros I've used (and they are quite a few) does that.

Moreover, if you have set up your Linux using RAID, and at some time you want to remove RAID, it's a nightmare most of the times. With a separate /boot partition, the procedue is way, way simpler.

@ Tux 99: You have in there ALL boot kernel images, as well as the grub config. You can adjust what kernel image you need, and what not, and edit the grub config accordingly, no matter which distro you're booted at. Moreover, the procedure to have one grub for every linux distro in there, is greatly simlified.

Do you think this is useless? Methinks it's a great convienience.

I keep just a small (256M) swap file in my systems, just in case. But you can do without any swap in 99% of the cases.

I have a larger swap (3.2 GB, which is slightly larger than my physical RAM) in my laptop, because I use it to suspend to disk.

Separate /root and /usr doesn't mak sense, but separate /var does in server systems (all logfiles are stored in there, and they can be huge).

Also extremely convenient is a small (not more than 100M) /boot partition, in case you want to play with various linux distros in parallel.

Google is your best friend...

http://wiki.archlinux.org/index.php/Broadcom_BCM4312

Please note the part of the wiki about the interface swapping- it looks to be the very same issue you are having.

Pretty sure that "kernel-source" was not needed.

gcc, make and (possibly) patch were, though, if not installed by default.

Static Ip's managed by the router (which of course also acts as an intenet gateway) is by FAR the simplest and cleanest solution.

You do not need dhcp/wins if you use static addresses, and regarding DNS, you can rely to the DNS server which is pinned on your router, or explicitly define a different one on any of your machines- no matter if they are Linux or Windoze.

I do not need such a utility, as midnight commander (or at least the latest MC versions from SVN) do show the occupied and free disk space on the right bottom of each panel.

What you mentioned above is for... uhhh, windoze.

Open a console and type in

ping www.google.com

If you get no response, then you must enter the Mandriva Control Center and set your network in there to use the aforementioned modem for connection.

The Mandriva-specific network scripts have been made with ease of use in mind, and as such they are complex- IMHO a tad too complex for their own good.

smbclient is enough, you don't need a full samba, nor any samba configuration.

To access the windoze shares, just open dolphin or konqueror and type in the address bar

smb://DOWNSTAIRSMEDIAPC

Before DOWNSTAIRSMEDIAPC you can add the domain name, if you have set any.

Which way do you try to connect to the synth device?

Jack may be necessary. The best way to manage jack is qjackctrl, although I do not know if such an old machine will complain for the resources needed.

Apparently, all needed modules are loaded, so it's not an OS issue.