Commonly Used Sudo Commands for (*)Ubuntu/Unity Crash Recovery

[ventrical]

Here is a really streamlined and reliable way to make a bootable USB disk with an (*)ubuntu image.

1. Download the ISO
2. Insert your USB stick in the knowledge that it’s going to get wiped
3. Open the “Disks” application
4. Choose your USB stick and click on the cog icon on the righthand side
5. Choose “Restore Disk Image”
6. Browse to and select the ISO you downloaded in #1
7. Click “Start restoring”
8. Wait
9. Boot and select “Try Ubuntu….”
10. Done *

[ventrical]

How to boot with SystemD

courtesy of elfin post

to boot with systemd in utopic is simple

boot, edit the boot line - find the 'linux line and add init=/lib/systemd/systemd then F10 will boot with systemd instead of upstart

when you're sure all is ok you can edit grub and add it there

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash init=/lib/systemd/systemd "

don't forget to update grub after changing that

[zika]

Two more ways to go over the fence and fully/completely adopt SystemD:
1.

sudo apt-get install systemd-sysv

2.

sudo apt-get purge upstart

Use with caution (changes are reversible in almost all the cases, AMD mostly, NVidia might be tricky) and only if You're really determined. I was and still am and have no regrets. To the contrary.
Read appropriate thread to get more details about problems with NVidia etc.

[ventrical]

Two more ways to go over the fence and fully/completely adopt SystemD:
1.

sudo apt-get install systemd-sysv

2.

sudo apt-get purge upstart

Use with caution (changes are reversible in almost all the cases, AMD mostly, NVidia might be tricky) and only if You're really determined. I was and still am and have no regrets.

Thanks zika.

So it's not as easy as editing grub back to it's default and re-installing upstart?

I'm just asking ?

Regards..

[zika]

Thanks zika.
So it's not as easy as editing grub back to it's default and re-installing upstart?
I'm just asking ?
Regards..

Two more ways to go over the fence and fully/completely adopt SystemD:
1.

sudo apt-get install systemd-sysv

2.

sudo apt-get purge upstart

Use with caution (changes are reversible in almost all the cases, AMD mostly, NVidia might be tricky) and only if You're really determined. I was and still am and have no regrets. To the contrary.
Read appropriate thread to get more details about problems with NVidia etc.

In these „two more ways“ there is not any change in /etc/default/grub needed as I've written in a thread mentioned. Change back, as I wrote is a „simple“ (mind the caveat I explained) purge of systemd-sysv or install of upstart since devs have done a good job and those two simply do not coexist together but do ask for other one when removed.

[zika]

The only caveat is that I had to edit out

init=/lib/systemd/systemd

from grub menu. So it is very well automated.

As I wrote in message You've quoted, because You've put it there. Rarely clean job that dev(s) have done.

[ventrical]

As I wrote in message You've quoted, because You've put it there. Rarely clean job that dev(s) have done.

I asked elfy to move it there. That it would be more topical there in systemd experience.

But I'll put the link here for reference.

http://ubuntuforums.org/showthread.p...9#post13146459

Thank you elfy.

Thank you zika.

[ventrical]

Upgrading to a new development cycle: Notes:

The rules remain the same but the speed of information is dynamic and can sometimes often collide. This 15.05 Vivid Vervet Cycle came very quickly, as expected by some, as a continuance of the anticipated rolling release philology.

Also, there is a certain order or 'flowchart' to follow when executing this proceedure. There are several diffirent methods that seem to work well for some and not so well for others. Mistakes will be made and systems will break - but for the most part the rolling releases have been designed to present us testers with somewhat of a fucntioning desktop experience (or a least a working X terminal).

There are basically two main files that have to be edited and updated. The first file is sources.list which can be found here :

/etc/apt/sources.list

and the Ubuntu.info file which can be found here:

/usr/share/python-apt/templates/Ubuntu.info

These two files are very different from each other but are essential for the proper update/upgrade to the new development cycle.


When the command:

sudo sed -i 's/utopic/vivid/g' /etc/apt/sources.list

is executed followed by:

sudo apt-get update && sudo apt-get dist-upgrade

and

sudo apt-get update
sudo apt-get upgrade

it will convert the sources.list text to the current repositories for (vivid) but it will also convert the templates in Ubuntu.info to /devel/

This may seem to be very confusing. Back a few cycles ago we were able to use /devel/ verebose to change our sources.list and get updates/upgrades but now it does not seem to work so , in this cycle, it is more prudent to use the first part of the release cycle name. Again , in this case that is /vivid/.

Cariboo907 has detailed the proceedure to insert the new template for the /vivid/ cycle here at this link:

https://wiki.ubuntu.com/U%2B1/common...doesn.27t_work

Make sure to append this info at the top of the Ubuntu.info file.

There is a changelog URL. It can either be left in or commented out. Some say it is useful (and probably is) but it still reported errors on one of my installs. Surf the pertinent echos in Ubuntu Development Release and decide for yourselves. Try different things. It's free


Also some will have the proposed repositories turned on. Other would beg to differ to have them disabled. It is most surely if you have them enabled that you will bork your desktop and network , unless, of course , you are an advanced user.

Regards..

[ventrical]

If you are having problems with apport reporting random bugs you can always turn it off.

Buckyball reported this: http://ubuntuforums.org/showthread.p...8#post13160868

and zika reported this: http://ubuntuforums.org/showthread.p...4#post13160964

Regards..

[ventrical]

Startup Disk Creator is not working correctly, loaded with bugs and will bust a persistent ver 3.0 USB ISO when it is updated. However, that USB will work on ver 2.0 hardware but not version 3.0 hardware. Then , after sitting over night in off state it will not boot up at all and is not recognized by ver 3.0 hardware. It will make it appear that you ver 3.0 USB has a hardware brick, which , in fact, is no the case. If you have a similar bust then remove your partition from USB flash _drive, create a new partition and mark it ext4 and then try below.

Here is a method already posted that will fix that.

http://ubuntuforums.org/showthread.p...0#post13145410