tester-wiki
15127
Comment:
|
15095
Fixed some typos.
|
Deletions are marked like this. | Additions are marked like this. |
Line 44: | Line 44: |
## The best way to get a devlopment release from an '''existing install of Ubuntu''' is to follow these | ## The best way to get a development release from an '''existing install of Ubuntu''' is to follow these |
Line 61: | Line 61: |
Link for Trusty launchpad. |
|
Line 75: | Line 73: |
[[http://cdimage.ubuntu.com/daily-live/current/|Trsuty Tahr Daily Image ISOs]] | [[http://cdimage.ubuntu.com/daily-live/current/|Trusty Tahr Daily Image ISOs]] |
Line 131: | Line 129: |
How to find your souces.list- this list is used to set repositories and can be done manually. It is also informative to have on hand if you decide to do a transitional upgrade from Oneiric Ocelot to Precise Pangolin or upcomming Trusty Tahr. | How to find your sources.list - this list is used to set repositories and can be done manually. It is also informative to have on hand if you decide to do a transitional upgrade from Oneiric Ocelot to Precise Pangolin or upcoming Trusty Tahr. |
Line 139: | Line 137: |
Here is a list of commonly used Ubuntu/Linux terminal Codes (not neccessarily in order and open to interpretation) of TT Crash Recovery Codes -To be updated: | Here is a list of commonly used Ubuntu/Linux terminal Codes (not necessarily in order and open to interpretation) of TT Crash Recovery Codes -To be updated: |
Line 143: | Line 141: |
{{attachment:hover1bak.png|1. This command is used to auto edit the sources.list file on an install of Suacy Salamander or Raring Ringtail and could be considered as a first step to converting to Trusty Tahr. However this and other commands may be moot after Alpha .iso are released. You can still play it safe and test the kernels but breakage may occur nonetheless.}} '''sudo sed -i 's/saucy/trusty/g' /etc/apt/sources.list''' | {{attachment:hover1bak.png|1. This command is used to auto edit the sources.list file on an install of Saucy Salamander or Raring Ringtail and could be considered as a first step to converting to Trusty Tahr. However this and other commands may be moot after Alpha .iso are released. You can still play it safe and test the kernels but breakage may occur nonetheless.}} '''sudo sed -i 's/saucy/trusty/g' /etc/apt/sources.list''' |
Line 153: | Line 151: |
{{attachment:hover1bak.png|5.This command is an essential command if you are a elementary beta tester as it will upgrade the GRUB bootloader after changes to the system using other commands, are made (like upgrading a kernel). If you have tried to carry out a proceedure and wonder why it had not taken effect on the next boot, it is likely that you did not sudo update-grub.}} '''sudo update-grub''' | {{attachment:hover1bak.png|5.This command is an essential command if you are a elementary beta tester as it will upgrade the GRUB bootloader after changes to the system using other commands, are made (like upgrading a kernel). If you have tried to carry out a procedure and wonder why it had not taken effect on the next boot, it is likely that you did not sudo update-grub.}} '''sudo update-grub''' |
Introduction
Say hello to Trusty Tahr. -- twocamels 2013-04-27 16:24:11
New Beta Testers Warnings
Trusty Tahr is the codename for the new development cycle. If you are a new Beta tester and want to upgrade your repositories to the new development cycle then you must be advised that there are certain risks of breakage that could take place on your system(s). it is always advised that you have an extra system (hardware) or an extra harddrive to experiment with. If you are not familiar with experimenting with computer hardware or software then U+1 is not the forum for you, however, if you are willing to be on the cutting edge of Ubuntu release and understand that there could be breakage and want to contribute then the Ubuntu community welcomes you and your valued contributions.
New Notes About the Release Schedule
Notes and Links to be forthcoming when they are made available.
Download ISO
Some sudo Command Definitions
sudo basically means superusers-do. It is the basic command that gives access to administrative files that may need root authentication. There is a large database on sudo and sudoers definitions and uses in the following links. SudoUbuntuManuals and SudoersUbuntuManual
Here are some common codes of interest to help with Trusty recovery in the event of a crash.
How to find your sources.list - this list is used to set repositories and can be done manually. It is also informative to have on hand if you decide to do a transitional upgrade from Oneiric Ocelot to Precise Pangolin or upcoming Trusty Tahr.
gksu gedit /etc/apt/sources.list
Here is a list of commonly used Ubuntu/Linux terminal Codes (not necessarily in order and open to interpretation) of TT Crash Recovery Codes -To be updated:
sudo sed -i 's/saucy/trusty/g' /etc/apt/sources.list
sudo apt-get update && sudo apt-get dist-upgrade
sudo apt-get update
sudo apt-get upgrade
aptitude update && aptitude safe-upgrade
sudo update-grub
lspci
uname -a
lsb_release -a
sudo dpkg -i --configure -a
sudo reboot sudo poweroff
sudo apt-get -f install
sudo apt-get -f remove
sudo apt-get purge nvidia*, sudo apt-get install nvidia-current
sudo service lightdm stop
sudo service gdm start
Todo
Ideas:
We should use MoinMoin Syntax Parsers (http://moinmo.in/HelpOnParsers) where commands/code are presented. Parsers ensure code/commands are not converted to smileys and other MoinMoin stuff, therefore presented without errors.
- We had some amazing threads, specially since the OO cycle, which maybe we could use here;
- The stickies at Ubuntu+1 have some information that can probably be summarized / simplified here - investigate;
- Add a "What is a development cycle" section: How Ubuntu is developed, by who, where, how, when and where it is released (Alphas, Betas, RCs, etc), who tests it, how it is tested, where bugs are reported, how to report bugs properly, who manages bugs reports, etc. A basic vision of how Ubuntu development works."
Log files: A lot of people don't know they exist, where they are stored, the type of information available in each log file, how to open them, how to search them easily for valuable information. EDIT:I'll contribute to this portion - I already have something written, as well as log searching scripts posted at Ubuntu+1 threads (posted by Effenberg0x0)
Cleaned!
U+1/tester-wiki (last edited 2017-12-03 02:49:17 by dale-f-beaudoin)