[opensuse] experience: update to 15.1 from 15.0
have laptop with bad rotating rust. using to monitor/update other systems and read mail, ... with tmux and system on external 8gb cf-card which is no longer compatible to any of my cameras. burned 15.0 iso image using dd updated several times over last several weeks added repos and several apps for convenience did s/15.0/15.1 /etc/zypp/repos.d/* zypper -v ref;zypper -v dup --no-r -d;zypper -v dup --no-r rebooted zypper -v ref;zypper -v up --no-r -d;zypper -v up --no-r rebooted working system with no apparent problems except required "netconfig update -f" or would not resolve addrs has wheel group reboot requires systemctl isolate reboot;systemctl restart network wicked wickedd or no network available when system comes back df -m / Filesystem 1M-blocks Used Available Use% Mounted on LiveOS_rootfs 6758 4737 1659 75% / with 15.0 was only ~60% iirc both with --no-recommends and no *-lang files quite usable as remote monitor/workstation. no file storage. -- (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
Hi, You can try to use BFQ scheduler to slightly speed things up, as described in my blog here: http://www.vacuum-tube.eu/wp/?p=612 + noatime option for ext4 partitions. Additionally, I bought a number of el-cheapo KingSpec SSD from Aliexpress, today 720 GB cost only 57 Euro including shipping. Speed tests can be seen here, for an old i3 PC its quite good: https://www.youtube.com/watch?v=YT8Co1ObqSs&feature=youtu.be
On 24 May 2019, at 17:03, Patrick Shanahan <paka@opensuse.org> wrote:
have laptop with bad rotating rust. using to monitor/update other systems and read mail, ... with tmux and system on external 8gb cf-card which is no longer compatible to any of my cameras.
burned 15.0 iso image using dd updated several times over last several weeks added repos and several apps for convenience
did s/15.0/15.1 /etc/zypp/repos.d/* zypper -v ref;zypper -v dup --no-r -d;zypper -v dup --no-r rebooted zypper -v ref;zypper -v up --no-r -d;zypper -v up --no-r rebooted
working system with no apparent problems except required "netconfig update -f" or would not resolve addrs has wheel group
reboot requires systemctl isolate reboot;systemctl restart network wicked wickedd or no network available when system comes back
df -m / Filesystem 1M-blocks Used Available Use% Mounted on LiveOS_rootfs 6758 4737 1659 75% /
with 15.0 was only ~60% iirc both with --no-recommends and no *-lang files
quite usable as remote monitor/workstation. no file storage.
-- (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
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 24/05/2019 16.45, Andrei Verovski wrote:
Hi,
You can try to use BFQ scheduler to slightly speed things up, as described in my blog here:
http://www.vacuum-tube.eu/wp/?p=612
+ noatime option for ext4 partitions.
Consider "lazytime". -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 05/24/2019 09:03 AM, Patrick Shanahan wrote:
has wheel group
I still can't explain why my fresh NET install (minimal X) did not include wheel group. Per did NET install similar (though he had http and others I didn't), but got a wheel group. Apparently we have found the reason on the factory list:
What package installs wheel group? :-?
scarabeus@bugaboo: ~ $ LC_ALL=C zypper in 'group(wheel)' Loading repository data... Reading installed packages... 'group(wheel)' not found in package names. Trying capabilities. 'system-group-wheel' providing 'group(wheel)' is already installed. Resolving package dependencies... Nothing to do. So you need system-group-wheel. Tom I don't know if this is new, but of the many, many, many installs I have done since SuSE 7.0 Pro (Air), I've never had to look for a separate package to install for wheel. Plus it would seem that we have broken dependencies, since both sudo and pam look to the wheel group. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin wrote:
On 05/24/2019 09:03 AM, Patrick Shanahan wrote:
has wheel group
I still can't explain why my fresh NET install (minimal X) did not include wheel group. Per did NET install similar (though he had http and others I didn't), but got a wheel group.
Apparently we have found the reason on the factory list: [snip] So you need system-group-wheel.
Tom
I don't know if this is new, but of the many, many, many installs I have done since SuSE 7.0 Pro (Air), I've never had to look for a separate package to install for wheel.
Thorsten mentioned it briefly on -factory, it weas changed about two years ago.
Plus it would seem that we have broken dependencies, since both sudo and pam look to the wheel group.
It is essentially your install "with no-recommends" that causes the issue for you - but if pam and sudo actually _need_ group wheel, they ought to have "requires group(wheel)". -- Per Jessen, Zürich (14.5°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 25/05/2019 09.05, Per Jessen wrote:
David C. Rankin wrote:
On 05/24/2019 09:03 AM, Patrick Shanahan wrote:
has wheel group
I still can't explain why my fresh NET install (minimal X) did not include wheel group. Per did NET install similar (though he had http and others I didn't), but got a wheel group.
Apparently we have found the reason on the factory list: [snip] So you need system-group-wheel.
Tom
I don't know if this is new, but of the many, many, many installs I have done since SuSE 7.0 Pro (Air), I've never had to look for a separate package to install for wheel.
Thorsten mentioned it briefly on -factory, it weas changed about two years ago.
Plus it would seem that we have broken dependencies, since both sudo and pam look to the wheel group.
It is essentially your install "with no-recommends" that causes the issue for you - but if pam and sudo actually _need_ group wheel, they ought to have "requires group(wheel)".
Yes, this seems a case where "no recommends" bites you and causes problems. I have *never* used that setting, because I thought it could cause obscure problems, and it seems I'm right. If I really do not want something it wants to install, I taboo it. Otherwise, disks are big. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 25/05/2019 09.05, Per Jessen wrote:
David C. Rankin wrote:
On 05/24/2019 09:03 AM, Patrick Shanahan wrote:
has wheel group
I still can't explain why my fresh NET install (minimal X) did not include wheel group. Per did NET install similar (though he had http and others I didn't), but got a wheel group.
Apparently we have found the reason on the factory list: [snip] So you need system-group-wheel.
Tom
I don't know if this is new, but of the many, many, many installs I have done since SuSE 7.0 Pro (Air), I've never had to look for a separate package to install for wheel.
Thorsten mentioned it briefly on -factory, it weas changed about two years ago.
Plus it would seem that we have broken dependencies, since both sudo and pam look to the wheel group.
It is essentially your install "with no-recommends" that causes the issue for you - but if pam and sudo actually _need_ group wheel, they ought to have "requires group(wheel)".
Yes, this seems a case where "no recommends" bites you and causes problems. I have *never* used that setting, because I thought it could cause obscure problems, and it seems I'm right.
Yeah, during installation I have never used it either. I don't even know where it is :-) I do have a lengthy list of stuff I deselect though. I wish I could just load it, or better yet, specify a list to linuxrc. When I update production systems, I virtually always use --no-recommends, sometimes after quickly checking what might have been installed (with it). -- Per Jessen, Zürich (16.6°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
On 25/05/2019 12.22, Per Jessen wrote:
Carlos E. R. wrote:
Yes, this seems a case where "no recommends" bites you and causes problems. I have *never* used that setting, because I thought it could cause obscure problems, and it seems I'm right.
Yeah, during installation I have never used it either. I don't even know where it is :-) I do have a lengthy list of stuff I deselect though. I wish I could just load it, or better yet, specify a list to linuxrc.
True. I have a paper with things to remove and things to add. Automation would be nice.
When I update production systems, I virtually always use --no-recommends, sometimes after quickly checking what might have been installed (with it).
I don't risk it. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Per Jessen <per@computer.org> [05-25-19 06:23]:
Carlos E. R. wrote:
On 25/05/2019 09.05, Per Jessen wrote:
David C. Rankin wrote:
On 05/24/2019 09:03 AM, Patrick Shanahan wrote:
has wheel group
I still can't explain why my fresh NET install (minimal X) did not include wheel group. Per did NET install similar (though he had http and others I didn't), but got a wheel group.
Apparently we have found the reason on the factory list: [snip] So you need system-group-wheel.
Tom
I don't know if this is new, but of the many, many, many installs I have done since SuSE 7.0 Pro (Air), I've never had to look for a separate package to install for wheel.
Thorsten mentioned it briefly on -factory, it weas changed about two years ago.
Plus it would seem that we have broken dependencies, since both sudo and pam look to the wheel group.
It is essentially your install "with no-recommends" that causes the issue for you - but if pam and sudo actually _need_ group wheel, they ought to have "requires group(wheel)".
Yes, this seems a case where "no recommends" bites you and causes problems. I have *never* used that setting, because I thought it could cause obscure problems, and it seems I'm right.
Yeah, during installation I have never used it either. I don't even know where it is :-) I do have a lengthy list of stuff I deselect though. I wish I could just load it, or better yet, specify a list to linuxrc.
When I update production systems, I virtually always use --no-recommends, sometimes after quickly checking what might have been installed (with it).
I do also, except on *original* install. but after install I remove *many* packages, then add the odd packages I particularly want/need. -- (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 05/25/2019 02:05 AM, Per Jessen wrote:
It is essentially your install "with no-recommends" that causes the issue for you - but if pam and sudo actually _need_ group wheel, they ought to have "requires group(wheel)".
They do, just su to root and type 'visudo', scroll to bottom: ## Uncomment to allow members of group wheel to execute any command # %wheel ALL=(ALL) ALL ## Same thing without a password %wheel ALL=(ALL) NOPASSWD: ALL Doesn't make a whole lot of sense to have 'sudo' install without 'wheel' when upstream on 'sudo' expects it to be present for its default config. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin wrote:
On 05/25/2019 02:05 AM, Per Jessen wrote:
It is essentially your install "with no-recommends" that causes the issue for you - but if pam and sudo actually _need_ group wheel, they ought to have "requires group(wheel)".
They do, just su to root and type 'visudo', scroll to bottom:
## Uncomment to allow members of group wheel to execute any command # %wheel ALL=(ALL) ALL
## Same thing without a password %wheel ALL=(ALL) NOPASSWD: ALL
In my default config, it is all commented out.
Doesn't make a whole lot of sense to have 'sudo' install without 'wheel' when upstream on 'sudo' expects it to be present for its default config.
Maybe 'sudo' ought to have a "requires group(wheel)" ? I don't use sudo very often. -- Per Jessen, Zürich (15.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
26.05.2019 11:50, Per Jessen пишет:
David C. Rankin wrote:
On 05/25/2019 02:05 AM, Per Jessen wrote:
It is essentially your install "with no-recommends" that causes the issue for you - but if pam and sudo actually _need_ group wheel, they ought to have "requires group(wheel)".
They do, just su to root and type 'visudo', scroll to bottom:
## Uncomment to allow members of group wheel to execute any command # %wheel ALL=(ALL) ALL
## Same thing without a password %wheel ALL=(ALL) NOPASSWD: ALL
In my default config, it is all commented out.
And in other distributions none of these entries exists at all by default.
Doesn't make a whole lot of sense to have 'sudo' install without 'wheel' when upstream on 'sudo' expects it to be present for its default config.
a) did you bother to actually look at *upstream* at all? Example sudoers included upstream does not mention any wheel group at all. b) Example sudoers upstream also includes such entries as # fred can run commands as oracle or sybase without a password fred ALL = (DB) NOPASSWD: ALL # on the alphas, john may su to anyone but root and flags are not allowed john ALPHA = /usr/bin/su [!-]*, !/usr/bin/su *root* # jen can run anything on all machines except the ones # in the "SERVERS" Host_Alias jen ALL, !SERVERS = ALL Does it mean that every distribution must now create users with these names and these privileges?
Maybe 'sudo' ought to have a "requires group(wheel)" ? I don't use sudo very often.
It was already explained on factory list that sudo does not *need* wheel. The above is just example; it does not mean group name *must* be wheel. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/05/2019 11.13, Andrei Borzenkov wrote:
26.05.2019 11:50, Per Jessen пишет:
David C. Rankin wrote:
On 05/25/2019 02:05 AM, Per Jessen wrote:
It is essentially your install "with no-recommends" that causes the issue for you - but if pam and sudo actually _need_ group wheel, they ought to have "requires group(wheel)".
They do, just su to root and type 'visudo', scroll to bottom:
## Uncomment to allow members of group wheel to execute any command # %wheel ALL=(ALL) ALL
## Same thing without a password %wheel ALL=(ALL) NOPASSWD: ALL
...
a) did you bother to actually look at *upstream* at all? Example sudoers included upstream does not mention any wheel group at all.
Well, then it is an openSUSE addition. In that case, perhaps the config file should mention that the package has to be added, that commenting out the line is not enough. Either that, or make the package a requirement. ...
Maybe 'sudo' ought to have a "requires group(wheel)" ? I don't use sudo very often.
It was already explained on factory list that sudo does not *need* wheel. The above is just example; it does not mean group name *must* be wheel.
-- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [05-26-19 06:49]:
On 26/05/2019 11.13, Andrei Borzenkov wrote:
26.05.2019 11:50, Per Jessen пишет:
David C. Rankin wrote:
On 05/25/2019 02:05 AM, Per Jessen wrote:
It is essentially your install "with no-recommends" that causes the issue for you - but if pam and sudo actually _need_ group wheel, they ought to have "requires group(wheel)".
They do, just su to root and type 'visudo', scroll to bottom:
## Uncomment to allow members of group wheel to execute any command # %wheel ALL=(ALL) ALL
## Same thing without a password %wheel ALL=(ALL) NOPASSWD: ALL
...
a) did you bother to actually look at *upstream* at all? Example sudoers included upstream does not mention any wheel group at all.
Well, then it is an openSUSE addition. In that case, perhaps the config file should mention that the package has to be added, that commenting out the line is not enough. Either that, or make the package a requirement.
or maybe just remove the "wheel" comments and adjust the suggestions as Andrei has described. appears now that group "wheel" is just and addition point of confusion. why have it if there are means to accomplish the same results w/o it?
...
Maybe 'sudo' ought to have a "requires group(wheel)" ? I don't use sudo very often.
It was already explained on factory list that sudo does not *need* wheel. The above is just example; it does not mean group name *must* be wheel.
-- Cheers / Saludos,
Carlos E. R. (from 15.0 x86_64 at Telcontar)
-- (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 05/26/2019 06:18 AM, Patrick Shanahan wrote:
appears now that group "wheel" is just and addition point of confusion. why have it if there are means to accomplish the same results w/o it?
Why have to other means when the use of 'wheel' has been the established way to accomplish configuring both sudo and pam since the beginning of both. I agree there is confusion, but it is largely self-inflicted. Seems the simplest way is just to have wheel as a depends of sudo and pam to avoid this problem altogether without having to start patching config files to unnecessarily remove what could be handled with a simple dependency. KISS philosophy. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/05/2019 02.20, David C. Rankin wrote:
On 05/26/2019 06:18 AM, Patrick Shanahan wrote:
appears now that group "wheel" is just and addition point of confusion. why have it if there are means to accomplish the same results w/o it?
Why have to other means when the use of 'wheel' has been the established way to accomplish configuring both sudo and pam since the beginning of both. I agree there is confusion, but it is largely self-inflicted. Seems the simplest way is just to have wheel as a depends of sudo and pam to avoid this problem altogether without having to start patching config files to unnecessarily remove what could be handled with a simple dependency. KISS philosophy.
I'm interested in knowing how to use wheel. When I started using Linux some document or man page said that it was some abusive or "nazi" thing and Linux is not like that, but they never explained what, nor what it was for or how to use it. I assume that they referred to some university Unix account where a small group of users had the power to use the wheel and others didn't, and there were abuses. So I never found out. Do you have some link that explains it? Or do you feel up to writing something? :-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 27/05/2019 02.20, David C. Rankin wrote:
On 05/26/2019 06:18 AM, Patrick Shanahan wrote:
appears now that group "wheel" is just and addition point of confusion. why have it if there are means to accomplish the same results w/o it?
Why have to other means when the use of 'wheel' has been the established way to accomplish configuring both sudo and pam since the beginning of both. I agree there is confusion, but it is largely self-inflicted. Seems the simplest way is just to have wheel as a depends of sudo and pam to avoid this problem altogether without having to start patching config files to unnecessarily remove what could be handled with a simple dependency. KISS philosophy.
I'm interested in knowing how to use wheel.
Maybe start here: https://en.opensuse.org/SDB:Administer_with_sudo -- Per Jessen, Zürich (18.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/05/2019 11.40, Per Jessen wrote:
Carlos E. R. wrote:
On 27/05/2019 02.20, David C. Rankin wrote:
On 05/26/2019 06:18 AM, Patrick Shanahan wrote:
appears now that group "wheel" is just and addition point of confusion. why have it if there are means to accomplish the same results w/o it?
Why have to other means when the use of 'wheel' has been the established way to accomplish configuring both sudo and pam since the beginning of both. I agree there is confusion, but it is largely self-inflicted. Seems the simplest way is just to have wheel as a depends of sudo and pam to avoid this problem altogether without having to start patching config files to unnecessarily remove what could be handled with a simple dependency. KISS philosophy.
I'm interested in knowing how to use wheel.
Maybe start here: https://en.opensuse.org/SDB:Administer_with_sudo
Ah! Thanks. That means that only people in the wheel group can sudo to root (using their own pw or root's depending on 'Defaults targetpw'). Nothing strange here, after being told :-) Also I notice now that some may have: #Defaults targetpw # ask for the password of the target user i.e. root #ALL ALL=(ALL) ALL # WARNING! Only use this together with 'Defaults targetpw'! while others may have instead: #Defaults targetpw # ask for the password of the target user i.e. root #%users ALL=(ALL) ALL # WARNING! Only use this together with 'Defaults targetpw'! This poses a new question: What is the role in this of those pam configs that David mentioned?:
And for /etc/pam.d/su in order for members of wheel to be able to su without a password you need:
auth sufficient pam_wheel.so trust use_uid auth required pam_wheel.so use_uid
Or is there just what that paragraph says? Activate those two lines, and from then on, the "su -" doesn't ask for a password if the user belongs to "wheel" group? Sorry, to me "wheel" has been surrounded in a mystery halo. It can't be that simple! -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 05/26/2019 04:13 AM, Andrei Borzenkov wrote:
a) did you bother to actually look at *upstream* at all? Example sudoers included upstream does not mention any wheel group at all.
b) Example sudoers upstream also includes such entries as
Yes I did, why would openSuSE be patching the default config from upstream to include 'wheel' anyway it the wheel group wasn't a dependency? Don't change the subject. Why is wheel included in the default sudoers file if wheel isn't a dependency to sudo here? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Andrei Borzenkov -
Andrei Verovski -
Carlos E. R. -
David C. Rankin -
Patrick Shanahan -
Per Jessen