Prev: who said slackware not support old versions?
Next: sadc system activity collector missing from slackware 13
From: jr4412 on 23 May 2010 18:36
On 23 May, 22:05, Bud <B...(a)bud.invalid.msn.com> wrote:
> Ever look at your fstab in /etc ?

mountpoints (ie your '/etc/fstab' stuff) are not useful in this
context.

'cdda2wav -scanbus' shows the device spec's required.
From: jr4412 on 23 May 2010 18:58
Mike,

> Adding device direction as per man page fixed this, but then I got hangs.

is your machine busy with other stuff (print/db/web servers, other
users)?? obviously, it helps to keep usage low whilst copying; quick
checks with (for eaxmple) 'uptime' and 'netstat -untapvee' will give
you an idea.

also, apologies for suspecting trolling, sorry.
From: Mike Jones on 24 May 2010 05:38
Responding to jr4412:

> Mike,
>
>> Adding device direction as per man page fixed this, but then I got
>> hangs.
>
> is your machine busy with other stuff (print/db/web servers, other
> users)?? obviously, it helps to keep usage low whilst copying; quick
> checks with (for eaxmple) 'uptime' and 'netstat -untapvee' will give you
> an idea.
>
> also, apologies for suspecting trolling, sorry.


Easy to do I suppose. It just takes one moment...

Anyhoo, I think it would be a goodidea to run some process checking on
this, as I'm still wondering if I have a hardware glitch.

Checklist...

* Can others do this? = yes

* Can I do this = no

* Same commands? = yes

* Same configs? = unknown

* Hardware glitch = possible


Testing time.

First up though, a "did this and got that" report, coming next.

--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.
First  |  Prev  | 
Pages: 1 2 3 4 5 6 7 8
Prev: who said slackware not support old versions?
Next: sadc system activity collector missing from slackware 13