You're probably spoiled by the package manager. Ports are neat, but apt is a dream. At the very least you'll have to get used to a different way of doing things. If you use a lot of custom repositories (e.g. rarewares) you might encounter a few headaches getting all the software you want. There are some things, like 'apt-cache search' that it's not immediately obvious how to do on ports. I think you're just supposed to string together 'find' and 'grep' commands, since ports is just a tree full of text files. # cd/usr/ports # make quicksearch name=whatever
Re:Wrong marketing did them in, clock *does* matte
on
Is AMD Dead Yet?
·
· Score: 1
"That number, generated by marketroids, is absolutely meaningless, but it was meant to imply that this chip was more powerful than an Intel 2200 MHz chip"
No, the XXXX+ numbers were to show the performance of that CPU relative to a 1 GHz AthlonXP (originally a 1 GHz Athlon), if the performance of the AthlonXP was linear. ie, if there was a 2200 MHz AthlonXP, then the Athlon64 2200+ would have the same performance, while only running at 1800 MHz.
The AMD numbers were always relative to themselves. It was all the tabloids (er, I mean computer rags) that confused them with "this compares to an Intel chip running at 2200 MHz".
The only time that "Performance Rating" numbers were relative to Intel was back in the 586/Pentium days, when IBM, Cyrix, and company tried to show their 586-class CPUs were as fast as the Pentium, PentiumPro, and P2.
Re:It is all about the platform.
on
Is AMD Dead Yet?
·
· Score: 1
You have that backwards. Intel is very fond of requiring new chipsets and/or new sockets for each revision of their CPUs: PPro -> P2, new chipset, new slot, new motherboard P2 -> P3, new chipset, new socket, new motherboard P3 -> P4, new chipset, new socket, new motherboard several revisions of the P4 required new chipsets, new sockets, and new motherboards P4 -> Core, new chipset, new socket, new motherboard Core -> Core2, new chipset, new socket, new motherboard several revisions of the Core2 chipsets require new chipsets, new sockets, and new motherboards
Several chip revisions with Intel have also required new RAM (RIMM, DIMM, FB-DIMM, DDR1, DDR2, etc)
Socket 754 allowed for Duron, Sempron, Athlon CPUs Socket 939 allowed for Sempron, Athlon, AthlonMP, AthlonXP, Athlon64, Athlon64 X2 Socket 940 allowed for Athlon64, Opteron Socket AM2 allowed for Athlon64, Athlon64 X2, Opteron Socket AM2+ is the bastard child
So long as you don't continuously run the bleeding-edge, you could upgrade your AMD system with newer CPUs and more RAM. And you could transfer your RAM from system to system if you replaced the motherboard.
AMD has been the more upgrade-as-you-go friendly. Intel has been the replace-everything-when-you-swap-CPUs group.
Re:It is all about the platform.
on
Is AMD Dead Yet?
·
· Score: 1
Not true. The original AMD 8000-series of chipsets for Opteron systems were rock solid. It wasn't until they discontinued these and started to rely on third-parties for their chipsets that things went downhill. Tyan motherboards based around the 8000-series chipsets may not have been the fastest, but they were super-stable. We still have some original Thunder K8SD motherboards running here, almost 5 years later.
Except that compared to Zimbra, Citadel, Scalix, eGroupware, OpenGroupware, and even Kolab are crap. None of them have as nice of a webmail setup, nor as nice Outlook/Evolution/Kontact connectors, nor as nice of PDA setups (especially when it comes to Blackberries and over-the-air-sync).
When it comes to Exchange alternatives, there's really only Zimbra and FirstClass. And FirstClass is just a pile of junk that should never be considered for anything.
The greatest thing MS will get from buying Yahoo! will be to kill Zimbra.
What's worse are the people who send you an e-mail, and then call to see if you received it!! If you were going to call, why'd you send the e-mail??? Or who call to find out why you haven't replied yet, even though they only sent it 3 minutes ago.
Or the people who send an e-mail, expect it to be received within 10 seconds, and complain when time-critical issues are not received right away. Don't use an asynchronous, mostly-reliable, non-realtime medium for synchronous, reliable, realtime duties!!
Example: I have memberships on a lot of sites, like here. I can't remember all my passwords. I could keep them cleartext in a spreadsheet, or someone could allow me a means of storing them in my personal DB that a keyring app could hook up to (or me directly, from the mysql prompt, if I have the knowledge to do so and so choose).
It's called the KDE Wallet.:) It stores usernames and passwords for anything that requires it, whether it be local apps, remote apps, websites, or whatnot. There's even a mini-text editor in there to keep free-form text if you want. You can even have separate wallets for online vs. local info. And it's accessible to any and all KDE apps.
Each wallet is protected by a separate password (or you can configure the manager to use a single master password), and the contents are stored encrypted on disk.
Now, if only someone would port this to Windows, and Mac, and add hooks for non-KDE apps to access it.
Depends on how high-level you need to go on the CAD chart. There are several open-source CAD programs out there. The two that I know of are QCad (2D) and Cycas 3D. We use both of these in our tech ed. courses in the local school district. We stopped paying for AutoCAD back in the Windows 3.1 days... sticking it out with ancient 486es and Pentiums runnning the 16-bit version of AutoCAD. About 5 years ago, we migrated two labs to QCad on Windows 98, then to QCAD and Cycus on Debian Linux.
These work fine for educational uses, not sure about professional use, though, as that's not my area.
Your issue is probably more about the differences between POP3 and IMAP message storage/retrieval.
When people here "e-mail client" they tend to think of POP3, where the client connects to the mail server, downloads the messages to the local computer, and then makes them available from that computer only.
When people think "webmail" they tend to think about having all their messages stored on some remote server, accessible via any computer with an Internet connection and a web browser.
Well, if you use an IMAP server, you get the best of both: a local client optimised for messaging duties, and messages stored on a remote server accessible from any computer with an Internet connection and an IMAP client (which can be webmail clients).
POP3 is pretty much dead and useless, or should be killed off at any rate.:) Store all your messages on an IMAP server. Access them from anywhere with any IMAP client. If you need offline access to your messages, then use an IMAP client with "offline" or "disconnected IMAP" support. Then it keeps your local copy in sync with the server message store.
It was only DOS and MacOS which couldn't cope well unless you had an expensive hard drive.
MS-DOS, PC-DOS, and DR-DOS all ran beautifully without harddrives. Our first computer was an IBM clone with 2 5.25" floppy bays and a whopping 512 KB of RAM. We ran MS-DOS 3.1, and 5.0 on there for several years. Worked just fine.
It was Windows that couldn't handle not having local storage. DOS ran just fine with just removable (floppy-based) storage.
E-mail isn't "dying" or "becoming obsolete". IM, SMS, etc are not replacing e-mail. They server different purposes.
Back in the pre-computer days, if you needed to reach someone right away to chat about whatever, you picked up the phone. Instant, synchronous, real-time communication.
If you just wanted to update someone on your life and didn't need an instant reply, then you sat down, wrote a letter and mailed it to them. Eventually they'd receive it, read it, and send a reply back. More in-depth, and asynchronous.
And so it is with digital communications. If you need to reach someone right away, then you send them an IM or SMS. Instant, synchronous, pretty much real-time communication. Or, if you don't really want a reply, but just want to update people on what you are doing, then you update your online profile (wherever that might be).
If you don't need an instant reply, or you have more to say than will fit in 80 characters, then you sit down, write an e-mail, and send it to them. Eventually they receive it, read, and reply. Asynchronous communication.
Sometimes one method works better than the other. One is not replacing the other. They server different purposes, have different uses, and are used at different times.
It's not like this is a new thing, either. Different age groups use different modes of communications.
And, how is this different from putting up an open access point?
If you want a private network, then you can put WEP/WPA and a password on the connection. You can add VPN software. You can use MAC filtering. You can use IP filtering. Etc.
It's the same thing with web servers, with mail servers, etc.
There's nothing inherently private or public with these things. What you do with them after installation is what matters.
No, I'm putting up a web server so that I can access my files remotely. I'm not advertising it, I'm not posting it on a bulletin board. I'm just putting up a web server. That does not automatically make it private. Nor does that automatically make it public. It just makes it available to access.
Why would putting a server up on port 80 be considered public anymore than putting up a wireless access point? I don't see how having a web server is "implied public". Just because I put it there doesn't mean I want everyone to access it. That's a poor example to use.
First of all, it's called the page file, not the swap file. This isn't Unix and this isn't Windows 3.x. If you're going to pretend to know something about this aspect of Windows, you'd do well to at least use the correct name.
What's in a name? The function is the same. That's like complaining about someone calling your Ferrari a car. Oooh, how nasty of them!
Second, and far more importantly -- You do not get fragmentation in the page file unless the page file is resized, and the only time the page file gets resized is when you consume ALL your physical memory, and ALL the memory in the page file. On a system with 1 GB of memory (which will be given a 1.5GB page file), you will have 2.5 GB of memory that you have to fill up first. Windows XP & later will display a pop-up balloon when this happen.
Fragmentation NEVER HAPPENS OTHERWISE. Why is this such a major concern to you?
Yes, it does happen. The default size of the page file is not 1.5x RAM. It usually starts at 768 MB and then grows over time. For fun, you can run the defrag program in XP and check the stats output to see how many fragments there are to the page file. I've seen some systems with dozens of fragments in a 768 MB page file.
All the aboriginal cultures of the world would disagree with your European notion of "personal property rights". They seemed to get along just fine for hundreds/thousands of years without the notion of personal property, ownership of land, and so on.
Community property, territorial ownership, yes. But not personal.
My original cell phone, a Panasonic TX-220, had a single-keypress lock function. However, it required holding down the lock key for 2 seconds to enable or disable (with an auto-enable after 10 seconds feature). Never had it accidentally lock or unlock on me, and I found it to be a lot more usable than the "top-left button, then bottom-left button" process to un/lock my current phone.
Don't dismiss a single-key lock process because you can't think of a way to make it work.:) It's been done before, it's been done well, and lots of us really miss it.
The Linux VServer project offers kernel patches that accomplish roughly the same thing.
In the resource-separation spectrum, it's something like:
chroot syscall
linux vserver / freebsd jail / solaris containers
vmware / virtualbox / qemu / other hardware emulating vms
xen / vmware esx / solaris zones (or partitions or whatever it's called)
separate physical boxes
Forgot to mention that wireless is also a half-duplex medium where only a single station can be transmitting data at time. Put 10+ computers onto the same access point, and you are looking at serious contention on that 300+ Mbps of bandwidth. Think back to the good ol' days of 10 Mbps ethernet using unmanaged hubs. Of 100 Mbps ethernet using unmanaged hubs.
Slashdot Mirror
# make quicksearch name=whatever
"That number, generated by marketroids, is absolutely meaningless, but it was meant to imply that this chip was more powerful than an Intel 2200 MHz chip"
No, the XXXX+ numbers were to show the performance of that CPU relative to a 1 GHz AthlonXP (originally a 1 GHz Athlon), if the performance of the AthlonXP was linear. ie, if there was a 2200 MHz AthlonXP, then the Athlon64 2200+ would have the same performance, while only running at 1800 MHz.
The AMD numbers were always relative to themselves. It was all the tabloids (er, I mean computer rags) that confused them with "this compares to an Intel chip running at 2200 MHz".
The only time that "Performance Rating" numbers were relative to Intel was back in the 586/Pentium days, when IBM, Cyrix, and company tried to show their 586-class CPUs were as fast as the Pentium, PentiumPro, and P2.
You have that backwards. Intel is very fond of requiring new chipsets and/or new sockets for each revision of their CPUs:
PPro -> P2, new chipset, new slot, new motherboard
P2 -> P3, new chipset, new socket, new motherboard
P3 -> P4, new chipset, new socket, new motherboard
several revisions of the P4 required new chipsets, new sockets, and new motherboards
P4 -> Core, new chipset, new socket, new motherboard
Core -> Core2, new chipset, new socket, new motherboard
several revisions of the Core2 chipsets require new chipsets, new sockets, and new motherboards
Several chip revisions with Intel have also required new RAM (RIMM, DIMM, FB-DIMM, DDR1, DDR2, etc)
Socket 754 allowed for Duron, Sempron, Athlon CPUs
Socket 939 allowed for Sempron, Athlon, AthlonMP, AthlonXP, Athlon64, Athlon64 X2
Socket 940 allowed for Athlon64, Opteron
Socket AM2 allowed for Athlon64, Athlon64 X2, Opteron
Socket AM2+ is the bastard child
So long as you don't continuously run the bleeding-edge, you could upgrade your AMD system with newer CPUs and more RAM. And you could transfer your RAM from system to system if you replaced the motherboard.
AMD has been the more upgrade-as-you-go friendly. Intel has been the replace-everything-when-you-swap-CPUs group.
Not true. The original AMD 8000-series of chipsets for Opteron systems were rock solid. It wasn't until they discontinued these and started to rely on third-parties for their chipsets that things went downhill. Tyan motherboards based around the 8000-series chipsets may not have been the fastest, but they were super-stable. We still have some original Thunder K8SD motherboards running here, almost 5 years later.
Can't comment on the desktop side of things.
Except that compared to Zimbra, Citadel, Scalix, eGroupware, OpenGroupware, and even Kolab are crap. None of them have as nice of a webmail setup, nor as nice Outlook/Evolution/Kontact connectors, nor as nice of PDA setups (especially when it comes to Blackberries and over-the-air-sync).
When it comes to Exchange alternatives, there's really only Zimbra and FirstClass. And FirstClass is just a pile of junk that should never be considered for anything.
The greatest thing MS will get from buying Yahoo! will be to kill Zimbra.
What's worse are the people who send you an e-mail, and then call to see if you received it!! If you were going to call, why'd you send the e-mail??? Or who call to find out why you haven't replied yet, even though they only sent it 3 minutes ago.
Or the people who send an e-mail, expect it to be received within 10 seconds, and complain when time-critical issues are not received right away. Don't use an asynchronous, mostly-reliable, non-realtime medium for synchronous, reliable, realtime duties!!
Example: I have memberships on a lot of sites, like here. I can't remember all my passwords. I could keep them cleartext in a spreadsheet, or someone could allow me a means of storing them in my personal DB that a keyring app could hook up to (or me directly, from the mysql prompt, if I have the knowledge to do so and so choose).
It's called the KDE Wallet. :) It stores usernames and passwords for anything that requires it, whether it be local apps, remote apps, websites, or whatnot. There's even a mini-text editor in there to keep free-form text if you want. You can even have separate wallets for online vs. local info. And it's accessible to any and all KDE apps.
Each wallet is protected by a separate password (or you can configure the manager to use a single master password), and the contents are stored encrypted on disk.
Now, if only someone would port this to Windows, and Mac, and add hooks for non-KDE apps to access it.
:D
"I wonder if you can even call it a network game on a non-routeable protocol."
...
There are just so many things wrong with that statement, it's hard to decide where to start
I take it you've never played any of the variations on double-solitaire with your buddies?? :)
Depends on how high-level you need to go on the CAD chart. There are several open-source CAD programs out there. The two that I know of are QCad (2D) and Cycas 3D. We use both of these in our tech ed. courses in the local school district. We stopped paying for AutoCAD back in the Windows 3.1 days ... sticking it out with ancient 486es and Pentiums runnning the 16-bit version of AutoCAD. About 5 years ago, we migrated two labs to QCad on Windows 98, then to QCAD and Cycus on Debian Linux.
These work fine for educational uses, not sure about professional use, though, as that's not my area.
Most computer magazines use redirect URLs on their own servers for this purpose.
Your issue is probably more about the differences between POP3 and IMAP message storage/retrieval.
:) Store all your messages on an IMAP server. Access them from anywhere with any IMAP client. If you need offline access to your messages, then use an IMAP client with "offline" or "disconnected IMAP" support. Then it keeps your local copy in sync with the server message store.
When people here "e-mail client" they tend to think of POP3, where the client connects to the mail server, downloads the messages to the local computer, and then makes them available from that computer only.
When people think "webmail" they tend to think about having all their messages stored on some remote server, accessible via any computer with an Internet connection and a web browser.
Well, if you use an IMAP server, you get the best of both: a local client optimised for messaging duties, and messages stored on a remote server accessible from any computer with an Internet connection and an IMAP client (which can be webmail clients).
POP3 is pretty much dead and useless, or should be killed off at any rate.
It was only DOS and MacOS which couldn't cope well unless you had an expensive hard drive.
MS-DOS, PC-DOS, and DR-DOS all ran beautifully without harddrives. Our first computer was an IBM clone with 2 5.25" floppy bays and a whopping 512 KB of RAM. We ran MS-DOS 3.1, and 5.0 on there for several years. Worked just fine.
It was Windows that couldn't handle not having local storage. DOS ran just fine with just removable (floppy-based) storage.
E-mail isn't "dying" or "becoming obsolete". IM, SMS, etc are not replacing e-mail. They server different purposes.
Back in the pre-computer days, if you needed to reach someone right away to chat about whatever, you picked up the phone. Instant, synchronous, real-time communication.
If you just wanted to update someone on your life and didn't need an instant reply, then you sat down, wrote a letter and mailed it to them. Eventually they'd receive it, read it, and send a reply back. More in-depth, and asynchronous.
And so it is with digital communications. If you need to reach someone right away, then you send them an IM or SMS. Instant, synchronous, pretty much real-time communication. Or, if you don't really want a reply, but just want to update people on what you are doing, then you update your online profile (wherever that might be).
If you don't need an instant reply, or you have more to say than will fit in 80 characters, then you sit down, write an e-mail, and send it to them. Eventually they receive it, read, and reply. Asynchronous communication.
Sometimes one method works better than the other. One is not replacing the other. They server different purposes, have different uses, and are used at different times.
It's not like this is a new thing, either. Different age groups use different modes of communications.
And, how is this different from putting up an open access point?
If you want a private network, then you can put WEP/WPA and a password on the connection. You can add VPN software. You can use MAC filtering. You can use IP filtering. Etc.
It's the same thing with web servers, with mail servers, etc.
There's nothing inherently private or public with these things. What you do with them after installation is what matters.
No, I'm putting up a web server so that I can access my files remotely. I'm not advertising it, I'm not posting it on a bulletin board. I'm just putting up a web server. That does not automatically make it private. Nor does that automatically make it public. It just makes it available to access.
Why would putting a server up on port 80 be considered public anymore than putting up a wireless access point? I don't see how having a web server is "implied public". Just because I put it there doesn't mean I want everyone to access it. That's a poor example to use.
First of all, it's called the page file, not the swap file. This isn't Unix and this isn't Windows 3.x. If you're going to pretend to know something about this aspect of Windows, you'd do well to at least use the correct name.
What's in a name? The function is the same. That's like complaining about someone calling your Ferrari a car. Oooh, how nasty of them!
Second, and far more importantly -- You do not get fragmentation in the page file unless the page file is resized, and the only time the page file gets resized is when you consume ALL your physical memory, and ALL the memory in the page file. On a system with 1 GB of memory (which will be given a 1.5GB page file), you will have 2.5 GB of memory that you have to fill up first. Windows XP & later will display a pop-up balloon when this happen. Fragmentation NEVER HAPPENS OTHERWISE. Why is this such a major concern to you?
Yes, it does happen. The default size of the page file is not 1.5x RAM. It usually starts at 768 MB and then grows over time. For fun, you can run the defrag program in XP and check the stats output to see how many fragments there are to the page file. I've seen some systems with dozens of fragments in a 768 MB page file.
There are only two great beers in Canada, one from each coast:
All the rest are swill, which is why they are exported to the US, and why we sold our major breweries to the US. :)
All the aboriginal cultures of the world would disagree with your European notion of "personal property rights". They seemed to get along just fine for hundreds/thousands of years without the notion of personal property, ownership of land, and so on.
Community property, territorial ownership, yes. But not personal.
My original cell phone, a Panasonic TX-220, had a single-keypress lock function. However, it required holding down the lock key for 2 seconds to enable or disable (with an auto-enable after 10 seconds feature). Never had it accidentally lock or unlock on me, and I found it to be a lot more usable than the "top-left button, then bottom-left button" process to un/lock my current phone.
:) It's been done before, it's been done well, and lots of us really miss it.
Don't dismiss a single-key lock process because you can't think of a way to make it work.
That's the beauty of Kontact. Each "module" is actually a separate application. All Kontact adds is a GUI wrapper around all the separate apps.
If you want to use the full e-mail, schedule, addressbook, todo, RSS reader then you can fire up Kontact.
If you only want to check your e-mail, then either fire up Kontact, or just KMail. All the data is the same.
If you only want to check your calendar, then either fire up Kontact, or just .
And so on. You can easily move from using a few of the individual apps on their own, to the full-blown Kontact. Or vice versa.
It's quite nice to work with, and something I wish Evolution/Outlook/etc did.
Small correction: 7771 should be written as 1777.
7771 would give permissions rwsrws--t
1777 would give permissions rwxrwxrwt
The Linux VServer project offers kernel patches that accomplish roughly the same thing.
In the resource-separation spectrum, it's something like:
chroot syscall
linux vserver / freebsd jail / solaris containers
vmware / virtualbox / qemu / other hardware emulating vms
xen / vmware esx / solaris zones (or partitions or whatever it's called)
separate physical boxes
Forgot to mention that wireless is also a half-duplex medium where only a single station can be transmitting data at time. Put 10+ computers onto the same access point, and you are looking at serious contention on that 300+ Mbps of bandwidth. Think back to the good ol' days of 10 Mbps ethernet using unmanaged hubs. Of 100 Mbps ethernet using unmanaged hubs.