https://ols2006.108.redhat.com/2007/Reprints/
These are the pdf form of presentations various Linux developers gave at that meeting. A lot of it is very interesting...
For example you can learn about Ultrawideband wireless and the state of Linux support at:
https://ols2006.108.redhat.com...z-gonzalez-Reprint.pdf
Or what is realy going on and what is wrong and what is right about Linux ACPI support..
https://ols2006.108.redhat.com...ts/brown_1-Reprint.pdf
Linux is now the defacto-standard OS used in the telecommunications industry, replacing hugely expensive custom software, Unix systems, and hardware. How does Linux performance and aviability work into this and proposes the creation of a 'PAC' tool to help end users monitor and analyze these important metrics.
https://ols2006.108.redhat.com...nts/linkov-Reprint.pdf
The one that I found pretty interesting was about leasons learned about Nortel's large scale Linux roll out.
https://ols2006.108.redhat.com.../szeideman-Reprint.pdf
If you have 291,000 computers on 350 different locatiosn with 8000 subnets.. all of them running half a dozen different operating systems.. How do you integrate Linux to it and save money?
Well the answer is a Linux SOE. SOE is a 'standard operating environment'. It's a custom Linux release developed by Nortel using a combination of a commercially supported off the shelf Linux distribution (Redhat), third party packages, and Nortel's own packages, standardized hardware platform, and infrastructure to deploy, configure and install Linux on a massive scale.
The OS is built on a stack..
Level 0 is the hardware
Level 1 is the Vendor OS.
Level 2 is the Global config -- packages and configurations common to everyone.
Level 3 is the Location Specific -- configurations specific to a paticular reagion, they use cfengine for configuring large numbers of systems centrally
Level 4 is Group Specific -- packages/programs only used by paticular groups.
Level 5 is Patching -- follow up on security updates, software updates, and other things.
I figure a lot of what they are talking about applies to most any reasonably sized company wanting to use Linux. It's probably the the different between having a cheap and managable custom Linux setup for a paticular business vs having a nasty hard to manage and expesive mess on your hands.
These are the pdf form of presentations various Linux developers gave at that meeting. A lot of it is very interesting...
For example you can learn about Ultrawideband wireless and the state of Linux support at:
https://ols2006.108.redhat.com...z-gonzalez-Reprint.pdf
Or what is realy going on and what is wrong and what is right about Linux ACPI support..
https://ols2006.108.redhat.com...ts/brown_1-Reprint.pdf
Linux is now the defacto-standard OS used in the telecommunications industry, replacing hugely expensive custom software, Unix systems, and hardware. How does Linux performance and aviability work into this and proposes the creation of a 'PAC' tool to help end users monitor and analyze these important metrics.
https://ols2006.108.redhat.com...nts/linkov-Reprint.pdf
The one that I found pretty interesting was about leasons learned about Nortel's large scale Linux roll out.
https://ols2006.108.redhat.com.../szeideman-Reprint.pdf
If you have 291,000 computers on 350 different locatiosn with 8000 subnets.. all of them running half a dozen different operating systems.. How do you integrate Linux to it and save money?
Well the answer is a Linux SOE. SOE is a 'standard operating environment'. It's a custom Linux release developed by Nortel using a combination of a commercially supported off the shelf Linux distribution (Redhat), third party packages, and Nortel's own packages, standardized hardware platform, and infrastructure to deploy, configure and install Linux on a massive scale.
The OS is built on a stack..
Level 0 is the hardware
Level 1 is the Vendor OS.
Level 2 is the Global config -- packages and configurations common to everyone.
Level 3 is the Location Specific -- configurations specific to a paticular reagion, they use cfengine for configuring large numbers of systems centrally
Level 4 is Group Specific -- packages/programs only used by paticular groups.
Level 5 is Patching -- follow up on security updates, software updates, and other things.
I figure a lot of what they are talking about applies to most any reasonably sized company wanting to use Linux. It's probably the the different between having a cheap and managable custom Linux setup for a paticular business vs having a nasty hard to manage and expesive mess on your hands.
Facebook
Twitter