Thanks for actually reading the article dumbass. They just put 802.11 in to your standard run-of-the-mill thin client device. Whoopee shit.
It works over LAN, which means you need software serving up your desktop over wireless LAN. It's not a wireless monitor - a wireless monitor would be a little SVGA dongle that plugs in to whatever video card you choose.
They don't even say if it uses your local video card when docked, you you might not get cool 3d and shiznit even when docked.
I know you guys'll read the comments here because of the sick fucks that you are, so I figure this is as good a place as any to thank you for not coming out with RH8, and for going with a point release.
RedHat 8 would have made my life miserable by breaking compatability without a good reason. Thanks.
Since most machines can only have one hostname, I'd recommend using the low 8 characters of the MAC address of the primary NIC in hex, or the serial number that your accounting department gave the machine for asset tracking. Not all webservers are always webservers, not all BSD machines are always BSD, not all machines in Chibougamou are always in Chibougamou. So stop trying to think of them in that way.
Instead, realize that all well-run single-IT-Department farms that big use DHCP or something similar, which can be based on MAC address.
Then, figure out how you're often going to be thinking of the machines. By location, by OS, by task, etc. So, ff558843.hardware.foo.com would be the box's bona-fide name.
Then, using your l337 DHCP and DNS skillz, make sure that your DNS provides you with all the other conventions that you want. For example: ff558843.hardware.foo.com would have CNAMEs called:
The biggest problem with AMD chips is the motherboard.
While the Athlon is a great chip, you can't get a 4-way SMP system with it yet. And most high-end boxes need SMP. They're so expensive to build that customers need a clear upgrade path - and if dropping in a second processor isn't easy, they don't want the solution.
I build LVS/HA clusters for a living, and one thing I don't think I can do without is the EMP, (Emergency Management Port) which isn't available on AMD motherboards.
The chip really is a smaller portion of the decision. When I build a cluster, I usually recommend an Intel L440GX motherboard, which has all the necessities like onboard dual SCSI, EEPro and EMP. Once you pick out the best motherboard for the lifecycle of the system, you look at the processors that it supports.
If AMD had a motherboard similar to the L440GX that supported SMP thunderbirds, they'd break in to that market. But they don't.
Their motherboards are designed for low-cost deployed workstations or gamers.
Really, motherboard choice is more important than chip choice if you're building LVS, HA, Beowulf, etc. PPC is an option, though.
In all honesty, the kernel knows much better than you do which files it's always accessing, so it can optimize itself better than you.
Type in "free" and you'll see that almost all your RAM is in use -- that's because it's got a RAM buffer of most recently accessed files so they can be accessed again faster. In fact, if you create a temporary file and then delete it, often that file will never touch the disk.
This, of course, is why you have to unmount disks - the unmounting writes the buffers to the disk so that the changes won't be lost.
So, it's already done for you, assuming you want a RAMdisk of your most frequently accessed files.
Sometimes, people want a rarely used file to be easily accessed to reduce load times, which is something that buffering won't help with. So, you just flip the sticky bit on the file, and it's done for you.
By making a RAMdisk, you're taking away from the available RAM that the kernel could be using for intelligent buffering, and actually slowing down the machine.
I use QNX just about every day, so I can tell you that they simply don't care about security that much. If I get root on a QNX box, that's enough permissions to overwrite all the passwd and shadow files on all the QNX boxes on the same network. This is a feature, not a bug, since it means I can also write to//27/dev/modem from node 12. QNX is *legions* ahead of Linux in terms of clustering, it's just less sexy because it's proprietary. The quality of the engineering in that product is nothing less than stellar in all areas that they care about. So what if you can decrypt the passwd file on my life support or Air Traffic Control? By the time those systems are deployed, they don't even have a shell installed, let alone telnetd! QNX was not the right choice for the I-Opener, because the I-Opener hasn't ended up being the kind of embedded device QNX was designed for. Nobody cares if you root a QNX box because any QNX box where that would be a problem isn't rootable even by the people that should have root. Do you think people go around telnetting to traffic lights or to the ABS system in your car? Of course not. Those systems don't allow anyone to log in at all, period, whether you know the password or not. QNX is so heavily optimized for high-performance clusters and hard real-time systems that nobody in their right mind would use it for something where this was an issue. You have to use the right tool for the job, and while QNX is a great tool for its jobs, it was not the right tool for the I-Opener. Fixing this problem won't be worth their time.
It doesn't have a segmented filesystem. The way QNX works is that you can specify a node on the network with//. So,//1/tmp/ is the/tmp/ directory on node 1, and//3/usr/ is the/usr/ directory on node 3. All machines on a QNX network have node numbers, and root privileges are not quashed. (!) But, you can also NFS mount//3/usr/local as/usr/local on all machines and stuff, so it's not really segmented. With QNX, not only can you access the filesystems of the other machines in this way, but you can also access other processors and shared memory! QNX was designed from the ground-up to support clustering and all that stuff that's just becoming sexy now.
Well, even though this story was posted before, it's still a really cool project. I saw their presentation at the Ottawa Linux Symposium, and it's way cool. The page posted on the main page is ABANDONNED and you should look at the project here: www.rt-control.com They've got a lot of new cool stuff going on that's not mentionned on the dead page.
http://www.cs.brown.edu/system/software/mix/faq.ht ml
It's an old mirror, so it's still got the free version. And, I found this on the first page of a simple google search, I didn't have to post an Ask-Slashdot!
You should still use VNC, too, so you can migrate their GUI use, not just their app use.
Could it have possibly ended up better for RedHat? The people with large amounts of money to invest are not OSS writers. They're professional money people. What better way to boost the interest in your IPO than to generate a frenzy like this? It's starting to hit all sorts of media, and by the time this stock hits the market, EVERY SINGLE trader will KNOW that everyone that knows anything about the internals of this company wants in on the deal.
The stock will, of course, shoot straight up. Not becuase investors like RedHat, not because they like OSS, but because the people on the "inside" of the company have lots of faith in it. It would be very illegal for RedHat employees to create a frenzy like this during the Pre-IPO quiet period, so RedHat managed to create all sorts of press without breaking those rules. Hats off to them, they're going to be rich.
RedHat is using the/. community to publicize their IPO. People couldn't get in on this, so they're going around to every media outlet they can find, telling them how great this IPO is going to be, and that they can't get in. It couldn't be better planned.
Myself, I did get the EMail. I know where my EMail address was harvested from, it wasn't hard to figure that out. I can't participate because I'm Canadian, though. Even though Canada and the US both signed the NAFTA that makes my exclusion illegal. Oh, well, I'm not going to complain, because that will simply reward RedHat and ETrade for this sham.
The website for this stuff says that you can connect several (10) iBooks in the same house to the same ISP through the same bridge. Does that mean that this "hub" also does IP Masquerading (aka Network Address Translation) in hardware?
Can you disable that if you want to give the iBooks real IPs, or what?
I do the exact same thing here at my work, using the latest Samba RPM and the latest netatalk+asun SRPM from the PPC distro (More up to date than any other RPMs I could find). The trick is that you have to change the way the netatalk SRPM tracks its version number, or you won't be able to make an i386 RPM from it.:)
You should also rebuild samba with the --with-netatalk switch (RTFM) so that it can reasonably handle the resource forks for the apple files (.AppleDouble/). Be careful how your Linux and Window~1 machines handle the resource forks.
Lastly, you should take a close look at how each machine handles text files. Windows, Apple and Linux are all different, and if you serve all those OSes from the same file structure, you'll be opening a new can of worms. Netatalk+asun is supposed to handle CR/LF translation, but for some reason I can only get it to translate when downloading from the server, not when uploading to the server. I posted the problem to a couple of netatalk/atalk mailing lists to no avail.
But, we got around the problem by using CVS to handle file sharing - since we share mostly HTML docs, this has proved to be the best way for text files, though we still use NFS/SMBd/AFPd for other stuff.
I'm a WAVE@HOME cablemodem subscriber right now, and I can tell you that it's not only about technical support. See, these big companies don't consider the end-user the customer. The end-user is the *product* to sell advertising to.
The system requirements listed on the page aren't the requirements for the network, they're the requirements for the proprietary client software. The CD they send you to install the "network" actually installs their proprietary client (Usually a modified NetScape) and change all your settings. Icons are replaced with their logos, etc. They expect to make their money off advertising on the things they force you to look at.
@HOME recently bought EXCITE. AOL bought Netscape's portal. Yahoo paid IBM a shitload of money to make it the default start page on Aptivas. See where this is going? ADSL subscribers in Ottawa are forced to use a web proxy, and I'm taking bets on how long till they get a proxy that strips out banners and replaces them with home-grown advertising. They're selling the ADSL at such a profit-loss that that's the only way they'll make money in the long run.
End users don't have money - advertisers do. What has to happen is for the government to be pressured by the people in to regulating a difference between connectivity providers and content providers.
Slashdot Mirror
Thanks for actually reading the article dumbass. They just put 802.11 in to your standard run-of-the-mill thin client device. Whoopee shit.
It works over LAN, which means you need software serving up your desktop over wireless LAN. It's not a wireless monitor - a wireless monitor would be a little SVGA dongle that plugs in to whatever video card you choose.
They don't even say if it uses your local video card when docked, you you might not get cool 3d and shiznit even when docked.
I know you guys'll read the comments here because of the sick fucks that you are, so I figure this is as good a place as any to thank you for not coming out with RH8, and for going with a point release.
RedHat 8 would have made my life miserable by breaking compatability without a good reason. Thanks.
Since most machines can only have one hostname, I'd recommend using the low 8 characters of the MAC address of the primary NIC in hex, or the serial number that your accounting department gave the machine for asset tracking. Not all webservers are always webservers, not all BSD machines are always BSD, not all machines in Chibougamou are always in Chibougamou. So stop trying to think of them in that way.
t h-rack.detroit.datacentre.foo.comr e.external-sites.foo.com
3 rd-rack.chicago.datacentre.foo.come .internal-sites.foo.com
Instead, realize that all well-run single-IT-Department farms that big use DHCP or something similar, which can be based on MAC address.
Then, figure out how you're often going to be thinking of the machines. By location, by OS, by task, etc. So, ff558843.hardware.foo.com would be the box's bona-fide name.
Then, using your l337 DHCP and DNS skillz, make sure that your DNS provides you with all the other conventions that you want. For example:
ff558843.hardware.foo.com would have CNAMEs called:
box0005.7-2.redhat.oses.foo.com
3rd-from-top.4
web0002.insecu
Also, ff558843.hardware.foo.com might have the following CNAMES:
box0002.4-5.openbsd.oses.foo.com
4th-from-top.
ssl0005.secur
Once you have it set up and your DHCP/DNS scripted right, you'll wonder how you ever survived without it.
Their "Linux Certified" laptops have winmodems that don't work with open-source drivers.
It's not as hard as it sounds, assuming you have the resources. I'll leave out the details and just give a brief overview.
/mnt/obsd/bigfile (so it compresses better)
/etc/fstab in it right!)
1.) Get a local box with similar hardware
2.) Install 6.2 and oBSD in a dual-boot.
3.) On the CoLo, clear off a spare partition the same size as the oBSD partition on the local box.
4.) Config oBSD on the local box to use the same networking info as the CoLo box, and allow remote access.
5.) On the local box, fill up the oBSD partition with dd if=/dev/zero of=/mnt/obsd/bigfile ; rm
6.) On the local box, umount the oBSD partition and dd if=/dev/hda4 | gzip - > oBSDPartition.img.gz
7.) SCP/FTP the huge-ass file to the CoLo
8.) dd thru gzip the file in to the blank partition. (hope you set up
9.) Set up lilo to boot in to oBSD, reboot it, and pray.
There are a whole lot of gotchas with this, but if you think it though for a day or so first, you might manage.
The biggest problem with AMD chips is the motherboard.
While the Athlon is a great chip, you can't get a 4-way SMP system with it yet. And most high-end boxes need SMP. They're so expensive to build that customers need a clear upgrade path - and if dropping in a second processor isn't easy, they don't want the solution.
I build LVS/HA clusters for a living, and one thing I don't think I can do without is the EMP, (Emergency Management Port) which isn't available on AMD motherboards.
The chip really is a smaller portion of the decision. When I build a cluster, I usually recommend an Intel L440GX motherboard, which has all the necessities like onboard dual SCSI, EEPro and EMP. Once you pick out the best motherboard for the lifecycle of the system, you look at the processors that it supports.
If AMD had a motherboard similar to the L440GX that supported SMP thunderbirds, they'd break in to that market. But they don't.
Their motherboards are designed for low-cost deployed workstations or gamers.
Really, motherboard choice is more important than chip choice if you're building LVS, HA, Beowulf, etc. PPC is an option, though.
In all honesty, the kernel knows much better than you do which files it's always accessing, so it can optimize itself better than you.
Type in "free" and you'll see that almost all your RAM is in use -- that's because it's got a RAM buffer of most recently accessed files so they can be accessed again faster. In fact, if you create a temporary file and then delete it, often that file will never touch the disk.
This, of course, is why you have to unmount disks - the unmounting writes the buffers to the disk so that the changes won't be lost.
So, it's already done for you, assuming you want a RAMdisk of your most frequently accessed files.
Sometimes, people want a rarely used file to be easily accessed to reduce load times, which is something that buffering won't help with. So, you just flip the sticky bit on the file, and it's done for you.
By making a RAMdisk, you're taking away from the available RAM that the kernel could be using for intelligent buffering, and actually slowing down the machine.
I use QNX just about every day, so I can tell you that they simply don't care about security that much. If I get root on a QNX box, that's enough permissions to overwrite all the passwd and shadow files on all the QNX boxes on the same network. This is a feature, not a bug, since it means I can also write to //27/dev/modem from node 12. QNX is *legions* ahead of Linux in terms of clustering, it's just less sexy because it's proprietary. The quality of the engineering in that product is nothing less than stellar in all areas that they care about. So what if you can decrypt the passwd file on my life support or Air Traffic Control? By the time those systems are deployed, they don't even have a shell installed, let alone telnetd! QNX was not the right choice for the I-Opener, because the I-Opener hasn't ended up being the kind of embedded device QNX was designed for. Nobody cares if you root a QNX box because any QNX box where that would be a problem isn't rootable even by the people that should have root. Do you think people go around telnetting to traffic lights or to the ABS system in your car? Of course not. Those systems don't allow anyone to log in at all, period, whether you know the password or not. QNX is so heavily optimized for high-performance clusters and hard real-time systems that nobody in their right mind would use it for something where this was an issue. You have to use the right tool for the job, and while QNX is a great tool for its jobs, it was not the right tool for the I-Opener. Fixing this problem won't be worth their time.
It doesn't have a segmented filesystem. The way QNX works is that you can specify a node on the network with //. So, //1/tmp/ is the /tmp/ directory on node 1, and //3/usr/ is the /usr/ directory on node 3. All machines on a QNX network have node numbers, and root privileges are not quashed. (!) But, you can also NFS mount //3/usr/local as /usr/local on all machines and stuff, so it's not really segmented. With QNX, not only can you access the filesystems of the other machines in this way, but you can also access other processors and shared memory! QNX was designed from the ground-up to support clustering and all that stuff that's just becoming sexy now.
Ya know, it would help if people did simple google
searches before posting to askSlashdot. But I guess that's asking a little much.
http://www.linuxvirtualserver.org
RedHat also has Piranha, but that's (IMO) a cheap
hack made to meet a deadline.
Well, even though this story was posted before, it's still a really cool project. I saw their presentation at the Ottawa Linux Symposium, and it's way cool. The page posted on the main page is ABANDONNED and you should look at the project here: www.rt-control.com They've got a lot of new cool stuff going on that's not mentionned on the dead page.
http://www.cs.brown.edu/system/software/mix/faq.ht ml
It's an old mirror, so it's still got the free version. And, I found this on the first page of a simple google search, I didn't have to post an Ask-Slashdot!
You should still use VNC, too, so you can migrate their GUI use, not just their app use.
Could it have possibly ended up better for RedHat? The people with large amounts of money to invest are not OSS writers. They're professional money people. What better way to boost the interest in your IPO than to generate a frenzy like this? It's starting to hit all sorts of media, and by the time this stock hits the market, EVERY SINGLE trader will KNOW that everyone that knows anything about the internals of this company wants in on the deal.
/. community to publicize their IPO. People couldn't get in on this, so they're going around to every media outlet they can find, telling them how great this IPO is going to be, and that they can't get in. It couldn't be better planned.
The stock will, of course, shoot straight up. Not becuase investors like RedHat, not because they like OSS, but because the people on the "inside" of the company have lots of faith in it. It would be very illegal for RedHat employees to create a frenzy like this during the Pre-IPO quiet period, so RedHat managed to create all sorts of press without breaking those rules. Hats off to them, they're going to be rich.
RedHat is using the
Myself, I did get the EMail. I know where my EMail address was harvested from, it wasn't hard to figure that out. I can't participate because I'm Canadian, though. Even though Canada and the US both signed the NAFTA that makes my exclusion illegal. Oh, well, I'm not going to complain, because that will simply reward RedHat and ETrade for this sham.
The website for this stuff says that you can
connect several (10) iBooks in the same house to
the same ISP through the same bridge. Does that
mean that this "hub" also does IP Masquerading
(aka Network Address Translation) in hardware?
Can you disable that if you want to give the
iBooks real IPs, or what?
I do the exact same thing here at my work, using the latest Samba RPM and the latest netatalk+asun SRPM from the PPC distro (More up to date than any other RPMs I could find). The trick is that you have to change the way the netatalk SRPM tracks its version number, or you won't be able to make an i386 RPM from it. :)
You should also rebuild samba with the --with-netatalk switch (RTFM) so that it can reasonably handle the resource forks for the apple files (.AppleDouble/). Be careful how your Linux and Window~1 machines handle the resource forks.
Lastly, you should take a close look at how each machine handles text files. Windows, Apple and Linux are all different, and if you serve all those OSes from the same file structure, you'll be opening a new can of worms. Netatalk+asun is supposed to handle CR/LF translation, but for some reason I can only get it to translate when downloading from the server, not when uploading to the server. I posted the problem to a couple of netatalk/atalk mailing lists to no avail.
But, we got around the problem by using CVS to handle file sharing - since we share mostly HTML docs, this has proved to be the best way for text files, though we still use NFS/SMBd/AFPd for other stuff.
bash# echo "90 10 9 ^ * 1024 3 ^ / p" | dc
83
bash#
90 billion bytes is 83 gigs, kiddies.
(And reverse Polish is your friend)
I'm a WAVE@HOME cablemodem subscriber right now,
and I can tell you that it's not only about technical support. See, these big companies don't consider the end-user the customer. The end-user is the *product* to sell advertising to.
The system requirements listed on the page aren't the requirements for the network, they're the requirements for the proprietary client software. The CD they send you to install the "network" actually installs their proprietary client (Usually a modified NetScape) and change all your settings. Icons are replaced with their logos, etc. They expect to make their money off advertising on the things they force you to look at.
@HOME recently bought EXCITE. AOL bought Netscape's portal. Yahoo paid IBM a shitload of money to make it the default start page on Aptivas. See where this is going? ADSL subscribers in Ottawa are forced to use a web proxy, and I'm taking bets on how long till they get a proxy that strips out banners and replaces them with home-grown advertising. They're selling the ADSL at such a profit-loss that that's the only way they'll make money in the long run.
End users don't have money - advertisers do. What has to happen is for the government to be pressured by the people in to regulating a difference between connectivity providers and content providers.