The Cochise Linux user Group in conjunction with the Ubuntu-Arizona Local Community Team will be conducting their third Installation Festival on 28 October 2017, 10-4pm at the University of Arizona South Learning Resource Center, 1140 N. Colombo Ave. Sierra Vista AZ.
Welcome to the Ubuntu-Arizona LoCo Team Website. We are an "Approved" Ubuntu LoCo Team, and a volunteer organization within the State of Arizona who are committed to Ubuntu advocacy and education. Our goal is to increase the public awareness and use of Ubuntu and Open Source in our state. Working with the state LUG's to pool our resource and expand our out reach is essential to meeting our goals. We follow the Ubuntu Code of Conduct. **Membership: Join our Team!**
It is time for the AZLOCO Team to be re-verified by the LoCo Council. We are on the agenda for their 12 September 2017 meeting at 2000 UTC (1300 our time). The meeting will take place on #Ubuntu-meeting on irc.freenode.net. Attend the meeting if you can to support your local Team.
This is a recent email to the ubuntu-devel mailing list that describes not only recent changes to the do-release-upgrade process, but how it works in general. It is also posted here.
If you are unaccustomed to the command-line...first of all, you should learn the command line. But for now, the do-release-upgrade utility is used to upgrade from one Ubuntu release to another. The graphical desktop utility utilizes this as well.
During today's installfest we had a system with keyboard issues. The specific details were this: An ASUS laptop E200H, ubuntu 17.04 with gnome, and an encrypted hard drive. The system booted up to the screen where it requests the disk encryption password. At this point in time, the system did not allow the use of the laptop's keyboard. It did however recognize an external USB keyboard.
This is a handy tool if ever find you need a Lan and only have wifi and a laptop/Desktop with wifi
and work on most distros of linux
step 1. Connect to the wifi
step 2. Open Network Manager (Gnome) Click edit connections,
step 3. Click add, Ethernet should be viewed then create it and name it Wifi Tether
step 4. on the general tab uncheck automatically connect to this network when it is available
step 5. on the IPv4 Settings Tab, change Automatic (DHCP) to Shared to other computers
I have 10 Proxmox servers to maintain all are basically the same, AMD FX 8350 CPU and asus motherboards with several more servers coming soon. FX 8350's are known to run hot and stock coolers weak per web searches. AMD just released a new wraith Cooler to help this issue. Time to figure out if there is a issue and how to fix it if there is a problem.
Testing (this should work on any debian based system)
sudo apt-get install lm-sensors (a program to check system sensors including temp)