I have a friend who works with the tech support for the netpliance i-opener. He has mentioned a few interesting points that I shall pass along.
1) They apparently cut all sorts of corners in bringing this baby out to the world before the competition. The units apparently cost them ~$600 per unit and they sell them at 199 (99 on sale right now).
2) They don't require any sort of contract because they don't need to. Theoretically they are the only ones who can provide the service for them. Definitely a loss up front, but they plan on making it up in the service.
3) Netpliance is set to have their IPO sometime really soon. One wonders if they'll postpone this or not.
4) As of today there was no official netpliance party line on the situation. basic summary of the interesting posts:
1) winchip 180mhz chip with 32 meg ram/16 flash
2) ram is upgradable to 64 via standard laptop type memory upgrade (hear that imac memory will work) bios might restrict use of more ram
3) I bought a USB->Ethernet controller from ChumpUSA for ~40 today and it came with a Turbolinux CD (SMC EZ connect USB) so I presume there is usb->Ethernet support on the cd 8-)
4) There is a 44 pin IDE header that will only work with the 2.5" notebook drives. Normal IDE uses 40 pins and have seperate power input, whilst the 44 pin versions provide power on the last 4 pins to the notebook HD's (one will notice the lack of a power plug on the notebook ide drives).
5) 10-inch 16bbp color bax res is 800x600
can't think of much else. looks neat, I gotta get me one of these babies!
Last semester I wrote a couple of concept papers about DNS tunneling for an independant research course. At the time I didn't know about the 1998 CERT advisory, and when I went to go dl the code to see what it did, the link was gone 8-( here are the papers: http://www.cs.utexas.edu/users/duckskip/DNS.htm http://www.cs.utexas.edu/users/duckskip/dns-final- report.htm They were meant more as thought provoking and are thus a little light on details, but should make some of the people out there start thinking in that direction. Anyways, for those who want to read and give me comments on the papers, my email is skip@ikansas.com
I'm not sure how much people know about these rc files and the way they are set up, but redhat uses a system v style approach to starting up the system (like irix and solaris) that uses loads of files, each of which has a single purpose (start nfs, start samba, start snmp, kill snmpd) Slackware uses a bsd style approach (like bsd and sunos) where each of the 5-10 rc files has a more general purpose (start the network interface, load ALL the network services, load ALL the modules, etc)
Each one has its pluses and minuses. Envision having to configure a solaris box over a serial port. The sheer number of cofiguration files makes it a pain to configure over a console. If you had a monitor and graphics card plugged into it and a pretty display it would be ok, but having to vi multiple files sucks.
Bsd style is easier to configure, since you only have 5 files to edit period, but is also more succeptable to those annoying topy's (I once accidently delted an "f" out of "fi" and boy did that screw things up, especially since it was in a remote machine in a script that dealt with the network services, had to drive over there and sit down in front of the box to fix it...)
To say one is better than the other is a religous debate and I choose not to partake. I have to use both, so I learned to deal with both.
whenever the first problem occurs, a core file is generated (I believe) in both ~ and ~/.gnome-desktop.If you delete both of them then it seems at least that the next time you startx it works....
the second issue, where you get the root warning thingie over and over again, I think I figured out that if you were NOT in root's home directory when you startx this message would appear, causeing mucho annoyance
Slashdot Mirror
I have a friend who works with the tech support for the netpliance i-opener. He has mentioned a few interesting points that I shall pass along.
1) They apparently cut all sorts of corners in bringing this baby out to the world before the competition. The units apparently cost them ~$600 per unit and they sell them at 199 (99 on sale right now).
2) They don't require any sort of contract because they don't need to. Theoretically they are the only ones who can provide the service for them.
Definitely a loss up front, but they plan on making it up in the service.
3) Netpliance is set to have their IPO sometime really soon. One wonders if they'll postpone this or not.
4) As of today there was no official netpliance party line on the situation.
basic summary of the interesting posts:
1) winchip 180mhz chip with 32 meg ram/16 flash
2) ram is upgradable to 64 via standard laptop type memory upgrade (hear that imac memory will work) bios might restrict use of more ram
3) I bought a USB->Ethernet controller from ChumpUSA for ~40 today and it came with a Turbolinux CD (SMC EZ connect USB) so I presume there is usb->Ethernet support on the cd 8-)
4) There is a 44 pin IDE header that will only work with the 2.5" notebook drives. Normal IDE uses 40 pins and have seperate power input, whilst the 44 pin versions provide power on the last 4 pins to the notebook HD's (one will notice the lack of a power plug on the notebook ide drives).
5) 10-inch 16bbp color bax res is 800x600
can't think of much else. looks neat, I gotta get me one of these babies!
Last semester I wrote a couple of concept papers about DNS tunneling for an independant research course. At the time I didn't know about the 1998 CERT advisory, and when I went to go dl the code to see what it did, the link was gone 8-( here are the papers: http://www.cs.utexas.edu/users/duckskip/DNS.htm http://www.cs.utexas.edu/users/duckskip/dns-final- report.htm They were meant more as thought provoking and are thus a little light on details, but should make some of the people out there start thinking in that direction. Anyways, for those who want to read and give me comments on the papers, my email is skip@ikansas.com
apparently the "." key is not functional on all systems, where's the redhat RPM for that? ;-)
I'm not sure how much people know about these rc files and the way they are set up, but redhat uses a system v style approach to starting up the system (like irix and solaris) that uses loads of files, each of which has a single purpose (start nfs, start samba, start snmp, kill snmpd) Slackware uses a bsd style approach (like bsd and sunos) where each of the 5-10 rc files has a more general purpose (start the network interface, load ALL the network services, load ALL the modules, etc)
.02
Each one has its pluses and minuses. Envision having to configure a solaris box over a serial port. The sheer number of cofiguration files makes it a pain to configure over a console. If you had a monitor and graphics card plugged into it and a pretty display it would be ok, but having to vi multiple files sucks.
Bsd style is easier to configure, since you only have 5 files to edit period, but is also more succeptable to those annoying topy's (I once accidently delted an "f" out of "fi" and boy did that screw things up, especially since it was in a remote machine in a script that dealt with the network services, had to drive over there and sit down in front of the box to fix it...)
To say one is better than the other is a religous debate and I choose not to partake. I have to use both, so I learned to deal with both.
anyways... just my
whenever the first problem occurs, a core file is generated (I believe) in both ~ and ~/.gnome-desktop .If you delete both of them then it seems at least that the next time you startx it works....
the second issue, where you get the root warning thingie over and over again, I think I figured out that if you were NOT in root's home directory when you startx this message would appear, causeing mucho annoyance
just my experiences....
skip