On Sat, 2002-01-12 at 09:26, Bob Miller wrote:
> I'm trying to get an Icecast server going this morning.
> 
> I installed Globecom Jukebox over the last couple of days, and
> successfully ripped one CD (just 799 CDs to go (-: ).  But so far, I
> haven't heard it actually play anything.  Need icecast to get the
> sound to a machine with speakers.

uhm, good luck...  fortunately, linux is much better about sharing the
processor than windoze.  i _hated_ ripping cd's under '98...  surprised
i actually got any work done back at stream...

i'm trying to finish a project here at work that was due yesterday.

> Don't worry.  It'll all be better in a couple of days when you wipe
> the disk and install a completely different OS. (-:

gee, thanks.  it's the nicest jab to the ribs i've ever felt...

the problem here is that i'm not sure whether i have a hardware or
software problem.  i suppose i could load up winXP and just let it run
for a day or two...

> If you have a second computer, pinging the crashed box is useful.
> When a Unix/Linux box responds to a ping, it happens inside the TCP/IP
> stack.  If you get a pong back, then you know that the box is
> accepting interrupts and able to run them.  That means the problem is
> probably outside the kernel.

i may have another computer in a week or so.  i'll give that a try if i
haven't, uhm, re-installed...

> Otherwise, you know you have a wedged kernel, and either you've
> created a bad kernel config (Hi, Mike!), installed a buggy driver, or
> the kernel just has bugs (which never happens, because this is Linux!
> *-: )

not, i.  it's redhat's "proprietary" kernel (you know, the one that has
five times the crap that comes with the normal kernel...  s'truth!  when
installing, redhat reports the "kernel" package as > 100 mb...)  i
suppose i'll just try a recompile with a newer kernel and see if that
works.

> Another good test is switching to a different virtual console.
> CTL-ALT-F1 through F9.  But buggy X servers sometimes break that.

i'll give that a try too.  though it didn't seem as if the keyboard was
responding.

now that i think about it, i should check into being a guinea pig for
the kernel developers.  considering how much i like "bleeding edge"
software...

if anybody can break it through normal use, it'd be me.  ;)

Reply via email to