I use Starband an sat broadband company in the US, and the parent is mostly right. Starband uses a "accelerator" proxy which helps http traffic greatly. Using this, you click a link in the browser, nothing happens for 1-3 secs and then the page floods down. Takes a little to get used to but very usable. Without the proxy, http is very painful.
Starband also has problems with P2P, CVS, rsync. In general, it is last (only) choice option, but it is better than dialup.
Or you could just use GoboLinux
It stores packages in/Programs/Foo/1.0/
bin
sbin
lib
And so on. There is a set of scripts for managing a/System/Links/* heirarchy and a legacy heirarchy.
I have a Siemens 2line 8 wireless handset + 1 wired baseset (original gigaset). It is almost 5 years old and is starting to show its age (handsets dying unable to find replacements). Other than that it has worked great. It is easy to learn how to use but you're friends will be confused at first.
I am the a founder of a very successful web design firm during the dot-com years. We we're lucky and got out before the bust and we're still comfortable.
We never accepted any VC or private funding. How did we do it. 1. Keep expenses low at first. Work out of the basement/home. 2. Since you have low expenses undercut your competition in order to establish a client base/references/portfolio. 3. Develop a few key strategic partnerships in order to bring in bigger clients. 4. At this point you should be able to raise you expenses. 5. At this point things should be going fairly well if you're competent. Just manage expenses and only increase them in order to grow the business.
Just the same old business theory as the last few centuries. It still works. We didn't follow it during the dot-com years and that's why everything blew up so badly.
They use similar techniques to automate dependency checking during package creation.
They've also rethought the FS heirarchy. This includes breaking/bin,/lib,/usr/* into package subheirarchies. There are then management tools that reconstruct the tree via symlinks.
Big advantage is managing you packages. Even if you've installed from source.
I am probably going to have to help educate my children in math and science and check over the textbooks for errors (there was a/. story in the last 6 months about textbook errors).
Gee, teaching your kids something. Imagine that!!
The problem with education in the US isn't the schools. The problem is parents assuming the public schools will provide 100% of the education a child needs.
That is like assuming social security will provide for 100% of your retirement.
You're missing the point. The post 2-up was wondering about what rights you have though general copyright without using the GPL.
A good example is the package daemontools available from DJB. It is not redistributable. The tarball doesn't contain any LICENSE but does contain a copyright.
Now what can I do with this tarball? The previous poster what wondering if he could modify it as long as he doesn't redistribute the changes. Now logically that sounds reasonable but I don't know.
You can legally buy a gun. You can't legally go and shoot someone with it. You CAN legally take it apart, and make a plant holder out of it. I believe that you CAN'T legally turn a semiautomatic gun into a fully auto.
If your state/county laws enable you to own a fully auto firearm you can turn your AR-15 in a M-16. Same with an AK-47.
It is not converting a gun into full auto that is illegal. OWNING a full auto gun IS illegal.
Even outright ownership doesn't give you full rights of use.
It does until you break other laws with it. DTV is doing the equivalent of suing everyone how purchased a slimjim or a standard lock pick set.
I view it as proof that the markets really don't believe SCO's claims. If investors thought SCO had an actual chance against IBM, Linux related stocks would be hit hard. As is SCOX (or whatever the ticker is) is just being run up by daytraders.
Having said that though, check out the case Frearson v Loe, dated 1878 (google is your friend). I gather (in my naive IANAL way) that it is an often quoted precedent. The case determined that non-commercial experimentation is okay, even in the face of patents. Can writing free software be considered to be an experiment?
Ignoring the patent clause of the GPL.
That could be dangerous. It could be argued that writing/developing Linux/Gnome/etc. can infringe but then can only be used for Non-commercial purposes. As soon as you setup a server for an ecommerce site, the patent is in effect. In order to be legal the end user needs to license the patent. Now this isn't SCO because the concensus is they don't have any applicable patents. They're just waving around the term IP.
Actually, the more I think about it this could be a good thing. Just need a clearinghouse to handle the licensing fees. This would let OSS develop patented technologies without fear.
Another great feature I miss from the Amiga is the virtual screens. Each application could create a window or screen. Each screen had a menubar at the top. If you drag the menubar down it shows the screen behind the current one. You could layer the screen arbitrily(sp) deep.
Extending and modernizing that we could extend our virtual desktops. Imagine a virtual desktop switcher that works like this.
Rather than a AxB grid make it a smooth rectangle. Each virtual desktop is a smaller rectangle within it. You can move around and layer each rectangle. Then there is a wire rectangle which represents the view displayed on the monitor.
With suitable hardware accel. each desktop could be resized
First off, this is not a network shared memory scheme. RDMA could be used to implement one very efficently though.
It will not allow arbitary access to your memory space. In fact, it would prevent a great number of buffer overflow exploits
The best analogy is the difference between PIO and UDMA modes of your IDE devices (or any device). This is all about offloading work from your CPU. It is moving the TCP/IP stack from the kernel to the network card for a very specific protocol.
Here's how RDMA would work layered over (under?) HTTP.
- browser creates GET request in a buffer
- browser tells NIC address of buffer and who to send it to.
- NIC does a DMA transfer to get buffer. OS not involved
- NIC opens RDMA connection to webserver
- server NIC has already been told by the webserver what buffer it should put incoming data
- webserver unblocks once data in buffer and parses it.
- webserver creates HTML page in second buffer.
- webserver tells server NIC to do a RDMA transfer from buffer to browser host
- client NIC takes data and puts it in browser buffer
- browser unblocks parse HTML and displays it.
All of this with minimal interaction with the TCP/IP stack. RDMA just allows you to move a buffer from one machine to another without alot of memory copying in the TCPIP stack.
In fact, the RDMA protocol could be emulated completely in software. It would probably have a small overhead verses current techniques but would still be useful. Just imagine real RDMA on the server and emulated RDMA on the clients (cheaper NIC). The server has less overhead and most clients have cycles to spare!
So your saying that an ultra proprietary solution that is locked into one os is better than a solution that is actually cross platform, performs reasonably well compared to competition in the SAME market, and is relatively open and free comparatively?
You might want to check the backside of your pants...I think your head is in there somewhere.
But what are the actual technical differences? The Duron and Athlon had different size caches. Is that how they're gonna differentiat them? How about the CPU interconnects?
Re:32 compatibility mode vs. true 64 bit apps...
on
AMD Opteron Due In April
·
· Score: 2, Informative
You will probably need a 32bit glibc. 32bit code runs in a different processor mode (think the V86 mode used in dosemu)
Slashdot Mirror
I use Starband an sat broadband company in the US, and the parent is mostly right. Starband uses a "accelerator" proxy which helps http traffic greatly. Using this, you click a link in the browser, nothing happens for 1-3 secs and then the page floods down. Takes a little to get used to but very usable. Without the proxy, http is very painful.
Starband also has problems with P2P, CVS, rsync. In general, it is last (only) choice option, but it is better than dialup.
I have this right now using GoboLinux using symlinks. Works extremely well.
Or you could just use GoboLinux It stores packages in /Programs/Foo/1.0/
bin
sbin
lib
And so on. There is a set of scripts for managing a /System/Links/* heirarchy and a legacy heirarchy.
I have a Siemens 2line 8 wireless handset + 1 wired baseset (original gigaset). It is almost 5 years old and is starting to show its age (handsets dying unable to find replacements). Other than that it has worked great. It is easy to learn how to use but you're friends will be confused at first.
So, I've make millions writing software that runs on Linux. In fact, without linux my company would have folded very early on.
If you want to make money, which is better Windows or Linux. Very difficult question. The fact is, it really doesn't matter.
I am the a founder of a very successful web design firm during the dot-com years. We we're lucky and got out before the bust and we're still comfortable.
We never accepted any VC or private funding. How did we do it.
1. Keep expenses low at first. Work out of the basement/home.
2. Since you have low expenses undercut your competition in order to establish a client base/references/portfolio.
3. Develop a few key strategic partnerships in order to bring in bigger clients.
4. At this point you should be able to raise you expenses.
5. At this point things should be going fairly well if you're competent. Just manage expenses and only increase them in order to grow the business.
Just the same old business theory as the last few centuries. It still works. We didn't follow it during the dot-com years and that's why everything blew up so badly.
>Last I knew a nipple was, by default,
/. is full of virgins.
>an ouput device
And people wonder why
Take a look at http://www.gobolinux.org/
/bin, /lib, /usr/* into package subheirarchies. There are then management tools that reconstruct the tree via symlinks.
They use similar techniques to automate dependency checking during package creation.
They've also rethought the FS heirarchy. This includes breaking
Big advantage is managing you packages. Even if you've installed from source.
I also seem to remember a PowerPC port for NT. Either 3.5 or 5.
I have to agree. The Sanford Uni-ball has been my favorite for 15 years. Just bought a box of 12 for $7.99 so they're cheap too.
And in 20-30 years when all the baby boomers are gone, the medical industry is going to see a bubble burst not seen since the dot.com bubble.
The problem with education in the US isn't the schools. The problem is parents assuming the public schools will provide 100% of the education a child needs.
That is like assuming social security will provide for 100% of your retirement.
You're missing the point. The post 2-up was wondering about what rights you have though general copyright without using the GPL.
A good example is the package daemontools available from DJB. It is not redistributable. The tarball doesn't contain any LICENSE but does contain a copyright.
Now what can I do with this tarball? The previous poster what wondering if he could modify it as long as he doesn't redistribute the changes. Now logically that sounds reasonable but I don't know.
If your state/county laws enable you to own a fully auto firearm you can turn your AR-15 in a M-16. Same with an AK-47.
It is not converting a gun into full auto that is illegal. OWNING a full auto gun IS illegal.
It does until you break other laws with it. DTV is doing the equivalent of suing everyone how purchased a slimjim or a standard lock pick set.
Not really.
/.'ers.
I view it as proof that the markets really don't believe SCO's claims. If investors thought SCO had an actual chance against IBM, Linux related stocks would be hit hard. As is SCOX (or whatever the ticker is) is just being run up by daytraders.
A good number of them are probably
Ignoring the patent clause of the GPL.
That could be dangerous. It could be argued that writing/developing Linux/Gnome/etc. can infringe but then can only be used for Non-commercial purposes. As soon as you setup a server for an ecommerce site, the patent is in effect. In order to be legal the end user needs to license the patent. Now this isn't SCO because the concensus is they don't have any applicable patents. They're just waving around the term IP.
Actually, the more I think about it this could be a good thing. Just need a clearinghouse to handle the licensing fees. This would let OSS develop patented technologies without fear.
Remember we're talking about the embeded space not servers. This means the target audience is Electrical Engineers not "Software Engineers".
They're generally not as Windows-centric as IT. They WILL frequent LinuxDevices.com. And they will share the rebuttal with their PHB.
Another great feature I miss from the Amiga is the virtual screens. Each application could create a window or screen. Each screen had a menubar at the top. If you drag the menubar down it shows the screen behind the current one. You could layer the screen arbitrily(sp) deep.
Extending and modernizing that we could extend our virtual desktops. Imagine a virtual desktop switcher that works like this.
Rather than a AxB grid make it a smooth rectangle. Each virtual desktop is a smaller rectangle within it. You can move around and layer each rectangle. Then there is a wire rectangle which represents the view displayed on the monitor.
With suitable hardware accel. each desktop could be resized
Does this patent apply only to online rental stores or does it apply to brick and mortar stores too?
> I'd be looking for replacement products.
You mean Windows? SCO claim all Unixes. What is the current state of plan9?
First off, this is not a network shared memory scheme. RDMA could be used to implement one very efficently though.
It will not allow arbitary access to your memory space. In fact, it would prevent a great number of buffer overflow exploits
The best analogy is the difference between PIO and UDMA modes of your IDE devices (or any device). This is all about offloading work from your CPU. It is moving the TCP/IP stack from the kernel to the network card for a very specific protocol.
Here's how RDMA would work layered over (under?) HTTP.
- browser creates GET request in a buffer
- browser tells NIC address of buffer and who to send it to.
- NIC does a DMA transfer to get buffer. OS not involved
- NIC opens RDMA connection to webserver
- server NIC has already been told by the webserver what buffer it should put incoming data
- webserver unblocks once data in buffer and parses it.
- webserver creates HTML page in second buffer.
- webserver tells server NIC to do a RDMA transfer from buffer to browser host
- client NIC takes data and puts it in browser buffer
- browser unblocks parse HTML and displays it.
All of this with minimal interaction with the TCP/IP stack. RDMA just allows you to move a buffer from one machine to another without alot of memory copying in the TCPIP stack.
In fact, the RDMA protocol could be emulated completely in software. It would probably have a small overhead verses current techniques but would still be useful. Just imagine real RDMA on the server and emulated RDMA on the clients (cheaper NIC). The server has less overhead and most clients have cycles to spare!
But what are the actual technical differences? The Duron and Athlon had different size caches. Is that how they're gonna differentiat them? How about the CPU interconnects?
You will probably need a 32bit glibc. 32bit code runs in a different processor mode (think the V86 mode used in dosemu)
There was another project in C64 Magazine that did the same thing. Used it until I got my Amiga with a newtek capture.