I whole heartedly agree with the anonymous brave guy. As a consumer, I don't need server class or high end workstation class equipment for my personal machines, and I can typically buy hardware that is just as perceptibly stable to me. This is different if you're specifying out requirements for an aviation console or emergency services ground vehicle console or some other high criticality use case, but you also want a metaphorical chain of support to a vendor that you can yank on if it hits the fan in those circumstances. It's even better if you can get a surety bond on guaranteed system quality, but you'll be paying through the nose for that.
They're fans of Intelli-sense, not Visual Studio. If their text editor can't immediately guess which function they should be using, they freeze up and forget how to check the reference documentation.
Seconded. I've had a RAID1 mirror on my primary workstation at home for roughly... 4 years. I had one of those "oh, drat, my drive is starting to click, and we all know what that means..." moments and barely had time to backup the/home partition to an external machine while I went hardware shopping. Since that event window closed, that configuration has saved my butt twice. One time, the mirrored pair started to go after kinetic shock from moving to a new residence, and it didn't even stress me out to wait for a new pair from my online vendor of choice. I don't know what happened the second time, but I'm guessing that some bad components on the mobo were dirtying the 5V and 3.3V power rails into the drive connector because the whole rig decided to go kaput shortly after in a way that forced an upgrade to the latest CPU socket du jour mobo. Thankfully, I was already budgeting for new guts for that rig due to performance demands.
Well, someone did a pretty bang up job peddling the idea that bitcoins are cryptographically sound using the same tech, but this post is likely to be modded into oblivion for taking a shot at one of the slashdot sacred cows.
chntpw has been in the wild since 1997. It's wonderful that the researcher just realized that it works on cloud volumes just as well as physical volumes, but this it flat out not news. It's also mitigated by deploying an Active Directory domain controller if you want to stick with windows or rolling one yourself with krb5/ldap/samba/etc. if you want your backend servers running unix of whatever variant you like.
Elliptic curve cryptography looks great on a machine running HollywoodOS at your local cineplex, but I have yet to see a single convincing argument for using it for real life cryptography beyond the cool factor and a bunch of hand waving. It's weak and suffers from weird factorization and Fourier based cryptanalysis, and it's simply inferior to exponentiation based algorithms such as those using in Diffie-Hellman variants, RSA, DSS, krb5, etc.
Seconded. Google isn't the paragon of perfection that many believe them to be, but they are better than a majority of the industry players, but this is a bogus charge. If you want your data secure, then secure it. Insurance companies won't pay for stolen vehicle claims when the driver leaves the keys in the ignition with the doors unlocked, and Google shouldn't be smacked for receiving a signal that is broadcast to everyone in cleartext through the ether. This is really just an excuse for some tort lawyers to rake in a payday, not send a message to people to be morally correct in their business dealings.
User admin with password admin on SSID linksys in the wild is as incompetent than simply failing to install doorknobs and deadbolts on your house. I understand that everyone can't be an expert at everything, but you should atleast consult with someone that does know the basics to help you install your wi-fi router with the minimum security enabled.
As long as the system allows for concurrent deployment of multiple processes, multiple installation paths, and doesn't start services as daemons on conflicting ports, you can have hordes of developers on the same development server. This doesn't typically work well for OS, embedded, or resource intensive development projects, but it's a breeze for web projects and some basic application development. Still, this is 2013, and it costs less to get someone setup with a company laptop than it does to give them health insurance. The only reason to lock people into centralized development machines instead of a portable is about physical control of the source code, and that is an employer's prerogative if they so choose.
There are use cases for multiple systems, and sharp companies make use of as many of these systems to fill their niches as they need. Put up a source code management system like rcs/cvs/svn/git/mercurial/bazaar/sourcesafe/bitkeeper/etc. If you need a whiteboard area for people to track projects, requirements, milestones, and other cultural information that's good for employees to know, slap together a wiki. If you need a dumping ground for large amounts of junk media files and other random crap (this litters SCM and bloats on disk storage if it exceeds a certain threshold), then set up a shared Z: or H: drive by all means, but don't expect it to facilitate shared development on curated central libraries unless it's just temporary transferring files when a merge is too complicated. If you want to go the microsoft route and give thousands and millions to a software vendor, then do so by all means.
No tool is a golden hammer. No tool is the best for every job. If you try to make one tool do everything, you're setting yourself up for failure. Listen to other people and be willing to go along with solutions that you may personally resist at first if they give you confidence to believe they know what they're talking about (or they're signing your paychecks).
You still need to lock your files before you bang hard on the awesome Office built in functionality. It doesn't change the fact that you diff and merge your changes with Bob from accounting while he's working on the same thing, you check yours in, then he checks his in, and magically your changes disappeared. I wasn't arguing about the value of the internal revision tracking of the tools in question; your changes will still get blown away the first time you work on a document at the same time with 2-5 other people and it turns into swiss cheese. They worked on their copy that they checked out at 9am just like you did when Alice mailed all of you that check just pushed a new revision and needs your review and commentary. In fact, the built in tools of applications you choose to work with make the problem worse because of people being over confident about their pet tools.
Yes, by all means, let's dictate what people should be doing instead of letting them decide for themselves what the best solution should be through trial and error!
I have a vastly different criticism from what I typically hear about Canonical and Ubuntu. Circa Ubuntu 12.04, I started noticing severely degrading quality in the underlying platform scripts, default configurations, and over platform management in Ubuntu. Command line sysadmin conventions typically left alone by the sprawling masses of "gotta change for change's sake" developers suddenly came under fire. What was once a very stable system under the hood was suddenly forgotten and uncared for, so I left. I didn't care about Unity because I've been using Fluxbox for nearly 8-9 years prior, but I did care that it was suddenly ridiculously difficult to bring up a stable NFSv4 w/ krb5 auth, that they were by default using linux software raid partition versions that weren't compatible with CentOS, and that iptables wasn't integrated into the baseline OS in a very sane way. I found out that the default build configuration of ntp didn't support autokey. I found out that the default build configuration for OpenSSL and other crypto related packages had no support for FIPS 140-2.
In other words, with the release of 12.04, ubuntu told me that they suddenly didn't care about enterprise users any more, so I moved on to what I have found to be a superior option for my needs. I understand that I could have rolled my own packages from scratch, but I didn't feel that was an efficient use of my time since switching to Fedora or RHEL/CentOS/SL gave me what I needed by default. I had already cast away the bottomless time sink that was managing gentoo machines, and I wasn't interested in dealing with another only a year later with Ubuntu.
This works great with only one caveat: most office documents are binary files (or are treated like binary files by the SCM), so you'll need to put a process in place to lock the file in question prior to editing to prevent people stomping over others' changes to them.
I don't understand why a bunch of Fisher-Price crap belongs on a computer in the first place unless you've got a 3 year old. I would still keep the access controls locked down to an adult level.
I believe that VLC has been using vdpau, vaapi, and xvmc for hardware offloading since that rig could have been classified as state of the art, so you most likely have been using hardware acceleration the whole time.
Last I checked, people hung up on degrees and academic pedigree don't get out of the lab much and fight for research grants. Musk has built up multiple companies and started to make the world tilt on its axis to his whim. I don't think it really matters what degree he has at this point, nor do I think it matters what you think of him, either.
Microsoft's roots are being one of the most open big vendors in the industry? You just made my day with that joke. Go talk to someone that knows a thing or two about Kerberos and get them to tell you how open and awesome Active Directory is because it uses open protocols. I recall Microsoft withholding publication of their changes to Kerberos that preventing it from interoperating with MIT krb5. I also recall their withholding publication of the EAP-PEAP changes to RADIUS that they made in conjunction with Cisco to lock out other players in the earlier adoption phase of 802.11 eleven protocols. They haven't exactly been a real champion of openness and interoperability in the industry.
Slashdot Mirror
I whole heartedly agree with the anonymous brave guy. As a consumer, I don't need server class or high end workstation class equipment for my personal machines, and I can typically buy hardware that is just as perceptibly stable to me. This is different if you're specifying out requirements for an aviation console or emergency services ground vehicle console or some other high criticality use case, but you also want a metaphorical chain of support to a vendor that you can yank on if it hits the fan in those circumstances. It's even better if you can get a surety bond on guaranteed system quality, but you'll be paying through the nose for that.
They're fans of Intelli-sense, not Visual Studio. If their text editor can't immediately guess which function they should be using, they freeze up and forget how to check the reference documentation.
RAM disks are for initrds and initramfs images.
When you listen to fools, the mob rules.
Seconded. I've had a RAID1 mirror on my primary workstation at home for roughly... 4 years. I had one of those "oh, drat, my drive is starting to click, and we all know what that means..." moments and barely had time to backup the /home partition to an external machine while I went hardware shopping. Since that event window closed, that configuration has saved my butt twice. One time, the mirrored pair started to go after kinetic shock from moving to a new residence, and it didn't even stress me out to wait for a new pair from my online vendor of choice. I don't know what happened the second time, but I'm guessing that some bad components on the mobo were dirtying the 5V and 3.3V power rails into the drive connector because the whole rig decided to go kaput shortly after in a way that forced an upgrade to the latest CPU socket du jour mobo. Thankfully, I was already budgeting for new guts for that rig due to performance demands.
Well, someone did a pretty bang up job peddling the idea that bitcoins are cryptographically sound using the same tech, but this post is likely to be modded into oblivion for taking a shot at one of the slashdot sacred cows.
Active directory (or some alternative) will allow you to assign admin rights to a domain user and disable local user accounts.
chntpw has been in the wild since 1997. It's wonderful that the researcher just realized that it works on cloud volumes just as well as physical volumes, but this it flat out not news. It's also mitigated by deploying an Active Directory domain controller if you want to stick with windows or rolling one yourself with krb5/ldap/samba/etc. if you want your backend servers running unix of whatever variant you like.
Elliptic curve cryptography looks great on a machine running HollywoodOS at your local cineplex, but I have yet to see a single convincing argument for using it for real life cryptography beyond the cool factor and a bunch of hand waving. It's weak and suffers from weird factorization and Fourier based cryptanalysis, and it's simply inferior to exponentiation based algorithms such as those using in Diffie-Hellman variants, RSA, DSS, krb5, etc.
Google is the best MOOC every since they opened their doors in '98, but you have to brush up on your research skills to appreciate it.
Seconded. Google isn't the paragon of perfection that many believe them to be, but they are better than a majority of the industry players, but this is a bogus charge. If you want your data secure, then secure it. Insurance companies won't pay for stolen vehicle claims when the driver leaves the keys in the ignition with the doors unlocked, and Google shouldn't be smacked for receiving a signal that is broadcast to everyone in cleartext through the ether. This is really just an excuse for some tort lawyers to rake in a payday, not send a message to people to be morally correct in their business dealings.
User admin with password admin on SSID linksys in the wild is as incompetent than simply failing to install doorknobs and deadbolts on your house. I understand that everyone can't be an expert at everything, but you should atleast consult with someone that does know the basics to help you install your wi-fi router with the minimum security enabled.
As long as the system allows for concurrent deployment of multiple processes, multiple installation paths, and doesn't start services as daemons on conflicting ports, you can have hordes of developers on the same development server. This doesn't typically work well for OS, embedded, or resource intensive development projects, but it's a breeze for web projects and some basic application development. Still, this is 2013, and it costs less to get someone setup with a company laptop than it does to give them health insurance. The only reason to lock people into centralized development machines instead of a portable is about physical control of the source code, and that is an employer's prerogative if they so choose.
There are use cases for multiple systems, and sharp companies make use of as many of these systems to fill their niches as they need. Put up a source code management system like rcs/cvs/svn/git/mercurial/bazaar/sourcesafe/bitkeeper/etc. If you need a whiteboard area for people to track projects, requirements, milestones, and other cultural information that's good for employees to know, slap together a wiki. If you need a dumping ground for large amounts of junk media files and other random crap (this litters SCM and bloats on disk storage if it exceeds a certain threshold), then set up a shared Z: or H: drive by all means, but don't expect it to facilitate shared development on curated central libraries unless it's just temporary transferring files when a merge is too complicated. If you want to go the microsoft route and give thousands and millions to a software vendor, then do so by all means.
No tool is a golden hammer. No tool is the best for every job. If you try to make one tool do everything, you're setting yourself up for failure. Listen to other people and be willing to go along with solutions that you may personally resist at first if they give you confidence to believe they know what they're talking about (or they're signing your paychecks).
You still need to lock your files before you bang hard on the awesome Office built in functionality. It doesn't change the fact that you diff and merge your changes with Bob from accounting while he's working on the same thing, you check yours in, then he checks his in, and magically your changes disappeared. I wasn't arguing about the value of the internal revision tracking of the tools in question; your changes will still get blown away the first time you work on a document at the same time with 2-5 other people and it turns into swiss cheese. They worked on their copy that they checked out at 9am just like you did when Alice mailed all of you that check just pushed a new revision and needs your review and commentary. In fact, the built in tools of applications you choose to work with make the problem worse because of people being over confident about their pet tools.
Yes, by all means, let's dictate what people should be doing instead of letting them decide for themselves what the best solution should be through trial and error!
I have a vastly different criticism from what I typically hear about Canonical and Ubuntu. Circa Ubuntu 12.04, I started noticing severely degrading quality in the underlying platform scripts, default configurations, and over platform management in Ubuntu. Command line sysadmin conventions typically left alone by the sprawling masses of "gotta change for change's sake" developers suddenly came under fire. What was once a very stable system under the hood was suddenly forgotten and uncared for, so I left. I didn't care about Unity because I've been using Fluxbox for nearly 8-9 years prior, but I did care that it was suddenly ridiculously difficult to bring up a stable NFSv4 w/ krb5 auth, that they were by default using linux software raid partition versions that weren't compatible with CentOS, and that iptables wasn't integrated into the baseline OS in a very sane way. I found out that the default build configuration of ntp didn't support autokey. I found out that the default build configuration for OpenSSL and other crypto related packages had no support for FIPS 140-2.
In other words, with the release of 12.04, ubuntu told me that they suddenly didn't care about enterprise users any more, so I moved on to what I have found to be a superior option for my needs. I understand that I could have rolled my own packages from scratch, but I didn't feel that was an efficient use of my time since switching to Fedora or RHEL/CentOS/SL gave me what I needed by default. I had already cast away the bottomless time sink that was managing gentoo machines, and I wasn't interested in dealing with another only a year later with Ubuntu.
This works great with only one caveat: most office documents are binary files (or are treated like binary files by the SCM), so you'll need to put a process in place to lock the file in question prior to editing to prevent people stomping over others' changes to them.
That's why you hire a receptionist at that point.
I don't understand why a bunch of Fisher-Price crap belongs on a computer in the first place unless you've got a 3 year old. I would still keep the access controls locked down to an adult level.
I believe that VLC has been using vdpau, vaapi, and xvmc for hardware offloading since that rig could have been classified as state of the art, so you most likely have been using hardware acceleration the whole time.
Whatever gave you the idea that Larry Page's ex-gf would do such a thing?! GASP!
Trolling a week old necro'd comment for +1 internet points.
Last I checked, people hung up on degrees and academic pedigree don't get out of the lab much and fight for research grants. Musk has built up multiple companies and started to make the world tilt on its axis to his whim. I don't think it really matters what degree he has at this point, nor do I think it matters what you think of him, either.
Incorrect. man audisp-remote(8)
Microsoft's roots are being one of the most open big vendors in the industry? You just made my day with that joke. Go talk to someone that knows a thing or two about Kerberos and get them to tell you how open and awesome Active Directory is because it uses open protocols. I recall Microsoft withholding publication of their changes to Kerberos that preventing it from interoperating with MIT krb5. I also recall their withholding publication of the EAP-PEAP changes to RADIUS that they made in conjunction with Cisco to lock out other players in the earlier adoption phase of 802.11 eleven protocols. They haven't exactly been a real champion of openness and interoperability in the industry.
Depends. How well can you write a research grant proposal?