Funny... cause that "onboard" raid is most likely NOT a true raid controller. Sure, there are real raid controllers that get build into mboards, but that generally adds a good $200+ to the cost, and is almost always SCSI. Sata "RAID" cards that cost less than $100 are usually just sata cards with a RAID tag in the bios for certain basic raid-like functions. They do not handle the actual raid IO, the OS (in this case Windows) does the work. A true RAID card will appear as a single device (or multiple LUNs if its handling more than one raid set) to the OS, the individual physical devices are abstracted by the controller, though monitoring apps should be able to give status on the individual drives. For examples of real raid, see 3ware, and notice they arent cheap, mainly because they have their own CPU, ram, bios, etc, basically a SBC just to handle the RAID stuff.
most likely its just BIOS headers for some RAID functions. The actual RAID stuff is done by the OS. Almost if not all "SATA RAID" cards that cost less than $100 are just SATA controllers with a thing in the cards bios that says RAID. The OS will still see the individual drives and will have to piece them together. Go search Linux Sata Raid and you will see many, many articles on this. A "true" raid card will show up as a single device to the os (or several LUNs), you will not see the individual physical drives.
If you were doing this with Linux, I would suggest just using md. It works in most cases. For raid1 it mirrors to the point where you can take one drive out and mount it as a non-raid single disk somewhere else. Handy for troubleshooting when ubuntu decides to change uuid drive mappings and thus refuses to rebuild the now broken raid set.....
Yes, SQL. If you keep your raw data in SQL, it is easy to export data to any format you might need now or in the future.
slapcat > myldaptree.ldiff
Done. You now have an Ldiff file that can be re-imported directly, or parsed quite easily, not sure why Exporting seems difficult?
LDAP gets you a long way, but you will sooner or later end up with several apps that don't support it. The result is horrible password sync hacks, multiple passwords per user, etc.
gssapi/SASL, or if its a horribly broken ap that doesnt do that either, its trivial to write an authorize/authenticate plugin for it, just about everything supports LDAP though, or "AD" which is usually LDAP with the MS schema in mind that can be bent to use a normal LDAP directory instead. Password sync (to get the broken NT4/LANMAN and KRB5 passwords) is as simple as compiling smbk5pwd (for openldap) and making sure the things allowed to change user passwords only use the passwd exop in LDAP, which pam and most other items that can allow that have an option for. Its not a hack, though you do end up with several different hashes of the same thing, as intended, but you can thank MS and MIT for using their own standard for hashing instead of plug-in cryptos, and pushing that for use in certain standards (WPA2 and Kerberos).
The idea is to put raw user info in SQL, including their clear-text password.
Um, no. All it takes is one rogue admin with the access to "Manage" that database, and suddenly they can pull the CEO's password without anyone noticing, or a misconfigured SQL server running a non-ssl connection leaking that plain-text across the wire. If you are properly implementing a two-factor system (rsa securid or some equiv) this isnt as big a deal, but still... no.
Of course, lock down that SQL server like you've never locked down anything before! It should have a very limited interface for updating user data.
You should do this with any machine regardless. Lock it down so only those that need it can get in, and they only have access to what needs to be worked on... standard policy
Next, export user data to relevant external databases such as LDAP, NIS, SASL, that obscure sqlite app, Kerberos, DMZ services, etc, and you'll have much less pain keeping everything in sync.
Why? You end up with multiple copies of the same data spread across a multitude of disparate systems. OpenLDAP plugs directly into SASL, Kerberos, Samba, Securid, FreeRadius and many other systems that are NOT really directories and therefore should not have the data themselves. Instead they query LDAP for what they need, and LDAP is configured to let them read only what they need, securely (access to attrs=BLAH by ssf=128 dn.exact="cn=someapp,dc=example,dc=com" read). The ssl certs required are trivial to setup, just use CA.pl a few times, create a CA and a few test certs and you quickly get the hang of it. Setting up LDAPS is generally easier than trying to make sure all your SQL connections are secure as well (only start the ldaps service instead of ldap+ldaps, and use ssf=128 for all acls). With that in place, there is absolutely no risk of sending plain-text passwords in the clear over the wire, where your sql implementation seems ready and willing to do exactly that.
would it not be possible to configure a single server, that proxies or delegates queries to all the other servers he has set up.
I asked about proxying openLDAP to AD, so I could have users in both, yet query them all just by asking the openLDAP server. If this was possible for multiple delegated servers, then this is the approach I'd take - start with 1+all the old ones, then gradually migrate them into just a few servers.
and yes, I'd probably go for RHDS, Active Directory seems to be one of those products that starts off with just a windows 2008 server, then requires more CALS, then needs a SQL Server licence, and then really expensive backup software, and then needs all printers to be connected to it, and then needs Sharepoint adding to the mix, and then... you get the idea:)
OpenLDAP has a few backend plugins that let you do crazy stuff like that, more specifically, the LDAP backend lets you run a proxy to AD (or any other directory that can talk LDAP). Set that up, map a few attribs or get the AD schema on OpenLDAP, and you should be good to go. You can also sync to AD, so if your link to it goes away the data is still local. OpenLDAP has come a long long way in replication, and it works quite well now, much better than even just a year ago. Set one server up with your data, tell it its a syncprovider, then just configure another one to use it as its data source and it will pull down the whole tree (or just the parts you specify) from scratch.
Get a FXS card or blackbox adapter and plug it into an empty jack. Setup the box or the computer with the fxs card for some sort of VoIP service, possibly even run an Astrisk box of some flavor with the cell-phone trunk module (ie: use your cellphone as a trunk/gateway for the PBX). If you do this, be sure to disconnect the lead at the MPOE (main point of entry), usually a screw terminal on the side of the house or in your basement where the telco's line comes in and is split off to all the jacks in the house. Otherwise, you might get their dialtone on top of everything you try, and it might try (and fail) to actually place calls, along with annoying tone messages. As mentioned previously, phone wiring is not generally setup as ethernet capable, either due to chaining, or using crap cat3 UTP or even single pair lines. You might be able to get a marginal 10bT signal going, but replace it with cat5/6 if you seriously want to use it for networking (similarly, CaTv cable can be used for 10b2 for short runs, I had my house wired that way in the 90's cause I didnt feel like paying out the $100s for 10bT hubs and cards and cat5, and had plenty of 10b2 ne2000 cards, extra rg6 and rg59, T connectors and terminators laying around, and its bandwidth was plenty fast to share the 33.6 modem:) ).
One for my personal Cell phone back in march, two for my business cell in march and april. The calls clearly violate FCC regs by being completely automated, no mention of the company name, calling numbers already on the DNC, etc. The first call I opted to talk to a rep, when he connected and mumbled the name of the company, I asked his name and the company name, and he hung up. Second call I told them I was on the DNC, that I was filing a complaint and to make sure I was on their DNC as well. Third call I told them they were in violation as I was already on both the national DNC and theirs, the rep again hung up on me.
If you get one of these types of calls, just go Here: http://esupport.fcc.gov/complaints.htm and fill out the form. In a week or two you get the print copy mailed to you of your filing.
What happened at Chernobyl was human error. Yes, the reactor design is bad and unstable, but it can work safely as long as you don't make any silly mistakes (like reduce the power too fast). The same as a car - it can work safely, as long as you do not make silly mistakes (like falling asleep while driving or driving drunk).
But its much less likely to blow up if the design makes it impossible to do so in the first place. Your car analogy would be better served comparing a traffic safety officer driving a volvo to a drunken redneck handed the keys to an F1 race car with no safety equipment. Modern designs are fail-safe, almost anything can go wrong and the worst that will happen is the reactor shuts down, you have to constantly try to balance the unstable point that keeps the reaction going.
Ever since some years ago we read on/. that they had discovered the secret behind geckos' amazing abilities, I've been waiting for practical applications of this in the form of gecko tape and the soon-to-follow gecko shoes and gloves.
...
Not to detract too much from your post... but Ive been using gecko tape and gloves for a few years now though probably not as advanced as the stuff in TFA:
Greptile is 3m's name for it. I use handlebar tape made with it on my road bike, and before it went out of production (Seems to be only used for golf equipment and Nascar steering wheels these days), had the gloves to match. With the gloves on the tape it was like a weak velcro. Even with normal gloves it has more grip than normal tape.
Tm
Re:Can't pay for your car? Ride a bicycle!
on
Cellular Repo Man
·
· Score: 1
...To simulate the situation presented earlier, try adding another kid and about 100 lbs worth of groceries to your daily ride and see how far you go.
I think the fact you seemingly require 100lbs+ of Costco crap, where he does not is itself very telling. I do just fine without bulk buying from Costco or WalMart, and can do most grocery trips by bike. Most times a large backpack is enough, though panniers and a rack to hold more helps when I need more than basics. Try more frequent smaller capacity trips. I manage to get by with one ~30min trip (rt, couch to kitchen) a week. It takes far less time than driving the extra distance to the bulk buy facility (Costco, Sams club, etc), wandering around an enormous warehouse trying to find what you need, loading a cart full of crap half of which will spoil before it gets used, loading it all into a car, then unloading and trying to organize it all. The nearest CostCo is at least 10mi away, Safeway is only 2 and doesnt require an annual fee for the privilege of shopping there.
Location and street conditions do play a factor, as I know certain parts of Atlanta would be almost suicidal to ride a bike to the store, though most areas have back road ways of bypassing the major highways.
Im not sure what bike trailer you have seen, but the Bob brand is rated to 70Lbs, and the Burley Nomad can do 100Lbs+ with 8000cu.in capacity. You can also add on a Xtracycle extension to carry your 2 kids (pic of it on their main page: Xtracycle.com). Granted, doing this while living on a Mountain is probably not ideal, but still not impossible.
No, but plenty of mass. Its not all in a single line either, so you would get some fairly large moments around the junctions of the various modules (F=M*a, and T=F*r), the solar panel wings, basically anything off the line of thrust. Remember, the ISS was not designed as a spaceship, it was designed to sit in a (fairly) stable orbit where the g forces (aka DeltaV or Acceleration, which is constant during orbital shift) would be limited to minor orbital corrections. Trying to blast it to mars without it falling apart would take a long time without either seriously bracing the modules better or adding thrust to critical points to balance the torques (or both). Getting it to another orbit is more likely, but would still take a while.
When my 2k box slows, its almost always a ff session I closed that didnt go away, and is eating 99% cpu. Killing it via taskmanager makes everything happy again.
...with a little speech recognition software, it would be awesome! Wheel autonomously around a party, someone calls it over and tells it what they want, it mixes it for them right there and hands it to them, then moves on.
Given the choice between a plasma, and a same-sized cheaper more energy efficient LCD with higher refresh that doesnt come with the legends of plasma-burn-in/burn-out, and doesnt feel like you are standing in front of an oven.... I went with the lcd.
So stop wasting karma here and write to those who should care:
Obama himself, his cabinet members, YOUR state representatives. They probably dont read/., and the only way your opinion makes any little shred of difference in this is to get it in front of someone that might have a tiny speck of influence. Hell, if enough people complain about the same thing, someone (that staffer that read your email) might actually start to believe it and mention it to someone else, who might mention it again, and so on, and thats how CHANGE starts. Otherwise its the same insiders telling the same crap to the "new" people, so you end up with the same crap all over again.
The bp6 I ran with 333's oc'd to 500+ until the caps went bad (which there are kits to replace, as I did with an Asus a7m266-d board that I still run dual fx chips in), and now I still run a TH7-II Raid (ordered normal, they shipped me the raid version). For the longest time with a 1.6G P4, upgraded for a whole $20 to a newer northwood P4 now running around 3.1Ghz. Not bad for a mobo thats almost 8 years old.
How about a cost-effective, portable, and accurate method in countries where we're used to overpaying for the NON-cost-effective methods?
The paper will cost more per square inch than a $1000bill...
thank you Bush (and all former champions of free market economics/anti-socialist) for the "free market" of health care, where they make a higher profit by keeping us sick so that we need more of their services.
For a large bomber craft, its supprisingly
quiet, especially if compared to something like a C5 galaxy or C17 Globmaster, or even an F-18 (well, it did have its afterburner lit).
There's absolutely no excuse for banks to not have rolled out a checking system that uses much larger one-time-use account numbers and allows merchants to verify that the check won't bounce. They've been twiddling their thumbs.
... and raking in the $$. They wont change their ways because each bounced check is an opportunity for them to collect lots of fees. At least $20 from the person trying to pass off the bad check, and another $20-30 from the account that got overdrawn. To top it off, once that account is overdrawn, they get those fees on Every withdrawal until they stop coming in. For fake checks, they will still charge your account for trying to pass off the bad check. To them, its not broken, its a source of revenue.
-Tm
If you were doing this with Linux, I would suggest just using md. It works in most cases. For raid1 it mirrors to the point where you can take one drive out and mount it as a non-raid single disk somewhere else. Handy for troubleshooting when ubuntu decides to change uuid drive mappings and thus refuses to rebuild the now broken raid set.....
-Tm
TCP is generally only used for excessively large requests or zone transfers
Tm
Yes, SQL. If you keep your raw data in SQL, it is easy to export data to any format you might need now or in the future.
slapcat > myldaptree.ldiff
Done. You now have an Ldiff file that can be re-imported directly, or parsed quite easily, not sure why Exporting seems difficult?
LDAP gets you a long way, but you will sooner or later end up with several apps that don't support it. The result is horrible password sync hacks, multiple passwords per user, etc.
gssapi/SASL, or if its a horribly broken ap that doesnt do that either, its trivial to write an authorize/authenticate plugin for it, just about everything supports LDAP though, or "AD" which is usually LDAP with the MS schema in mind that can be bent to use a normal LDAP directory instead. Password sync (to get the broken NT4/LANMAN and KRB5 passwords) is as simple as compiling smbk5pwd (for openldap) and making sure the things allowed to change user passwords only use the passwd exop in LDAP, which pam and most other items that can allow that have an option for. Its not a hack, though you do end up with several different hashes of the same thing, as intended, but you can thank MS and MIT for using their own standard for hashing instead of plug-in cryptos, and pushing that for use in certain standards (WPA2 and Kerberos) .
The idea is to put raw user info in SQL, including their clear-text password.
Um, no. All it takes is one rogue admin with the access to "Manage" that database, and suddenly they can pull the CEO's password without anyone noticing, or a misconfigured SQL server running a non-ssl connection leaking that plain-text across the wire. If you are properly implementing a two-factor system (rsa securid or some equiv) this isnt as big a deal, but still... no.
Of course, lock down that SQL server like you've never locked down anything before! It should have a very limited interface for updating user data.
You should do this with any machine regardless. Lock it down so only those that need it can get in, and they only have access to what needs to be worked on... standard policy
Next, export user data to relevant external databases such as LDAP, NIS, SASL, that obscure sqlite app, Kerberos, DMZ services, etc, and you'll have much less pain keeping everything in sync.
Why? You end up with multiple copies of the same data spread across a multitude of disparate systems. OpenLDAP plugs directly into SASL, Kerberos, Samba, Securid, FreeRadius and many other systems that are NOT really directories and therefore should not have the data themselves. Instead they query LDAP for what they need, and LDAP is configured to let them read only what they need, securely (access to attrs=BLAH by ssf=128 dn.exact="cn=someapp,dc=example,dc=com" read). The ssl certs required are trivial to setup, just use CA.pl a few times, create a CA and a few test certs and you quickly get the hang of it. Setting up LDAPS is generally easier than trying to make sure all your SQL connections are secure as well (only start the ldaps service instead of ldap+ldaps, and use ssf=128 for all acls). With that in place, there is absolutely no risk of sending plain-text passwords in the clear over the wire, where your sql implementation seems ready and willing to do exactly that.
-T
would it not be possible to configure a single server, that proxies or delegates queries to all the other servers he has set up.
I asked about proxying openLDAP to AD, so I could have users in both, yet query them all just by asking the openLDAP server. If this was possible for multiple delegated servers, then this is the approach I'd take - start with 1+all the old ones, then gradually migrate them into just a few servers.
and yes, I'd probably go for RHDS, Active Directory seems to be one of those products that starts off with just a windows 2008 server, then requires more CALS, then needs a SQL Server licence, and then really expensive backup software, and then needs all printers to be connected to it, and then needs Sharepoint adding to the mix, and then... you get the idea :)
OpenLDAP has a few backend plugins that let you do crazy stuff like that, more specifically, the LDAP backend lets you run a proxy to AD (or any other directory that can talk LDAP). Set that up, map a few attribs or get the AD schema on OpenLDAP, and you should be good to go. You can also sync to AD, so if your link to it goes away the data is still local. OpenLDAP has come a long long way in replication, and it works quite well now, much better than even just a year ago. Set one server up with your data, tell it its a syncprovider, then just configure another one to use it as its data source and it will pull down the whole tree (or just the parts you specify) from scratch.
-T
-T
What better way to make unfortunate evidence disappear?
If you get one of these types of calls, just go Here: http://esupport.fcc.gov/complaints.htm and fill out the form. In a week or two you get the print copy mailed to you of your filing.
Im glad they are acting on these @holes.
What happened at Chernobyl was human error. Yes, the reactor design is bad and unstable, but it can work safely as long as you don't make any silly mistakes (like reduce the power too fast). The same as a car - it can work safely, as long as you do not make silly mistakes (like falling asleep while driving or driving drunk).
But its much less likely to blow up if the design makes it impossible to do so in the first place. Your car analogy would be better served comparing a traffic safety officer driving a volvo to a drunken redneck handed the keys to an F1 race car with no safety equipment. Modern designs are fail-safe, almost anything can go wrong and the worst that will happen is the reactor shuts down, you have to constantly try to balance the unstable point that keeps the reaction going.
Ever since some years ago we read on /. that they had discovered the secret behind geckos' amazing abilities, I've been waiting for practical applications of this in the form of gecko tape and the soon-to-follow gecko shoes and gloves.
...
Not to detract too much from your post... but Ive been using gecko tape and gloves for a few years now though probably not as advanced as the stuff in TFA:
Greptile is 3m's name for it. I use handlebar tape made with it on my road bike, and before it went out of production (Seems to be only used for golf equipment and Nascar steering wheels these days), had the gloves to match. With the gloves on the tape it was like a weak velcro. Even with normal gloves it has more grip than normal tape.
Tm
...To simulate the situation presented earlier, try adding another kid and about 100 lbs worth of groceries to your daily ride and see how far you go.
I think the fact you seemingly require 100lbs+ of Costco crap, where he does not is itself very telling. I do just fine without bulk buying from Costco or WalMart, and can do most grocery trips by bike. Most times a large backpack is enough, though panniers and a rack to hold more helps when I need more than basics. Try more frequent smaller capacity trips. I manage to get by with one ~30min trip (rt, couch to kitchen) a week. It takes far less time than driving the extra distance to the bulk buy facility (Costco, Sams club, etc), wandering around an enormous warehouse trying to find what you need, loading a cart full of crap half of which will spoil before it gets used, loading it all into a car, then unloading and trying to organize it all. The nearest CostCo is at least 10mi away, Safeway is only 2 and doesnt require an annual fee for the privilege of shopping there.
Location and street conditions do play a factor, as I know certain parts of Atlanta would be almost suicidal to ride a bike to the store, though most areas have back road ways of bypassing the major highways.
Im not sure what bike trailer you have seen, but the Bob brand is rated to 70Lbs, and the Burley Nomad can do 100Lbs+ with 8000cu.in capacity. You can also add on a Xtracycle extension to carry your 2 kids (pic of it on their main page: Xtracycle.com). Granted, doing this while living on a Mountain is probably not ideal, but still not impossible.
Not much friction on the ISS...
No, but plenty of mass. Its not all in a single line either, so you would get some fairly large moments around the junctions of the various modules (F=M*a, and T=F*r), the solar panel wings, basically anything off the line of thrust. Remember, the ISS was not designed as a spaceship, it was designed to sit in a (fairly) stable orbit where the g forces (aka DeltaV or Acceleration, which is constant during orbital shift) would be limited to minor orbital corrections. Trying to blast it to mars without it falling apart would take a long time without either seriously bracing the modules better or adding thrust to critical points to balance the torques (or both). Getting it to another orbit is more likely, but would still take a while.
Tm
Tm
Tm
tm
tm
Just one example..
T
The bp6 I ran with 333's oc'd to 500+ until the caps went bad (which there are kits to replace, as I did with an Asus a7m266-d board that I still run dual fx chips in), and now I still run a TH7-II Raid (ordered normal, they shipped me the raid version). For the longest time with a 1.6G P4, upgraded for a whole $20 to a newer northwood P4 now running around 3.1Ghz. Not bad for a mobo thats almost 8 years old.
How about a cost-effective, portable, and accurate method in countries where we're used to overpaying for the NON-cost-effective methods?
The paper will cost more per square inch than a $1000bill...
thank you Bush (and all former champions of free market economics/anti-socialist) for the "free market" of health care, where they make a higher profit by keeping us sick so that we need more of their services.
Tm
tm
Thats no moon! Its a space station!!
To think, if we changed launch vehicles for payloads, we could have our very own deathstar by now!
tm
Tm
The Music Video.... ot, but worth it. (scene in it might be nsfw, otherwise just creepy).
There's absolutely no excuse for banks to not have rolled out a checking system that uses much larger one-time-use account numbers and allows merchants to verify that the check won't bounce. They've been twiddling their thumbs.
... and raking in the $$. They wont change their ways because each bounced check is an opportunity for them to collect lots of fees. At least $20 from the person trying to pass off the bad check, and another $20-30 from the account that got overdrawn. To top it off, once that account is overdrawn, they get those fees on Every withdrawal until they stop coming in. For fake checks, they will still charge your account for trying to pass off the bad check. To them, its not broken, its a source of revenue.
tm
Fork OpenID, I'm in control now.
ftfy
tm