User:Dramsey

• Asian fonts
• Bugs
• Communicate
• Docs Beat
• Fonts SIG
• IBus Input Method
• Input Methods
• Internationalization Project - I18N
• Localization Project - L10N

David Ramsey

About Dramsey

Email: MailTo (dramsey AT fedoraproject DOT org)

Dramsey with friends

Located on the far right of this picture (in the pink shirt,) I am a Fedora 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25 and 26 user currently experiencing the x86_64 and i686 versions. I am trying to integrate useful system administration ideas for my Fedora systems.

• I am very interested in large memory model programs and multi-core computer systems. I enjoy using virtual machines (VMs) in order to develop a formidable system solution. Through the use of VMs, I am able to try out a variety of software solutions on a VM prior to installation of the software on my production system.

• I have taken RH033VT, RH131VT, RH142VT, RH253VT, and RH301VT coursework, in order to further establish my Red Hat educational foundation.

• Recently, I have greatly enjoyed 24 hour access to the Live Access Labs running Red Hat Enterprise Linux 5. Now, I have the Red Hat Enterprise Linux 6 Beta running on a VM.

• My next training classes will be the "Red Hat Enterprise System Monitoring and Performance Tuning" - RH442VT, "Red Hat Enterprise Security: Network Services" - RHS333, and "Red Hat Enterprise SELinux Policy Administration" - RHS429 as well as "Red Hat Enterprise Linux Update Course" - RHUP305 and Red Hat Command Line Skills Virtual (RH190VT) - RH190VT
• Currently, I am reviewing "Building a Secure Computer System" by Morrie Gasser at the http://www.cs.unomaha.edu/~stanw/gasserbook.pdf URL and "Security Guide A Guide to Securing Fedora Linux Edition 14.2" at http://docs.fedoraproject.org/en-US/Fedora/14/html-single/Security_Guide/index.html URL.

• {Boost/Improve/Get Better} Gaming FPS & PC Performance!! --Optimize Your System - {Tutorial/Guide}

Virtual Machine Information

FYI on Virtual Machine Information integration

• Each VM has either 3072 MB of RAM for i686 guest systems or 8192 MB of RAM for x86_64 guest systems as well as two CPU cores allocated for execution and evaluation purposes within an established baseline VM system.
• My latest Fedora 12 (Constantine) kernel is 2.6.32.12-115.fc12.i686.PAE. I am very interested in progress in GRUB Ext4 support, NFSv4Default and NetworkManager System Connections
• Good to see how the iBus Intelligent Input Bus "input framework method system" and Ext4 file system "checksum feature for the journal" have developed.
• Very interesting to see how the Yum Langpack Plugin and the Udisks disk management improvements are proceeding.
• When I have the VMs running with 1536 MB of RAM, I am able to enjoy using VMs for executing my Fedora 9, 10, 11, and 12 systems. With the effective use of VMs, I am able to concurrently run 9 VMs on my workstation. There are three pictures at the bottom of this page:
  1. Left shows 1 VM with Fedora 11.
  2. Center shows 1 VM with Fedora 12.
  3. Right shows 4 VMs with 3 VMs on Fedora 9 and with 1 VM on Fedora 10.

Current running systems

Using embedded code have updates automatically done for running systems' status

x86_64 architecture systems

