you're going to pay for radio??? satellite radio quality is less than 128kbps mp3 (try it out, can you hear the compression artifacts?), fades when you drive under a bridge and in bad weather, and requires repeaters in cities. why not spend that money on a car mp3 player that'll put a few gigs in your car?
there are a few solutions. the empeg is extinct. the ssi neo is cheap. it's not good, but it's cheap. the phatbox is probably the best solution for you (especially if you're getting an aftermarket stereo). if you're scared of small companies, the phatbox also comes as the kenwood music keg (it runs linux, too).
10 gigs in my car. haven't listened to the radio in months.
a file of what? what's in it, random data? how do i know when i found it?
i hope they dont use my method of hiding data: tar files bzip2 tar file xor it with my social security number hexdump to ascii file generate gif of the hex in the ascii file gpg encrypt gif gzip the gpg text (twice!) divide file into ints, swap endien-ness, reform uuencode the file hide contents in id3v2 tag of my "nofx" mp3s
it does NOT play OGG. only the desktop software component of it supports playback and encoding of ogg files. the music keg currently only plays mp3, wma, and wav.
of course, this is a product of these guys and has been available for a while (and it does run linux!).
i used to be a gov'ment contractor. then i went the dotcom way. after that went away, i got a software job in private industry.
so, having done both, i can say that i will never ever go back to government software. i can tolerate dull work, but the fact that all the engineers around me were so beaten down, unmotivated, and unambitious was seriously depressing. the documentation was pretty painful too (but let's not get into that).
can you image working in an office where your boss (literally) kicks you out of the building at 5pm because you're not authorized to charge your time to any project after that (you will have exceeded your weekly hour charges)? can you imagine having "the mainframe" (actually just an sgi o2) have timesharing software on it that computes the cpu hours consumed and charges them to your project (don't play any mp3's!)? can you imagine coming up with a really cool-simple-efficient-practical-elegant solution to a problem and having it rejected because it wasn't documented years ago?
the dot commers (i was one) developed software and had a great time (i personally made alot of money, despite being layed off several times). the government workers can collect their dependable checks forever, but they will never enjoy their work.
i can't believe this wasn't picked up by slashdot already, but Kenwood USA is releasing a car mp3 player that runs linux! this is yet another victory in the embedded market.
i believe the product was actually made by these guys, but now it's being carried in retail chains.
other than this, ces was a total disappointment. nothing new or original there.
users in the wheel group can "take the wheel", as it were. if you're not in wheel, you don't get to drive. wheel is still implemented on openbsd and freebsd (dunno about net)
problems booting emacs
on
GNU Emacs 21
·
· Score: 1
i tried upgrading my old p2, and i keep getting the same problem, emacs won't recognize my network card. originally, i thought the problem was with the new emacs network drivers (i had to update all the/emacs/network*.el files anyway) but i checked the man pages and it said emacs should support my cards without having to recompile the emacs kernel.
i tried wiping the disk and reformatting it (using emacsdisk) to emacs3fs, but now i can't seem to find an emacs disk image that i can install from (and i can't do an ftp install because my network card doesnt work).
please help me. i was using emacs as my nat and firewall, as well as a personal web server (i could never get named running properly in emacs, but that's a different story)
dmesg attached below:
--------
EMACS 21 (GENERIC) #653: Sat Apr 28 13:57:59 MDT 2001
josecuervo@emacs.gnu.org:/usr/src/sys/arch/i386/co mpile/GENERIC
cpu0: Intel Pentium II (Klamath) ("GenuineIntel" 686-class, 512KB L2 cache) 267 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SYS,MTRR,PGE,MC A,CMOV,MMX
real mem = 133791744 (130656K)
avail mem = 119136256 (116344K)
using 1658 buffers containing 6791168 bytes (6632K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(2e) BIOS, date 04/16/99, BIOS32 rev. 0 @ 0xfd7b0
pcibios0 at bios0: rev. 2.1 @ 0xfd7b0/0x850
pcibios0: PCI IRQ Routing Table rev. 1.0 @ 0xfdf40/160 (8 entries)
pcibios0: PCI Interrupt Router at 000:07:0 ("Intel 82371FB PCI-ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc0000/0x8000 0xe4000/0xc000
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443LX PCI-AGP" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82443LX AGP" rev 0x03
pci1 at ppb0 bus 1
de0 at pci0 dev 14 function 0 "DEC DECchip 21140" rev 0x22: irq 11
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
sysbeep0 at pcppi0
npx0 at isa0 port 0xf0/16: using exception 16
pctr: 686-class user-level performance counters enabled
mtrr: Pentium Pro MTRR support
dkcsum: wd0 matched BIOS disk 80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
ex0: initialized
ed0: initialized
vi0: vim: initialized
pico0: device failed
pico1: initialized
joe0: initialized
de0: device failed
how about a computer built for your car?
these guys have made a hackable linux based computer that acts like a cd changer. arm processor, harddrive, etc. i wonder what else you can do with it? maybe the world's (physically) fastest web server.
these devices ship with linux, it's their embedded os. linux is making enormous gains in the embedded world due to the fact that it is both royalty free to ship, the source is completely available, the development tools are both free and familiar, and there is a fair amount of developers out there who are familiar with the kernel/drivers (but you already know this, of course).
consider a device like the oh-so-popular tivo or something more obscure like the phatbox or other portable devices. the makers of these devices have the options of:
paying a dollar to people like windriver (who effectively monopolized bsd, along with vxworks, psos, and others) or psion for every unit shipped
a couple of large bills to for a development license (qnx,...)
a mighty sum for development tools (green hills, nucleus,...)
all of the above (microsoft windows ce)
or, get it all for free by using linux.
under many of these options, i doubt these (probably very small) companies would have ever been able to afford to bring a product to market. and every dollar that doesn't go to a 3rd party at retail is a dollar that goes towards r&d for the super-tivo or whatever (or stays in your pocket).
december 1999, i moved into a new apt and ordered a dsl connection from the people at pacific bell. their friendly 3rd party installer came in and told me that all new installations get pppoe, and asked me to point him at my win98 machine. i point him at my machine, running beos (no comments).
"is that some unix thing?"
"yeah, sure, whatever"
"we don't support unix. only windows98 and mac."
"okay, i'll do it myself."
the guy then proceeds to hand me a usb cable modem. usb on beos? yeah right. i made him go and come back with an ethernet one. he leaves me with a working dsl connection and no way to use it.
what to do? pull out the old machine from the closet, throw win98 on it. there were no stable linux pppoe drivers at the time. it works. kinda. after startup, there is a lovely 2 minute (!!!) interval where it's "dialing up" and the entire os is locked by the proprietary connection software (the protocol it uses is a nice mixture of closed, undocumented, and proprietary connection and authentication methods).
their client leaks memory (hey, there's nothing else running on that machine). the machine crashes on average once every hour (yes, yes, windows blah blah... it's not THAT unstable). whenever the machine crashes, there is a 10 minute delay until the ppp lease expires and i am allowed to acquire a new ip address. so, crash, reboot, wait 10 minutes, and i'm back online (every hour). the client doesn't work on nt4. why should it, why would anyone ever want to use that?
in the course of the next 3 days, i spent more that 16 hours on the phone (i'm not making these numbers up, folks) with the people at pacbell, attempting to convince them that they did not tell me that they were gonna shaft me with pppoe when i signed their contract and i had no basis for assuming that they were going to do so, so they should put me back on bridged ethernet. nothing doing.
plan b: win98 goes out, freebsd goes in. freebsd had a great pppoe implementation. very easy to configure. now all my network traffic travels through the pppoe driver to the tunnel driver (both in userland) to ethernet. freebsd seems to authenticate much faster and doesn't crash. so far so good.
but wait... how come i can't reach some machines. well, i can, but the connection either dies or is painfully slow (0.5kb/sec). took me a while to figure this one out (thanks to freebsd web docs for finally resolving this, btw). pacbell, in their infinite wisdom, had created what is known as a black-hole router. beos (and later, windows), was sending ethernet frames at 1500byte mtu). freebsd, being too smart for that, fragmented packets into appropriate mtus for pppoe (1490, is it?). now, remote sites reassemble these packets and go "hmm, mtu 1500. okay", and respond at that frame size. so the return packets won't fit over pppoe. pacbell's routers are gracious enough to take these packets and drop them on the floor without informing anyone involved that it had done so or why. the solution: fix it so that the frames sent out by all host machines are small enough to fit in the pppoe pipeline.
and when we worked out all the major bugs, what have we come to learn? that pppoe is SLOW. my 384/150 connection could not stream up an mp3 at 112kb/s, and the central office was ON MY BLOCK!!!
the moral of the story is: get a cablemodem. and may pacific bell, sbc, their employees, investors, families, friends, neighbors, and pets burn in hell.
now, the first time i ever checked the pop address that came with my service (having never used it or given it to anyone), i found 6 pieces of spam in there already waiting for me. but that's a different story.
Slashdot Mirror
there are a few solutions. the empeg is extinct. the ssi neo is cheap. it's not good, but it's cheap. the phatbox is probably the best solution for you (especially if you're getting an aftermarket stereo). if you're scared of small companies, the phatbox also comes as the kenwood music keg (it runs linux, too).
10 gigs in my car. haven't listened to the radio in months.
mysql> select * from human where (human.trekkie=1 and human.techie=0);
Empty set (0.00 sec)
a file of what? what's in it, random data? how do i know when i found it?
i hope they dont use my method of hiding data:
tar files
bzip2 tar file
xor it with my social security number
hexdump to ascii file
generate gif of the hex in the ascii file
gpg encrypt gif
gzip the gpg text (twice!)
divide file into ints, swap endien-ness, reform
uuencode the file
hide contents in id3v2 tag of my "nofx" mp3s
it does NOT play OGG. only the desktop software component of it supports playback and encoding of ogg files. the music keg currently only plays mp3, wma, and wav.
of course, this is a product of these guys and has been available for a while (and it does run linux!).
i used to be a gov'ment contractor. then i went the dotcom way. after that went away, i got a software job in private industry.
so, having done both, i can say that i will never ever go back to government software. i can tolerate dull work, but the fact that all the engineers around me were so beaten down, unmotivated, and unambitious was seriously depressing. the documentation was pretty painful too (but let's not get into that).
can you image working in an office where your boss (literally) kicks you out of the building at 5pm because you're not authorized to charge your time to any project after that (you will have exceeded your weekly hour charges)? can you imagine having "the mainframe" (actually just an sgi o2) have timesharing software on it that computes the cpu hours consumed and charges them to your project (don't play any mp3's!)? can you imagine coming up with a really cool-simple-efficient-practical-elegant solution to a problem and having it rejected because it wasn't documented years ago?
the dot commers (i was one) developed software and had a great time (i personally made alot of money, despite being layed off several times). the government workers can collect their dependable checks forever, but they will never enjoy their work.
i can't believe this wasn't picked up by slashdot already, but Kenwood USA is releasing a car mp3 player that runs linux! this is yet another victory in the embedded market.
i believe the product was actually made by these guys, but now it's being carried in retail chains.
other than this, ces was a total disappointment. nothing new or original there.
actually, their bmw, audi, and volkswagen support is through the alpine mbus protocol (they use a standard adapter).
all i've ever wanted is 30 gigs of mp3's in my car. won't somebody buy this for a starving student?
the jargon file being of no help...
users in the wheel group can "take the wheel", as it were. if you're not in wheel, you don't get to drive. wheel is still implemented on openbsd and freebsd (dunno about net)
i tried upgrading my old p2, and i keep getting the same problem, emacs won't recognize my network card. originally, i thought the problem was with the new emacs network drivers (i had to update all the /emacs/network*.el files anyway) but i checked the man pages and it said emacs should support my cards without having to recompile the emacs kernel.
o mpile/GENERIC
C A,CMOV,MMX
i tried wiping the disk and reformatting it (using emacsdisk) to emacs3fs, but now i can't seem to find an emacs disk image that i can install from (and i can't do an ftp install because my network card doesnt work).
please help me. i was using emacs as my nat and firewall, as well as a personal web server (i could never get named running properly in emacs, but that's a different story)
dmesg attached below:
--------
EMACS 21 (GENERIC) #653: Sat Apr 28 13:57:59 MDT 2001
josecuervo@emacs.gnu.org:/usr/src/sys/arch/i386/c
cpu0: Intel Pentium II (Klamath) ("GenuineIntel" 686-class, 512KB L2 cache) 267 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SYS,MTRR,PGE,M
real mem = 133791744 (130656K)
avail mem = 119136256 (116344K)
using 1658 buffers containing 6791168 bytes (6632K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(2e) BIOS, date 04/16/99, BIOS32 rev. 0 @ 0xfd7b0
pcibios0 at bios0: rev. 2.1 @ 0xfd7b0/0x850
pcibios0: PCI IRQ Routing Table rev. 1.0 @ 0xfdf40/160 (8 entries)
pcibios0: PCI Interrupt Router at 000:07:0 ("Intel 82371FB PCI-ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc0000/0x8000 0xe4000/0xc000
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443LX PCI-AGP" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82443LX AGP" rev 0x03
pci1 at ppb0 bus 1
de0 at pci0 dev 14 function 0 "DEC DECchip 21140" rev 0x22: irq 11
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
sysbeep0 at pcppi0
npx0 at isa0 port 0xf0/16: using exception 16
pctr: 686-class user-level performance counters enabled
mtrr: Pentium Pro MTRR support
dkcsum: wd0 matched BIOS disk 80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
ex0: initialized
ed0: initialized
vi0: vim: initialized
pico0: device failed
pico1: initialized
joe0: initialized
de0: device failed
emacs$
how about a computer built for your car?
these guys have made a hackable linux based computer that acts like a cd changer. arm processor, harddrive, etc. i wonder what else you can do with it? maybe the world's (physically) fastest web server.
these devices ship with linux, it's their embedded os. linux is making enormous gains in the embedded world due to the fact that it is both royalty free to ship, the source is completely available, the development tools are both free and familiar, and there is a fair amount of developers out there who are familiar with the kernel/drivers (but you already know this, of course).
consider a device like the oh-so-popular tivo or something more obscure like the phatbox or other portable devices. the makers of these devices have the options of:
under many of these options, i doubt these (probably very small) companies would have ever been able to afford to bring a product to market. and every dollar that doesn't go to a 3rd party at retail is a dollar that goes towards r&d for the super-tivo or whatever (or stays in your pocket).
yes, i'm preaching to the choir. let them sing.
joe
december 1999, i moved into a new apt and ordered a dsl connection from the people at pacific bell. their friendly 3rd party installer came in and told me that all new installations get pppoe, and asked me to point him at my win98 machine. i point him at my machine, running beos (no comments).
"is that some unix thing?"
"yeah, sure, whatever"
"we don't support unix. only windows98 and mac."
"okay, i'll do it myself."
the guy then proceeds to hand me a usb cable modem. usb on beos? yeah right. i made him go and come back with an ethernet one. he leaves me with a working dsl connection and no way to use it.
what to do? pull out the old machine from the closet, throw win98 on it. there were no stable linux pppoe drivers at the time. it works. kinda. after startup, there is a lovely 2 minute (!!!) interval where it's "dialing up" and the entire os is locked by the proprietary connection software (the protocol it uses is a nice mixture of closed, undocumented, and proprietary connection and authentication methods).
their client leaks memory (hey, there's nothing else running on that machine). the machine crashes on average once every hour (yes, yes, windows blah blah... it's not THAT unstable). whenever the machine crashes, there is a 10 minute delay until the ppp lease expires and i am allowed to acquire a new ip address. so, crash, reboot, wait 10 minutes, and i'm back online (every hour). the client doesn't work on nt4. why should it, why would anyone ever want to use that?
in the course of the next 3 days, i spent more that 16 hours on the phone (i'm not making these numbers up, folks) with the people at pacbell, attempting to convince them that they did not tell me that they were gonna shaft me with pppoe when i signed their contract and i had no basis for assuming that they were going to do so, so they should put me back on bridged ethernet. nothing doing.
plan b: win98 goes out, freebsd goes in. freebsd had a great pppoe implementation. very easy to configure. now all my network traffic travels through the pppoe driver to the tunnel driver (both in userland) to ethernet. freebsd seems to authenticate much faster and doesn't crash. so far so good.
but wait... how come i can't reach some machines. well, i can, but the connection either dies or is painfully slow (0.5kb/sec). took me a while to figure this one out (thanks to freebsd web docs for finally resolving this, btw). pacbell, in their infinite wisdom, had created what is known as a black-hole router. beos (and later, windows), was sending ethernet frames at 1500byte mtu). freebsd, being too smart for that, fragmented packets into appropriate mtus for pppoe (1490, is it?). now, remote sites reassemble these packets and go "hmm, mtu 1500. okay", and respond at that frame size. so the return packets won't fit over pppoe. pacbell's routers are gracious enough to take these packets and drop them on the floor without informing anyone involved that it had done so or why. the solution: fix it so that the frames sent out by all host machines are small enough to fit in the pppoe pipeline.
and when we worked out all the major bugs, what have we come to learn? that pppoe is SLOW. my 384/150 connection could not stream up an mp3 at 112kb/s, and the central office was ON MY BLOCK!!!
the moral of the story is: get a cablemodem. and may pacific bell, sbc, their employees, investors, families, friends, neighbors, and pets burn in hell.
now, the first time i ever checked the pop address that came with my service (having never used it or given it to anyone), i found 6 pieces of spam in there already waiting for me. but that's a different story.