User rename: I don't want Joe Smith... My username is joesmith... Whenever I flip into root mode using sudo the dialog box keeps coming up with my real name instead of my logged in name. Sorry, but that will not work!
Try it, it does. You can use your real name, or your username.
Windows can't do virtualization properly. Configuration management can be done with OS X server. I'll give you terminal services, but windows sucks pretty bad at that, too.
Fair enough; I would be greatful if you could kindly inform me how to script disabling Sleep mode, turning off all forms of network sharing, remote access, bonjour, etc, and enabling the firewall.
All that stuff is included in a modern OS X by default. I've used VPN stuff on OSX since at least leopard, which came out in what... 2007? 3 versions ago? No need to command line install anything.
The chances of/etc/fstab or grub.conf getting corrupted are fairly small. They're also easy to fix. Having 1-2 bytes in a registry hive that is multiple tens of megabytes in size is another matter.
More to the point, supporting 3 or 4 different versions of Windows (like he was trying to do with Mac OS back to 10.3 or whatever) would be just as hard, given that there's both 32 and 64 bit registry hives to deal with, varying degrees of registry option support between 2k, XP, Vista and 7, and a myriad of different hardware setups to deal with.
They don't need to know much, they just need the right certificates and be able to play politics (ie, don't rock the boat). So they end up with people who know all the right stuff about Windows that they learned in night school
More often than not, they end up with chumps who couldn't find the cause of a problem (Windows, or otherwise) if it bit them in the face.
In my experience, the unix admin typically ends up solving the Microsoft problems if they have anything to do with networking, storage, virtualization, or hardware diagnostics. Which doesn't really leave a lot left for the solitaire expert to deal with.
I've met a couple of MCSEs who know what they're doing, but for the most part they're idiots.
Oh please. Of all the *nixes I have used (and I'm including SCO Openserver, Linux, FreeBSD, Solaris, and AIX) every single one has a different way of setting configuration changes./Applications is just another directory, like/opt on a sun box or/usr/local/ on a FreeBSD or Slackware box.
If you can't deal with that then give up your IT job and go back to flipping burgers at macdonalds.
I tried voice control on my Nokia. It was SHIT. Siri is far more advanced, and not only does it understand voice commands, it also understand context and hooks into various services on the phone, rather than simple number dialling.
Like it or not, requiring code signing is going to cut out 95% plus of the malware out there. Sure, you may still run into security vulnerabilities in preinstalled apps (this will always be a problem), but the easiest piece of the puzzle to break has always been the user. Disallow the user to run unsigned code (either controlled at the vendor level, or the corporate IT admin level) and that problem goes away.
Thing is, plenty are currently running it. There are plenty of open relays still out there too, and that hasn't been SMTP best practice for far longer.
I suspect you'll find that most of them started out based on the BSD reference implementation. Linux itself started out with a BSD-derived TCP/IP stack.
If they are not "current" working data they should be paged out. I don't care on the format, do a memory page dump for all I care, but carrying stuff around in memory to second guess your operatng system's VM subsystem is an ugly hack that has shown to have nasty consequences for every other task the user wants to do with his/her hardware.
Indeed IPv6 support is what drove me to the ISP i currently use, and what influenced the purchase of my current router...
Same here. We are not the majority of users however, most don't give a crap. Spending millions on new hardware to keep a few geeks happy is not going to bring in revenue. Until ipv6 can be monetized, it is not likely to happen. And at the moment, 99.99% of the world don't care.
err... rather: Maybe I should refine my equation above. If lost revenue due to lost customers + cost to deploy more ipv4 IS LESS THAN cost to deploy ipv6, guess what happens. This is the business case, and for many/most ISPs the numbers simply do not add up yet.
Maybe I should refine my equation above. If lost revenue due to lost customers + cost to deploy more ipv4 cost to deploy ipv6, guess what happens. This is the business case, and for many/most ISPs the numbers simply do not add up yet.
Slashdot Mirror
Try it, it does. You can use your real name, or your username.
Windows can't do virtualization properly. Configuration management can be done with OS X server. I'll give you terminal services, but windows sucks pretty bad at that, too.
OS X server. Next.
All that stuff is included in a modern OS X by default. I've used VPN stuff on OSX since at least leopard, which came out in what... 2007? 3 versions ago? No need to command line install anything.
The chances of /etc/fstab or grub.conf getting corrupted are fairly small. They're also easy to fix. Having 1-2 bytes in a registry hive that is multiple tens of megabytes in size is another matter.
More to the point, supporting 3 or 4 different versions of Windows (like he was trying to do with Mac OS back to 10.3 or whatever) would be just as hard, given that there's both 32 and 64 bit registry hives to deal with, varying degrees of registry option support between 2k, XP, Vista and 7, and a myriad of different hardware setups to deal with.
More often than not, they end up with chumps who couldn't find the cause of a problem (Windows, or otherwise) if it bit them in the face.
In my experience, the unix admin typically ends up solving the Microsoft problems if they have anything to do with networking, storage, virtualization, or hardware diagnostics. Which doesn't really leave a lot left for the solitaire expert to deal with.
I've met a couple of MCSEs who know what they're doing, but for the most part they're idiots.
You haven't looked into automator, or applescript then.
Oh please. Of all the *nixes I have used (and I'm including SCO Openserver, Linux, FreeBSD, Solaris, and AIX) every single one has a different way of setting configuration changes. /Applications is just another directory, like /opt on a sun box or /usr/local/ on a FreeBSD or Slackware box.
If you can't deal with that then give up your IT job and go back to flipping burgers at macdonalds.
And none of them actually worked.
I tried voice control on my Nokia. It was SHIT. Siri is far more advanced, and not only does it understand voice commands, it also understand context and hooks into various services on the phone, rather than simple number dialling.
How much is the windows upgrade btw?
Like it or not, requiring code signing is going to cut out 95% plus of the malware out there. Sure, you may still run into security vulnerabilities in preinstalled apps (this will always be a problem), but the easiest piece of the puzzle to break has always been the user. Disallow the user to run unsigned code (either controlled at the vendor level, or the corporate IT admin level) and that problem goes away.
Troll doesn't mean "running technology i don't myself understand".
Thing is, plenty are currently running it. There are plenty of open relays still out there too, and that hasn't been SMTP best practice for far longer.
Rogue dhcp servers? Locate on your managed switch, LART user. Or run 802.11X, if your network integrity is really important.
Plenty of places are already running ipv6. Plenty of people don't know how to implement/administer ipv4 properly either.
Clearly you have no idea what showstopper means.
I suspect you'll find that most of them started out based on the BSD reference implementation. Linux itself started out with a BSD-derived TCP/IP stack.
By protocol starting out GPL, i mean its reference implementation.
If they are not "current" working data they should be paged out. I don't care on the format, do a memory page dump for all I care, but carrying stuff around in memory to second guess your operatng system's VM subsystem is an ugly hack that has shown to have nasty consequences for every other task the user wants to do with his/her hardware.
Same here. We are not the majority of users however, most don't give a crap. Spending millions on new hardware to keep a few geeks happy is not going to bring in revenue. Until ipv6 can be monetized, it is not likely to happen. And at the moment, 99.99% of the world don't care.
err... rather: Maybe I should refine my equation above. If lost revenue due to lost customers + cost to deploy more ipv4 IS LESS THAN cost to deploy ipv6, guess what happens. This is the business case, and for many/most ISPs the numbers simply do not add up yet.
Maybe I should refine my equation above. If lost revenue due to lost customers + cost to deploy more ipv4 cost to deploy ipv6, guess what happens. This is the business case, and for many/most ISPs the numbers simply do not add up yet.
You mean like my ASA?