Version	Kernel	Status	Running	Memory	Swap space
Fedora 18 (Spherical Cow) one system running with VMware	3.11.10-100.fc18.x86_64		inprogress	8.0 GB	8.0 GB
Fedora 19 (Schrödinger's Cat) one system running with VMware	3.14.27-100.fc19.x86_64		inprogress	8.0 GB	8.0 GB
Fedora 20 (Heisenbug) one system running with VMware	4.0.5-100.fc20.x86_64		inprogress	8.0 GB	4.0 GB
Fedora 21 one system running with VMware	4.1.13-100.fc21.x86_64		inprogress	8.0 GB	4.0 GB
Fedora 22 one system running with VMware	4.2.6-200.fc22.x86_64		inprogress	8.0 GB	1.0 GB
Fedora 23 one system running with VMware	4.2.6-300.fc23.x86_64		inprogress	8.0 GB	1.0 GB
Fedora 24 one system running with VMware	4.3.0-1.fc24.x86_64		inprogress	8.0 GB	1.0 GB
Red Hat 7 (Beta) update link here with one system running with VMware	3.10.0-54.0.1.el7.x86_64		fail	8.0 GB	8.0 GB

i686 architecture systems

Version	Kernel	Status	Running	Memory	Swap space
Fedora 18 (Spherical Cow) one system running with VMware	3.11.10-100.fc18.i686		inprogress	3.0 GB	3.0 GB
Fedora 19 (Schrödinger's Cat) one system running with VMware	3.14.27-100.fc19.i686		inprogress	3.0 GB	3.0 GB
Fedora 20 (Heisenbug) one system running with VMware	4.0.5-100.fc20.i686		inprogress	3.0 GB	3.0 GB
Fedora 21 one system running with VMware	4.1.13-100.fc21.i686		inprogress	3.0 GB	3.0 GB
Fedora 22 one system running with VMware	4.2.6-200.fc22.i686		inprogress	3.0 GB	3.0 GB
Fedora 23 one system running with VMware	4.2.6-300.fc23.i686		inprogress	3.0 GB	3.0 GB
Fedora 24 one system running with VMware	4.3.0-1.fc24.i686		inprogress	3.0 GB	3.0 GB
Red Hat 6 (Beta) Beta one system running with VMware	2.6.32-19.el6.i686		inprogress	3.0 GB	4.0 GB
Red Hat 7 (Beta) update link here with one system running with VMware	3.10.0-54.0.1.el7.i686		fail	3.0 GB	4.0 GB

x86_64 and i686 kernels

January 03rd, 2011 Conceptual Drawing of x86_64 & i686 Interoperability

Where I get my x86_64 and i686 kernels - http://koji.fedoraproject.org/koji/packageinfo?packageID=8 Good information on http://kernelnewbies.org/LinuxChanges about Linux Changes especially the Linux 4.11 kernel.

system core and memory utilization

With 2017, another 24 cores and 192 GB of memory. Before I had been re-evaluating and determining how to best utilize the 96 cores and 336 GB of memory for effective systems. A periodic review of system resources is essential to providing an effective reallocation of system resources similar to the asset management theory.

• Seven x86_64 systems with two cores each, running about 112 GB of memory.

• Three i686 systems with two cores each, running about 12 GB of memory.

• Total allocated memory for systems will be ranging at about 124 GB of memory and will leave about 8 GB of memory free and four cores for the host systems operations.

• Eight x86_64 systems with two cores each, running about 128 GB of memory.

• Two i686 systems with two cores each, running about 8 GB of memory.

• Total allocated memory for systems will be ranging at about 136 GB of memory and will leave about 56 GB of memory free and four cores for the host systems operations.

• Consider implementing High-Availability (HA) between the systems.
  • High Availability
  • Linux-HA
  • How To Use pfSense To Load Balance Your Web Servers
  • HowtoForge High-Availability Tutorials
  • High availability and scalability of fedora commons
    • Fedora Commons
      1. Fedora Commons Examples
      2. Fedora Commons Features
  • Pacemaker
    • Make a Website Highly Available with IP Failover, Heartbeat and Pacemaker on Fedora 13
  • HA Cluster Infrastructure
  • Tool Set pdf file

• See the x86_64 and i686 interoperability system diagram for the system topology.

• Add additional resource diagrams.

• Place SELinux reference URLs, here.

• Place Virtual Machine description URLs, here.

• Parallel Programming "Food for thought" - Is Parallel Programming Hard, And, If So, What Can You Do About It?

• With the new motherboard at Supermicro® 4-CPU H8QGi+-F AMD® SR5690 Supermicro® 4-CPU H8QGi+-F image with 4x AMD® Opteron™ 6272 2.1GHz- 3.1GHz Max.Turbo-64Bit 16-Core. Total of 64 cores with an initial install of 64 GB of memory and a maximum 1 TB of memory. The total of 80 cores with 144 GB of memory is done.

Supermicro 4-CPU H8QGi+-F image

Software which I like to have running on my systems

Here are some relevant system administrator links: Red Hat Magazine - try searching for the RHCE Tips and Tricks opensource.com - The open source story continues to grow The Geek Stuff - good to review Linux in a Nutshell, 5th Edition - directory of Linux commands 10 Sites Offering Free Linux Courses Online - free online learning 13 Of the Best Linux Tutorials and OpenCourseWare on the Web - free tutorials 12 Amazing and Essential Linux Books To Enrich Your Brain and Library - recommended books Red Hat Enterprise Linux - Academic Editions Server - practice on Red Hat based systems

1. aide
2. dsniff
3. hdparm
4. iotop
5. logwatch
6. nmap
7. ntop (considering)
8. tripwire
9. wireshark
10. xosview
11. Iperf
12. ns-2

Some system information

Food for thought

This is a tip
My current workstation has eight (8) x86_64 computing cores and 16 GB of RAM as well as four 500 GB harddisks (SATA Seagate 7200.12.) The Seagate 7200.12, 500 GB harddisk is only "one" platter and is very quiet as well as very low power consumption and fast for my use. I am considering a plan on doing an upgrade to the Seagate 7200.12, 1 TB harddisk next calendar year. Another workstation has arrived with eight (8) x86_64 computing cores and 64 GB of RAM.

Another tip
Google's IPV6 web site - http://ipv6google.com/ try it.

This is important
A finding on my behalf regarding concurrent guest operating systems is to keep the ntp time clock in sync between the variety of guest VMs.

This is something else important
Fedora 12 Alpha with 3072MB of RAM. After that amount of 3 Gigabytes (GB) RAM, the 32-bit kernel is abending. Also, the "Swap" space is defined about 4 GB.

This is a note
The Fedora 11 and Fedora 12 Alpha version's "Swap" space are defined about 3 GB, versus the Fedora 9 and 10 versions' "Swap" space are defined about 2 GB when all versions were provided 1.5 GB of RAM.

This is an additional note
At this time, I am not really very impressed with the dracut product. The dracut execution time was about 15-25 minutes to update my kernels dependent on the virtual machine being used. As of September 22nd, 2009, I have used dracut about 40+ times. Maybe when the F12 Beta and/or F12 Final Release are made, dracut will be better. Update, with F12 Beta and RCs, the dracut execution time is now about 2-3 minutes.

This is a warning
A little FYI on updating to the 2.6.31-2.fc12.i686 and 2.6.31-2.fc12.i686.PAE kernels, a separate rpm install was needed of the bindutils-2.19.51.0.14-31.fc12.i686.rpm package from the original install media's iso, in order to address the bindutils dependency prior to updating to the 2.6.31-2.fc12.i686 and 2.6.31-2.fc12.i686.PAE kernels.

This is a caution
Currently, the Virtual PC 6.0.156.0 and the F12 Alpha iso are having some serious problems with getting X to work. Therefore, my /etc/inittab file on those test subsystems is set to run at runlevel 3 instead of 5.

Previous running systems

Version	Kernel	Status	Memory	Swap space
Fedora 9 (Sulphur)	2.6.27.25-78.2.56.fc9.i686		1.5 GB	2.0 GB
Fedora 10 (Cambridge)	2.6.27.30-170.2.82.fc10.i686		1.5 GB	2.0 GB
Fedora 11 (Leonidas)	2.6.30.5-43.fc11.i586 and 2.6.30.5-43.fc11.i686.PAE	and	1.5 GB and 1.5 GB	3.0 GB
Fedora 12 (Constantine) Alpha	2.6.31-33.fc12.i686 and 2.6.31-33.fc12.i686.PAE	and	1.5 GB and 1.5 GB	3.0 GB
Fedora 12 (Constantine) Alpha, Beta, and RC two systems running with VMware Hardware Profile 1Hardware Profile 2	2.6.32.26-175.fc12.i686.PAE	and	3.0 GB	4.0 GB
Fedora 13 (Goddard) two systems running with VMware Hardware Profile 3 Hardware Profile 4	2.6.34.7-66.fc13.i686.PAE	and	3.0 GB	4.0 GB
Fedora 13 (Goddard) Beta and Security Spin two systems running with VMware Hardware Profile 5 Hardware Profile 6	2.6.33.5-112.fc13.i686.PAE	and	3.0 GB	4.0 GB
Fedora 14 (Laughlin) three systems running with VMware Hardware Profile 11	2.6.35.14-106.fc14.x86_64		8.0 GB	4.0 GB
Hardware Profile 12	2.6.35.14-106.fc14.x86_64		8.0 GB	8.0 GB
Hardware Profile 8	2.6.35.14-106.fc14.i686.PAE		3.0 GB	4.0 GB
Fedora 14 (Laughlin) one system running with VMware Hardware Profile 10	2.6.35.14-106.fc14.x86_64		8.0 GB	4.0 GB
Fedora 14 (Laughlin) Rawhide and Beta one system running with VMware Hardware Profile 7	2.6.35.14-106.fc14.i686.PAE		3.0 GB	4.0 GB
Fedora 15 (Lovelock) Rawhide one system running with VMware Hardware Profile 13	2.6.43.8-2.fc15.x86_64		8.0 GB	4.0 GB
Fedora 15 (Lovelock) Rawhide one system running with VMware need Hardware Profile 9 data	2.6.43.8-2.fc15.i686		3.0 GB	0.0 GB
Fedora 16 (Verne) two systems running with VMware
Hardware Profile 14	3.6.11-7.fc16.x86_64		8.0 GB	4.0 GB
need Hardware Profile 15 data	3.6.11-7.fc16.x86_64		8.0 GB	4.0 GB
Fedora 16 (Verne) one system running with VMware need Hardware Profile 16 data	3.6.11-7.fc16.i686		3.0 GB	0.0 GB
Fedora 17 (Beefy Miracle) one system running with VMware	3.9.10-100.fc17.x86_64		8.0 GB	0.0 GB
Fedora 17 (Beefy Miracle) one system running with VMware	3.9.10-100.fc17.i686		3.0 GB	0.0 GB

Locations

1. Tokyo, Japan &
2. The University of Maryland - College Park, Maryland

Dancing penguin

Projects

Fedora Purchases

I purchased my Fedora Polo Shirts here at, Custom-embroidered logo shirts and apparel by Queensboro located in North Carolina, for $9.⁹⁵ each or Fedora Hat for $5.⁹⁵, including shipping. The place is called, "http://www.queensboro.com/" use this information for the Fedora Logo.

I purchased my Fedora Buttons here at, Custom Buttons, Promotional Buttons located in Ohio, for $18.⁰⁰ (100 quantity,) including shipping

To facilitate phone calls around the world, I use unlimited world Skype for only $12.⁹⁵ per month or free Skype to Skype chat, audio, and video for "Windows, Mac OS X or Linux" even for "iPhone."

Things I do

Both x86_64 and i686 versions of Fedora 9, Fedora 10, Fedora 11, Fedora 12, Fedora 13, Fedora 14, Fedora 15, Fedora 16, Fedora 17, Fedora 18 and Fedora 19 DVDs and USB Distribution in Japan see Akihabara "Electric City" and The University of Maryland - College Park, Maryland

Fedora Ambassadors Spreads Fedora around the globe Fedora Ambassador for Japan and Maryland

System Data URLs

1. How do I know how many file descriptors are being used system-wide in Red Hat Enterprise Linux?
2. Operating System Tuning Parameters
3. Phoenix/Tools

Fedora_9_and_Fedora_10

Fedora_11

Fedora_12_Sun_VirtualBox