i just wanted do add than IMHO automatically mounting "anything" in live
mode is the worst desgin decision ever
and btw. it produces bugs beyond your imagination...
for example:
on an customized live image there is an instance of nginx running... in
order to start nginx it checks if
You may want to participate in the following thread,
https://discourse.ubuntu.com/t/make-it-easy-to-create-a-persistent-as-
well-as-live-only-usb-live-drive/13671
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@ Michael Hudson-Doyle, @ Olivier Robert, and @ everybody else who is
interested,
I suggest a simple method to prepare the iso files for binary editing
without 'sacrificing' anythng.
Since repeated spaces are collapsed into one space by Launchpad's
comment editor, I will provide the man content
@@ Michael Hudson-Doyle, @ Olivier Robert, and everybody else who is
interested,
I suggest a simple method to prepare the iso files for binary editing
without 'sacrificing' anythng.
Since repeated spaces are collapsed into one space by Launchpad's
comment editor, I will provide the man content
@ Michael Hudson-Doyle, @ Olivier Robert,
What do you think of the following idea for Ubuntu Focal Fossa?
It is possible to add the boot option
- 'persistent' in order to create a persistent live drive
or
- 'nopersistent' in order to create a live-only drive.
I am looking for a method to edit
@nio-wiklund, @mwhudson : Thanks for your replies.
@nio-wiklund : Your solution would probably do the trick, but has the
inconvenient of indiscriminately replacing a string with another in the
whole image, hence possibly in places where it's not desired.
I think I will rather do one of those two
@Michael Hudson-Doyle,
I'm glad that you are reading this :-)
An alternative, that I can see beyond editing the whole iso file:
- Add a menuentry in the iso file. This menuentry should have the boot
option 'persistent' alongside the other boot options. So there would be
two standard boot
I am still reading this (although busy, hence the delay). I quite
strongly don't want to change the default but maybe we can make it
easier to disable than applying sed to the entire ISO (!). Probably the
forums or discourse.ubuntu.com would be a better place to discuss this.
--
You received
@Olivier,
I think that the developers will stop looking at a bug report after the
bug is fixed. So they might not read what we write here. (A discussion
here is OK for me, but it may not involve the people who can change the
code.)
Until you have collected enough opinion for your issue, there
I can raise my concern through another bug for sure, if necessary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851123
Title:
Ubuntu 19.10 and focal live cloned create and mount casper-rw
I tested the bugfix with the Xubuntu Focal daily iso file in BIOS mode
using the boot option 'toram', and it works :-)
See the attached screenshot: A casper-rw was not mounted; it was not
even created.
After that I rebooted without any extra boot option. The casper-rw
partition was created and
Imho, the default behaviour should be overall read-only, as it's more in
line with the general perception of a live system as an "I'm just
looking" thing. Straying away from this concept could make more than a
few people uncomfortable.
Moreover, having a default write behaviour can have adverse
casper in focal now turns off the automatic log persistence if toram or
todisk is used.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851123
Title:
Ubuntu 19.10 and focal live cloned create and
This bug was fixed in the package casper - 1.432
---
casper (1.432) focal; urgency=medium
* scripts/casper-helpers: pass --no-reread to sfdisk when creating the
casper-rw partition to reduce the risk of self-races (which probably only
happen in qemu-system-emulation i.e. in
I installed Xubuntu when running a persistent live Ubuntu system
1. With the options 'toram' 'nopersistent'
It was truly live-only (and the installation worked).
2. With the default settings (no extra boot option compared what comes
with the iso file)
The casper-rw partition received and
Been chatting with Sudodus.
Back in the days of 4GB and 8GB flash drives it was not so bad when SDC, mkusb
and Rufus used the whole drive to make a Live USB.
Nowadays with 64GB and larger flash drives it seems like a waste.
Making the remaining space Persistent is a great start but even on my
I tried booting a Startup Disk Creator 19.10 flashdrive with F6.
I typed a space and then "persistent".
The drive booted persistent and stayed persistent every time I used this
procedure, otherwise it just booted Live.
I then tried F6 with the word "toram", it booted to RAM.
Then with "nomodeset"
Exploring the boot option 'nopersistent':
The bug is there, but there is a workaround: add the boot option
'nopersistent'. This means that with 'nopersistent' and 'toram' all
partitions on the boot drive can be unmounted and the drive can be
unplugged or the casper-rw partition can be repaired or
I see and understand now that mounting casper-rw in live-only mode is by
intention and not a bug.
I think the important thing is that it is possible to unmount all
partitions on the drive when running live-only with 'toram'.
It is also valuable to learn about the boot option 'nopersistent.'
So
The point of the work I did on this was to automatically save the
installer logs to the media. I don't want to change the default
behaviour. However, we should make sure other use cases are possible.
You can put "nopersistent" on the command line to disable both creation
and mounting of casper-rw.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: casper (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851123
Title:
The same problem appears also in other configurations, not only with
cloned live systems but with all Ubuntu live systems made with 19.10 and
Focal Fossa. When running live-only (without the boot option
'persistent') the casper-rw partition will be mounted and busy.
I tested and verified the
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1851123
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "output of text mode commands via 'script' (file
typescript)"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+attachment/5302436/+files/typescript.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Adding some text files
** Attachment added: "ubuntu-focal-live-cloned_before-it-is-used.txt"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+attachment/5302435/+files/ubuntu-focal-live-cloned_before-it-is-used.txt
--
You received this bug notification because you are a
Adding screenshot from Focal Fossa
(I had to stop and start the graphical desktop environment from a text
screen to make it responsive, but that is another problem, I think not
related to the bug reported here.)
** Attachment added: "ubuntu-focal-live-cloned_creates-n-mounts-casper-rw.png"
Adding screenshot from 19.10
** Attachment added: "ubuntu-19.10-live-cloned_creates-n-mounts-casper-rw.png"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+attachment/5302437/+files/ubuntu-19.10-live-cloned_creates-n-mounts-casper-rw.png
--
You received this bug notification
27 matches
Mail list logo
