You seem very knowledgeable regarding filesystems in general. I'm interested in learning more about filesystems and how they work. To give you an idea of where I am, I believe I know what blocksize is, but I don't know what an extent is, and how it relates to performance (or why the grandparent would like extents several megabytes large).
What resources would you suggest to people who are looking to learn more?
I don't think I'm allowed to tell you the price they quoted me, but they're really friendly if you give them a call and ask for a quote. I don't think their prices are excessive at all. The steepest part is that there is an initial cost of purchasing a WORM (write once, read many) drive for archival purposes. The nice part of that is that the drive is yours. You take it if/when you cancel your service along with your discs.
If you'd like, I can get you in touch with my contact there.
Great, now they've got to deal with the same sort of things we do. Archiving every bit of email that comes into the system, and making sure it's available online for searching and retrieval.
I'm interested in how they're going to be doing it. I've been looking at Global Relay for my own mail archiving. I wonder what they'll end up going with. I asked this a while ago on my blog, too.
Looking at the edited photo, I have to wonder how they found out that it didn't come right out of the camera like that. I mean, I've seen quite a few 'shops in my time, and I got nothing. *cough*
Hi! This is offtopic, but as a former slackware admin, I've got to ask. How did you manage to scale it to a large environment?
I got to a few dozen machines and used to spend all my time patching and admining multiple users. I eventually moved to CentOS authenticated over AD with Likewise Open. I'm interested in hearing how other people do it.
Forgive me, because I'm a linux guy (that's all I've ever used and known), and because of that, I don't know what the benefits of having an AIX machine on the desktop would be.
I understand that on certain large hardware, AIX is preferable due to hardware or other requirements, but what is the draw on the desktop? Is there superior software, or stability? Management tools?
I manage Linux servers, and I have linux on my desktop because it seems effortless to me now, but I can't imagine that if I had one of the BSDs, Solaris, or any other unix that my experience would be different. What is the draw? I'm not flaming or trolling, I'm really interested in being educated.
Radio shack used to have a clause like that too. They even claimed everything you produced for a year after you left. Laughable. As if my sales training there would lead to creating something useful.
Some of the information in the threads is out of date, but the ideas are useful and interesting to read. I need to go back through Ask Slashdot and get the more recent threads that seem to act as references
If you like good, and old was good, but new is bad, guess which one you'd rather go with?
I think slashdot is usable, but it gets in my way a lot, and I find myself doing things to make it usable rather than being pleased by enhanced features.
It sounds like your plan is similar to mine, with the exception of the deltas for time. We're going to be getting 10Mb between our primary and secondary, as opposed to the 1.5Mb T1 we have right now, but they could be on the same network and it would still take me half an hour to do an rsync because it's got to index the files.
I'm currently keeping 1.3 million files (~450GB) in sync over that T1. Fortunately, there are usually only a few dozen GB a day, but sometimes there are more. It's madness, but we're improving it.
Slashdot Mirror
really? you've really never met a linux user? I'm afraid that you've had a very poor sampling of developers then.
Can't it be both?
Or maybe there will be more/better mission critical software available on Linux.
Or XP VMs will still be running fine
Awesome link. Thanks very much!
You seem very knowledgeable regarding filesystems in general. I'm interested in learning more about filesystems and how they work. To give you an idea of where I am, I believe I know what blocksize is, but I don't know what an extent is, and how it relates to performance (or why the grandparent would like extents several megabytes large).
What resources would you suggest to people who are looking to learn more?
I don't think I'm allowed to tell you the price they quoted me, but they're really friendly if you give them a call and ask for a quote. I don't think their prices are excessive at all. The steepest part is that there is an initial cost of purchasing a WORM (write once, read many) drive for archival purposes. The nice part of that is that the drive is yours. You take it if/when you cancel your service along with your discs.
If you'd like, I can get you in touch with my contact there.
Great, now they've got to deal with the same sort of things we do. Archiving every bit of email that comes into the system, and making sure it's available online for searching and retrieval.
I'm interested in how they're going to be doing it. I've been looking at Global Relay for my own mail archiving. I wonder what they'll end up going with. I asked this a while ago on my blog, too.
Looking at the edited photo, I have to wonder how they found out that it didn't come right out of the camera like that. I mean, I've seen quite a few 'shops in my time, and I got nothing. *cough*
What are you using to get Slack to auth against LDAP? Do you have an NIS/LDAP gateway or what?
Hi! This is offtopic, but as a former slackware admin, I've got to ask. How did you manage to scale it to a large environment?
I got to a few dozen machines and used to spend all my time patching and admining multiple users. I eventually moved to CentOS authenticated over AD with Likewise Open. I'm interested in hearing how other people do it.
Forgive me, because I'm a linux guy (that's all I've ever used and known), and because of that, I don't know what the benefits of having an AIX machine on the desktop would be.
I understand that on certain large hardware, AIX is preferable due to hardware or other requirements, but what is the draw on the desktop? Is there superior software, or stability? Management tools?
I manage Linux servers, and I have linux on my desktop because it seems effortless to me now, but I can't imagine that if I had one of the BSDs, Solaris, or any other unix that my experience would be different. What is the draw? I'm not flaming or trolling, I'm really interested in being educated.
I'd still pay to see that movie shot again from the military perspective, and to find out what happened after.
I dig the S.P.E.C.T.R.E.-like thing too
Radio shack used to have a clause like that too. They even claimed everything you produced for a year after you left. Laughable. As if my sales training there would lead to creating something useful.
He created a filesystem and named it after himself. It doesn't sound like he was down with the whole anonymity thing...
Sure. I keep them on my work computer, so I'll have to check when I get a chance there. Thanks for digging the idea.
wait, did you mean
grep '^[$#]'
?
Nice! Thanks!
I have to parse files with bash sometimes, and I use these:
^# = line with a leading comment
^$ = empty line
They're simple, but work usually. You can make them a lot more bullet proof by adding in blank checking between the characters, but it seems to work.
cat httpd.conf | grep -v \^\# | grep -v \^\$ | less
makes httpd.conf a lot more readable.
only 1 @, arbitrary number of .'s in either direction...
I don't know if a leading dot is valid. I like I don't know if you could have .com@slashdot.org
I think it's got to be prepended with an alphanumeric.
Yea, I stopped trying code I didn't understand the first time I tried the bash fork bomb
I like it, but I've got a bookmark folder called "Slash-doc" where I store useful threads that contain a lot of information.
I've got a lot of threads bookmarked.
Best Practices for Process Documentation
How would you make a distributed Office system
Quality Open Source / Calendar / Messaging Systems
and some others.
Some of the information in the threads is out of date, but the ideas are useful and interesting to read. I need to go back through Ask Slashdot and get the more recent threads that seem to act as references
new doesn't necessarily mean good.
If you like good, and old was good, but new is bad, guess which one you'd rather go with?
I think slashdot is usable, but it gets in my way a lot, and I find myself doing things to make it usable rather than being pleased by enhanced features.
That's just wrong and abusive of the system. Great for freaking people out, though
You've pretty much got to take netmask into account. Lots of valid IPs end with 0 and 255.
It sounds like your plan is similar to mine, with the exception of the deltas for time. We're going to be getting 10Mb between our primary and secondary, as opposed to the 1.5Mb T1 we have right now, but they could be on the same network and it would still take me half an hour to do an rsync because it's got to index the files.
I'm currently keeping 1.3 million files (~450GB) in sync over that T1. Fortunately, there are usually only a few dozen GB a day, but sometimes there are more. It's madness, but we're improving it.