[opensuse-factory] USB installation instrucctions issues.

older
[opensuse-factory] Automount with...

Carlos E. R.

18 Nov 2013 18 Nov '13

14:01

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, A question on the forum about copying the ISO image to an USB stick for installation has prompted me to check the instructions, and I found some issues. They have been improved a lot, yes, but important parts have been removed. The forum poster, as imagewriter has failed (whom to do we report to issues with that program?), tried other instructions on internet:

...

After a reccomendation on ServerFault.com I tried using Unetbootin to copy the ISO to the stick, while that resulted in a bootable stick it doesn't appear that the ISO works with it as the only option to come up is "Default" and that then refuses to boot, just keeps going round and round the "booting in 10 seconds" thing, and resetting the timer every 10 seconds.

Unetbootin is known to not work. I wrote a paragraph about that, but the paragraph has been removed: +++····················· Note: do not try to apply procedures found in internet for other distributions "to convert the images into bootable sticks". Doing that will break the images. The openSUSE images are already prepared for being used directly on usb sticks, no further steps are needed. ·····················++- The current instructions also mention how to «create a persistent file system» These are obsolete for 13.1, as it uses a different persistence method (and I think it does not work for 12.3 at all). After a lot of discussion here on the mail list, I added a paragraph about an alternate method that works when dd does not: +++····················· Alternate method to write ISO to USB As above, but using "cp" instead of "dd". # umount /dev/sdX # cp /path/to/downloaded.iso /dev/sdX # sync ·····················++- which has also been removed. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlKKHdQACgkQtTMYHG2NR9VZmgCdEfrTEd26QqfybhNOYZoA2w1C 5b8AnAs1b4ZRAiHBjOHaDavmnU6HL29P =veGO -----END PGP SIGNATURE-----

Show replies by date

cagsm

18 Nov 18 Nov

14:07

i just write all the bytes from the .iso file to an usb stick raw that never gave me trouble to boot from it on systems in the timeframe of the past 5 years or so winblows can do that with that susestudioimagewriter just fine never had any trouble there either On Mon, Nov 18, 2013 at 3:01 PM, Carlos E. R. wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

A question on the forum about copying the ISO image to an USB stick for installation has prompted me to check the instructions, and I found some issues. They have been improved a lot, yes, but important parts have been removed.

The forum poster, as imagewriter has failed (whom to do we report to issues with that program?), tried other instructions on internet:

...
After a reccomendation on ServerFault.com I tried using Unetbootin to copy the ISO to the stick, while that resulted in a bootable stick it doesn't appear that the ISO works with it as the only option to come up is "Default" and that then refuses to boot, just keeps going round and round the "booting in 10 seconds" thing, and resetting the timer every 10 seconds.

Unetbootin is known to not work. I wrote a paragraph about that, but the paragraph has been removed:

+++····················· Note: do not try to apply procedures found in internet for other distributions "to convert the images into bootable sticks". Doing that will break the images. The openSUSE images are already prepared for being used directly on usb sticks, no further steps are needed. ·····················++-

The current instructions also mention how to «create a persistent file system» These are obsolete for 13.1, as it uses a different persistence method (and I think it does not work for 12.3 at all).

After a lot of discussion here on the mail list, I added a paragraph about an alternate method that works when dd does not:

+++····················· Alternate method to write ISO to USB

As above, but using "cp" instead of "dd".

# umount /dev/sdX # cp /path/to/downloaded.iso /dev/sdX # sync ·····················++-

which has also been removed.

- -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux)

iEYEARECAAYFAlKKHdQACgkQtTMYHG2NR9VZmgCdEfrTEd26QqfybhNOYZoA2w1C 5b8AnAs1b4ZRAiHBjOHaDavmnU6HL29P =veGO -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Bernhard Voelker

14:28

On 11/18/2013 03:01 PM, Carlos E. R. wrote:

...

After a lot of discussion here on the mail list, I added a paragraph about an alternate method that works when dd does not:

+++····················· Alternate method to write ISO to USB

As above, but using "cp" instead of "dd".

# umount /dev/sdX # cp /path/to/downloaded.iso /dev/sdX # sync ·····················++-

Why would dd(1) not work? There's no issue known for it, neither in openSUSE's bugzilla nor in the upstream 'coreutils' project. Please provide more info. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Carlos E. R.

20:02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-11-18 15:28, Bernhard Voelker wrote:

...

On 11/18/2013 03:01 PM, Carlos E. R. wrote:

...

