As discussed in https://bugs.mageia.org/show_bug.cgi?id=27354#c120 the gui for isodumper could use some improvements to make it's usage clearer. The button to write to device should be on a line by itself after the lines for adding a persistent partition and option encryption selection with an encryption key to make it clear those options should be selected, if desired, before selecting the write to device button. The backup and format features should be separate in some way, to make it clear they do not apply to the persistent partiton. If the backup option is kept, there should likely be a restore feature included too.
CC: (none) => andrewsfarm
CC: (none) => fri
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=27354
____FUNCTIONALITY DISCUSSION __Restoring I believe the restoring method is to write the backed up image. Maybe there could be a text line about that. I see no reason to add a specific function - keep it simple. __Keep settings displayed when done (from the earlier bug) When Isodumper finishes it resets the controls immediately. It would be nice if instead the check boxes remained set so user see he did not forget them - IMO they should remain as they were used, analogous to the log is visible and i believe the encryption key is preserved already (dots remain). __Log "everything" Also log backing up and formatting In the end of isodumper.log, add a note to check /var/log/magiback.log for more details.
___LAYOUT AND OPERATION PROPOSAL It should be no doubt what is related, what will execute, when. Some dividing lines, texts, wording helps. Controls should be in the order user should consider them: 1) Select device 2) No backup -OR- Backup only -OR- backup first then continue. 3) Format OR write, with adjacent parameters. 4) One and only one button to start - and if both bakcup and format/write is selected, both are performed in one go. Below is a suggestion mockup; Using radio buttons ( ) to select what to do. Eye button to view entered encryption key ( <o> in mockup ) One text line explaining how to restore. (Should be more air between lines than in this ASCII mockup...) =============================================================== I S O D U M P E R =============================================================== Select device to work on New device connected? [____________d_r_o_p_d_o_w_n_____________] [Update list] =============================================================== (o) No backup - be very sure you will not miss current content! ( ) Only Backup and stop. Back up device content to: ( ) Backup and continue. [__Selects_and_display_target_file _] /To restore the backup, use the Write image option below./ =============================================================== ( ) Format whole device [f.syst.dropdown] label:[text________] (o) Write image from: [___Selects_and_display_source_file___] [x] Add persistent partition (for Mageia Live) [ ] Encrypt partition using key [ooooooo_____________] <o> =============================================================== When you are sure all options are correct, start: [ EXECUTE ] [___________Progress_bar___________] xx% Current operation: yadayada... =============================================================== < log window > =============================================================== All in one clear step by step dialog Backup + format/write executes in one go - user need not start again. (Important: abort if backup fail!) Emphasize possibilites using graying out; "Backup and stop" => Grey oput everything concering formating and writing. Selecting Write greys out formattin parameteres and vice versa Encrypt box is cleared and greyed when Add persistent is not selected.
___LAYOUT AND OPERATION PROPOSAL - Formatting flexibility § Most of our desktops can ask for LUKS key i think? - Then users can have a new easy way to store and share sensitive data: Enable encryption also for formatting, and I think it should enforce filesystem ext4. § Offer flash optimised file sytems available for both full formatting and for persistent partition. - NILFS2, F2FS ? They need extra packages installed? (Dont NTFS and ExFAT too, btw?) - To be investigated: Can Mageia Live use NILFS2 / F2FS for persistence? § If Add persistent partition is selected, the label text field should be forced to "mgalive-persist". Nicer to show instead of hiding. Below is a variant of the mockup, with the common partition choices moved together: filesystem, label, encryption. =============================================================== I S O D U M P E R =============================================================== Select device to work on New device connected? [____________d_r_o_p_d_o_w_n_____________] [Update list] =============================================================== (o) No backup - be very sure you will not miss current content! ( ) Only Backup and stop. Back up device content to: ( ) Backup and continue. [__Selects_and_display_target_file _] /To restore the backup, use the Write image option below./ =============================================================== ( ) Format whole device as one partition. (o) Write image from: [___Selects_and_display_source_file___] [x] Add persistent partition (for Mageia Live) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - File system to use: [file system dropdown] Partition label: [text________] [ ] Encrypt partition using key [ooooooo_____________] <o> =============================================================== When you are sure all options are correct, start: [ EXECUTE ] [___________Progress_bar___________] xx% Current operation: yadayada... =============================================================== < log window > ===============================================================
Maybe cleaner per below; § Less items but same functions. Intention is to make it both easier for user to understand, and to program, than earlier suggestion. § Short text describe how it operates. § loooong key field because the modern recommendation is to use some common words as keys. § added some "air"... § Because the progress bar shows the progress of *current* operation, it is now placed *below* the text for current operation. § The "For Mageia Live" option when selected enforce the label to be "mgalive-persist", and limits the selection of filesystems to what latest released Mageia Lives supports for persistence. So same controls can be used for both cases of creating partition. =============================================================== I S O D U M P E R =============================================================== Select device to work on New device connected? [____________d_r_o_p_d_o_w_n_____________] [Update list] =============================================================== /The selected operations will be executed in order from top to bottom./ /If both write image and create partition are selected, the partition/ /Will be created in the free space after the image. [ ] BACKUP device to:[___Selects_and_display_target_file ____] /To restore the backup, use the Write image option below./ [ ] Write IMAGE from:[___Selects_and_display_source_file_____] [ ] Create PARTITION of type:[file system dropdown] Label:[text_____________] [ ] For Mageia Live persistence [ ] Encrypt partition using LUKS, with key: <o> Key: [ooooooo__________________________________________] /Mageia will ask for key at boot or when you try to use it./ =============================================================== When you are sure all options are correct, start: [ EXECUTE ] Current operation: yadayada... [_____Progress_bar_of_current_operation______] xx% =============================================================== < log window > ===============================================================
In Mageia 7 and 7.1 the .gpg files are detached signatures so the command to verify the iso sha3 sum file is # gpg --verify Mageia-7.1-Live-Xfce-i586.iso.sha3.gpg Mageia-7.1-Live-Xfce-i586.iso.sha3 gpg: Signature made 2019-07-14T17:11:16 EDT gpg: using RSA key 835E41F4EDCA7A90 gpg: Good signature from "Mageia Release <release@mageia.org>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: B210 76A0 CBE4 D93D 66A9 D08D 835E 41F4 EDCA 7A90 In Mageia 8 beta 1 the .gpg files contain signed copies of the sum files instead of detached signatures so the command is ... gpg --verify Mageia-8-beta1-Live-Xfce-i586.iso.sha3.gpg gpg: Signature made 2020-08-02T04:57:02 EDT gpg: using RSA key B21076A0CBE4D93D66A9D08D835E41F4EDCA7A90 gpg: Good signature from "Mageia Release <release@mageia.org>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: B210 76A0 CBE4 D93D 66A9 D08D 835E 41F4 EDCA 7A90 As is, isodumper works for m8 beta 1, but not for m7 or m7.1 gpg signatures. The gpg signatures for beta2 should be detached signatures as in m7 or m7.1. Not sure if you'd like this as part of this bug report or separate. Ideally isodumper should handle either type of signature. If the command fails with ... # gpg --verify Mageia-7.1-Live-Xfce-i586.iso.md5.gpg gpg: no signed data gpg: can't hash datafile: No data automatically try again with the file name added ... # gpg --verify Mageia-7.1-Live-Xfce-i586.iso.md5.gpg Mageia-7.1-Live-Xfce-i586.iso.md5 gpg: Signature made 2019-07-14T17:11:16 EDT gpg: using RSA key 835E41F4EDCA7A90 gpg: Good signature from "Mageia Release <release@mageia.org>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: B210 76A0 CBE4 D93D 66A9 D08D 835E 41F4 EDCA 7A90
Found another problem when copying a beta 2 iso image. From /var/log/magiback.log ... 2020-12-05 20:11:49,890 INFO Mageia key already present 2020-12-05 20:11:49,890 INFO Signature file /s3/m8/Mageia-8-beta2-Live-GNOME-x86_64/Mageia-8-beta2-Live-GNOME-x86_64.iso.sha3.gpg not found 2020-12-05 20:16:12,125 INFO The sha3 sum check is OK and the sum is signed So it's incorrectly reporting to the user that the sum is signed, when a signature does not exist.
*** Bug 27631 has been marked as a duplicate of this bug. ***
*** Bug 18268 has been marked as a duplicate of this bug. ***
Hello, I pushed 1.31, not yet packaged.
Will be interesting to try :) Unfortunately I see it failed build 9 hours ago. Another issue: Isodumper put Live on a USB stick, later it formatted FAT32, and now diskdrake shows an obscenely long name for it, trigging bug 27882. Diskdrake should truncate or linewrap the name, but the name is weird and far too long.
> Will be interesting to try :) > > Unfortunately I see it failed build 9 hours ago. I didn't put a tag, I would have a first feedback before. > > Another issue: Isodumper put Live on a USB stick, later it formatted FAT32, > and now diskdrake shows an obscenely long name for it, trigging bug 27882. > Diskdrake should truncate or linewrap the name, but the name is weird and > far too long. I don't reproduce it. I formatted in FAT32 giving "Yves" as name. In details of diskdrake, I get as Name a long number of 16 digits. In man page of mkfs.fat, I see only this which can be random, but limited to 32 bits :-i VOLUME-ID Sets the volume ID of the newly created filesystem; VOLUME-ID is a 32-bit hexadecimal number (for example, 2e24ec82). The default is a number which depends on the filesystem creation time. This is nothing of hundreds characters.
Plugged in that USB stick in my main machine, then issued dmesg: [180835.195692] usb 1-1.1: new high-speed USB device number 7 using ehci-pci [180835.274869] usb 1-1.1: New USB device found, idVendor=0781, idProduct=5583, bcdDevice= 1.00 [180835.274873] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [180835.274875] usb 1-1.1: Product: SanDisk 3.2Gen1 [180835.274877] usb 1-1.1: Manufacturer: USB [180835.274878] usb 1-1.1: SerialNumber: 05010d030318e205b4beb0eccdac031437f98c6b2da2d7d40eba28ac4de6b5e84bd200000000000000000000e91136d5ff1315108355810792282c8a [180835.275503] usb-storage 1-1.1:1.0: USB Mass Storage device detected [180835.277080] scsi host11: usb-storage 1-1.1:1.0 [180836.278507] scsi 11:0:0:0: Direct-Access USB SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6 [180836.283121] sd 11:0:0:0: [sdg] 30031872 512-byte logical blocks: (15.4 GB/14.3 GiB) [180836.284369] sd 11:0:0:0: [sdg] Write Protect is off [180836.284373] sd 11:0:0:0: [sdg] Mode Sense: 43 00 00 00 [180836.285370] sd 11:0:0:0: [sdg] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [180836.314493] sdg: sdg1 sdg2 < sdg5 sdg6 sdg7 > [180836.318371] sd 11:0:0:0: [sdg] Attached SCSI removable disk
As a reminder, it could be useful to add in the Report window, the information provided by "blkid" of the Label or volume name of the device one is going to overwrite, e.g. using blkid on a pendrive containing a mageia iso, it will show: /dev/sdc1: UUID="2021-01-13-22-31-41-00" LABEL="Mageia-8-rc-x86_64" ... /dev/sdc2: SEC_TYPE="msdos" LABEL_FATBOOT="MGALIVE-ESP" LABEL="MGALIVE-ESP" ... in this way you know what is going to override.
CC: (none) => ghibomgx
Created attachment 12539 [details] New gui, asking for confirmation of non signed image 1.40 release is coming in cauldron
Created attachment 12540 [details] Ready to go
Looks like a dream come true :) Pity I don't run Cauldron In Report window the line "Content partition(s)" I think it would be more clear if it say: "Target currently contain the following partition(s):" Likewise "Image:" -> "Image to write:" To make new users confident they understand it all. But wait with new version until we tested it The dialogue to me feel like a huge improvement this far :)
(In reply to Morgan Leijström from comment #16) > Looks like a dream come true :) > Pity I don't run Cauldron > In Report window the line "Content partition(s)" > I think it would be more clear if it say: > "Target currently contain the following partition(s):" > Likewise "Image:" -> "Image to write:" I'd use "ISO Image to copy", since it isn't being written to. > To make new users confident they understand it all. > But wait with new version until we tested it > The dialogue to me feel like a huge improvement this far :)
Behind the GUI, I guess the base is same code including fix as for Bug 28466 ? Do we need to test something specific except that it operates as commended by the GUI?
Yes, all previous fix are included. What is important to check also is that commutation between greyed or active widgets is coherent, because there a lot of change on this side. Under the hood, there is no change.
The window frame should say IsoDumper, not "phyton3" ;) "The validation of GPG signature failed" To be more specific: "Validation of the GPG signature of the checksum file failed"
(In reply to Morgan Leijström from comment #20) > The window frame should say IsoDumper, not "phyton3" ;) > Is it by launching with isodumper command or with "python3 isodumper.py"? Which Desktop?
Just your screenshot. I have not installed Cauldron yet. Another note based on your screenshot, in Report window: /dev/sdd1: Type exfat Label Yves I suggest to insert "=" and ",": /dev/sdd1: Type=exfat, Label=Yves
Ok. Will do.
First trials on cauldron :) A few comments: a) Nice that you in partition type can select persistent partition, and it then set the label correctly. Maybe it could be improved to somehow show the filesystem type, i.e to then switch to show ext4? b) We do support also at least Btrfs and F2FS (in mga8) for persistence. And i have tried them, writing a wiki page with it. It would be nice if IsoDumper could format them too. c) At end of writing, log window show as last line: The sha3 sum check is OK c1) IMO, Better avoid the blank line before that line, for consistency c2) It never told if it checked pgp key or not! d) Disable run button when a setting is illegal. I.e "backup to device" checked, but no file chosen. e) When target for backup is have too little space, it correctly pop up warning. After user OK it, e1) if only backup was selected, everything is greyed out. Expected: user should be able to change everything. e2) if also write was selected it start writing- that is definitely wrong, user wanted to save the content... Expected: Just abort and let user change everything. Simply: if no room for backing up just abort all execution and let user change another location or herself disable backup. f) Playing with it a bit, i.e unplugging stick while writing, replugging and making setting again, there is some general asyncronousity between what it is set to do and do. I.e it can start write to device despite no device is selected, it complain no backup file is selected but that field still contain the file name it had last run, etc. Somehow the executing part is not using what is currently in the dialogue! g) Possibly a new setting for formatting: add setting for leaving part of space unused. I.e Leave [XXX]MB unpartitioned (default to 0). Use case: User can later create i.e FAT32 for sharing files with non Linux OS:es, while still having i.e ext4 persistence. Like here: https://wiki.mageia.org/en/User:Morgano/Persistent_live_systems#Plugging_it_into_other_systems
(In reply to Morgan Leijström from comment #24) > b) We do support also at least Btrfs and F2FS (in mga8) for persistence. And > i have tried them, writing a wiki page with it. It would be nice if > IsoDumper could format them too. > Hi Morgan, I didn't find the wiki page you refer to.
I was not clear, sorry, not a separate wiki page, but chapters in my page on Live systems. (I really should bite the bullet and publish it officially!) https://wiki.mageia.org/en/User:Morgano/Persistent_live_systems#Swap_file_on_F2FS_persistence https://wiki.mageia.org/en/User:Morgano/Persistent_live_systems#Swap_file_on_Btrfs_persistence
OK. I don't intend to have more choices in format types. The tool must stay simple. However, we can default to another format type if it is more advantageous than ext4. I have no advice about that.
OK. Then keep ext4 as default; most compatible, stable, and lots of tools.
Hello, 1.41 is now in cauldron, and I hope that all points are dealt with: (In reply to Morgan Leijström from comment #24) > a) Nice that you in partition type can select persistent partition, and it > then set the label correctly. Maybe it could be improved to somehow show > the filesystem type, i.e to then switch to show ext4? ext4 is displayed > > > b) We do support also at least Btrfs and F2FS (in mga8) for persistence. And > i have tried them, writing a wiki page with it. It would be nice if > IsoDumper could format them too. It still uses ext4 only > > c) At end of writing, log window show as last line: > > The sha3 sum check is OK > > c1) IMO, Better avoid the blank line before that line, for consistency Perhaps I have missed that. > > c2) It never told if it checked pgp key or not! Message added when gpg is checked > > > d) Disable run button when a setting is illegal. > I.e "backup to device" checked, but no file chosen. Should be OK > > > e) When target for backup is have too little space, it correctly pop up > warning. After user OK it, > e1) if only backup was selected, everything is greyed out. Expected: user > should be able to change everything. > e2) if also write was selected it start writing- that is definitely wrong, > user wanted to save the content... Expected: Just abort and let user change > everything. > Simply: if no room for backing up just abort all execution and let user > change another location or herself disable backup. Should be OK. > > > f) Playing with it a bit, i.e unplugging stick while writing, replugging and > making setting again, there is some general asyncronousity between what it > is set to do and do. I.e it can start write to device despite no device is > selected, it complain no backup file is selected but that field still > contain the file name it had last run, etc. Somehow the executing part is > not using what is currently in the dialogue! Should be OK. > > > g) Possibly a new setting for formatting: add setting for leaving part of > space unused. I.e Leave [XXX]MB unpartitioned (default to 0). Use case: > User can later create i.e FAT32 for sharing files with non Linux OS:es, > while still having i.e ext4 persistence. Like here: > https://wiki.mageia.org/en/User:Morgano/ > Persistent_live_systems#Plugging_it_into_other_systems I'm still reluctant to add this feature.
Any progress? Could we have it in mga8 testing for wider testing?
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=29966
I added a section describing this new interface in https://wiki.mageia.org/en/IsoDumper_Writing_ISO_images_on_USB_sticks
Much nicer. I'd add a line just above the Create line with ... Optionally, for use by live iso images add persistence with an extra partition: Then shift the Create line slightly to the right, and the Encrypt line slightly more to the right to indicate they are part of the Optional persistence, and the encryption is only for use with the created partition.
It is possible to just create a partition, for general use. With or without encryption. With or without backing up first. - I like the modularity :) But you are right in that maybe there should be something reminding users the possibility to create persistence. What about extending the sentence "If both write image and create partition are selected, the partition will be created in the free space after the image." to "If both write image and create partition are selected, the partition will be created in the free space after the image, and if the label is "mgalive-persist" Mageia Live will use it for persistence. Hm, maybe also automate: if the name of ISO fits the pattern Mageia*Live* then preselect the persistence options?
The general adding of partitions should be left for diskdrake. Keep it simple, as the purpose of the package is for use copying an iso image to a usb stick, or restoring the backup created from a stick. Perhaps it should not allow it (grayed out) to be used to create a persistence partition unless the iso image is a Mageia live iso. Likewise the encryption option should only be selectable when creating a persistence partition. Do one task, and do it well. :-)
The main reason for Isodumper is to let users format and write removable media in a *safe* and *simple* way. Mainly hindering them from writing to a wrong disk... Diskdrake is far too cumbersome, quirky, and do not protect users from formatting wrong disk. For this purpose diskdrake is dangerous. That said i did write an instruction... https://wiki.mageia.org/en/Persistent_live_systems#Creating_persistence_using_only_Live_itself