Uh, which BSD ? They are not all the same you know. They don't all come with an Awesome manual. So specify which one you are talking about, and stop sounding like someone who has never used them.
I plan on making a homemade EEG (Electro-encephalogram, scan brainwaves) for an Xmas present to myself
Neat! I've had a fair bit of experience with EEG and ERP work, (I have worked in a couple of university labs doing just that) and I think it would be no more than making a clean little amp. Check out this email which has actual schematics. Have fun!
I don't know about how open source this is, but antarcti.ca can render computer networks into 2D or 3D maps. You might also want to check the slashdot story on this.
I'm still looking for the 'magic solution' myself - trouble is, it is rather complicated to get this right. It sure is fun though! Some links I have found handy in the past, probably more for those people who don't know all that much about it:
Winamp, and as a consequence, xmms, have always seemed clunky in terms of UI to me. Freeamp is better, but in my opinion GQmpeg, even though it is just a frontend to mpg123, has the best interface. It also has some really neat skins (check the PDA one).
The topic IS OS specific. It is mostly about using ripit, a perl script, on FreeBSD. It apparently can be installed from ports. NetBSD has 'ports', but it refers to the different archs that can run it. Ok, so I let that one slide and I s/ports/pkgsrc. Ripit is not in pkgsrc. I could perhaps get it working and pkg it up just so I could use that article ? No, I'm much more likely to use cdparanoia or something which is already in pkgsrc. But the article does not mention cdparanoia.
And the other little things. The cd device is different under between FreeBSD and NetBSD, so if I tried to follow his instructions, I would not get very far.
So, it's value to me as a NetBSD user ? Not a lot. The article may as well just be titled 'Ripping MP3s in UNIX' for all I care. A suggested title would be 'Ripping Audio under FreeBSD using Ripit'.
Also, you say FreeBSD and OpenBSD don't have the 'new style' init scripts 'yet' ? I assume you refer to/etc/rc.d on NetBSD 1.5 and greater, and if so - it has already been established that OpenBSD at least will not be getting them. Unless things have changed since Theo last said 'no'.
These two cases are not the same. Yes there are many Linux distros, but they all use the same kernel and mostly the same userland, the major exception being the binary package tools. The BSD's do NOT use the same kernel (BIG differences), and the userland is often significantly different too. Only someone who does not use the different BSD versions would call one of them in particular 'BSD'. When FreeBSD 4.4 just came out, at least Slashdot did not report that 'BSD 4.4' is out. So keep *that* up.
Let me put it this way - articles written about FreeBSD or OpenBSD are of no interest to me, as the content is often irrelevant to what I use (NetBSD). So it is an incorrect shorthand, at best. If you are talking about FreeBSD, call it FreeBSD. Daily Daemonnews uses the term BSD correctly (which is hopefully as I have here). Slashdot does not in mant cases.
It would be really nice if the slashdot crowd stopped using "BSD" to mean one of the *BSD's. This article is about FreeBSD, hence the title should have said "FreeBSD". They are not the same, sometimes they are not even similar. A relevant example to this topic - the process of ripping on NetBSD is not the same as FreeBSD, as NetBSD treats all IDE drives as SCSI, hence one can use tools meant for SCSI drives on and IDE system. The same with burning as well, eg FreeBSD have 'burncd' or something in their userland specifically for IDE burners, but NetBSD can use the 'cdrecord' package on an IDE drive (which only supports SCSI burning).
So, I implore you - specify the 'BSD' you are talking about - trust me they are not at all alike in many respects.
Re:Sorry, dd chopped mp3 files do not always work.
on
Splitting Mp3's
·
· Score: 0
aye, I have a bunch of mp3's that make this "skreech" with mpg123 but are fine in xmms. Can you detail how to "clean them up" ?
LCC [or insert any other compiler other than GCC] ? It'll probably never happen. GCC is not the best compiler in the world, and at certain things (optimisations, for example), it is rubbish. However, it is more portable than anything else around, and, let's face it, we are stuck with it. There are a lot of people very pissed off that they have to use it (I'm most familiar with the attitudes and bitches of people who use/develop NetBSD regarding GCC), however there is no even remotely mature compiler that could drop into it's place in the project.
That's not to say it won't happen, but it won't happen soon. --
You have a great point. The handheld arena is very young, even in "computer years", and problems such as these for the Agenda VR3 will just kill it off quicker. I can understand these companies wanting to "get it out there" as quick as possible, in order to get some return. Who is to blame ? The release engineers ? The marketing guys who promised it too early ? Probably nobody, these things just happen.
But this does not bode well for the company itself. Would you be prepared to "buy another lemon" next time ? Personally, I would need some serious convincing (and maybe free stuff;).
It's not like the road isn't littered with enough carcasses as it is - for example, I have several friends who are Apple Newton fanatics, to this day. They live it. They breath it. The problem is, it's dead. Apple gave up. The parts are enormously expensive. The OS is buggy.
Pedantic ? Perhaps. However, I can see why the comment was made. Consider if your friend said to you several times during a conversation something along the lines of "I was on Netscape last night, and I found this great website". Only slightly annoying, right ? But what if your friend's friend started saying it, etc ? Viola, a new generation of users learn improper syntax concerning the use of the "internet"
Which reminds me of my main point.;-) Who does not know someone that says "internet" when they mean "World Wide Web" ? Port 80 is just one of them folks, but Joe User doesn't know this. It's annoying. It's frustrating. It may also be pedantic - if so, a pedant I am. --
Slashdot Mirror
Uh, which BSD ? They are not all the same you know. They don't all come with an Awesome manual. So specify which one you are talking about, and stop sounding like someone who has never used them.
I plan on making a homemade EEG (Electro-encephalogram, scan brainwaves) for an Xmas present to myself
Neat! I've had a fair bit of experience with EEG and ERP work, (I have worked in a couple of university labs doing just that) and I think it would be no more than making a clean little amp. Check out this email which has actual schematics. Have fun!
Hack on something you may not have before. Check out some of the Ports of NetBSD. In particular, the Dreamcast and the Playstation 2. Or maybe the HITACHI Super-H family based Windows CE PDA machines are more your style.
1984 seems to be drawing ever closer... especially since September of this year.
If you have no idea what I am talking about, start here, or just jump straight to this summary.
I don't know about how open source this is, but antarcti.ca can render computer networks into 2D or 3D maps. You might also want to check the slashdot story on this.
Robot Challenge link from the story.
Multihoming and BGP FAQ - has some links to the RFC's etc.
Avi Freedman's site has some very useful docs, in particular his Multihoming for the small ISP, and his newer BGP Routing docs. He even has a powerpoint presentation titled "How to Multi Home" but I have not seen it.
General Discussion, and
Developer info.
xmms was formerly known as x11amp. Here is the slashdot story from when this happened.
GQmpeg
GQmpeg Skins.
http://download.nullsoft.com/winamp/client/Winamp- 0.a1-1.i386.rpm
The topic IS OS specific. It is mostly about using ripit, a perl script, on FreeBSD. It apparently can be installed from ports. NetBSD has 'ports', but it refers to the different archs that can run it. Ok, so I let that one slide and I s/ports/pkgsrc. Ripit is not in pkgsrc. I could perhaps get it working and pkg it up just so I could use that article ? No, I'm much more likely to use cdparanoia or something which is already in pkgsrc. But the article does not mention cdparanoia.
/etc/rc.d on NetBSD 1.5 and greater, and if so - it has already been established that OpenBSD at least will not be getting them. Unless things have changed since Theo last said 'no'.
And the other little things. The cd device is different under between FreeBSD and NetBSD, so if I tried to follow his instructions, I would not get very far.
So, it's value to me as a NetBSD user ? Not a lot. The article may as well just be titled 'Ripping MP3s in UNIX' for all I care. A suggested title would be 'Ripping Audio under FreeBSD using Ripit'.
Also, you say FreeBSD and OpenBSD don't have the 'new style' init scripts 'yet' ? I assume you refer to
These two cases are not the same. Yes there are many Linux distros, but they all use the same kernel and mostly the same userland, the major exception being the binary package tools. The BSD's do NOT use the same kernel (BIG differences), and the userland is often significantly different too. Only someone who does not use the different BSD versions would call one of them in particular 'BSD'. When FreeBSD 4.4 just came out, at least Slashdot did not report that 'BSD 4.4' is out. So keep *that* up.
Let me put it this way - articles written about FreeBSD or OpenBSD are of no interest to me, as the content is often irrelevant to what I use (NetBSD). So it is an incorrect shorthand, at best. If you are talking about FreeBSD, call it FreeBSD. Daily Daemonnews uses the term BSD correctly (which is hopefully as I have here). Slashdot does not in mant cases.
It would be really nice if the slashdot crowd stopped using "BSD" to mean one of the *BSD's. This article is about FreeBSD, hence the title should have said "FreeBSD". They are not the same, sometimes they are not even similar. A relevant example to this topic - the process of ripping on NetBSD is not the same as FreeBSD, as NetBSD treats all IDE drives as SCSI, hence one can use tools meant for SCSI drives on and IDE system. The same with burning as well, eg FreeBSD have 'burncd' or something in their userland specifically for IDE burners, but NetBSD can use the 'cdrecord' package on an IDE drive (which only supports SCSI burning).
So, I implore you - specify the 'BSD' you are talking about - trust me they are not at all alike in many respects.
aye, I have a bunch of mp3's that make this "skreech" with mpg123 but are fine in xmms. Can you detail how to "clean them up" ?
All I want to know is when OpenBSD is going to get SMP for any platform...
Usually, after NetBSD gets it running just fine, they will port it.
--
LCC [or insert any other compiler other than GCC] ? It'll probably never happen. GCC is not the best compiler in the world, and at certain things (optimisations, for example), it is rubbish. However, it is more portable than anything else around, and, let's face it, we are stuck with it. There are a lot of people very pissed off that they have to use it (I'm most familiar with the attitudes and bitches of people who use/develop NetBSD regarding GCC), however there is no even remotely mature compiler that could drop into it's place in the project.
That's not to say it won't happen, but it won't happen soon.
--
You have a great point. The handheld arena is very young, even in "computer years", and problems such as these for the Agenda VR3 will just kill it off quicker. I can understand these companies wanting to "get it out there" as quick as possible, in order to get some return. Who is to blame ? The release engineers ? The marketing guys who promised it too early ? Probably nobody, these things just happen.
;).
;)
But this does not bode well for the company itself. Would you be prepared to "buy another lemon" next time ? Personally, I would need some serious convincing (and maybe free stuff
It's not like the road isn't littered with enough carcasses as it is - for example, I have several friends who are Apple Newton fanatics, to this day. They live it. They breath it. The problem is, it's dead. Apple gave up. The parts are enormously expensive. The OS is buggy.
Don't try to tell them it's dead, though
--
Pedantic ? Perhaps. However, I can see why the comment was made. Consider if your friend said to you several times during a conversation something along the lines of "I was on Netscape last night, and I found this great website". Only slightly annoying, right ? But what if your friend's friend started saying it, etc ? Viola, a new generation of users learn improper syntax concerning the use of the "internet"
;-) Who does not know someone that says "internet" when they mean "World Wide Web" ? Port 80 is just one of them folks, but Joe User doesn't know this. It's annoying. It's frustrating. It may also be pedantic - if so, a pedant I am.
Which reminds me of my main point.
--