PDA

View Full Version : two newbie questions



Chris Kantarjiev
2004-04-01, 15:55
I've just ordered a wireless squeezebox and started installing
the software. I've poked around the archives a bit but haven't
found answers to these questions - any help will be appreciated.

- The Installation.txt is pretty barebones. My server is an OpenBSD
box. A few hints about typical configs and directory layout would
be appreciated - do folks tend to create a new user to run this
and then run it via a "su" out of /etc/rc, or something along
those lines? Does the slimserver code expect to find its modules
under .?

- While my MP3s live on the OpenBSD box, so far all my clients are
PCs. So my m3u playlists are created by winamp and either have
relative addressing or a prefix of M: to point the client programs
at the right place. I'd like to put in a small hack to allow
SlimServer to understand the M: syntax - where's a likely place
to start?

Thanks,
chris

Pat Farrell
2004-04-01, 16:45
In the spirit that some answers quickly are better than all answers
later, I'll take a stab...

At 05:55 PM 4/1/2004, Chris Kantarjiev wrote:
>- The Installation.txt is pretty barebones. My server is an OpenBSD
>box. A few hints about typical configs and directory layout would
>be appreciated - do folks tend to create a new user to run this
>and then run it via a "su" out of /etc/rc, or something along
>those lines? Does the slimserver code expect to find its modules
>under .?

The Linux RPMs install the software under /usr/local/slimserver
There is one critical config file, /etc/slimserver.config
There is also a /etc/sysconfig/slimserver that handles
startup from /etc/rc/d/init.d

The program really likes being started from a root job, but executes
under a privledgeless account of "slimserver"
The standard RPM puts the appropriate entries so that
automated startup works as you expect.

So if you do it by hand, I would definitely make a new user,
slimserver with suitable low or zero privs.

In today's release, there is a log file written to /tmp/slimserver.log
This can be changed by editing the /etc/sysconfig/slimserver
I'm working on a general, cross platform approach

>- While my MP3s live on the OpenBSD box, so far all my clients are
>PCs. So my m3u playlists are created by winamp and either have
>relative addressing or a prefix of M: to point the client programs
>at the right place. I'd like to put in a small hack to allow
>SlimServer to understand the M: syntax - where's a likely place
>to start?

There is a place to define the directory for your playlists.
Why not just move them there, and maybe write a perl script to
remove all the M: references and make it connect properly.
Probably a oneliner with suitable -p -e

HTH,
Pat

Tom Newton
2004-04-01, 16:55
Chris Kantarjiev wrote:

>
>
> - While my MP3s live on the OpenBSD box, so far all my clients are
> PCs. So my m3u playlists are created by winamp and either have
> relative addressing or a prefix of M: to point the client programs
> at the right place. I'd like to put in a small hack to allow
> SlimServer to understand the M: syntax - where's a likely place
> to start?

Good point.. i'd like to be able to download playlists and play them on my
box (where the music is mounted under /mnt/music) or some windows box where
it's L: (don't ask). Be good to have something that could "sanitize" a
playlist before download...

--

Tom Newton

dean
2004-04-01, 17:00
It would be great if somebody could write up improved directions based
on their installation experience. I'd be happy to update the
Installation.txt file...


On Apr 1, 2004, at 3:45 PM, Pat Farrell wrote:

> In the spirit that some answers quickly are better than all answers
> later, I'll take a stab...
>
> At 05:55 PM 4/1/2004, Chris Kantarjiev wrote:
>
> - The Installation.txt is pretty barebones. My server is an OpenBSD
> box. A few hints about typical configs and directory layout would
> be appreciated - do folks tend to create a new user to run this
> and then run it via a "su" out of /etc/rc, or something along
> those lines? Does the slimserver code expect to find its modules
> under .?
>
> The Linux RPMs install the software under /usr/local/slimserver
> There is one critical config file, /etc/slimserver.config
> There is also a /etc/sysconfig/slimserver that handles
> startup from /etc/rc/d/init.d
>
> The program really likes being started from a root job, but executes
> under a privledgeless account of "slimserver"
> The standard RPM puts the appropriate entries so that
> automated startup works as you expect.
>
> So if you do it by hand, I would definitely make a new user,
> slimserver with suitable low or zero privs.
>
> In today's release, there is a log file written to /tmp/slimserver.log
> This can be changed by editing the /etc/sysconfig/slimserver
> I'm working on a general, cross platform approach
>
>
> - While my MP3s live on the OpenBSD box, so far all my clients are
> PCs. So my m3u playlists are created by winamp and either have
> relative addressing or a prefix of M: to point the client programs
> at the right place. I'd like to put in a small hack to allow
> SlimServer to understand the M: syntax - where's a likely place
> to start?
>
> There is a place to define the directory for your playlists.
> Why not just move them there, and maybe write a perl script to
> remove all the M: references and make it connect properly.
> Probably a oneliner with suitable -p -e
>
> HTH,
> Pat
>

Tom Newton
2004-04-02, 17:18
Peter Pouliot wrote:

> Here's how I sanitize playlists....
> it may not be pretty but it works...
>
> #!/bin/sh
> #
> perl -pi -e 's|file:\\\\localhost\\Volumes\\MP3\\|/mp3/|g;' *.m3u ;

<snip>

Oooow! Too many forks! What was wrong with making it perl and not sh? :)

Can do that OK, would just like to automate it a bit more for my windowsy
amigos :)

--

Tom Newton