Why would dd(1) not work? There's no issue known for it, neither in openSUSE's bugzilla nor in the upstream 'coreutils' project. Please provide more info.

I did when we discussed the instructions about a month or two ago. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKKcj0ACgkQtTMYHG2NR9X2ygCdGpo6X6mYyZedyJWJX5Mu8D+E tGQAniII1qK4JXnfA2fuTec101IVMDF+ =bKAQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Bernhard Voelker

22:27

On 11/18/2013 09:02 PM, Carlos E. R. wrote:

...

On 2013-11-18 15:28, Bernhard Voelker wrote:

...
On 11/18/2013 03:01 PM, Carlos E. R. wrote:

...
Why would dd(1) not work? There's no issue known for it, neither in openSUSE's bugzilla nor in the upstream 'coreutils' project. Please provide more info.

I did when we discussed the instructions about a month or two ago.

Hi Carlos, IIRC that was the "short read" issue, right? Well, I can only say that dd(1) is quite a low-level tool with much useful low-level functionality. Unfortunately, it therefore does not meet the intuitive expectations of many users regarding such short reads. If unsure, you can always use iflag=fullblock. BTW: that iflag option has been standardized only 2 years ago [1]. BTW2: someone should mention this issue in dd's wikipedia page [2]. Volunteers? [1] http://austingroupbugs.net/view.php?id=406 [2] http://en.wikipedia.org/wiki/Dd_(Unix) Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Carlos E. R.

22:43

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-11-18 23:27, Bernhard Voelker wrote:

...

On 11/18/2013 09:02 PM, Carlos E. R. wrote:

...

...
I did when we discussed the instructions about a month or two ago.

...

IIRC that was the "short read" issue, right?

No, not that one. The starting point was some new user asking for help on the forums about how to create the usb stick, using another Linux distro (thus, no Bugzillas here). The dd command failed, writeimage also failed, unet??? also failed. Googling or asking elsewhere, it was advised to use a plain "cp" or "cat" to create the image, and this finally worked. Some other people corroborated that it worked. Then I started a thread on the mail list asking how was it possible that "cp" worked. It was a long thread, which concluded, IIRC, that "cp" was also a valid command to use in order to create the image. We talked about adding this new information to the wiki, and I finally added it, and Rajko validated it. Some other incorrect advice was removed. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKKl/QACgkQtTMYHG2NR9W08ACfcYacAHKR81Z95MvXwuKAtB3L sdUAniZO0vmHhCMJxKnaA1o+1MuZ028P =wBxf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Bernhard Voelker

22:53

On 11/18/2013 11:43 PM, Carlos E. R. wrote:

...

On 2013-11-18 23:27, Bernhard Voelker wrote:

...
IIRC that was the "short read" issue, right?

No, not that one. The starting point was some new user asking for help on the forums about how to create the usb stick, using another Linux distro (thus, no Bugzillas here). The dd command failed, writeimage also failed, unet??? also failed. Googling or asking elsewhere, it was advised to use a plain "cp" or "cat" to create the image, and this finally worked. Some other people corroborated that it worked.

Then I started a thread on the mail list asking how was it possible that "cp" worked. It was a long thread, which concluded, IIRC, that "cp" was also a valid command to use in order to create the image. We talked about adding this new information to the wiki, and I finally added it, and Rajko validated it. Some other incorrect advice was removed.

Thanks for the summary. However, I cannot imagine a case for copying the content of a single file (or device) with "cp" which would not work with "dd" (plus the correct options). Would you like to shed some light on this (and dig in the archives), or should we draw the curtain over this case? Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

cagsm

22:59

isnt there some project guys who are methinks with these pendrivelinux website or stuff who offer their tiny installer/handler for a great number of distros, amongst them also suse methinks but i know for sure for example linux based tails (tor) distro. that pendrivelinux installer stack extracts the files from inside the tails .iso file (with 7zip commandline) and then puts it on a fat(fat12/16/32/whatever) usb disk or usb stick or usb key even and then adds some isolinux binary and config files and folders and some bootloader and bootsector onto this fat usb device and then all is running happily and tails tor distro can boot up and you can for example bootstrap into tor or upgrade some other tails usb stick with the more recent release. isolinux hybridlinux and other buzzwords come to my mind. On Mon, Nov 18, 2013 at 11:53 PM, Bernhard Voelker wrote:

...

On 11/18/2013 11:43 PM, Carlos E. R. wrote:

...
On 2013-11-18 23:27, Bernhard Voelker wrote:

...
IIRC that was the "short read" issue, right?

