From: sean <tech.junk@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] Music Retrieval
Date: Tue, 04 Sep 2007 21:58:25 -0400 [thread overview]
Message-ID: <46DE0D41.6080308@verizon.net> (raw)
In-Reply-To: <20070904131110.70e1a4d7@pascal.spore.ath.cx>
Dan Farrell wrote:
> On Tue, 04 Sep 2007 14:01:08 -0400
>
>
>> I was only trying out Amarok.
>
> What did you think? I thought it was super cool, except it's resource
> utilization is so high i don't run it anymore if I can avoid.
I thought it looked interesting, but much more then I really need.
Took a while for playback getting started when I put a music CD in the
player.
Like the capabilities of Internet radio, played with a bit, before removal.
>> I suspect they aren't sending the information via icmp, so just the
>> fact that the server is "pingable" really doesn't provide useful
>> information in this particular case.
>
> yeah, but it is a lot more likely that the server would be down than
> that it's just misconfigured. servers go down all the time; they are
> generally seldom administered. so it seems to me a ping is a good
> first step in testing access to these servers. im guessing CDDB does
> use IP, so if icmp can get through, so can tcp (udp,or any other
> protocols encapsulated in ip).
Audacious works fine on info retrieval, Amarok only worked a short bit,
even when both installed together.
Still tend to think that something was not right when the package was
emerged.
Anyway, I will stick with Audacious for now.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-09-05 2:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 18:00 [gentoo-user] Music Retrieval sean
2007-09-02 18:18 ` b.n.
2007-09-02 19:22 ` sean
2007-09-04 15:52 ` sjohnson
2007-09-04 18:01 ` sean
2007-09-04 18:11 ` [gentoo-user] [OT] " Dan Farrell
2007-09-05 1:58 ` sean [this message]
2007-09-05 1:51 ` [gentoo-user] " sean
2007-09-05 15:23 ` Dan Farrell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46DE0D41.6080308@verizon.net \
--to=tech.junk@verizon.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox