I was going to do an install today but when I tried to import mount points from the old install the feature apparently is no longer in the partitioner. I certainly hope that feature is coming back soon....?? Anybody know? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/02/18 11:00, Chuck Davis wrote:
I was going to do an install today but when I tried to import mount points from the old install the feature apparently is no longer in the partitioner. I certainly hope that feature is coming back soon....?? Anybody know?
Here I am solely working from memory so I may be wrong...:-). Try left-clicking on the HDD (sdx, sdy, or whichever) in the LEFT column of the partitioner and you should find that the options will appear. BC -- Always be nice to people on your way up -- you'll see the same people on your way down. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin:
On 08/02/18 11:00, Chuck Davis wrote:
I was going to do an install today but when I tried to import mount points from the old install the feature apparently is no longer in the partitioner. I certainly hope that feature is coming back soon....?? Anybody know?
Here I am solely working from memory so I may be wrong...:-).
Check first the next time, it *has changed* .
Try left-clicking on the HDD (sdx, sdy, or whichever) in the LEFT column of the partitioner and you should find that the options will appear.
BC
-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team Linux user #548252 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin:
On 08/02/18 11:00, Chuck Davis wrote:
I was going to do an install today but when I tried to import mount points from the old install the feature apparently is no longer in the partitioner. I certainly hope that feature is coming back soon....?? Anybody know?
Here I am solely working from memory so I may be wrong...:-).
Check first the next time, it *has changed* .
It is very difficult to check something like that, as it only happens during system installation. Where is now that feature, import fstab? I also wanted to use this old feature and failed to find it a week ago. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin:
On 08/02/18 11:00, Chuck Davis wrote:
I was going to do an install today but when I tried to import mount points from the old install the feature apparently is no longer in the partitioner. I certainly hope that feature is coming back soon....?? Anybody know?
Here I am solely working from memory so I may be wrong...:-).
Check first the next time, it *has changed* .
It is very difficult to check something like that, as it only happens during system installation.
Where is now that feature, import fstab? I also wanted to use this old feature and failed to find it a week ago.
Maybe see boo#1078552 https://bugzilla.opensuse.org/show_bug.cgi?id=1078552 It's for leap15, but also about the new partitioner. -- Per Jessen, Zürich (1.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2018-02-08 at 16:41 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin:
On 08/02/18 11:00, Chuck Davis wrote:
I was going to do an install today but when I tried to import mount points from the old install the feature apparently is no longer in the partitioner. I certainly hope that feature is coming back soon....?? Anybody know?
Here I am solely working from memory so I may be wrong...:-).
Check first the next time, it *has changed* .
It is very difficult to check something like that, as it only happens during system installation.
Where is now that feature, import fstab? I also wanted to use this old feature and failed to find it a week ago.
Maybe see boo#1078552
https://bugzilla.opensuse.org/show_bug.cgi?id=1078552
It's for leap15, but also about the new partitioner.
It is related, but different feature. It existed in the past. This was, point the installer to an existing system root, it would read the fstab there, and apply it, instead of trying to guess where to install or asking where to install. It would also, at that point, read the user list and password, maybe other things. It did not read the package list, though. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlp8hNMACgkQtTMYHG2NR9UujQCgiJc/zxtyg+DPusTVJUMdhOjw NM8AnRd5B8ERLj60/T9v0PFCggp3O8F1 =i8nr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op donderdag 8 februari 2018 18:11:47 CET schreef Carlos E. R.:
On Thursday, 2018-02-08 at 16:41 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin:
On 08/02/18 11:00, Chuck Davis wrote:
I was going to do an install today but when I tried to import mount points from the old install the feature apparently is no longer in the partitioner. I certainly hope that feature is coming back soon....?? Anybody know?
Here I am solely working from memory so I may be wrong...:-).
Check first the next time, it *has changed* .
It is very difficult to check something like that, as it only happens during system installation.
Where is now that feature, import fstab? I also wanted to use this old feature and failed to find it a week ago.
Maybe see boo#1078552
https://bugzilla.opensuse.org/show_bug.cgi?id=1078552
It's for leap15, but also about the new partitioner.
It is related, but different feature. It existed in the past.
This was, point the installer to an existing system root, it would read the fstab there, and apply it, instead of trying to guess where to install or asking where to install.
It would also, at that point, read the user list and password, maybe other things. It did not read the package list, though
Not at that point, but at the point of user creation, same as where it is now.
-- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar)
-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team Linux user #548252 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-08 18:39, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 18:11:47 CET schreef Carlos E. R.:
On Thursday, 2018-02-08 at 16:41 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin:
On 08/02/18 11:00, Chuck Davis wrote: > I was going to do an install today but when I tried to import mount > points from the old install the feature apparently is no longer in > the > partitioner. I certainly hope that feature is coming back > soon....?? Anybody know?
Here I am solely working from memory so I may be wrong...:-).
Check first the next time, it *has changed* .
It is very difficult to check something like that, as it only happens during system installation.
Where is now that feature, import fstab? I also wanted to use this old feature and failed to find it a week ago.
Maybe see boo#1078552
https://bugzilla.opensuse.org/show_bug.cgi?id=1078552
It's for leap15, but also about the new partitioner.
It is related, but different feature. It existed in the past.
This was, point the installer to an existing system root, it would read the fstab there, and apply it, instead of trying to guess where to install or asking where to install.
It would also, at that point, read the user list and password, maybe other things. It did not read the package list, though
Not at that point, but at the point of user creation, same as where it is now.
In the old implementation, the import was earlier and affected several settings. The user settings were visible later, though, but the moment of saying from where to import was when reading fstab. I have not seen yet the new implementation in 15.0, busy. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
Op donderdag 8 februari 2018 21:06:32 CET schreef Carlos E. R.:
On 2018-02-08 18:39, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 18:11:47 CET schreef Carlos E. R.:
On Thursday, 2018-02-08 at 16:41 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin: > On 08/02/18 11:00, Chuck Davis wrote: >> I was going to do an install today but when I tried to import mount >> points from the old install the feature apparently is no longer in >> the >> partitioner. I certainly hope that feature is coming back >> soon....?? Anybody know? > > Here I am solely working from memory so I may be wrong...:-).
Check first the next time, it *has changed* .
It is very difficult to check something like that, as it only happens during system installation.
Where is now that feature, import fstab? I also wanted to use this old feature and failed to find it a week ago.
Maybe see boo#1078552
https://bugzilla.opensuse.org/show_bug.cgi?id=1078552
It's for leap15, but also about the new partitioner.
It is related, but different feature. It existed in the past.
This was, point the installer to an existing system root, it would read the fstab there, and apply it, instead of trying to guess where to install or asking where to install.
It would also, at that point, read the user list and password, maybe other things. It did not read the package list, though
Not at that point, but at the point of user creation, same as where it is now. In the old implementation, the import was earlier and affected several settings. The user settings were visible later, though, but the moment of saying from where to import was when reading fstab.
Nope, just cheched with the 42.3 install media. Import of mountpoints was only accessible through choosing the Expert Partitioner which sent you through to the detailed partitioning part where one would see "Import existing mountpoints" . The user import was, like now, in the user config part. The only practical difference is in the fact that the partitioner does not suggest the mountpoints.
I have not seen yet the new implementation in 15.0, busy.
-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team Linux user #548252 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-08 a las 23:00 +0100, Knurpht - Gertjan Lettink escribió:
Op donderdag 8 februari 2018 21:06:32 CET schreef Carlos E. R.:
On 2018-02-08 18:39, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 18:11:47 CET schreef Carlos E. R.:
On Thursday, 2018-02-08 at 16:41 +0100, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote: > Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin: >> On 08/02/18 11:00, Chuck Davis wrote: >>> I was going to do an install today but when I tried to import mount >>> points from the old install the feature apparently is no longer in >>> the >>> partitioner. I certainly hope that feature is coming back >>> soon....?? Anybody know? >> >> Here I am solely working from memory so I may be wrong...:-). > > Check first the next time, it *has changed* .
It is very difficult to check something like that, as it only happens during system installation.
Where is now that feature, import fstab? I also wanted to use this old feature and failed to find it a week ago.
Maybe see boo#1078552
https://bugzilla.opensuse.org/show_bug.cgi?id=1078552
It's for leap15, but also about the new partitioner.
It is related, but different feature. It existed in the past.
This was, point the installer to an existing system root, it would read the fstab there, and apply it, instead of trying to guess where to install or asking where to install.
It would also, at that point, read the user list and password, maybe other things. It did not read the package list, though
Not at that point, but at the point of user creation, same as where it is now. In the old implementation, the import was earlier and affected several settings. The user settings were visible later, though, but the moment of saying from where to import was when reading fstab.
Nope, just cheched with the 42.3 install media. Import of mountpoints was only accessible through choosing the Expert Partitioner which sent you through to the detailed partitioning part where one would see "Import existing mountpoints" . The user import was, like now, in the user config part. The only practical difference is in the fact that the partitioner does not suggest the mountpoints.
42.3 can import fstab? Where, exactly? I could not find it a week ago when I needed it. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlp84WkACgkQja8UbcUWM1z1gwD9Enp+RW6DGFn5Vptp/Uq2idY1 VQWrPeSNkQQkkKz4VW4A/3LFOp/XQx+YEDnivHz6R6r92+eLlR/De2N/g46Q+CtR =PWd2 -----END PGP SIGNATURE-----
Op vrijdag 9 februari 2018 00:46:49 CET schreef Carlos E. R.:
El 2018-02-08 a las 23:00 +0100, Knurpht - Gertjan Lettink escribió:
Op donderdag 8 februari 2018 21:06:32 CET schreef Carlos E. R.:
On 2018-02-08 18:39, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 18:11:47 CET schreef Carlos E. R.:
On Thursday, 2018-02-08 at 16:41 +0100, Per Jessen wrote:
Carlos E. R. wrote: > On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote: >> Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin: >>> On 08/02/18 11:00, Chuck Davis wrote: >>>> I was going to do an install today but when I tried to import >>>> mount >>>> points from the old install the feature apparently is no longer in >>>> the >>>> partitioner. I certainly hope that feature is coming back >>>> soon....?? Anybody know? >>> >>> Here I am solely working from memory so I may be wrong...:-). >> >> Check first the next time, it *has changed* . > > It is very difficult to check something like that, as it only happens > during system installation. > > Where is now that feature, import fstab? I also wanted to use this > old > feature and failed to find it a week ago.
Maybe see boo#1078552
https://bugzilla.opensuse.org/show_bug.cgi?id=1078552
It's for leap15, but also about the new partitioner.
It is related, but different feature. It existed in the past.
This was, point the installer to an existing system root, it would read the fstab there, and apply it, instead of trying to guess where to install or asking where to install.
It would also, at that point, read the user list and password, maybe other things. It did not read the package list, though
Not at that point, but at the point of user creation, same as where it is now.
In the old implementation, the import was earlier and affected several settings. The user settings were visible later, though, but the moment of saying from where to import was when reading fstab.
Nope, just cheched with the 42.3 install media. Import of mountpoints was only accessible through choosing the Expert Partitioner which sent you through to the detailed partitioning part where one would see "Import existing mountpoints" . The user import was, like now, in the user config part. The only practical difference is in the fact that the partitioner does not suggest the mountpoints.
42.3 can import fstab? Where, exactly? I could not find it a week ago when I needed it.
-- Cheers Carlos E. R.
(from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith))
At the point of the partitioning proposal, pick Expert ... . The detailed screen has an option "Import existing mount points". Once you click that a dialogue opens providing an option to whether or not format existing paritions. And before you ask, this is restricted to "system volumes" -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team Linux user #548252 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-09 00:51, Knurpht - Gertjan Lettink wrote:
Op vrijdag 9 februari 2018 00:46:49 CET schreef Carlos E. R.:
42.3 can import fstab? Where, exactly? I could not find it a week ago when I needed it.
At the point of the partitioning proposal, pick Expert ... . The detailed screen has an option "Import existing mount points". Once you click that a dialogue opens providing an option to whether or not format existing paritions. And before you ask, this is restricted to "system volumes"
Thanks, I'll try this when I get back home. It is too late for that machine, but I want to know where I missed it :-) -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
Op donderdag 8 februari 2018 15:19:08 CET schreef Carlos E. R.:
On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin:
On 08/02/18 11:00, Chuck Davis wrote:
I was going to do an install today but when I tried to import mount points from the old install the feature apparently is no longer in the partitioner. I certainly hope that feature is coming back soon....?? Anybody know?
Here I am solely working from memory so I may be wrong...:-).
Check first the next time, it *has changed* .
It is very difficult to check something like that, as it only happens during system installation.
What is so hard about firing up a VM with an install medium, and check before guessing ?
Where is now that feature, import fstab? I also wanted to use this old feature and failed to find it a week ago.
Fired up a VM with the NET install iso, Expert Partitioner says: "Start with existing partitions" ..... What it doesn't do (yet?) is importing the mountpoints. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team Linux user #548252 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2018-02-08 at 17:00 +0100, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 15:19:08 CET schreef Carlos E. R.:
On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin:
On 08/02/18 11:00, Chuck Davis wrote:
I was going to do an install today but when I tried to import mount points from the old install the feature apparently is no longer in the partitioner. I certainly hope that feature is coming back soon....?? Anybody know?
Here I am solely working from memory so I may be wrong...:-).
Check first the next time, it *has changed* .
It is very difficult to check something like that, as it only happens during system installation.
What is so hard about firing up a VM with an install medium, and check before guessing ?
Takes an ahour, as compared to someone already knowing :-) In my case, I tried hard last week to find the feature and failed. I need more eyes.
Where is now that feature, import fstab? I also wanted to use this old feature and failed to find it a week ago.
Fired up a VM with the NET install iso, Expert Partitioner says: "Start with existing partitions" ..... What it doesn't do (yet?) is importing the mountpoints.
Well, thanks for confirming. Notice that the feature did exist in the past, I have used it. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlp8g/sACgkQtTMYHG2NR9UeCgCdHxUOjoxLl9FyTK6a/LgfijUC EpYAn3cyXibcXTZXV0n6oBxd+fy4L6U3 =r2Bc -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op donderdag 8 februari 2018 18:08:04 CET schreef Carlos E. R.:
On Thursday, 2018-02-08 at 17:00 +0100, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 15:19:08 CET schreef Carlos E. R.:
On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin:
On 08/02/18 11:00, Chuck Davis wrote:
I was going to do an install today but when I tried to import mount points from the old install the feature apparently is no longer in the partitioner. I certainly hope that feature is coming back soon....?? Anybody know?
Here I am solely working from memory so I may be wrong...:-).
Check first the next time, it *has changed* .
It is very difficult to check something like that, as it only happens during system installation.
What is so hard about firing up a VM with an install medium, and check before guessing ?
Takes an ahour, as compared to someone already knowing :-
An hour? Took me 2 minutes to download the NET iso, 2 minutes to fire up the installer to the point of partitioning. And, in matters like testing I'd even take the hour to move from guessing to being sure.
In my case, I tried hard last week to find the feature and failed. I need more eyes.
Where is now that feature, import fstab? I also wanted to use this old feature and failed to find it a week ago.
Fired up a VM with the NET install iso, Expert Partitioner says: "Start with existing partitions" ..... What it doesn't do (yet?) is importing the mountpoints.
Well, thanks for confirming.
Notice that the feature did exist in the past, I have used it.
Me too. AFAICS the only thing it doesn't do (yet) is the mountpoints.
-- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar)
-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team Linux user #548252 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 18:08:04 CET schreef Carlos E. R.:
On Thursday, 2018-02-08 at 17:00 +0100, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 15:19:08 CET schreef Carlos E. R.:
On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin:
On 08/02/18 11:00, Chuck Davis wrote: > I was going to do an install today but when I tried to import > mount points from the old install the feature apparently is no > longer in the > partitioner. I certainly hope that feature is coming back > soon....?? Anybody know?
Here I am solely working from memory so I may be wrong...:-).
Check first the next time, it *has changed* .
It is very difficult to check something like that, as it only happens during system installation.
What is so hard about firing up a VM with an install medium, and check before guessing ?
Takes an ahour, as compared to someone already knowing :-
An hour? Took me 2 minutes to download the NET iso, 2 minutes to fire up the installer to the point of partitioning. And, in matters like testing I'd even take the hour to move from guessing to being sure.
I presume Carlos meant the time to get acquainted with setting up a VM. -- Per Jessen, Zürich (0.9°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op donderdag 8 februari 2018 18:56:35 CET schreef Per Jessen:
Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 18:08:04 CET schreef Carlos E. R.:
On Thursday, 2018-02-08 at 17:00 +0100, Knurpht - Gertjan Lettink
wrote:
Op donderdag 8 februari 2018 15:19:08 CET schreef Carlos E. R.:
On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin: > On 08/02/18 11:00, Chuck Davis wrote: >> I was going to do an install today but when I tried to import >> mount points from the old install the feature apparently is no >> longer in the >> partitioner. I certainly hope that feature is coming back >> soon....?? Anybody know? > > Here I am solely working from memory so I may be wrong...:-).
Check first the next time, it *has changed* .
It is very difficult to check something like that, as it only happens during system installation.
What is so hard about firing up a VM with an install medium, and check before guessing ?
Takes an ahour, as compared to someone already knowing :-
An hour? Took me 2 minutes to download the NET iso, 2 minutes to fire up the installer to the point of partitioning. And, in matters like testing I'd even take the hour to move from guessing to being sure.
I presume Carlos meant the time to get acquainted with setting up a VM.
Even then, better than guessing. The hour spent would be a one time issue, and create some means of reference to what's really there, also for future occasions. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team Linux user #548252 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-08 18:56, Per Jessen wrote:
Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 18:08:04 CET schreef Carlos E. R.:
On Thursday, 2018-02-08 at 17:00 +0100, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 15:19:08 CET schreef Carlos E. R.:
On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin: > On 08/02/18 11:00, Chuck Davis wrote: >> I was going to do an install today but when I tried to import >> mount points from the old install the feature apparently is no >> longer in the >> partitioner. I certainly hope that feature is coming back >> soon....?? Anybody know? > > Here I am solely working from memory so I may be wrong...:-).
Check first the next time, it *has changed* .
It is very difficult to check something like that, as it only happens during system installation.
What is so hard about firing up a VM with an install medium, and check before guessing ?
Takes an ahour, as compared to someone already knowing :-)
An hour? Took me 2 minutes to download the NET iso, 2 minutes to fire up the installer to the point of partitioning. And, in matters like testing I'd even take the hour to move from guessing to being sure.
I presume Carlos meant the time to get acquainted with setting up a VM.
He is much faster than me :-) But first I have to decide which VM to use, look at its user and partition current setup, write it somewhere, stop it if it is in use (and start it first to look inside), boot it from "external" media (reach the bios window to change boot settings, takes several attempts to get to that window), then get to the point where the install can import settings. My virtual machines run slow - it took the system minutes the other day to boot 42.3 install system in real hardware. Perhaps 7 minutes, I have no idea why so much. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
Op donderdag 8 februari 2018 21:14:11 CET schreef Carlos E. R.:
On 2018-02-08 18:56, Per Jessen wrote:
Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 18:08:04 CET schreef Carlos E. R.:
On Thursday, 2018-02-08 at 17:00 +0100, Knurpht - Gertjan Lettink
wrote:
Op donderdag 8 februari 2018 15:19:08 CET schreef Carlos E. R.:
On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote: > Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin: >> On 08/02/18 11:00, Chuck Davis wrote: >>> I was going to do an install today but when I tried to import >>> mount points from the old install the feature apparently is no >>> longer in the >>> partitioner. I certainly hope that feature is coming back >>> soon....?? Anybody know? >> >> Here I am solely working from memory so I may be wrong...:-). > > Check first the next time, it *has changed* .
It is very difficult to check something like that, as it only happens during system installation.
What is so hard about firing up a VM with an install medium, and check before guessing ?
Takes an ahour, as compared to someone already knowing :-)
An hour? Took me 2 minutes to download the NET iso, 2 minutes to fire up the installer to the point of partitioning. And, in matters like testing I'd even take the hour to move from guessing to being sure.
I presume Carlos meant the time to get acquainted with setting up a VM.
He is much faster than me :-)
But first I have to decide which VM to use, look at its user and partition current setup, write it somewhere, stop it if it is in use (and start it first to look inside), boot it from "external" media (reach the bios window to change boot settings, takes several attempts to get to that window), then get to the point where the install can import settings. My virtual machines run slow - it took the system minutes the other day to boot 42.3 install system in real hardware. Perhaps 7 minutes, I have no idea why so much.
It doesn't even need a complete VM to see this. Start Vbox, add the iso to it (as a virtual optical disk) and boot. That really is all I did. In fact, I abused an already available VM, by booting from the iso, instead of it's virtual harddisk ( vdi ). If your Leap 42.3 system takes 7 minutes to boot, something definitely is wrong. Even a P4 with 5400 rpm HDD and 2 GB RAM doesn't take that long. Run systemd-analyze blame to see what's slowing down the machine. Furthermore, you seem to be missing my point: "believe", "guess", "from memory" are no valid testing criteria. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team Linux user #548252 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2018-02-08 a las 23:10 +0100, Knurpht - Gertjan Lettink escribió:
Op donderdag 8 februari 2018 21:14:11 CET schreef Carlos E. R.:
On 2018-02-08 18:56, Per Jessen wrote:
Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 18:08:04 CET schreef Carlos E. R.:
On Thursday, 2018-02-08 at 17:00 +0100, Knurpht - Gertjan Lettink
wrote:
Op donderdag 8 februari 2018 15:19:08 CET schreef Carlos E. R.: > On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote: >> Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin: >>> On 08/02/18 11:00, Chuck Davis wrote: >>>> I was going to do an install today but when I tried to import >>>> mount points from the old install the feature apparently is no >>>> longer in the >>>> partitioner. I certainly hope that feature is coming back >>>> soon....?? Anybody know? >>> >>> Here I am solely working from memory so I may be wrong...:-). >> >> Check first the next time, it *has changed* . > > It is very difficult to check something like that, as it only > happens during system installation.
What is so hard about firing up a VM with an install medium, and check before guessing ?
Takes an ahour, as compared to someone already knowing :-)
An hour? Took me 2 minutes to download the NET iso, 2 minutes to fire up the installer to the point of partitioning. And, in matters like testing I'd even take the hour to move from guessing to being sure.
I presume Carlos meant the time to get acquainted with setting up a VM.
He is much faster than me :-)
But first I have to decide which VM to use, look at its user and partition current setup, write it somewhere, stop it if it is in use (and start it first to look inside), boot it from "external" media (reach the bios window to change boot settings, takes several attempts to get to that window), then get to the point where the install can import settings. My virtual machines run slow - it took the system minutes the other day to boot 42.3 install system in real hardware. Perhaps 7 minutes, I have no idea why so much.
It doesn't even need a complete VM to see this. Start Vbox, add the iso to it (as a virtual optical disk) and boot. That really is all I did. In fact, I abused an already available VM, by booting from the iso, instead of it's virtual harddisk ( vdi ).
Yes, I would use an existing VM, but I would have to locate a suitable one for testing the import, booting them for having a look inside, and then rebooting the one I want. Then carefully progress checking all the options to see where the one I want is, if it is somewhere.
If your Leap 42.3 system takes 7 minutes to boot, something definitely is wrong. Even a P4 with 5400 rpm HDD and 2 GB RAM doesn't take that long.
No, the installation system did. Not the installed system. The kernel and image took an awful time to load, and once it was running, it insisted on checking the floppy perhaps a hundred times at every step (well, not really a hundred times). Yes, I do have a real floppy drive in this machine...
Run systemd-analyze blame to see what's slowing down the machine.
Furthermore, you seem to be missing my point: "believe", "guess", "from memory" are no valid testing criteria.
No, so I simply asked whether somebody already knew. I did not want anyone to try. As I said, I did carefully search for this option in 42.3 install a week ago and did not find it, so there is no purpose in me trying again. It took me an hour of trying different procedures (three, I think) in order to get the exact partition layout I wanted, as I found no way to import the existing fstab. - -- Cheers Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlp84LcACgkQja8UbcUWM1xZpgD+K2RjyUV91U2xNGmHbpWF71sl rdyv3XF2bT3sNJ4PFWsA/jtRHkMJEl9Z+mX0O78H4BFDdu8WSI3sC1B4Tgtt8IRq =DZvZ -----END PGP SIGNATURE-----
Carlos E. R. composed on 2018-02-09 00:43 (UTC+0100):
No, the installation system did. Not the installed system. The kernel and image took an awful time to load, and once it was running, it insisted on checking the floppy perhaps a hundred times at every step (well, not really a hundred times). Yes, I do have a real floppy drive in this machine...
Include installation option BrokenModules=floppy to prevent that annoyance. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-09 01:18, Felix Miata wrote:
Carlos E. R. composed on 2018-02-09 00:43 (UTC+0100):
No, the installation system did. Not the installed system. The kernel and image took an awful time to load, and once it was running, it insisted on checking the floppy perhaps a hundred times at every step (well, not really a hundred times). Yes, I do have a real floppy drive in this machine...
Include installation option
BrokenModules=floppy
to prevent that annoyance.
But you see, I do have a floppy, I want the system to be aware of it. I alse heard the DVD drive being probed as many times. The probing was fast, move the head a bit and spin the motor; but it was done too many times. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [02-09-18 07:27]:
On 2018-02-09 01:18, Felix Miata wrote:
Carlos E. R. composed on 2018-02-09 00:43 (UTC+0100):
No, the installation system did. Not the installed system. The kernel and image took an awful time to load, and once it was running, it insisted on checking the floppy perhaps a hundred times at every step (well, not really a hundred times). Yes, I do have a real floppy drive in this machine...
Include installation option
BrokenModules=floppy
to prevent that annoyance.
But you see, I do have a floppy, I want the system to be aware of it. I alse heard the DVD drive being probed as many times. The probing was fast, move the head a bit and spin the motor; but it was done too many times.
this is understood, but you were concerned about the time involved and remarked that the install trying to access or setup the floppy was consuming a great amount of time. also, the install was only a test for an availble or not feature. all besides the fact that you could install the floppy drive after all was said and done, even if more was said than done. you have voiced much concern about features being lost, but seem much determined to present impediments to finding ways to ascertain the features are lost. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-09 13:50, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-09-18 07:27]:
On 2018-02-09 01:18, Felix Miata wrote:
Carlos E. R. composed on 2018-02-09 00:43 (UTC+0100):
No, the installation system did. Not the installed system. The kernel and image took an awful time to load, and once it was running, it insisted on checking the floppy perhaps a hundred times at every step (well, not really a hundred times). Yes, I do have a real floppy drive in this machine...
Include installation option
BrokenModules=floppy
to prevent that annoyance.
But you see, I do have a floppy, I want the system to be aware of it. I alse heard the DVD drive being probed as many times. The probing was fast, move the head a bit and spin the motor; but it was done too many times.
this is understood, but you were concerned about the time involved and remarked that the install trying to access or setup the floppy was consuming a great amount of time. also, the install was only a test for an availble or not feature. all besides the fact that you could install the floppy drive after all was said and done, even if more was said than done.
No, you are confused. I talked about three issues. I never said the floppy being an impediment for a quick test, as that is done in a virtual machine, and there I typically disable the floppy on the VM BIOS. The second issue is that in my desktop machine, the kernel loading (before it probes for anything) took minutes. Several minutes. It was astonishing. This also happens in my virtual machines, IIRC. And the third issue, in that desktop machine the system was probing the floppy (and the DVD drive) many times during the procedure. Issues two and three are not related at all with the quick test. Sorry if I have expressed myself in a way that increased the confusion.
you have voiced much concern about features being lost, but seem much determined to present impediments to finding ways to ascertain the features are lost.
You missed the point about me saying that I did use an actual hour, perhaps two, trying to find that missing feature. I failed to find it. Knurpht finally understood and told me where to find it :-) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. composed on 2018-02-09 14:41 (UTC+0100):
The second issue is that in my desktop machine, the kernel loading (before it probes for anything) took minutes. Several minutes. It was astonishing. This also happens in my virtual machines, IIRC.
I had slow kernel/initrd loading on 2-3 machines for over 2 years (maybe 3?), until about 2 weeks ago, reported here without response once or twice and also: https://www.linuxquestions.org/questions/linux-general-1/grub-legacy-delay-o... BIOS changes radically reduced the delays here. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2018-02-09 at 17:46 -0500, Felix Miata wrote:
Carlos E. R. composed on 2018-02-09 14:41 (UTC+0100):
The second issue is that in my desktop machine, the kernel loading (before it probes for anything) took minutes. Several minutes. It was astonishing. This also happens in my virtual machines, IIRC.
I had slow kernel/initrd loading on 2-3 machines for over 2 years (maybe 3?), until about 2 weeks ago, reported here without response once or twice and also: https://www.linuxquestions.org/questions/linux-general-1/grub-legacy-delay-o...
But I use Grub 2, not grub legacy. And, I use a separate /boot partition which is ext2, not ext4.
BIOS changes radically reduced the delays here.
If I recall correctly, my bios ahci settings are mislabeled, I had to try several rounds back in the time to get things working right. I would not like to touch those settings again. Besides that, it is the 42.3 install system which takes minutes to load, not the normal system. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlp+y90ACgkQtTMYHG2NR9VYuACcC36MgXkheJjQlap6QfVTWCda isUAoJYYs1xZULZf3BJPAtycCrmsd2gr =QsRM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. wrote:
On 2018-02-09 01:18, Felix Miata wrote:
Carlos E. R. composed on 2018-02-09 00:43 (UTC+0100):
No, the installation system did. Not the installed system. The kernel and image took an awful time to load, and once it was running, it insisted on checking the floppy perhaps a hundred times at every step (well, not really a hundred times). Yes, I do have a real floppy drive in this machine...
Include installation option
BrokenModules=floppy
to prevent that annoyance.
But you see, I do have a floppy, I want the system to be aware of it.
You only add the above during the installation.
I alse heard the DVD drive being probed as many times. The probing was fast, move the head a bit and spin the motor; but it was done too many times.
I haven't noticed that, but most of our systems don't have a DVD drive. -- Per Jessen, Zürich (1.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-09 14:12, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-02-09 01:18, Felix Miata wrote:
Carlos E. R. composed on 2018-02-09 00:43 (UTC+0100):
No, the installation system did. Not the installed system. The kernel and image took an awful time to load, and once it was running, it insisted on checking the floppy perhaps a hundred times at every step (well, not really a hundred times). Yes, I do have a real floppy drive in this machine...
Include installation option
BrokenModules=floppy
to prevent that annoyance.
But you see, I do have a floppy, I want the system to be aware of it.
You only add the above during the installation.
Maybe. By the time I noticed the floppy nuisance I had to decide whether to abort or continue. And I did not remember that hack :-) It is very easy in retrospect to suggest "do this or that" ;-)
I alse heard the DVD drive being probed as many times. The probing was fast, move the head a bit and spin the motor; but it was done too many times.
I haven't noticed that, but most of our systems don't have a DVD drive.
I only noticed it with the 42.3 upgrade, and because it happened a second later than it probed the floppy. YaST probed both a hundred times perhaps, in total. That is, probe, do something or another, perhaps put some text, probe again, and again, some dialog... It surprised me, but I did not take notes. It would need a video to find out when the probes were made. Notice that when the probe floppy issue happened years ago, each probe took several long seconds. This doesn't happen now, it has improved a lot. Each probe is fast now. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. composed on 2018-02-09 14:53 (UTC+0100):
It is very easy in retrospect to suggest "do this or that" ;-)
Hence use of various "cheats", e.g.: 1-online upgrades instead of offline or fresh installation 2-fresh installs using Grub instead of conventional boot media, copying and editing as required, an appropriate previously used stanza for the purpose and saved somewhere on the LAN. 3-alias Mnt='mount | egrep -v "cgroup|rpc|tmpfs|^sys|on /dev|on /proc|on /sys|on /var" | sort ' 4-alias rpmqa='rpm -qa | sort | grep ' :-D -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-09 19:33, Felix Miata wrote:
Carlos E. R. composed on 2018-02-09 14:53 (UTC+0100):
It is very easy in retrospect to suggest "do this or that" ;-)
Hence use of various "cheats", e.g.:
1-online upgrades instead of offline or fresh installation
Ah, I prefer offline upgrades. Online, if the system crashes or electricity fails, you may be doomed. Then they can add scripts to handle special situations. And since Leap or a bit before, the offline upgrade can keep all the repos you need and download from them. It is something I must write about in the wiki upgrade page. Although there is something that fails in my machines with this, but the yast logs were rotated too fast and I don't have a copy to do a bugzilla. The upgrade stopped some 570 rpms early: <http://susepaste.org/31345231>
2-fresh installs using Grub instead of conventional boot media, copying and editing as required, an appropriate previously used stanza for the purpose and saved somewhere on the LAN.
Hum.
3-alias Mnt='mount | egrep -v "cgroup|rpc|tmpfs|^sys|on /dev|on /proc|on /sys|on /var" | sort '
Ah! I like this one. Let me try... Nice! I'd have to add, ie remove, gvfsd-fuse and vmware-vmblock. What is the "|on" for? See this in man mount: Listing the mounts The listing mode is maintained for backward compatibility only. For more robust and customizable output use findmnt(8), especially in your scripts. Note that control characters in the mountpoint name are replaced with '?'. The following command lists all mounted filesystems (of type type): mount [-l] [-t type] The option -l adds labels to this listing. See below. Try findmnt, looks nice. I haven't read its manual yet.
4-alias rpmqa='rpm -qa | sort | grep '
:-D
I suppose this one you have to add what to grep on. Yes, it is something I do often, but I type it. Or recover from previous history. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. composed on 2018-02-09 2:10 (UTC+0100):
Felix Miata wrote:
Hence use of various "cheats", e.g.:
1-online upgrades instead of offline or fresh installation
Ah, I prefer offline upgrades. Online, if the system crashes or electricity fails, you may be doomed.
You might, but not here. "commit.downloadMode = DownloadAsNeeded" plus UPS do well enough avoiding any such trouble, proven over many moons via lots of TW installations.
2-fresh installs using Grub instead of conventional boot media, copying and editing as required, an appropriate previously used stanza for the purpose and saved somewhere on the LAN.
Hum.
Is that a question?
3-alias Mnt='mount | egrep -v "cgroup|rpc|tmpfs|^sys|on /dev|on /proc|on /sys|on /var" | sort '
Ah! I like this one. Let me try... Nice!
I'd have to add, ie remove, gvfsd-fuse and vmware-vmblock.
What is the "|on" for?
Other than preventing display of filesystems I have no interest in seeing listed, I don't remember.
See this in man mount:
Listing the mounts The listing mode is maintained for backward compatibility only.
For more robust and customizable output use findmnt(8), especially in your scripts. Note that control characters in the mountpoint name are replaced with '?'.
I don't see any options directing it to emulate my alias. -D is almost close, including *tmpfs, which is always 0% use and not filesystems on /dev/sd*.
The following command lists all mounted filesystems (of type type):
mount [-l] [-t type]
The option -l adds labels to this listing. See below.
Try findmnt, looks nice. I haven't read its manual yet.
4-alias rpmqa='rpm -qa | sort | grep '
:-D
I suppose this one you have to add what to grep on. Yes, it is something I do often, but I type it. Or recover from previous history.
Lots easier to type 5 characters than to locate and edit previous use in history, and (remember to) pipe through sort. For zypper I use mini-scripts, e.g. zypse, zypsei, zypseo, etc. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2018-02-09 at 17:16 -0500, Felix Miata wrote:
Carlos E. R. composed on 2018-02-09 2:10 (UTC+0100):
Felix Miata wrote:
Hence use of various "cheats", e.g.:
1-online upgrades instead of offline or fresh installation
Ah, I prefer offline upgrades. Online, if the system crashes or electricity fails, you may be doomed.
You might, but not here. "commit.downloadMode = DownloadAsNeeded" plus UPS do well enough avoiding any such trouble, proven over many moons via lots of TW installations.
I doubt that the 15 minutes granted by the typical UPS would be enough to finish the install, even if the network survives the power failure. The telco hardware in my house doesn't have batteries, I had to install an UPS of my own there.
2-fresh installs using Grub instead of conventional boot media, copying and editing as required, an appropriate previously used stanza for the purpose and saved somewhere on the LAN.
Hum.
Is that a question?
Thinking noise :-)
3-alias Mnt='mount | egrep -v "cgroup|rpc|tmpfs|^sys|on /dev|on /proc|on /sys|on /var" | sort '
Ah! I like this one. Let me try... Nice!
I'd have to add, ie remove, gvfsd-fuse and vmware-vmblock.
What is the "|on" for?
Other than preventing display of filesystems I have no interest in seeing listed, I don't remember.
Hum. I'll have to try without and see what happens. [...] Without the "|on" it doesn't work. debugfs on /sys/kernel/debug type debugfs (rw,relatime) ^^
See this in man mount:
Listing the mounts The listing mode is maintained for backward compatibility only.
For more robust and customizable output use findmnt(8), especially in your scripts. Note that control characters in the mountpoint name are replaced with '?'.
I don't see any options directing it to emulate my alias. -D is almost close, including *tmpfs, which is always 0% use and not filesystems on /dev/sd*.
No, I did not say that it displays the same thing. It doesn't. Just that it is a very intersting command for displaying the mounts - and I only used the default command with no options. I see options to display only certain filesystem types, but here it would be insteresting to not display certain types. Wait, there is, the word "no": -O, --options list Limit the set of printed filesystems. More than one option may be specified in a comma-separated list. The -t and -O options are cumulative in effect. It is different from -t in that each option is matched exactly; a leading no at the beginning does not have global meaning. The "no" can used for individual items in the list. The "no" prefix interpretation can be disabled by "+" prefix. -t, --types list Limit the set of printed filesystems. More than one type may be specified in a comma-separated list. The list of filesystem types can be prefixed with no to specify the filesystem types on which no action should be taken. For more details see mount(8). cer@Telcontar:~> findmnt -t no cgroup TARGET SOURCE FSTYPE OPTIONS /sys/fs/cgroup/systemd cgroup cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd /sys/fs/cgroup/hugetlb cgroup cgroup So it is not that way. Ah, it is "-t nocgroup". [...] Try: findmnt -t nocgroup,nosysfs,notmpfs,nosecurityfs,nodevtmpfs,nodebugfs,nodevpts,nomqueue,nohugetlbfs,nobinfmt_misc,noproc,noconfigfs,nopstore,notracefs - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlp+0AsACgkQtTMYHG2NR9VvvwCePidqZWcaftlSW/+/9bWTi22B 5hYAn13cRCVcsLTQNWhNJOjt3eHVhmes =PWZ5 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. composed on 2018-02-10 11:57 (UTC+0100):
On Friday, 2018-02-09 at 17:16 -0500, Felix Miata wrote:
"commit.downloadMode = DownloadAsNeeded" plus UPS do well enough avoiding any such trouble, proven over many moons via lots of TW installations.
I doubt that the 15 minutes granted by the typical UPS would be enough to finish the install, even if the network survives the power failure. The telco hardware in my house doesn't have batteries, I had to install an UPS of my own there.
commit.downloadMode = DownloadAsNeeded" downloads an rpm, installs that rpm, downloads, installs, downloads, installs, etc. Nothing breaks to hit Ctrl-C, and the worst from an exhausted battery on a smart UPS might be one rpm needs to be force reinstalled after power comes back on. It's not much different from having the power continually on, but having the WAN die for several hours in the middle of upgrading, which used to be quite common here. Zypper's fault handling is far better than DNF's. All 8 UPSes here are my own.
I don't see any options directing it to emulate my alias. -D is almost close, including *tmpfs, which is always 0% use and not filesystems on /dev/sd*.
No, I did not say that it displays the same thing. It doesn't. Just that it is a very intersting command for displaying the mounts - and I only used the default command with no options.
One crucial point of using an alias here is sorted output, an option I don't see in the man page of findmnt. I did try this: findmnt -D | grep SOURCE ; findmnt -D | sort | egrep -v 'tmpfs|SOURCE' In Konsole it works nicely, but on the vttys, the header from the first run has wildly different column spacing. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2018-02-10 at 06:59 -0500, Felix Miata wrote:
Carlos E. R. composed on 2018-02-10 11:57 (UTC+0100):
On Friday, 2018-02-09 at 17:16 -0500, Felix Miata wrote:
"commit.downloadMode = DownloadAsNeeded" plus UPS do well enough avoiding any such trouble, proven over many moons via lots of TW installations.
I doubt that the 15 minutes granted by the typical UPS would be enough to finish the install, even if the network survives the power failure. The telco hardware in my house doesn't have batteries, I had to install an UPS of my own there.
commit.downloadMode = DownloadAsNeeded" downloads an rpm, installs that rpm, downloads, installs, downloads, installs, etc. Nothing breaks to hit Ctrl-C, and the worst from an exhausted battery on a smart UPS might be one rpm needs to be force reinstalled after power comes back on. It's not much different from having the power continually on, but having the WAN die for several hours in the middle of upgrading, which used to be quite common here. Zypper's fault handling is far better than DNF's.
Install one rpm for the kernel, crash before installing the other kernel things rpm. The worst possible moment.
All 8 UPSes here are my own.
I don't see any options directing it to emulate my alias. -D is almost close, including *tmpfs, which is always 0% use and not filesystems on /dev/sd*.
No, I did not say that it displays the same thing. It doesn't. Just that it is a very intersting command for displaying the mounts - and I only used the default command with no options.
One crucial point of using an alias here is sorted output, an option I don't see in the man page of findmnt.
I did try this:
findmnt -D | grep SOURCE ; findmnt -D | sort | egrep -v 'tmpfs|SOURCE'
In Konsole it works nicely, but on the vttys, the header from the first run has wildly different column spacing.
Don't sort findmnt output, it gets worse, because it creates a tree of mountpoints. Don't use -D. And instead of grepping for "tmpfs", use -t notmpfs. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlp+6O8ACgkQtTMYHG2NR9Wq4QCfaKPtMWfwARTHSvGrA+l3W0oz lCMAoIDmAgU724SGTudQExkVSgW1cflr =a3sY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2018-02-10 at 13:43 +0100, Carlos E. R. wrote:
On Saturday, 2018-02-10 at 06:59 -0500, Felix Miata wrote:
Carlos E. R. composed on 2018-02-10 11:57 (UTC+0100):
On Friday, 2018-02-09 at 17:16 -0500, Felix Miata wrote:
"commit.downloadMode = DownloadAsNeeded" plus UPS do well enough avoiding any such trouble, proven over many moons via lots of TW installations.
I doubt that the 15 minutes granted by the typical UPS would be enough to finish the install, even if the network survives the power failure. The telco hardware in my house doesn't have batteries, I had to install an UPS of my own there.
commit.downloadMode = DownloadAsNeeded" downloads an rpm, installs that rpm, downloads, installs, downloads, installs, etc. Nothing breaks to hit Ctrl-C, and the worst from an exhausted battery on a smart UPS might be one rpm needs to be force reinstalled after power comes back on. It's not much different from having the power continually on, but having the WAN die for several hours in the middle of upgrading, which used to be quite common here. Zypper's fault handling is far better than DNF's.
Install one rpm for the kernel, crash before installing the other kernel things rpm. The worst possible moment.
I use "DownloadInHeaps", but in this case I would use "DownloadInAdvance". - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlp+6c0ACgkQtTMYHG2NR9V5RACdF8DVV3BxSyHJE273YAiGbhE+ ZCYAn27k6jXTeZQ6iWu2TCNgnCvEXIhR =/NG3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10 February 2018 at 13:43, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Saturday, 2018-02-10 at 06:59 -0500, Felix Miata wrote:
Carlos E. R. composed on 2018-02-10 11:57 (UTC+0100):
On Friday, 2018-02-09 at 17:16 -0500, Felix Miata wrote:
"commit.downloadMode = DownloadAsNeeded" plus UPS do well enough avoiding any such trouble, proven over many moons via lots of TW installations.
I doubt that the 15 minutes granted by the typical UPS would be enough to finish the install, even if the network survives the power failure. The telco hardware in my house doesn't have batteries, I had to install an UPS of my own there.
commit.downloadMode = DownloadAsNeeded" downloads an rpm, installs that rpm, downloads, installs, downloads, installs, etc. Nothing breaks to hit Ctrl-C, and the worst from an exhausted battery on a smart UPS might be one rpm needs to be force reinstalled after power comes back on. It's not much different from having the power continually on, but having the WAN die for several hours in the middle of upgrading, which used to be quite common here. Zypper's fault handling is far better than DNF's.
Install one rpm for the kernel, crash before installing the other kernel things rpm. The worst possible moment.
Fine, then you want to use atomic updates. Use them - transactional-update is supported in Leap 42.3, 15, and Tumbleweed https://lists.opensuse.org/opensuse-factory/2017-01/msg00367.html https://www.youtube.com/watch?v=oUREPvOObTw
All 8 UPSes here are my own.
I don't see any options directing it to emulate my alias. -D is almost close, including *tmpfs, which is always 0% use and not filesystems on /dev/sd*.
No, I did not say that it displays the same thing. It doesn't. Just that it is a very intersting command for displaying the mounts - and I only used the default command with no options.
One crucial point of using an alias here is sorted output, an option I don't see in the man page of findmnt.
I did try this:
findmnt -D | grep SOURCE ; findmnt -D | sort | egrep -v 'tmpfs|SOURCE'
In Konsole it works nicely, but on the vttys, the header from the first run has wildly different column spacing.
Don't sort findmnt output, it gets worse, because it creates a tree of mountpoints. Don't use -D. And instead of grepping for "tmpfs", use -t notmpfs.
- -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iEYEARECAAYFAlp+6O8ACgkQtTMYHG2NR9Wq4QCfaKPtMWfwARTHSvGrA+l3W0oz lCMAoIDmAgU724SGTudQExkVSgW1cflr =a3sY -----END PGP SIGNATURE-----
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-10 15:07, Richard Brown wrote:
On 10 February 2018 at 13:43, Carlos E. R. <> wrote:
Install one rpm for the kernel, crash before installing the other kernel things rpm. The worst possible moment.
Fine, then you want to use atomic updates. Use them - transactional-update is supported in Leap 42.3, 15, and Tumbleweed
https://lists.opensuse.org/opensuse-factory/2017-01/msg00367.html
Interesting! Let's see those links. [...] Oh... :-( TK> What do you need to be able to use it? TK> - A recent installation of Tumbleweed (updating from older versions, TK> especially installations made with openSUSE 13.x, will not work) TK> with btrfs and snapshots enabled. If your installation is not TK> recent enough, the script will tell and warn you and refuse to work. Ok, but my system has been upgraded from SuSE 6.2 upwards (ie, it is much older than 13.x), so it will not work. And I do not use btrfs, either. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 10 February 2018 at 19:59, Carlos E. R. <robin.listas@telefonica.net> wrote:
On 2018-02-10 15:07, Richard Brown wrote:
On 10 February 2018 at 13:43, Carlos E. R. <> wrote:
Install one rpm for the kernel, crash before installing the other kernel things rpm. The worst possible moment.
Fine, then you want to use atomic updates. Use them - transactional-update is supported in Leap 42.3, 15, and Tumbleweed
https://lists.opensuse.org/opensuse-factory/2017-01/msg00367.html
Interesting!
Let's see those links. [...] Oh... :-(
TK> What do you need to be able to use it? TK> - A recent installation of Tumbleweed (updating from older versions, TK> especially installations made with openSUSE 13.x, will not work) TK> with btrfs and snapshots enabled. If your installation is not TK> recent enough, the script will tell and warn you and refuse to work.
Ok, but my system has been upgraded from SuSE 6.2 upwards (ie, it is much older than 13.x), so it will not work. And I do not use btrfs, either.
Welcome to the 21st century, we have new technologies, built to address the problems with your primitive systems from the dark times. We think you'll find it interesting here if you adopt our modern ways ;) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 10 Feb 2018 20:21:36 +0100 Richard Brown <RBrownCCB@opensuse.org> wrote:
On 10 February 2018 at 19:59, Carlos E. R. <robin.listas@telefonica.net> wrote:
On 2018-02-10 15:07, Richard Brown wrote:
On 10 February 2018 at 13:43, Carlos E. R. <> wrote:
Install one rpm for the kernel, crash before installing the other kernel things rpm. The worst possible moment.
Fine, then you want to use atomic updates. Use them - transactional-update is supported in Leap 42.3, 15, and Tumbleweed
https://lists.opensuse.org/opensuse-factory/2017-01/msg00367.html
Interesting!
Let's see those links. [...] Oh... :-(
TK> What do you need to be able to use it? TK> - A recent installation of Tumbleweed (updating from older TK> versions, especially installations made with openSUSE 13.x, TK> will not work) with btrfs and snapshots enabled. If your TK> installation is not recent enough, the script will tell and TK> warn you and refuse to work.
Ok, but my system has been upgraded from SuSE 6.2 upwards (ie, it is much older than 13.x), so it will not work. And I do not use btrfs, either.
Welcome to the 21st century, we have new technologies, built to address the problems with your primitive systems from the dark times.
We think you'll find it interesting here if you adopt our modern ways ;)
Very amusing. But not terribly helpful ... How does he 'adopt your modern ways' if his system started life before your arbitrary cut off date? Even leaving aside his preference to avoid the 'one filesystem to rule them all' mantra. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10 February 2018 at 20:50, Dave Howorth <dave@howorth.org.uk> wrote:
Ok, but my system has been upgraded from SuSE 6.2 upwards (ie, it is much older than 13.x), so it will not work. And I do not use btrfs, either.
Welcome to the 21st century, we have new technologies, built to address the problems with your primitive systems from the dark times.
We think you'll find it interesting here if you adopt our modern ways ;)
Very amusing. But not terribly helpful ...
How does he 'adopt your modern ways' if his system started life before your arbitrary cut off date? Even leaving aside his preference to avoid the 'one filesystem to rule them all' mantra.
There isn't a commercially available operating system in the world that provides endless, retroactive support for systems installed originally N years in the past. Technology has developed a lot since 1999. Backwards compatibility/forwards migrate-ability cannot always be guaranteed. If you carry such expectations for a community maintained operating system, then the nicest word I can use to describe your mindset is 'deluded'. Especially when you consider the community organisation responsible for the operating system in question didn't even exist back in 1999 We will always do our best, but some new features and functionality will forever be unavailable to people who cling to installations inherited from a past full of now-obsolete technologies and now-invalid decisions. We can't always undo the consequences of mistakes made in the past. Nor can we expect the developers of the past to have built in forward compatibility for technologies they would have never been able to expect in the future. So to answer your question directly:
How does he 'adopt your modern ways' if his system started life before your arbitrary cut off date?
You install your system fresh, it's not hard. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-10 21:16, Richard Brown wrote:
On 10 February 2018 at 20:50, Dave Howorth <dave@howorth.org.uk> wrote:
Ok, but my system has been upgraded from SuSE 6.2 upwards (ie, it is much older than 13.x), so it will not work. And I do not use btrfs, either.
Welcome to the 21st century, we have new technologies, built to address the problems with your primitive systems from the dark times.
We think you'll find it interesting here if you adopt our modern ways ;)
Very amusing. But not terribly helpful ...
How does he 'adopt your modern ways' if his system started life before your arbitrary cut off date? Even leaving aside his preference to avoid the 'one filesystem to rule them all' mantra.
There isn't a commercially available operating system in the world that provides endless, retroactive support for systems installed originally N years in the past.
And where do you get the idea that I'm running SuSE 6.4? I'm running Leap 42.3, but the machine had the proper software and hardware upgrades during all that time, in the proper manner and the adequate manner. This is a supported scenario, and you should be proud of it, not criticize it. I'm sure that Windows may claim to support that scenario, but I'm almost sure that it will fail. Bravo! to Linux, and SuSE, SUSE, and openSUSE. On the other hand... My laptop started life with W7 on about 2010, and now has W10, so they also support upgrades... Not hardware upgrades because of Licensing, though. And now W10 is a continuous updated system, like Tumbleweed. So they say. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 2018-02-10 20:50, Dave Howorth wrote:
On Sat, 10 Feb 2018 20:21:36 +0100 Richard Brown <> wrote:
On 10 February 2018 at 19:59, Carlos E. R. <robin.listas@telefonica.net> wrote:
On 2018-02-10 15:07, Richard Brown wrote:
On 10 February 2018 at 13:43, Carlos E. R. <> wrote:
Install one rpm for the kernel, crash before installing the other kernel things rpm. The worst possible moment.
Fine, then you want to use atomic updates. Use them - transactional-update is supported in Leap 42.3, 15, and Tumbleweed
https://lists.opensuse.org/opensuse-factory/2017-01/msg00367.html
Interesting!
Let's see those links. [...] Oh... :-(
TK> What do you need to be able to use it? TK> - A recent installation of Tumbleweed (updating from older TK> versions, especially installations made with openSUSE 13.x, TK> will not work) with btrfs and snapshots enabled. If your TK> installation is not recent enough, the script will tell and TK> warn you and refuse to work.
Ok, but my system has been upgraded from SuSE 6.2 upwards (ie, it is much older than 13.x), so it will not work. And I do not use btrfs, either.
Welcome to the 21st century, we have new technologies, built to address the problems with your primitive systems from the dark times.
We think you'll find it interesting here if you adopt our modern ways ;)
Very amusing. But not terribly helpful ...
How does he 'adopt your modern ways' if his system started life before your arbitrary cut off date? Even leaving aside his preference to avoid the 'one filesystem to rule them all' mantra.
Right. I'm not going to risk btrfs, I'm scared shit by it. Yes, I'm very well aware of its advantages, but they do not manage to outweigh its risks. According to the Wikipedia, Btrfs was introduced on March 2009, and ext4 on October 2006, so they are from similar times. Besides that, I use XFS which shares devs with btrfs. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Richard Brown composed on 2018-02-10 20:21 (UTC+0100):
Carlos E. R. wrote:
Richard Brown wrote:
Fine, then you want to use atomic updates. Use them - transactional-update is supported in Leap 42.3, 15, and Tumbleweed
https://lists.opensuse.org/opensuse-factory/2017-01/msg00367.html
That looks a lot like the way DNF works in practice, which IME is awful, filling up filesystems with rpms, then complaining they cannot be installed; often impossible to fix if interrupted. I wonder if modern snapshot/rollback implementations would be as popular as they seem to be if their developers and users weren't using solid state storage devices instead of rotating rust. I remember when a complete OS fit on a 720k floppy, and know that previously they had fit on less than 160k.
I can't deal with Thorsten's diction. Is there a transcript somewhere for that video? Does it contain material missing from his year-ago list post?
Interesting!
Let's see those links. [...] Oh... :-(
TK> What do you need to be able to use it? TK> - A recent installation of Tumbleweed (updating from older versions, TK> especially installations made with openSUSE 13.x, will not work) TK> with btrfs and snapshots enabled. If your installation is not TK> recent enough, the script will tell and warn you and refuse to work.
Ok, but my system has been upgraded from SuSE 6.2 upwards (ie, it is much older than 13.x), so it will not work. And I do not use btrfs, either.
Welcome to the 21st century, we have new technologies, built to address the problems with your primitive systems from the dark times.
We think you'll find it interesting here if you adopt our modern ways ;)
Adopting requires adapting, which requires time. I don't much care for allocating time to fixing what ain't broke, like many who have been around more than 6 decades, and value what's left of our time more than we used to. I have more than enough excess of todos over round tuits. Many things work as well as they did days, weeks, months, years, decades or centuries ago, at least as well as new, ostensibly improved versions complete with their brand new bugs, and even when not as well, well enough to stick with, with or without reasons that have anything to do with the technology involved. My car, newly acquired 28 months ago, is 2 decades old. My house, which dad built when I was 13, is 53 years old. CD players had been around at least 5 years before I stopped buying vinyl. DVD player/recorders had been around more than a decade before I bought one. I still have no mobile phone or pay TV, and use daily the 12' satellite dish I bought 30 years ago. OS/2 was over a decade old before I switched to it (instead of Win98 or NT) from DesqView. I test drove SUSE roughly 5 years before using it to replace OS/2. EXT4 was mainstream probably a decade before I started using it instead of EXT3, and still I usually don't use it except for / filesystems. Installation targets and /homes here remain on rotating rust exclusively. Is the tail wagging the dog? BTRFS here would require magnitudes of changes in the way I do things, not the least of which are disk space allocation and backup/restore procedures. All of my installations are on multiboot PCs. Most of my installations have freespace somewhere in the 0-25% range on the / filesystem and have been installed without recommends, or separate filesystems for any but /home and /usr/local. I cannot see snapshotting on a single storage device in my foreseeable future. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10 February 2018 at 21:54, Felix Miata <mrmazda@earthlink.net> wrote:
https://lists.opensuse.org/opensuse-factory/2017-01/msg00367.html
That looks a lot like the way DNF works in practice, which IME is awful, filling up filesystems with rpms, then complaining they cannot be installed; often impossible to fix if interrupted.
Then you have fundamentally misunderstood the benefit of transactional-update Any issue, any failure, any problem with the upgrade leads to the snapshot being discarded. This can be detected during the update, or after the update on next boot. No data stored on disk. zero space in use. zero changes made to the running system. Nothing to fix, because nothing changed. Very different from the typically snapshot arrangement we have on 'traditional' *SUSE systems (yes, I am now referring to btrfs rootfs as 'traditional' - because it's old compared to this stuff). In that case we have to take snapshots before and after any update to take into account other activities on the rootfs, post install scripts, other services running, other user processes, and the like and that approach eats up space, and has more things that can go wrong with it. Transactional-update just uses 1 snapshot at a time, and has no need for historical ones (unless you really want them for some reason), so it's infinitely more efficient.
Welcome to the 21st century, we have new technologies, built to address the problems with your primitive systems from the dark times.
We think you'll find it interesting here if you adopt our modern ways ;)
Adopting requires adapting, which requires time. I don't much care for allocating time to fixing what ain't broke, like many who have been around more than 6 decades, and value what's left of our time more than we used to. I have more than enough excess of todos over round tuits. Many things work as well as they did days, weeks, months, years, decades or centuries ago, at least as well as new, ostensibly improved versions complete with their brand new bugs, and even when not as well, well enough to stick with, with or without reasons that have anything to do with the technology involved. My car, newly acquired 28 months ago, is 2 decades old. My house, which dad built when I was 13, is 53 years old. CD players had been around at least 5 years before I stopped buying vinyl. DVD player/recorders had been around more than a decade before I bought one. I still have no mobile phone or pay TV, and use daily the 12' satellite dish I bought 30 years ago. OS/2 was over a decade old before I switched to it (instead of Win98 or NT) from DesqView. I test drove SUSE roughly 5 years before using it to replace OS/2. EXT4 was mainstream probably a decade before I started using it instead of EXT3, and still I usually don't use it except for / filesystems. Installation targets and /homes here remain on rotating rust exclusively. Is the tail wagging the dog?
BTRFS here would require magnitudes of changes in the way I do things, not the least of which are disk space allocation and backup/restore procedures. All of my installations are on multiboot PCs. Most of my installations have freespace somewhere in the 0-25% range on the / filesystem and have been installed without recommends, or separate filesystems for any but /home and /usr/local. I cannot see snapshotting on a single storage device in my foreseeable future.
See my post titled 'Ancient History' and share your thoughts there, I think that's a better topic for such philosophical discussions. I think it's fair to say I find your mindset hard to grasp and think that you've had plenty of time to start getting to grips with this new stuff. I mean, it's not like you don't have much spare time - the amount you post on this mailinglist suggests you have an abundance of it ;) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. composed on 2018-02-10 07:43 (UTC-0500):
On Saturday, 2018-02-10 at 06:59 -0500, Felix Miata wrote:
commit.downloadMode = DownloadAsNeeded" downloads an rpm, installs that rpm, downloads, installs, downloads, installs, etc. Nothing breaks to hit Ctrl-C, and the worst from an exhausted battery on a smart UPS might be one rpm needs to be force reinstalled after power comes back on. It's not much different from having the power continually on, but having the WAN die for several hours in the middle of upgrading, which used to be quite common here. Zypper's fault handling is far better than DNF's.
Install one rpm for the kernel, crash before installing the other kernel things rpm. The worst possible moment.
Doesn't happen here: First, the rpm/zypper are robust, apparently depending little to none on particular versions for functionality following processing hiccups. Second: kernels are locked. They get separately installed if and when I choose. Typically it happens only right before a reboot that follows updating. Third: I have my own implementation of DownloadInHeaps (usually run from multi-user): 1: #!/bin/sh # /usr/local/zypstart zypper -v in --download-in-advance zypper libzypp libsolv-tools rpm openSUSE-release zypper -v in --download-in-advance device-mapper dmraid glibc lvm2 multipath-tools mdadm systemd udev 2: evaluate output, tweak locks, add/delete specific packages (typically glibc-locale, which often does not find freespace adequate: https://bugzilla.opensuse.org/show_bug.cgi?id=720150 ), etc. 3: zypper -v up -> g # (DownloadAsNeeded configured; repeat 2) 4: zypper -v up -> y 5: zypper -v dup -> g # (repeat 2) 6: zypper -v dup -> y # if TW or otherwise desired 7: zypper --no-refresh se -si | grep 'tem Pac' | grep -v plication # (repeat 2) 8: (optional) install (rpm -ivh) previously (wget) downloaded kernel 9: (optional) reboot Anywhere within points 2 thru 8 I've been able to interrupt, including reboot, before continuing, without apparent negative impact. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-10 20:57, Felix Miata wrote:
Carlos E. R. composed on 2018-02-10 07:43 (UTC-0500):
On Saturday, 2018-02-10 at 06:59 -0500, Felix Miata wrote:
commit.downloadMode = DownloadAsNeeded" downloads an rpm, installs that rpm, downloads, installs, downloads, installs, etc. Nothing breaks to hit Ctrl-C, and the worst from an exhausted battery on a smart UPS might be one rpm needs to be force reinstalled after power comes back on. It's not much different from having the power continually on, but having the WAN die for several hours in the middle of upgrading, which used to be quite common here. Zypper's fault handling is far better than DNF's.
Install one rpm for the kernel, crash before installing the other kernel things rpm. The worst possible moment.
Doesn't happen here:
First, the rpm/zypper are robust, apparently depending little to none on particular versions for functionality following processing hiccups.
Second: kernels are locked. They get separately installed if and when I choose. Typically it happens only right before a reboot that follows updating.
Third: I have my own implementation of DownloadInHeaps (usually run from multi-user):
1: #!/bin/sh # /usr/local/zypstart zypper -v in --download-in-advance zypper libzypp libsolv-tools rpm openSUSE-release zypper -v in --download-in-advance device-mapper dmraid glibc lvm2 multipath-tools mdadm systemd udev 2: evaluate output, tweak locks, add/delete specific packages (typically glibc-locale, which often does not find freespace adequate: https://bugzilla.opensuse.org/show_bug.cgi?id=720150 ), etc. 3: zypper -v up -> g # (DownloadAsNeeded configured; repeat 2) 4: zypper -v up -> y 5: zypper -v dup -> g # (repeat 2) 6: zypper -v dup -> y # if TW or otherwise desired 7: zypper --no-refresh se -si | grep 'tem Pac' | grep -v plication # (repeat 2) 8: (optional) install (rpm -ivh) previously (wget) downloaded kernel 9: (optional) reboot
Anywhere within points 2 thru 8 I've been able to interrupt, including reboot, before continuing, without apparent negative impact.
Ah :-) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. composed on 2018-02-09 07:26 (UTC-0500):
On 2018-02-09 01:18, Felix Miata wrote:
Carlos E. R. composed on 2018-02-09 00:43 (UTC+0100):
No, the installation system did. Not the installed system. The kernel and image took an awful time to load, and once it was running, it insisted on checking the floppy perhaps a hundred times at every step (well, not really a hundred times). Yes, I do have a real floppy drive in this machine...
Include installation option
BrokenModules=floppy
to prevent that annoyance.
But you see, I do have a floppy, I want the system to be aware of it.
So do I, several. Can't using it wait until after installation is done? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-09 17:43, Felix Miata wrote:
Carlos E. R. composed on 2018-02-09 07:26 (UTC-0500):
On 2018-02-09 01:18, Felix Miata wrote:
Carlos E. R. composed on 2018-02-09 00:43 (UTC+0100):
No, the installation system did. Not the installed system. The kernel and image took an awful time to load, and once it was running, it insisted on checking the floppy perhaps a hundred times at every step (well, not really a hundred times). Yes, I do have a real floppy drive in this machine...
Include installation option
BrokenModules=floppy
to prevent that annoyance.
But you see, I do have a floppy, I want the system to be aware of it.
So do I, several. Can't using it wait until after installation is done?
Oh, I don't use it. Since I bought the machine in 2009 I have used it less than a dozen times. I bought it just in case... I do have hundreds of floppies, though. I simply do not remember now if using "BrokenModules=floppy" would then make the machine not aware that there is a floppy after the install. Then I did not remember about "BrokenModules=floppy" at the time, and if I did, I would have to decide whether to reboot or continue :-D -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Carlos E. R. composed on 2018-02-09 19:30 (UTC+0100):
I simply do not remember now if using "BrokenModules=floppy" would then make the machine not aware that there is a floppy after the install.
The general rule is that cmdline options are options only for the specific boot for which they were included. The only possible exceptions I can think of are networking-related on an installation (linuxrc) boot. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2018-02-09 at 19:11 -0500, Felix Miata wrote:
Carlos E. R. composed on 2018-02-09 19:30 (UTC+0100):
I simply do not remember now if using "BrokenModules=floppy" would then make the machine not aware that there is a floppy after the install.
The general rule is that cmdline options are options only for the specific boot for which they were included. The only possible exceptions I can think of are networking-related on an installation (linuxrc) boot.
Yes, but if the installer is told to not see the floppy, it will not install nor do things related to the floppy, and thus floppy things would need to be done later, manually, without knowing what was left to be done (maybe nothing). - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlp+yagACgkQtTMYHG2NR9XdswCdFVX1EjXMah//b/qE8XAYI8pK zzMAnAmRAlU+2WqVRPTCZazHV2XpJfQv =HMdw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. composed on 2018-02-10 11:30 (UTC+0100):
On Friday, 2018-02-09 at 19:11 -0500, Felix Miata wrote:
Carlos E. R. composed on 2018-02-09 19:30 (UTC+0100):
I simply do not remember now if using "BrokenModules=floppy" would then make the machine not aware that there is a floppy after the install.
The general rule is that cmdline options are options only for the specific boot for which they were included. The only possible exceptions I can think of are networking-related on an installation (linuxrc) boot.
Yes, but if the installer is told to not see the floppy, it will not install nor do things related to the floppy, and thus floppy things would need to be done later, manually, without knowing what was left to be done (maybe nothing).
I'm pretty sure there is no configuring to be done WRT floppy drives. What little is actually required is integrated in the kernel to be done on the fly with each access. The BrokenModules option is just a way to get installation to complete without wasting time trying to kill the /dev/fd0 hardware in the process. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Carlos E. R. composed on 2018-02-08 21:14 (UTC+0100):
it took the system minutes the other day to boot 42.3 install system in real hardware. Perhaps 7 minutes, I have no idea why so much.
I usually do my installations from net installation media. When I catch a slow download.opensuse.org mirror for fetching the 6-part installation system, it likely takes around that long to get YaST started. The biggest packages commonly seem to come from the slowest mirrors. :-p -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-09 01:03, Felix Miata wrote:
Carlos E. R. composed on 2018-02-08 21:14 (UTC+0100):
it took the system minutes the other day to boot 42.3 install system in real hardware. Perhaps 7 minutes, I have no idea why so much.
I usually do my installations from net installation media. When I catch a slow download.opensuse.org mirror for fetching the 6-part installation system, it likely takes around that long to get YaST started. The biggest packages commonly seem to come from the slowest mirrors. :-p
No, I was using the full image on a USB 2 stick. It was very strange. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2018-02-08 at 21:14 +0100, Carlos E. R. wrote:
On 2018-02-08 18:56, Per Jessen wrote:
Knurpht - Gertjan Lettink wrote:
...
What is so hard about firing up a VM with an install medium, and check before guessing ?
Takes an ahour, as compared to someone already knowing :-)
An hour? Took me 2 minutes to download the NET iso, 2 minutes to fire up the installer to the point of partitioning. And, in matters like testing I'd even take the hour to move from guessing to being sure.
I presume Carlos meant the time to get acquainted with setting up a VM.
He is much faster than me :-)
But first I have to decide which VM to use, look at its user and partition current setup, write it somewhere, stop it if it is in use (and start it first to look inside), boot it from "external" media (reach the bios window to change boot settings, takes several attempts to get to that window), then get to the point where the install can import settings. My virtual machines run slow - it took the system minutes the other day to boot 42.3 install system in real hardware. Perhaps 7 minutes, I have no idea why so much.
I just booted "openSUSE-Tumbleweed-DVD-x86_64-Snapshot20180214-Media.iso" in vmware player. It is 25 minutes and the thing is still initializing. I haven't been able yet to do anything except enter on grub screen. USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND cer 18158 0.3 1.1 1110020 94580 pts/34 Sl+ 11:34 0:05 | | | \_ /usr/lib/vmware/bin/vmplayer It is 12:00 now... so 25 minutes including the 5 minutes to define the machine and point to the iso. It took some time trying to download some addon xml file, I think. Now it is "initializing..." Posibly RAM is too short. I use vmware defaults, 3/4 of a gig. I may have to go out and abort. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEUEARECAAYFAlqGuksACgkQtTMYHG2NR9UyPACWNx6oXrnqmnCuV8SWRji6yCDI GwCeKFcy9g+Tkie4D4WbQU5YXeoKeyo= =Blc+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Feb 16, 2018 at 2:02 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
Posibly RAM is too short. I use vmware defaults, 3/4 of a gig.
Could be too low. I run all VMs now with 1G after using 768M for some time. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-16 13:03, Andrei Borzenkov wrote:
On Fri, Feb 16, 2018 at 2:02 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
Posibly RAM is too short. I use vmware defaults, 3/4 of a gig.
Could be too low. I run all VMs now with 1G after using 768M for some time.
Yes, I aborted and restarted with 1 gig and it run fine. However, I failed to make it fully encrypted, which was the purpose of my testing. I'll try again, watching my step, and ask if it fails again. Basically, I did this: Expert partitioner, start with current proposal. Mine is going to use GPT. Delete all partitions except bios one. Add new partition, type "raw volume (unformatted). Next screen has LVM selected. Tick on "Encrypt device". Enter password. Then... I don't know, it is LVM, so go to volume management, and follow my nose... But on boot it doesn't ask for my disk password, something failed. I'll try again this afternoon, now I have to go. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Op vrijdag 16 februari 2018 12:02:35 CET schreef Carlos E. R.:
On Thursday, 2018-02-08 at 21:14 +0100, Carlos E. R. wrote:
On 2018-02-08 18:56, Per Jessen wrote:
Knurpht - Gertjan Lettink wrote: ...
What is so hard about firing up a VM with an install medium, and check before guessing ?
Takes an ahour, as compared to someone already knowing :-)
An hour? Took me 2 minutes to download the NET iso, 2 minutes to fire up the installer to the point of partitioning. And, in matters like testing I'd even take the hour to move from guessing to being sure.
I presume Carlos meant the time to get acquainted with setting up a VM.
He is much faster than me :-)
But first I have to decide which VM to use, look at its user and partition current setup, write it somewhere, stop it if it is in use (and start it first to look inside), boot it from "external" media (reach the bios window to change boot settings, takes several attempts to get to that window), then get to the point where the install can import settings. My virtual machines run slow - it took the system minutes the other day to boot 42.3 install system in real hardware. Perhaps 7 minutes, I have no idea why so much.
I just booted "openSUSE-Tumbleweed-DVD-x86_64-Snapshot20180214-Media.iso" in vmware player. It is 25 minutes and the thing is still initializing. I haven't been able yet to do anything except enter on grub screen.
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND cer 18158 0.3 1.1 1110020 94580 pts/34 Sl+ 11:34 0:05 | | | \_ /usr/lib/vmware/bin/vmplayer
It is 12:00 now... so 25 minutes including the 5 minutes to define the machine and point to the iso.
It took some time trying to download some addon xml file, I think. Now it is "initializing..."
Posibly RAM is too short. I use vmware defaults, 3/4 of a gig.
And not a bit too short. Requirements include 2GB of RAM
I may have to go out and abort.
-- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar)
-- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team Linux user #548252 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
17.02.2018 21:21, Knurpht - Gertjan Lettink пишет:
Posibly RAM is too short. I use vmware defaults, 3/4 of a gig.
And not a bit too short. Requirements include 2GB of RAM
Where are those reqiorements listed? I install all TW VMs with 1G RAM and net install, so far it worked. It is possible that new partitioner suddenly demands the whole 1G extra for itself of course. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-02-17 20:04, Andrei Borzenkov wrote:
17.02.2018 21:21, Knurpht - Gertjan Lettink пишет:
Posibly RAM is too short. I use vmware defaults, 3/4 of a gig.
And not a bit too short. Requirements include 2GB of RAM
Where?
Where are those reqiorements listed? I install all TW VMs with 1G RAM and net install, so far it worked. It is possible that new partitioner suddenly demands the whole 1G extra for itself of course.
I opened a Bugzilla perhaps a year or more ago about the installer not saying it was short of RAM. I run several install tests to find out the limit. All my Linux VMs have 1 gig or less, they run fine. I only had problems with the installers recently. VMware is not aware of those RAM requirements. Select "openSUSE 64 bit" and it automatically selects 3/4 gig ram and 20 gigs for the disk. Perhaps someone with authority can tell them, at the enterprise level. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Andrei Borzenkov wrote:
17.02.2018 21:21, Knurpht - Gertjan Lettink пишет:
Posibly RAM is too short. I use vmware defaults, 3/4 of a gig.
And not a bit too short. Requirements include 2GB of RAM
Where are those reqiorements listed? I install all TW VMs with 1G RAM and net install, so far it worked.
Ditto. Latest one with TW today. -- Per Jessen, Zürich (1.6°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zaterdag 17 februari 2018 20:04:25 CET schreef Andrei Borzenkov:
17.02.2018 21:21, Knurpht - Gertjan Lettink пишет:
Posibly RAM is too short. I use vmware defaults, 3/4 of a gig.
And not a bit too short. Requirements include 2GB of RAM
Where are those reqiorements listed? I install all TW VMs with 1G RAM and net install, so far it worked. It is possible that new partitioner suddenly demands the whole 1G extra for itself of course.
I stand corrected, it's 1 GB minimum, 2 GB recommended. See https://en.opensuse.org/Hardware_requirements In virt-manager's KVM/Qemu VM 1GB, 2GB, 4GB settings make a lot of difference, Specially running the installer. With 4GB the VM and install feel like installing on bare metal with 4GB of RAM. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team Linux user #548252 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2018-02-18 at 04:52 +0100, Knurpht - Gertjan Lettink wrote:
Op zaterdag 17 februari 2018 20:04:25 CET schreef Andrei Borzenkov:
17.02.2018 21:21, Knurpht - Gertjan Lettink пишет:
Posibly RAM is too short. I use vmware defaults, 3/4 of a gig.
And not a bit too short. Requirements include 2GB of RAM
Where are those reqiorements listed? I install all TW VMs with 1G RAM and net install, so far it worked. It is possible that new partitioner suddenly demands the whole 1G extra for itself of course.
I stand corrected, it's 1 GB minimum, 2 GB recommended. See https://en.opensuse.org/Hardware_requirements
That makes sense, thanks :-)
In virt-manager's KVM/Qemu VM 1GB, 2GB, 4GB settings make a lot of difference, Specially running the installer. With 4GB the VM and install feel like installing on bare metal with 4GB of RAM.
As I /only/ have 8 GiB of RAM, giving two to a virtual machine makes the entire machine slugish. I give two to the Windows 10 machine and I know. Linux machines, on the other hand, run fine with 3/4 of a gig, but of course not using memory hungry apps: I have no reason to run LO in a VM. It is the installer which has problems with memory: SWAP is not yet available to the machine. The installer doesn't say it is starving, but fails in strange ways. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlqJaH4ACgkQtTMYHG2NR9W7GQCgjkO6PFb8mEsUIgMpIm6S2CG/ jG4An10KMYBSpIx5HTQt8y+ZUGUr4nkF =YI8a -----END PGP SIGNATURE-----
On 09/02/18 01:19, Carlos E. R. wrote:
On 2018-02-08 14:49, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin:
On 08/02/18 11:00, Chuck Davis wrote:
I was going to do an install today but when I tried to import mount points from the old install the feature apparently is no longer in the partitioner. I certainly hope that feature is coming back soon....?? Anybody know? Here I am solely working from memory so I may be wrong...:-). Check first the next time, it *has changed* . It is very difficult to check something like that, as it only happens during system installation.
It doesn't mater, Carlos, just "check"... Sheesh!
Where is now that feature, import fstab? I also wanted to use this old feature and failed to find it a week ago.
BC -- Always be nice to people on your way up -- you'll see the same people on your way down. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 09/02/18 00:49, Knurpht - Gertjan Lettink wrote:
Op donderdag 8 februari 2018 01:42:38 CET schreef Basil Chupin:
On 08/02/18 11:00, Chuck Davis wrote:
I was going to do an install today but when I tried to import mount points from the old install the feature apparently is no longer in the partitioner. I certainly hope that feature is coming back soon....?? Anybody know? Here I am solely working from memory so I may be wrong...:-). Check first the next time, it *has changed* .
And why don't you first think before writing? I am not about to re-install from afresh in order to "check", alright?
Try left-clicking on the HDD (sdx, sdy, or whichever) in the LEFT column of the partitioner and you should find that the options will appear.
BC
BC -- Always be nice to people on your way up -- you'll see the same people on your way down. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (10)
-
Andrei Borzenkov -
Basil Chupin -
Carlos E. R. -
Chuck Davis -
Dave Howorth -
Felix Miata -
Knurpht - Gertjan Lettink -
Patrick Shanahan -
Per Jessen -
Richard Brown