No, not that one. The starting point was some new user asking for help on the forums about how to create the usb stick, using another Linux distro (thus, no Bugzillas here). The dd command failed, writeimage also failed, unet??? also failed. Googling or asking elsewhere, it was advised to use a plain "cp" or "cat" to create the image, and this finally worked. Some other people corroborated that it worked.

Then I started a thread on the mail list asking how was it possible that "cp" worked. It was a long thread, which concluded, IIRC, that "cp" was also a valid command to use in order to create the image. We talked about adding this new information to the wiki, and I finally added it, and Rajko validated it. Some other incorrect advice was removed.

Thanks for the summary. However, I cannot imagine a case for copying the content of a single file (or device) with "cp" which would not work with "dd" (plus the correct options). Would you like to shed some light on this (and dig in the archives), or should we draw the curtain over this case?

Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

cagsm

23:06

just verified this, and the usb key is a fat device with the help of these pendrivelinux guys or some software currently called or named "Universal-USB-Installer-1.9.4.7", and this creates some isolinux and/or syslinux folders on the top rootlevel of the fat formatted usb devices and then puts all sorts of configs (depending on which distro and what kind of linux and supported system it is dealing with) and then the usb device or disk is being made bootable and the actual content files in this case the ones from inside the tails .iso are extracted onto this usb disk device and then everything works fine. at least for tails it works this way, your milage may vary and results may differ if Universal-USB-Installer-1.9.4.7 is working on the other near infinite number of distros supposedly being supported by it. sample contents of disk toplevel: xxxx.xx.xx 00:14 <DIR> .disk xxxx.xx.xx 00:14 <DIR> live xxxx.xx.xx 00:55 49.070 Uni-USB-Installer-Copying.txt xxxx.xx.xx 00:55 17.888 Uni-USB-Installer-Readme.txt xxxx.xx.xx 00:42 18.092 license.txt xxxx.xx.xx 00:02 <DIR> syslinux xxxx.xx.xx 00:24 <DIR> uui xxxx.xx.xx 00:14 <DIR> isolinux 3 File(s) 85.050 bytes give it a try On Mon, Nov 18, 2013 at 11:59 PM, cagsm wrote:

...

isnt there some project guys who are methinks with these pendrivelinux website or stuff who offer their tiny installer/handler for a great number of distros, amongst them also suse methinks but i know for sure for example linux based tails (tor) distro. that pendrivelinux installer stack extracts the files from inside the tails .iso file (with 7zip commandline) and then puts it on a fat(fat12/16/32/whatever) usb disk or usb stick or usb key even and then adds some isolinux binary and config files and folders and some bootloader and bootsector onto this fat usb device and then all is running happily and tails tor distro can boot up and you can for example bootstrap into tor or upgrade some other tails usb stick with the more recent release.

isolinux hybridlinux and other buzzwords come to my mind.

On Mon, Nov 18, 2013 at 11:53 PM, Bernhard Voelker wrote:

...
On 11/18/2013 11:43 PM, Carlos E. R. wrote:

...
On 2013-11-18 23:27, Bernhard Voelker wrote:

...
IIRC that was the "short read" issue, right?

No, not that one. The starting point was some new user asking for help on the forums about how to create the usb stick, using another Linux distro (thus, no Bugzillas here). The dd command failed, writeimage also failed, unet??? also failed. Googling or asking elsewhere, it was advised to use a plain "cp" or "cat" to create the image, and this finally worked. Some other people corroborated that it worked.

Then I started a thread on the mail list asking how was it possible that "cp" worked. It was a long thread, which concluded, IIRC, that "cp" was also a valid command to use in order to create the image. We talked about adding this new information to the wiki, and I finally added it, and Rajko validated it. Some other incorrect advice was removed.

Thanks for the summary. However, I cannot imagine a case for copying the content of a single file (or device) with "cp" which would not work with "dd" (plus the correct options). Would you like to shed some light on this (and dig in the archives), or should we draw the curtain over this case?

Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Carlos E. R.

23:34

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-11-19 00:06, cagsm wrote:

...

just verified this, and the usb key is a fat device with the help of these pendrivelinux guys or some software currently called or named

There is a paragraph about this or a similar procedure in the wiki article. I can not say if it is valid or not. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKKo/wACgkQtTMYHG2NR9Vm3wCeNX2jEAnNBuGtOBlgylhPJt+c 7VsAnRh4KHLf9bGhbAH6HaCE+k41Il/Q =5yca -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

cagsm

19 Nov 19 Nov

