Don't forget this stuff is taught in the same classes where people learn that Internic assigns IP addresses, and that Classful divisions of the IPv4 addressing space are actually still meaningful.:P to Cisco and Microsoft for teaching this garbage to the people that they hope will run networks.
Not quite as high in specs, but it's less than half the price. I have a c860 with a 1 gb SD card and I've not had much desire for a laptop since getting it. My main portable use is just e-mail, web and wireless network auditing, so the little c860 with pdaXrom works fine for me.
Entrants must be residents of the UK, Ireland, France, Germany, Spain, Italy, the Netherlands, Denmark, Finland, Norway, Sweden, Belgium, Switzerland, Austria, Portugal or Greece and aged 18 or over. Winners may be required to provide proof of age and address.
Except that neither one of those companies operates in BC do they? Bell Canada is Ontario/Quebec, and Rogers traded BC to Shaw for parts of Ontario and the East Coast a couple years back.
No, they recommend Dual Opterons in that specific config if you want to get the VERY BEST performance from it.
That setup encodes HDTV in realtime! most of us don't need realtime HDTV encoding to MPEG 4 you only need that if you also have an HDV camcorder....and no patience.
What does Gentoo have to do with it? Nano is a GNU product coded by a Debian user....from the Nano FAQ:
1.4. What is the history behind nano?
Funny you should ask!
In the beginning...
For years Pine was THE program used to read email on a Unix system. The Pico text editor is the portion of the program one would use to compose his or her mail messages. Many beginners to Unix flocked to Pico and Pine because of their well organized, easy to use interfaces. With the proliferation of GNU/Linux in the mid to late 90's, many University students became intimately familiar with the strengths (and weaknesses) of Pine and Pico.
Then came Debian...
The Debian GNU/Linux distribution, known for its strict standards in distributing truly "free" software (i.e. software with no restrictions on redistribution), would not include a binary package for Pine or Pico. Many people had a serious dilemma: they loved these programs, but they were not truly free software in the GNU sense of the word.
The event...
It was in late 1999 when Chris Allegretta (our hero) was yet again complaining to himself about the less-than-perfect license Pico was distributed under, the 1000 makefiles that came with it and how just a few small improvements could make it the Best Editor in the World (TM). Having been a convert from Slackware to Debian, he missed having a simple binary package that included Pine and Pico, and had grown tired of downloading them himself.
Finally something snapped inside and Chris coded and hacked like a madman for many hours straight one weekend to make a (barely usable) Pico clone, at the time called TIP (Tip Isn't Pico). The program could not be invoked without a filename, could not save files, had no help menu, spell checker, and so forth. But over time it improved, and with the help of a few great coders it matured to the (hopefully) stable state it is today.
In February 2001, nano was declared an official GNU program by Richard Stallman. Nano also reached its first production release on March 22, 2001.
If so you ought to be ashamed. C'mon, look at the picture of the chip with the lenses on it, the cheesy stickers on the CF cards, the cut and paste screenshots, the video of the solar optical chip (mirror) if none of that bothers you e-mail me and we'll talk real estate. (On second thought, don't. I don't want to have to explain what a swamp is...)
I mean really does anyone think for a second that Quantum would put up with another company trying to trademark the word Quantum in reference to storage devices? or are they supposed to be involved and for some reason they think letting these guys break it to the press is the best way to go?
Re:"Always trust code from Microsoft"
on
Do You Code Sign?
·
· Score: 1
That's strange, because I had a hell of a time getting web site certificates from both Verisign and Thawte (a verisign subsidiary) because we are a municipal government in Canada, so more manual checking was required because we don't have a business licence number for them to look up. (we issue business licences for certain types of businesses, but we aren't a business in that sense ourselves. They DID call and they had us fax documents to them to prove we at least have access to things like the town charter... I thought their proceedures in our case were very thorough.
By the same token the other big SciFi myth of the 80's...the acid spitting alien that creates an acid that can burn through anything in seconds doesn't work either... how does the alien survive if it's acid burns trough anything (including aliens of the same species)?
The lasers use mirrors. The mirrors in the laser have to be able to withstand the energy of the laser. Therefore there IS a mirror that can reflect the laser without absorbing enough of it to do damage.
With a laser guidance system you still get some data if your light is reflected away vs reflected back at you (something is there to reflect it) if the laser is the weapon and it's reflected off at some arbitary angle rather than being absorbed so it can do it's damage it simply goes until it hits something else that will absorb the energy.
Hence it becomes a battle of "he who has the shiniest armour wins".
Laser weapons are a really bad idea. All you need to do to defend against them is make your stuff out of something that reflects the laser's wavelength.
Are we going to see a new era of laser weapons, mirror shields and dead civilians caught by reflections?
Winamp doesn't NEED to be run as Admin, you just need to give your user Full Access rights to Winamp's directory.
Point is you shouldn't have to, the user should only have to have read + execute permissions for winamp, and winamp should store any playlists etc in the user's "My Documents" where it can safely assume that user has write permissions. It's not the fault of the ACL system that that isn't so, it's the fault of Nullsoft (and windows programmers in general) that things like this happen in windows.
Some people have some guts, calling Windows ACL better than unixy permissions, when the later stops wiruses, which the former still can't do today. So much for the better system.
Now I'm no Windows supporter, but the ACL system is not to blame for viruses, the defaults that MS has forced on us contribute to virus spread, and unfortunately many of the defaults can't be fixed because other parts of the OS and end user programs rely on certain pemissions being granted on certain areas of the filesystem, but were it not for stubborn programs there's no reason ACLs could not be used to limit access effectively.
I hate, for example that Winamp 2.x requires auper user/admin privledges to operate properly, but that's not to be blamed on the file system, or the permissions system, but on Winamp.
I like the graininess of windows ACLs, and I think it would be nice to have a more grainy standard for unixy OSes, but history has given us the user-group-world model and it could be a while before something else is agreed upon.
If you don't think you can get any better than DVD quality you probably can't on your current set. That's why you'll be needing a new Sony HDTV so you can see all the benefits that Blue ray brings, and to really appreciate the difference you'll need it to be at least 52".
Considering how Google has a volume of 7.3 million shares and Microsoft 138 million shares, I would say you are comparing apples and oranges by strictly looking at stock price.
Ok, Here is what really needs to be done, and a linux distor that supported this would have the ease of apt and the ease of.app both rolled into one.
1. The package manager (be it apt/dpkg or rpm, or ipk... whatever... doesn't matter) has to understand a new package type the.app package (this could be done through a seperate program, but it's best that the core package manager handles this.
2. the Gui (be it KDE, Gnome, etc) has to recognize that folders with a.app extension need to be treated differently and that there should be a script inside to tell it what to do with it. (the script will hold MIME data, icon and executable locations within the folder)
When a GUI displays a.app folder it displays the icon in it not the folder icon.
When a.app is clicked it doesn't open the folder, instead it runs the autorun script which aadjusts MIME data if necessary, adjusts the default PATH envronment variable, tells the package manager that you have foo installed and what the path to it is, then launches the program.
When you move the.app to a new location it will automatically adjust the next time the application is clicked, and re-set any ncessary MIME data, PATHs, and Package info in the package manager's datadase.
The other part the gui is responsible for is trash. When a.app is dragged to the trash the gui has to recognize that it is a.app and undo those settings.
It could be done fairly trivially. Then any desktop Linux system that supported the.app package type could use any.app product, whether it is bought in a shrinkwrapped package, or downloaded.
The package manager would be responsible for updating the.app programs the same way it updates.rpm or.deb from it's repository. It could also install them automatically the same as it does now....and like apple's.app linux.app folders could have multiple executables for different hardware platforms, so you could support as many CPU architectures as the developer wanted.
Of course this means extra bloat, and some wasted disk space with duplication of libraries, but disk is cheap now and the ease of use more than makes up for that sacrifice.
There is no reason why server based distros would have to convert, it's only an ease of use thing for desktop software. The rule of thumb ought to be if it relys on X it should be in an app package.
I don't think it is all that hard to implement a system like this, but it would take co-operation between KDE, Gnome and all the package management teams to come up with a standard and individually implement their part of it.
Again, you really need to spend some time with a Mac to see what I mean. The.app folder isn't the directory where the applications go it is the application package, like a.rpm..but it's really a folder. to the user it looks like an executable, to the system it's the directory where the executable and all supporting libraries that are not a part of the core operating system live.
For example if I download foo.app and put it on my desktop I can click foo.app and foo opens , but at the shell level if I cd INTO foo.app I see bin, lib, etc and various other things with files needed for foo to run.
When foo.app is dragged to the trash (deleted) it removes the program foo and all related config because you are really deleteing the install directory of foo.
clicking on foo.app runs a script that chacks if foo has been previously run, and if not sets up mime types and such to tell the OS what kind of documents foo can open. when you trash foo.app a second script runs to clean that up.
It is doable in Linux, but the package manager and the desktop software have to talk to eachother.
I don't think you really understand, or perhaps I don't understand, because I don't see how pacman is different from any other package manager
The thing with.app application folders is they are self contained, and can be dragged around to anywhere you want, delete the program just by dragging it to the trash...
But on top of that you can also update through a linux like package manager. (although apple only uses that feature to update apple software, but there is nothing stopping them from adding all kinds of software to the repository.
Sure you can manually download a.rpm or a.deb package today, and even though it is not in the official repository you can install it, but dependancies can still be a problem if that manually downloaded program is meant for a different distro, and it's nowhere near as easy and intuitive as.app
The place where package repositories break down is when you want something that isn't in your distro's repository.
In order for it to just work like on a Mac there needs to be a bit of an overhaul in the way packages are handled.
I don't want to come off soundling like a Mac freak, but I think that the way for Linux shareware to work is for Linux systems to adopt something akin to the Mac's.app packaging.
I'm a big fan of apt for servers but it just doesn't work well for this particular model..app packaging does.
And it's at least $150 more valuable if it has Windows XP embedded to run IE vs if it has Linux to run Firefox alongside it's VNC/Citrix/remote desktop client.
Slashdot Mirror
Don't forget this stuff is taught in the same classes where people learn that Internic assigns IP addresses, and that Classful divisions of the IPv4 addressing space are actually still meaningful. :P to Cisco and Microsoft for teaching this garbage to the people that they hope will run networks.
If linux is your thing try one of
these
Not quite as high in specs, but it's less than half the price.
I have a c860 with a 1 gb SD card and I've not had much desire for a laptop since getting it.
My main portable use is just e-mail, web and wireless network auditing, so the little c860 with pdaXrom works fine for me.
Entrants must be residents of the UK, Ireland, France, Germany, Spain, Italy, the Netherlands, Denmark, Finland, Norway, Sweden, Belgium, Switzerland, Austria, Portugal or Greece and aged 18 or over. Winners may be required to provide proof of age and address.
Except that neither one of those companies operates in BC do they? Bell Canada is Ontario/Quebec, and Rogers traded BC to Shaw for parts of Ontario and the East Coast a couple years back.
No, they recommend Dual Opterons in that specific config if you want to get the VERY BEST performance from it.
...and no patience.
That setup encodes HDTV in realtime! most of us don't need realtime HDTV encoding to MPEG 4 you only need that if you also have an HDV camcorder.
What does Gentoo have to do with it? ...from the Nano FAQ:
Nano is a GNU product coded by a Debian user.
1.4. What is the history behind nano?
Funny you should ask!
In the beginning...
For years Pine was THE program used to read email on a Unix system. The Pico text editor is the portion of the program one would use to compose his or her mail messages. Many beginners to Unix flocked to Pico and Pine because of their well organized, easy to use interfaces. With the proliferation of GNU/Linux in the mid to late 90's, many University students became intimately familiar with the strengths (and weaknesses) of Pine and Pico.
Then came Debian...
The Debian GNU/Linux distribution, known for its strict standards in distributing truly "free" software (i.e. software with no restrictions on redistribution), would not include a binary package for Pine or Pico. Many people had a serious dilemma: they loved these programs, but they were not truly free software in the GNU sense of the word.
The event...
It was in late 1999 when Chris Allegretta (our hero) was yet again complaining to himself about the less-than-perfect license Pico was distributed under, the 1000 makefiles that came with it and how just a few small improvements could make it the Best Editor in the World (TM). Having been a convert from Slackware to Debian, he missed having a simple binary package that included Pine and Pico, and had grown tired of downloading them himself.
Finally something snapped inside and Chris coded and hacked like a madman for many hours straight one weekend to make a (barely usable) Pico clone, at the time called TIP (Tip Isn't Pico). The program could not be invoked without a filename, could not save files, had no help menu, spell checker, and so forth. But over time it improved, and with the help of a few great coders it matured to the (hopefully) stable state it is today.
In February 2001, nano was declared an official GNU program by Richard Stallman. Nano also reached its first production release on March 22, 2001.
Cuz, it looks like people are getting fooled.
...even for a second? anyone?
Are they really?
Who here was fooled
If so you ought to be ashamed. C'mon, look at the picture of the chip with the lenses on it, the cheesy stickers on the CF cards, the cut and paste screenshots, the video of the solar optical chip (mirror) if none of that bothers you e-mail me and we'll talk real estate. (On second thought, don't. I don't want to have to explain what a swamp is...)
I mean really does anyone think for a second that Quantum would put up with another company trying to trademark the word Quantum in reference to storage devices? or are they supposed to be involved and for some reason they think letting these guys break it to the press is the best way to go?
That's strange, because I had a hell of a time getting web site certificates from both Verisign and Thawte (a verisign subsidiary) because we are a municipal government in Canada, so more manual checking was required because we don't have a business licence number for them to look up. (we issue business licences for certain types of businesses, but we aren't a business in that sense ourselves. They DID call and they had us fax documents to them to prove we at least have access to things like the town charter... I thought their proceedures in our case were very thorough.
By the same token the other big SciFi myth of the 80's ...the acid spitting alien that creates an acid that can burn through anything in seconds doesn't work either... how does the alien survive if it's acid burns trough anything (including aliens of the same species)?
The lasers use mirrors. The mirrors in the laser have to be able to withstand the energy of the laser. Therefore there IS a mirror that can reflect the laser without absorbing enough of it to do damage.
With a laser guidance system you still get some data if your light is reflected away vs reflected back at you (something is there to reflect it) if the laser is the weapon and it's reflected off at some arbitary angle rather than being absorbed so it can do it's damage it simply goes until it hits something else that will absorb the energy.
Hence it becomes a battle of "he who has the shiniest armour wins".
I was just going to say the same thing.
Laser weapons are a really bad idea.
All you need to do to defend against them is make your stuff out of something that reflects the laser's wavelength.
Are we going to see a new era of laser weapons, mirror shields and dead civilians caught by reflections?
Winamp doesn't NEED to be run as Admin, you just need to give your user Full Access rights to Winamp's directory.
Point is you shouldn't have to, the user should only have to have read + execute permissions for winamp, and winamp should store any playlists etc in the user's "My Documents" where it can safely assume that user has write permissions. It's not the fault of the ACL system that that isn't so, it's the fault of Nullsoft (and windows programmers in general) that things like this happen in windows.
Some people have some guts, calling Windows ACL better than unixy permissions, when the later stops wiruses, which the former still can't do today. So much for the better system.
Now I'm no Windows supporter, but the ACL system is not to blame for viruses, the defaults that MS has forced on us contribute to virus spread, and unfortunately many of the defaults can't be fixed because other parts of the OS and end user programs rely on certain pemissions being granted on certain areas of the filesystem, but were it not for stubborn programs there's no reason ACLs could not be used to limit access effectively.
I hate, for example that Winamp 2.x requires auper user/admin privledges to operate properly, but that's not to be blamed on the file system, or the permissions system, but on Winamp.
I like the graininess of windows ACLs, and I think it would be nice to have a more grainy standard for unixy OSes, but history has given us the user-group-world model and it could be a while before something else is agreed upon.
xcacls is STILL a seperate download. Why can this functionality not be included as a standarad part of the windows operating system?
It's only a 45kb binary for cryin' out loud. who doesn't have 45kb of free space on thier HDD?
If you don't think you can get any better than DVD quality you probably can't on your current set. That's why you'll be needing a new Sony HDTV so you can see all the benefits that Blue ray brings, and to really appreciate the difference you'll need it to be at least 52".
Thanks for your money, have a nice day.
Considering how Google has a volume of 7.3 million shares and Microsoft 138 million shares, I would say you are comparing apples and oranges by strictly looking at stock price.
...is kind of amusing.
On the other hand...
GOOG +7.58
MSFT +0.89
You mean something like this
Ok, Here is what really needs to be done, and a linux distor that supported this would have the ease of apt and the ease of .app both rolled into one.
.app package (this could be done through a seperate program, but it's best that the core package manager handles this.
.app extension need to be treated differently and that there should be a script inside to tell it what to do with it.
.app folder it displays the icon in it not the folder icon.
.app is clicked it doesn't open the folder, instead it runs the autorun script which aadjusts MIME data if necessary, adjusts the default PATH envronment variable, tells the package manager that you have foo installed and what the path to it is, then launches the program.
.app to a new location it will automatically adjust the next time the application is clicked, and re-set any ncessary MIME data, PATHs, and Package info in the package manager's datadase.
.app is dragged to the trash the gui has to recognize that it is a .app and undo those settings.
.app package type could use any .app product, whether it is bought in a shrinkwrapped package, or downloaded.
.app programs the same way it updates .rpm or .deb from it's repository. It could also install them automatically the same as it does now. ...and like apple's .app linux .app folders could have multiple executables for different hardware platforms, so you could support as many CPU architectures as the developer wanted.
1. The package manager (be it apt/dpkg or rpm, or ipk... whatever... doesn't matter) has to understand a new package type the
2. the Gui (be it KDE, Gnome, etc) has to recognize that folders with a
(the script will hold MIME data, icon and executable locations within the folder)
When a GUI displays a
When a
When you move the
The other part the gui is responsible for is trash. When a
It could be done fairly trivially. Then any desktop Linux system that supported the
The package manager would be responsible for updating the
Of course this means extra bloat, and some wasted disk space with duplication of libraries, but disk is cheap now and the ease of use more than makes up for that sacrifice.
There is no reason why server based distros would have to convert, it's only an ease of use thing for desktop software. The rule of thumb ought to be if it relys on X it should be in an app package.
I don't think it is all that hard to implement a system like this, but it would take co-operation between KDE, Gnome and all the package management teams to come up with a standard and individually implement their part of it.
Again, you really need to spend some time with a Mac to see what I mean. The .app folder isn't the directory where the applications go it is the application package, like a .rpm ..but it's really a folder. to the user it looks like an executable, to the system it's the directory where the executable and all supporting libraries that are not a part of the core operating system live.
For example if I download foo.app and put it on my desktop I can click foo.app and foo opens , but at the shell level if I cd INTO foo.app I see bin, lib, etc and various other things with files needed for foo to run.
When foo.app is dragged to the trash (deleted) it removes the program foo and all related config because you are really deleteing the install directory of foo.
clicking on foo.app runs a script that chacks if foo has been previously run, and if not sets up mime types and such to tell the OS what kind of documents foo can open. when you trash foo.app a second script runs to clean that up.
It is doable in Linux, but the package manager and the desktop software have to talk to eachother.
I don't think you really understand, or perhaps I don't understand, because I don't see how pacman is different from any other package manager
.app application folders is they are self contained, and can be dragged around to anywhere you want, delete the program just by dragging it to the trash...
.rpm or a .deb package today, and even though it is not in the official repository you can install it, but dependancies can still be a problem if that manually downloaded program is meant for a different distro, and it's nowhere near as easy and intuitive as .app
The thing with
But on top of that you can also update through a linux like package manager. (although apple only uses that feature to update apple software, but there is nothing stopping them from adding all kinds of software to the repository.
Sure you can manually download a
The place where package repositories break down is when you want something that isn't in your distro's repository.
In order for it to just work like on a Mac there needs to be a bit of an overhaul in the way packages are handled.
I don't want to come off soundling like a Mac freak, but I think that the way for Linux shareware to work is for Linux systems to adopt something akin to the Mac's .app packaging.
.app packaging does.
I'm a big fan of apt for servers but it just doesn't work well for this particular model.
Why is this filed under Hardware?
And it's at least $150 more valuable if it has Windows XP embedded to run IE vs if it has Linux to run Firefox alongside it's VNC/Citrix/remote desktop client.
Does anyone have an idea when the macMinis are coming out with x86 chips..
i'm just wondering how they cool those puppies..
They will use Laptop chips so cooling will be less of an issue.