View Full Version : music held on multiple HD

2005-11-24, 17:08
I have the following setup :

slimcd running in a virtual pc
mounts a 80Gb FAT32 virtual drive

I ftp the flac/mp3 files across to it when adding incrementally and mount it directly when dumping large amounts of files on to it.

Now the above works ok, but I'm wondering what happens when I run out of space and mount another virtual or real HD to it. I'm sure I can have an alias pointing to the next drive if it was a linux type partition or shortcuts if it was a MS Windows pc.

I'm not a linux expert, so how would I go about creating the link between the first and next partitions (FAT32)?


2005-11-25, 00:07
I'm no expert.. but I think:
ln new_drive_mountpoint where_you_want_to_link_to

Try creating a small test partition and see if it works..

Patrick Dixon
2005-11-25, 01:50
I'm not a linux expert, so how would I go about creating the link between the first and next partitions (FAT32)?Mount the new drive/partition then, in the directory that SS expects it's music in, make a simlink to that mountpoint.

2005-11-25, 07:23
did a bit of digging and found this :

A feature of linking files is available in Linux. It works by "redirecting" a file to the actual file. It's referred to as a symbolic link. Don't confuse this term with the linking of programs, which is when binary programs are connected with libraries that they need to load in order to run.

The most simple way that I've ever used ln to create symbolic links is ln -s existing_file link. Evidently there's a hard link and a symbolic link; I've been using a symbolic link all along. You can also use the -f flag to force the command line to overwrite anything that might have the symbolic link's file name already.

To remove a symbolic link, simply type rm symbolic_link. It won't remove the file that it's linked to.

Neil, Patrick, thanks for the pointers

Thanks guys!

2005-11-25, 08:03
the links for libraries are the same as the ones for directories.

a symbolic link is obtained by invoking 'ln -s ...'.

A dynamic library could be called 'libxyz.so' for instance, but it would be a symbolic link to libxyz.so.1.4 which is the actual library. When a newer version of the library is installed (libxyz.so.1.5 for instance) the symbolic link gets moved to the newer library. That way the old library is still available and a simple change of link can undo an upgrade. This is much better than actually replacing the old library with the new one and then finding out the new one is buggy.

Now for symbolic linking of directories it could go as follows:

music folder = /music

disk 1 is mounted on /mnt/disk1
disk 2 is mounted on /mnt/disk2

then it's just a question of linking both to a directory in /music

ln -s /mnt/disk1 /music/disk1
ln -s /mnt/disk2 /music/disk2

if you then do an 'ls -l' in /music you will see

disk1 -> /mnt/disk1
disk2 -> /mnt/disk2

confirming your newly created links

Hope this helps,