The term you are looking for is "vision impaired", which means: people who have a lack of vision (blind) or have poor vision. The term "visually impaired" means: ugly.
Because it's not distributed, it's not redundant, and it's not scalable in the way I want it to be.
The scheme I'm proposing would be able to tie together 40 x 40GB/home partitions into one redundant, scalable, network-wide/home partition of about 800GB or so.
I have an office full of computers, relatively new-ish, all running Linux, all with 80-160GB hard drives.
I section off a part of each disk for OS -- root, usr, var, etc.
The rest is/home.
What I'd really like is to tie the/home partitions together in one single network-wide, redundant file system.
Here's how I'd plan it out:
Start with something like the NBD (kernel level network block device). Have a distributed block hash of some kind, mapping each virtual block to one or more physical blocks. Make that layer support redundancy, so that each block was repeated (or 3 for 2 checksummed, as in RAID) elsewhere on the network, so that the distributed block driver could survive at least one machine going down (later: build in multiple levels of redundancy so that blocks get mirrored in multiple places, and the virtual block driver could survive multiple machine failures).
Build a file system on top of that, just like regular NBD.
Now I'm not a file system guru but I expect this can be done with the right amount of cash inflow.
VMS is my favourite bug
on
Pet Bugs?
·
· Score: 2, Funny
My favourite bug from the VMS days is the one that reported, under certain conditions:
Warning: Hardware or software error.
... which was immensely useful, and narrowed the problem down to one of two things.
Here's an article on doing what you want, using Active Directory. It's not a good solution (NDS eDirectory is better, like others have posted) but it does work:
As the author of the SecurityFocus article in question, I'd just like to answer a few comments:
* Yup, I found this an interesting project for a number of reasons. It was WAY easier to set up than a standard Linux distro, but be aware that's because it has ONE purpose and one only -- to be a firewall. This is good and bad. As a simple, easy to install firewall system, I like it.
* I haven't played with www.dubbelle.com but I'll be sure to check it out shortly. There are lots of other good cut-down distros out there, and I'm sure there is place for all of them. The one advantage that IPCop has over a single floppy distro is a few extra features such as squid and IPSec.
* Sorry, the article really was meant to be a how-to, rather than a review. I'm sorry about those who were dissapointed expecting more of a review article but I prefer to write in the more practical sense. If you want a review, here's a one word one: GOOD. I'd be interested to hear what one poster (sloop) found "lacking" in the article, however.
* I hereby refuse to make any comment concerning Richard Morrell.
* Yup, Astaro is a fine distro too, and no doubt the fine folks at SecurityFocus will probably review it as well. I'm not that familiar with it myself so no doubt they'll get someone else to do the review.
I noticed a lot of stuff is missing from Mandrake 7.0. Like MySQL 3.22.x (retrograded to the GPL 3.20 version), midgard, etc. Also the PHP modules for LDAP and MySQL aren't there. Does anyone know where these have gone?
Its a business decision. Wrong or not. Nvidia has chosen to support their larger market (or perceived larger market). Can't fault them for that. But the great thing about the Unix community is that we are pretty much self supporting. With a spec we could write our own drivers, but even this they fail to do.
Damnit.
Goes off to dig out ye olde Voodoo 1
Incidentally can anyone point me to information on setting a voodoo 1 up in Debian? Only been running it for a week, replacing FreeBSD so be gentle. Oh, and someone have the possible jumper settings for an AWE-32? mutter . . . mutter Internal Modem . . . mutter
Slashdot Mirror
The term you are looking for is "vision impaired", which means: people who have a lack of vision (blind) or have poor vision. The term "visually impaired" means: ugly.
Should also mention the other members of the team that cooperated with Sol1 to get on the panel:
Babel Com Australia (us): www.babel.com.au
Les Bell & Associates: www.lesbell.com.au
Si2: www.si2.com.au
Because it's not distributed, it's not redundant, and it's not scalable in the way I want it to be.
/home partitions into one redundant, scalable, network-wide /home partition of about 800GB or so.
:)
The scheme I'm proposing would be able to tie together 40 x 40GB
Server-less networking for the masses.
I have an office full of computers, relatively new-ish, all running Linux, all with 80-160GB hard drives.
/home.
/home partitions together in one single network-wide, redundant file system.
I section off a part of each disk for OS -- root, usr, var, etc.
The rest is
What I'd really like is to tie the
Here's how I'd plan it out:
Start with something like the NBD (kernel level network block device). Have a distributed block hash of some kind, mapping each virtual block to one or more physical blocks. Make that layer support redundancy, so that each block was repeated (or 3 for 2 checksummed, as in RAID) elsewhere on the network, so that the distributed block driver could survive at least one machine going down (later: build in multiple levels of redundancy so that blocks get mirrored in multiple places, and the virtual block driver could survive multiple machine failures).
Build a file system on top of that, just like regular NBD.
Now I'm not a file system guru but I expect this can be done with the right amount of cash inflow.
My favourite bug from the VMS days is the one that reported, under certain conditions:
Warning: Hardware or software error.
... which was immensely useful, and narrowed the problem down to one of two things.
Here's an article on doing what you want, using Active Directory. It's not a good solution (NDS eDirectory is better, like others have posted) but it does work:
http://online.securityfocus.com/infocus/1563
As the author of the SecurityFocus article in question, I'd just like to answer a few comments:
* Yup, I found this an interesting project for a number of reasons. It was WAY easier to set up than a standard Linux distro, but be aware that's because it has ONE purpose and one only -- to be a firewall. This is good and bad. As a simple, easy to install firewall system, I like it.
* I haven't played with www.dubbelle.com but I'll be sure to check it out shortly. There are lots of other good cut-down distros out there, and I'm sure there is place for all of them. The one advantage that IPCop has over a single floppy distro is a few extra features such as squid and IPSec.
* Sorry, the article really was meant to be a how-to, rather than a review. I'm sorry about those who were dissapointed expecting more of a review article but I prefer to write in the more practical sense. If you want a review, here's a one word one: GOOD. I'd be interested to hear what one poster (sloop) found "lacking" in the article, however.
* I hereby refuse to make any comment concerning Richard Morrell.
* Yup, Astaro is a fine distro too, and no doubt the fine folks at SecurityFocus will probably review it as well. I'm not that familiar with it myself so no doubt they'll get someone else to do the review.
Del
I noticed a lot of stuff is missing from Mandrake 7.0. Like MySQL 3.22.x (retrograded to the GPL 3.20 version), midgard, etc. Also the PHP modules for LDAP and MySQL aren't there. Does anyone know where these have gone?
In case anyone else out there was looking for similar information:
3Dfx-HOWTO
Sound HOWTO
Still need AWE jumper settings, had the card for about 4 years, lord knows where the manuals are.
Its a business decision. Wrong or not. Nvidia has chosen to support their larger market (or perceived larger market). Can't fault them for that. But the great thing about the Unix community is that we are pretty much self supporting. With a spec we could write our own drivers, but even this they fail to do.
Damnit.
Goes off to dig out ye olde Voodoo 1
Incidentally can anyone point me to information on setting a voodoo 1 up in Debian? Only been running it for a week, replacing FreeBSD so be gentle. Oh, and someone have the possible jumper settings for an AWE-32? mutter . . . mutter Internal Modem . . . mutter