00:42

why i am writing this stuff, cos your cp copy command equals to extracting the contents of the tails iso in this example, thats probably also about your usb installation instructions and the cp command being used here live folder contents on tails xxxx.xx.xx 00:49 <DIR> . xxxx.xx.xx 00:49 <DIR> .. xxxx.xx.xx 00:39 20 Tails.module xxxx.xx.xx 00:14 39.280 filesystem.packages xxxx.xx.xx 00:13 908.271.616 filesystem.squashfs xxxx.xx.xx 00:14 10.412.036 initrd.img xxxx.xx.xx 00:14 10.583.656 initrd2.img xxxx.xx.xx 00:14 2.176.336 vmlinuz xxxx.xx.xx 00:14 2.335.680 vmlinuz2 7 File(s) 933,818,624 bytes On Tue, Nov 19, 2013 at 12:06 AM, cagsm wrote:

...

just verified this, and the usb key is a fat device with the help of these pendrivelinux guys or some software currently called or named "Universal-USB-Installer-1.9.4.7", and this creates some isolinux and/or syslinux folders on the top rootlevel of the fat formatted usb devices and then puts all sorts of configs (depending on which distro and what kind of linux and supported system it is dealing with) and then the usb device or disk is being made bootable and the actual content files in this case the ones from inside the tails .iso are extracted onto this usb disk device and then everything works fine.

at least for tails it works this way, your milage may vary and results may differ if Universal-USB-Installer-1.9.4.7 is working on the other near infinite number of distros supposedly being supported by it.

sample contents of disk toplevel: xxxx.xx.xx 00:14 <DIR> .disk xxxx.xx.xx 00:14 <DIR> live xxxx.xx.xx 00:55 49.070 Uni-USB-Installer-Copying.txt xxxx.xx.xx 00:55 17.888 Uni-USB-Installer-Readme.txt xxxx.xx.xx 00:42 18.092 license.txt xxxx.xx.xx 00:02 <DIR> syslinux xxxx.xx.xx 00:24 <DIR> uui xxxx.xx.xx 00:14 <DIR> isolinux 3 File(s) 85.050 bytes

give it a try

On Mon, Nov 18, 2013 at 11:59 PM, cagsm wrote:

...
isnt there some project guys who are methinks with these pendrivelinux website or stuff who offer their tiny installer/handler for a great number of distros, amongst them also suse methinks but i know for sure for example linux based tails (tor) distro. that pendrivelinux installer stack extracts the files from inside the tails .iso file (with 7zip commandline) and then puts it on a fat(fat12/16/32/whatever) usb disk or usb stick or usb key even and then adds some isolinux binary and config files and folders and some bootloader and bootsector onto this fat usb device and then all is running happily and tails tor distro can boot up and you can for example bootstrap into tor or upgrade some other tails usb stick with the more recent release.

isolinux hybridlinux and other buzzwords come to my mind.

On Mon, Nov 18, 2013 at 11:53 PM, Bernhard Voelker wrote:

...
On 11/18/2013 11:43 PM, Carlos E. R. wrote:

...
On 2013-11-18 23:27, Bernhard Voelker wrote:

...
IIRC that was the "short read" issue, right?

No, not that one. The starting point was some new user asking for help on the forums about how to create the usb stick, using another Linux distro (thus, no Bugzillas here). The dd command failed, writeimage also failed, unet??? also failed. Googling or asking elsewhere, it was advised to use a plain "cp" or "cat" to create the image, and this finally worked. Some other people corroborated that it worked.

Then I started a thread on the mail list asking how was it possible that "cp" worked. It was a long thread, which concluded, IIRC, that "cp" was also a valid command to use in order to create the image. We talked about adding this new information to the wiki, and I finally added it, and Rajko validated it. Some other incorrect advice was removed.

Thanks for the summary. However, I cannot imagine a case for copying the content of a single file (or device) with "cp" which would not work with "dd" (plus the correct options). Would you like to shed some light on this (and dig in the archives), or should we draw the curtain over this case?

Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Carlos E. R.

01:07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-11-19 01:42, cagsm wrote:

...

why i am writing this stuff, cos your cp copy command equals to extracting the contents of the tails iso in this example, thats probably also about your usb installation instructions and the cp command being used here

No. This command: cp image.iso /dev/sdb and this other: dd if=image.iso of=/dev/sdb do exactly the same (if all goes right; if not, there are some subtle, maybe dramatic, differences). Both are dangerous. Maybe one is simpler than the other. The cp command above does not extract the contents of the iso at all. If you are talking about the method to add multiple images on a FAT stick, I can not say a word about that.

