Interesting that they've expanded to a dual-processor setup with mini-itx. I suspect (and hope) that the next thing we see from the mini-itx world are mini-itx based blade-based computers. Something set at a price point at under $500 per blade w/ a 120G SATA HD, and 512M of memory. Would be great for the in-expensive server market. But then again, what do I know...
Ok, first off, and I cant stress this enough - two conduit tubes per wall per room. Excepting the bathroom. This conduit can be used in the future, even without being populated. This way, there is nothing to really "retrofit". I would say to use 1 - 1 1/2" conduit.
Now, if you have the $$ - I would recomend laying fiber. Remember, even though you put conduit in - your fiber must be put into flex tube for protection. I would put two runs of each single mode and multi mode fiber. Unless your certified in terminating it, I would have a licensed/certified person terminate the fiber into connections.
Do you plan on having an audio system? Maybe not now, but in the future? Make sure to run an extra conduit, and cut a zip box into the top corner of each room. Bathroom included on this one. And dont forget, some high end systems can use fiber to connect the speakers. I would say to put fiber, cat5, and coax into these drops.
You mentioned wireless. I would use wrap boards with cealing mount antennas. Put some conduit into the cealing - with a 1'x1' lockable box that becomes part of the cealing. If you run MikroTik's level 5 router os the units, you can have multiple AP's act as one, run WPA/WPA2, and for PC devices, also have them use IPSec back into a "Private" network.
TV? Yep, I would run seperate conduit for this - Pick logical locations for this. One in the bathroom too. You never know, you could want to put a little 13" tv in there for the umm.. rest breaks.
If you haven't already confirmed the building plan, I would take an area in the home, and put a 6x6 equipment room in. This is where all the conduit would terminate. Buy an equipment rack, and stud in into the floor there. But a couple patch pannels, I'm fond of the panduit minicom modular 48 port patch pannels, however, anything will work. Buy a fiber termination box for the rack as well. Put your phones into 66 blocks on the wall. I would also use cat5 for my phones, and not cat3. With the cost of cat5 being so low, it just makes sense. I would also use cat6 for the network in a new install.
Thought of VoIP? This sets you up great for it. You have a central place to put your VoIP server in, and connect it back into your PSTN network.
Anyway, Just some design thoughts. Hope they help.
Here are some simple policies I practice:
1. Unless currently being used, the computer remains at an "off" state.
2. Change your passwords often - how often is up to you, but be reasonable. I suggest 30 to 60 days for medium/low security, and 7 days for higher security. Remember, however, that any password can be breeched - it's just a matter of time.
3. Segregate your network (if you have one) into zones.
For Instance - You should not put your wireless access point straight off your network, instead, come off of your firewall in a new "wireless" zone. Terminate all wireless connection into your firewall via ipsec. Do not rely on WEP/WPA.
4. Block all outbound and inbound ports on your firewall, until you need them. I.E, don't just open up port 80 because you/think/ that you/might/ just run a web server.
5. Virus scanner.
6. Password protect/does not/ imply encrypt.
Anyway, these are just some basic concepts that are OS independent, and if your average user followed some of these guidelines, we'd all be in a better position.
IMHO, I feel that in the long run, your college degree really only matter to your mother. There are a few exceptions - MIT being one of them.
What really matters is the person. I didn't finish college, left in my sophomore year to take a job paying 85K. Turned out to a be a dot-bomb, but it was still good money. I've gone on to own several business's, work for several large companies, and currently own two ISP's, and work a security analyst for a hospital.
We recently hired a new graduate, out of a well known university. In doing this, I've seen that what you learn in college will not apply in the real world anyway. Your first real employer will have you forget everything you've learned, and re-teach you to do things the way they want them. This will continue with every subsequent employer until you reach a position that has Sr. in the title, at which time you will be the one making your new-hires forget what they've learned, and have them do things the way you (or your company policies) want them to.
So, in summation, my long winded point is this:
It really, really, does not matter what education you have listed in your resume, as long as you have a good work history, a good work ethic, and are capable of doing everything you say you can.
And if, by chance, you don't finish college - YOUR MOTHER WILL BUG YOU FOREVER ABOUT IT - especially around the holidays.
I would like to eat at The Restaurant at the End of the Universe before I die. I would probably have the steak, as I hear it's quite good, and then watch the destruction and rebirth of it all. Would anyone like to join me?
How do you feel about Ubuntu Linux in the enterprise environment? How will security and managability be handled, will you release your own tools for this? or will you use exsisting packages, optimized for Ubuntu? Or is Ubuntu going to be more geared twords the home user, with Redhat gaining in the area of Enterprise desktop viability. Also, as a whole, what is your opinion of linux in the work environment as an enterprise desktop?
Slashdot Mirror
Interesting that they've expanded to a dual-processor setup with mini-itx. I suspect (and hope) that the next thing we see from the mini-itx world are mini-itx based blade-based computers. Something set at a price point at under $500 per blade w/ a 120G SATA HD, and 512M of memory. Would be great for the in-expensive server market. But then again, what do I know...
Interesting, but will it work on a dead badger running GNU/Linux? Cause thats where do all my development work.
Utah will lead the nation is squelching peoples first amendment rights. Woohoo! We don't need no stinkin freedom.
Ok, first off, and I cant stress this enough - two conduit tubes per wall per room. Excepting the bathroom. This conduit can be used in the future, even without being populated. This way, there is nothing to really "retrofit". I would say to use 1 - 1 1/2" conduit.
Now, if you have the $$ - I would recomend laying fiber. Remember, even though you put conduit in - your fiber must be put into flex tube for protection. I would put two runs of each single mode and multi mode fiber. Unless your certified in terminating it, I would have a licensed/certified person terminate the fiber into connections.
Do you plan on having an audio system? Maybe not now, but in the future? Make sure to run an extra conduit, and cut a zip box into the top corner of each room. Bathroom included on this one. And dont forget, some high end systems can use fiber to connect the speakers. I would say to put fiber, cat5, and coax into these drops.
You mentioned wireless. I would use wrap boards with cealing mount antennas. Put some conduit into the cealing - with a 1'x1' lockable box that becomes part of the cealing. If you run MikroTik's level 5 router os the units, you can have multiple AP's act as one, run WPA/WPA2, and for PC devices, also have them use IPSec back into a "Private" network.
TV? Yep, I would run seperate conduit for this - Pick logical locations for this. One in the bathroom too. You never know, you could want to put a little 13" tv in there for the umm.. rest breaks.
If you haven't already confirmed the building plan, I would take an area in the home, and put a 6x6 equipment room in. This is where all the conduit would terminate. Buy an equipment rack, and stud in into the floor there. But a couple patch pannels, I'm fond of the panduit minicom modular 48 port patch pannels, however, anything will work. Buy a fiber termination box for the rack as well. Put your phones into 66 blocks on the wall. I would also use cat5 for my phones, and not cat3. With the cost of cat5 being so low, it just makes sense. I would also use cat6 for the network in a new install.
Thought of VoIP? This sets you up great for it. You have a central place to put your VoIP server in, and connect it back into your PSTN network.
Anyway, Just some design thoughts. Hope they help.
Here are some simple policies I practice: /think/ that you /might/ just run a web server.
/does not/ imply encrypt.
1. Unless currently being used, the computer remains at an "off" state.
2. Change your passwords often - how often is up to you, but be reasonable. I suggest 30 to 60 days for medium/low security, and 7 days for higher security. Remember, however, that any password can be breeched - it's just a matter of time.
3. Segregate your network (if you have one) into zones. For Instance - You should not put your wireless access point straight off your network, instead, come off of your firewall in a new "wireless" zone. Terminate all wireless connection into your firewall via ipsec. Do not rely on WEP/WPA.
4. Block all outbound and inbound ports on your firewall, until you need them. I.E, don't just open up port 80 because you
5. Virus scanner.
6. Password protect
Anyway, these are just some basic concepts that are OS independent, and if your average user followed some of these guidelines, we'd all be in a better position.
IMHO, I feel that in the long run, your college degree really only matter to your mother. There are a few exceptions - MIT being one of them. What really matters is the person. I didn't finish college, left in my sophomore year to take a job paying 85K. Turned out to a be a dot-bomb, but it was still good money. I've gone on to own several business's, work for several large companies, and currently own two ISP's, and work a security analyst for a hospital. We recently hired a new graduate, out of a well known university. In doing this, I've seen that what you learn in college will not apply in the real world anyway. Your first real employer will have you forget everything you've learned, and re-teach you to do things the way they want them. This will continue with every subsequent employer until you reach a position that has Sr. in the title, at which time you will be the one making your new-hires forget what they've learned, and have them do things the way you (or your company policies) want them to. So, in summation, my long winded point is this: It really, really, does not matter what education you have listed in your resume, as long as you have a good work history, a good work ethic, and are capable of doing everything you say you can. And if, by chance, you don't finish college - YOUR MOTHER WILL BUG YOU FOREVER ABOUT IT - especially around the holidays.
I would like to eat at The Restaurant at the End of the Universe before I die. I would probably have the steak, as I hear it's quite good, and then watch the destruction and rebirth of it all. Would anyone like to join me?
How do you feel about Ubuntu Linux in the enterprise environment? How will security and managability be handled, will you release your own tools for this? or will you use exsisting packages, optimized for Ubuntu? Or is Ubuntu going to be more geared twords the home user, with Redhat gaining in the area of Enterprise desktop viability. Also, as a whole, what is your opinion of linux in the work environment as an enterprise desktop?