...

...
...
...
Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Please trim the quoted material on your posts. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKKue4ACgkQtTMYHG2NR9WEwwCeIZhe2/+XJxdW0q2RegIIPXHN l0gAoJCIrUDNv7Jq9aHWZGkp6DkOVWgg =Mcq5 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Carlos E. R.

18 Nov 18 Nov

23:31

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-11-18 23:53, Bernhard Voelker wrote:

...

Thanks for the summary. However, I cannot imagine a case for copying the content of a single file (or device) with "cp" which would not work with "dd" (plus the correct options).

Me neither... but it happened.

...

Would you like to shed some light on this (and dig in the archives), or should we draw the curtain over this case?

http://lists.opensuse.org/opensuse/2013-08/msg00125.html [opensuse] Creating the distro USB stick with a simple 'cp' I would simply like to re-add that paragraph as an alternate method, as there was consensus that it was a valid method. Also the paragraph about persistent filesystem is obsolete for 13.1. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKKo2QACgkQtTMYHG2NR9UJGwCfbpS2pWonq05f18pKxC1/fRtH QoEAni1NOfD/Ya0OQFMMBoqgGN0u30uL =UUHS -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Christopher Hofmann

19 Nov 19 Nov

15:42

Hi all, Am 18.11.2013 15:01, schrieb Carlos E. R.:

...

Unetbootin is known to not work. I wrote a paragraph about that, but the paragraph has been removed:

I heavily worked on this page since it was way to complicated. Not even advanced users were able to follow it. However I removed the warning about instructions for other distibutions by accident. I re-added it, since it is of course valid.

...

The current instructions also mention how to «create a persistent file system» These are obsolete for 13.1, as it uses a different persistence method (and I think it does not work for 12.3 at all).

Honestly I did not check this. It was also there before I reworked it - but because of the size of the document it was not obvious that it was there. So if this is obsolete we can remove it, of course.

...

After a lot of discussion here on the mail list, I added a paragraph about an alternate method that works when dd does not:

I would only add this step with a clear description in which case this should be done. Otherwise it is confusing. Maybe it fits in the "Troubleshooting" section. Christopher -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Carlos E. R.

15:53

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2013-11-19 16:42, Christopher Hofmann wrote:

...

I heavily worked on this page since it was way to complicated. Not even advanced users were able to follow it.

I like most of the changes a lot, thanks.

...

...
The current instructions also mention how to «create a persistent file system» These are obsolete for 13.1, as it uses a different persistence method (and I think it does not work for 12.3 at all).

Honestly I did not check this. It was also there before I reworked it - but because of the size of the document it was not obvious that it was there. So if this is obsolete we can remove it, of course.

I learnt about it recently, too. AFAIK that method works till version 12.2, I read messages that it does not work for 12.3. And 13.1 has a different persistent filesystem that is enabled by default (I tried it on the rescue image, and other people corroborated on other images). I do not know how it works, nor how to enable or disable. It is important to rework that part, or remove till someone explains the method, because the described method will not work on 13.1, AFAIK. I think I saw a method to temporarily hide text in the wiki :-?

...

...
After a lot of discussion here on the mail list, I added a paragraph about an alternate method that works when dd does not:

I would only add this step with a clear description in which case this should be done. Otherwise it is confusing.

Maybe it fits in the "Troubleshooting" section.

That's fine with me. I can have a go at it later. But AFAIK it can be used in any case instead of the classic "dd" method. It is just an alternate method. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKLiZQACgkQtTMYHG2NR9WP7gCgmJ+TGh9ZDQozEZ0I8+jLbSs5 3yoAoIRKISbJBBPp0DsxqUfRboquVK9I =J70F -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Christopher Hofmann

21 Nov 21 Nov

11:01

Hi, Am 19.11.2013 16:53, schrieb Carlos E. R.:

...

But AFAIK it can be used in any case instead of the classic "dd" method. It is just an alternate method.

If course. But it needs some 'justification'. e.g. something like "In some rare cases 'dd' does not work properly. In this case ..." Otherwiese people that don't have a clue will be unsure which option to use and feel inconfiednt. Christopher -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

3810

Age (days ago)

3813

Last active (days ago)

List overview

Download

15 comments

4 participants

participants (4)

Bernhard Voelker
cagsm
Carlos E. R.
Christopher Hofmann

[opensuse-factory] USB installation instrucctions issues.

tags

participants (4)