On Wed, Oct 26, 2022 at 05:04:35AM +0200, Ramon Fischer wrote
> Hello Walter,
>
> I do not think, that this is a bug, since it is the default file, which
> should not be edited by the user.
Firstly "grep -i uncomment /etc/sudoers" results in...
## Uncomment to enable special input methods.
User "waltdnes" is a member of "wheel". If the "wheel" line is
uncommented in /etc/sudoers, sudo works for me.
So you could create the file "/etc/sudoers.d/000" with the following
content:
%wheel ALL=(ALL:ALL) ALL
%wheel ALL=(ALL:ALL) NOPASSWD: ALL
and your user is able to synchronise
On Wednesday, 26 October 2022 03:06:19 BST Walter Dnes wrote:
> On Tue, Oct 25, 2022 at 11:07:14PM +0100, Michael wrote
>
> > sync-type = rsync
> > #sync-uri = rsync://rsync.gentoo.org/gentoo-portage
> > sync-uri = rsync://192.168.1.252/gentoo-portage
>
> Thanks Michael (and Adam). I did
On Wed, Oct 26, 2022 at 3:42 AM Ramon Fischer wrote:
>
> I do not know, what the developers were thinking to encourage the user
> to edit a default file, which gets potentially overwritten after each
> package update...
>
> "etc-update" helps to have an eye on, but muscle memory and fast fingers
Hello list,
I'm installing Gentoo on a new Juno laptop, and I've reached the point of
booting into the new system. I have a separate /usr partition and I'm using
dracut to create an initramfs.
On booting the new system I get an error I haven't heard of before: dracut
complaining "sysroot has
Interesting! Thank you for your research!
After working 20 hours straight - uptime said so - I did not feel like
it to do deeper research myself. :)
-Ramon
On 26/10/2022 13:31, Rich Freeman wrote:
On Wed, Oct 26, 2022 at 3:42 AM Ramon Fischer wrote:
I do not know, what the developers were
Peter Humphrey wrote:
> Hello list,
>
> I'm installing Gentoo on a new Juno laptop, and I've reached the point of
> booting into the new system. I have a separate /usr partition and I'm using
> dracut to create an initramfs.
>
> On booting the new system I get an error I haven't heard of before:
On Tue, Oct 25, 2022 at 11:07:14PM +0100, Michael wrote
>
> No, you shouldn't have to do any such thing. Just make sure you
> have set up in your '/etc/portage/repos.conf/gentoo.conf' the correct
> rsync mirror and commented out the server on the Internet; e.g.:
OK, I tried it on my other
On Wednesday, 26 October 2022 16:47:46 BST Dale wrote:
> Peter Humphrey wrote:
> > Hello list,
> >
> > I'm installing Gentoo on a new Juno laptop, and I've reached the point of
> > booting into the new system. I have a separate /usr partition and I'm
> > using
> > dracut to create an initramfs.
>
On Wednesday, 26 October 2022 16:48:29 BST Walter Dnes wrote:
> On Tue, Oct 25, 2022 at 11:07:14PM +0100, Michael wrote
>
> > No, you shouldn't have to do any such thing. Just make sure you
> > have set up in your '/etc/portage/repos.conf/gentoo.conf' the correct
>
> > rsync mirror and
On Wed, 26 Oct 2022 10:21:06 -0600, Grant Taylor wrote:
> > dispatch-conf even gives you the opportunity to edit it before
> > applying.
>
> Yep.
>
> I almost always reject the changes suggested on config files that I've
> modified and accept them on files that I've not modified.
>
> I
Indeed, an intersting question, which you actually already answered
yourself. I just tested it myself:
$ visudo -f /etc/sudoers.d/00-wheel
%wheel ALL=(ALL) ALL
$ sudo --list
User ramon may run the following commands on :
(ALL) ALL
$ sudo -f
On Wed, 26 Oct 2022 20:04:10 +0200, Ramon Fischer wrote:
> Also a very interesting question!
>
> I just tested this with "visudo" and it does not intercept this.
>
> If "su" is disabled, you are locked out and you are forced to enter
> your system via a live USB stick and a "chroot" in order to
On 10/26/22 12:22 PM, Neil Bothwick wrote:
You need to be root to write to /etc/sudoers.d. If someone has that
access, you are already doomed!
And what happens if someone uses the existing root-via-sudo access to
break sudo?
You loose root-via-sudo access.
Someone could become root, via
On Wed, 26 Oct 2022 20:38:35 +0200, Ramon Fischer wrote:
> I thought in a too complicated way.
>
> Why not just remove the entry from "/etc/sudoers.d/zzz", while
> being in a "chroot"?
Still too complicated. Just mount the root partition from a live USB and
delete the file. no need for a
Rich Freeman wrote:
> If you use an x11-based merge tool then it will also refuse to attempt
> an automatic
> merge if X11 isn't available. (Obviously you can't actually run the
> manual merge if the tool uses X11 and that isn't available.)
>
>
I'd like to try a GUI based tool. Is that what you
On 2022-10-26, Dale wrote:
> Rich Freeman wrote:
>> If you use an x11-based merge tool then it will also refuse to attempt
>> an automatic
>> merge if X11 isn't available. (Obviously you can't actually run the
>> manual merge if the tool uses X11 and that isn't available.)
>>
>>
>
> I'd like to
On 10/26/22 12:04 PM, Ramon Fischer wrote:
Also a very interesting question!
}:-)
I just tested this with "visudo" and it does not intercept this.
Nor should it.
It's perfect legitimate sudoers syntax.
The location; /etc/sudoers.d/zz vs the end of /etc/sudoers
(proper), doesn't
On 10/26/22 2:08 PM, Neil Bothwick wrote:
So they have root access, nothing has changed. How they get root
access is irrelevant, just that they have it.
No, how they get root access is not irrelevant.
If your only access to root is via sudo and you break sudo you no longer
have root access.
On Wed, 26 Oct 2022 14:17:30 -0600, Grant Taylor wrote:
> On 10/26/22 2:08 PM, Neil Bothwick wrote:
> > So they have root access, nothing has changed. How they get root
> > access is irrelevant, just that they have it.
>
> No, how they get root access is not irrelevant.
>
> If your only
On 10/26/22 3:27 PM, Ramon Fischer wrote:
Why was I thinking of a chroot?
Maybe because of reading "grup/grub" a few e-mails before and thinking
of "grub-mkconfig"...
Or maybe because entering a chroot is such a prominent thing to do when
booting off of Gentoo media to do an installation
On 10/26/22 12:35 PM, Jack wrote:
Could you not interrupt grup and append "single" or "init=/bin/bash" to
the kernel command line?
Maybe.
It will depend on how complex your configuration is.
I don't remember if Gentoo requires root's password when entering single
user mode or not. (I've
On Wed, 26 Oct 2022 13:28:49 -0600, Grant Taylor wrote:
> > You need to be root to write to /etc/sudoers.d. If someone has that
> > access, you are already doomed!
>
> And what happens if someone uses the existing root-via-sudo access to
> break sudo?
So they have root access, nothing has
I have created an issue at their Git repository. Maybe there will be
solution for this:
https://github.com/sudo-project/sudo/issues/190
-Ramon
On 26/10/2022 21:28, Grant Taylor wrote:
On 10/26/22 12:22 PM, Neil Bothwick wrote:
You need to be root to write to /etc/sudoers.d. If someone
Ah, of course!
Why was I thinking of a chroot?
Maybe because of reading "grup/grub" a few e-mails before and thinking
of "grub-mkconfig"...
-Ramon
On 26/10/2022 22:06, Neil Bothwick wrote:
On Wed, 26 Oct 2022 20:38:35 +0200, Ramon Fischer wrote:
I thought in a too complicated way.
Why
On 10/26/22 3:13 PM, Neil Bothwick wrote:
They and you are different people. You are looking at it from the
perspective of a user accidentally locking themself out of the system,
so su is the best way to be able to fix it. I agree with you there. I
was looking at it from the perspective of a
On 2022-10-26, Matt Connell wrote:
> On Tue, 2022-10-25 at 21:31 +, Grant Edwards wrote:
>> Google led me to several pages where the problem was not having gvfs
>> installed. I do have gvfs installed, but I suspect it's broken. I get
>> the impression that
>>
>> $ gio list sftp:///
>>
On Wed, 2022-10-26 at 16:22 +, Grant Edwards wrote:
> Apparently, that error is cause by lack of a DBUS session. I just
> happened to stumble across a posting somewhere by somebody who had the
> same problem. How they figured out that was the problem remains a
> mystery.
It is likely that
On 2022.10.26 14:04, Ramon Fischer wrote:
Also a very interesting question!
I just tested this with "visudo" and it does not intercept this.
If "su" is disabled, you are locked out and you are forced to enter
your system via a live USB stick and a "chroot" in order to edit
"/etc/shadow" to
On 10/25/22 9:44 PM, Matt Connell wrote:
Calm down.
I am calm.
The suggestion to not edit the (/etc/sudoeres) configuration file is one
of those types of things that if nobody objects to then eventually not
doing so will become defacto policy. So I objected, calmly, but with
emphasis.
On Wed, Oct 26, 2022 at 1:15 PM Neil Bothwick wrote:
>
> On Wed, 26 Oct 2022 10:21:06 -0600, Grant Taylor wrote:
>
> > > dispatch-conf even gives you the opportunity to edit it before
> > > applying.
> >
> > Yep.
> >
> > I almost always reject the changes suggested on config files that I've
> >
On 2022-10-26, Grant Edwards wrote:
> The problem wasn't that the daemon was missing. There is a DBUS
> daemon, and other things that use DBUS (e.g. notifications) work fine.
>
> What was apparently missing was a "session"
>
> $ set | grep dbus
(same result with "grep DBUS")
> $
Also a very interesting question!
I just tested this with "visudo" and it does not intercept this.
If "su" is disabled, you are locked out and you are forced to enter your
system via a live USB stick and a "chroot" in order to edit
"/etc/shadow" to set a root password via "mkpasswd" and
On Wed, Oct 26, 2022 at 12:24 PM Grant Edwards
wrote:
>
> On 2022-10-26, Corbin wrote:
> > Help!
> >
> > The last update I did built/installed bin-uitls. It is now producing
> > seg-faults. I forgot to make a quickpkg of the old bin-utils before
> > upgrading.
>
> The first thing I would do is
On Wed, 2022-10-26 at 14:37 -0400, Rich Freeman wrote:
> Another possible issue is bad -march settings. That usually is an
> issue if you change your CPU and boot off of an existing hard drive.
> If you're going to upgrade your CPU you should rebuild all of @system
> (at least) with -march set to
Help!
The last update I did built/installed bin-uitls. It is now producing
seg-faults. I forgot to make a quickpkg of the old bin-utils before
upgrading.
Added problem, dead optical drive. No cdrom/dvd or bluray.
How can I fix this without having to reinstall from scratch?
On 2022-10-26, Corbin wrote:
> Help!
>
> The last update I did built/installed bin-uitls. It is now producing
> seg-faults. I forgot to make a quickpkg of the old bin-utils before
> upgrading.
The first thing I would do is run a RAM test overnight. IME,
segfaulting binutils or gcc has usually
On 2022-10-26, Matt Connell wrote:
> On Wed, 2022-10-26 at 16:22 +, Grant Edwards wrote:
>> Apparently, that error is cause by lack of a DBUS session. I just
>> happened to stumble across a posting somewhere by somebody who had the
>> same problem. How they figured out that was the problem
On 10/26/22 12:31 AM, Walter Dnes wrote:
My regular user has script "settime" in ${HOME}/bin
#!/bin/bash
date
/usr/bin/sudo /usr/bin/rdate -nsv ca.pool.ntp.org
/usr/bin/sudo /sbin/hwclock --systohc
date
/etc/sudoers.d/001 has, amongst other things, two lines...
waltdnes x8940 = (root)
On 2022-10-26, Grant Taylor wrote:
> To the sudo developers, the /etc/sudoers file is *SUPPOSED* *TO* /be/
> /edited/.
And editing that file is how I configure sudo. And when an emerge
update changes /etc/sudoers, the edited file is left as-is and there
is a message that you need to run
Of course, that would be sufficient.
I thought in a too complicated way.
Why not just remove the entry from "/etc/sudoers.d/zzz", while being
in a "chroot"?
-Ramon
On 26/10/2022 20:35, Jack wrote:
Could you not interrupt grup and append "single" or "init=/bin/bash"
to the kernel
On 10/26/22 1:42 AM, Ramon Fischer wrote:
and your user is able to synchronise your clock again.
I'm not sure that will work as hoped. See my other reply about PTY and
testing the commands at the command line for more explanation of what I
suspect is happening.
I do not know, what the
On Wed, 26 Oct 2022 15:22:42 +0100, Peter Humphrey wrote:
> On booting the new system I get an error I haven't heard of before:
> dracut complaining "sysroot has no proper sysfs layout". I'm sure I've
> done something stupid, but where do I start debugging this? Google
> hasn't helped.
Is
Of course, you are free to do so, but then blindly overwriting default
configuration files is a Layer 8 problem.
-Ramon
On 26/10/2022 19:12, Grant Edwards wrote:
On 2022-10-26, Grant Taylor wrote:
To the sudo developers, the /etc/sudoers file is *SUPPOSED* *TO* /be/
/edited/.
And editing
On Wed, Oct 26, 2022 at 5:26 PM Grant Edwards wrote:
>
> On 2022-10-26, Dale wrote:
> > Rich Freeman wrote:
> >> If you use an x11-based merge tool then it will also refuse to attempt
> >> an automatic
> >> merge if X11 isn't available. (Obviously you can't actually run the
> >> manual merge if
On Wed, Oct 26, 2022 at 05:42:24PM +0100, Michael wrote
> On Wednesday, 26 October 2022 16:48:29 BST Walter Dnes wrote:
> > * In https://wiki.gentoo.org/wiki/Local_Mirror the file to change is
> > given as /etc/portage/repos.conf/gentoo-mirror.conf There is no such
> > file on my system. Should
Do you also use "vim" from time to time?
Because it is also able to compare two (or more?) files, similiar to
"sdiff":
$ vi -d file1 file2
or:
$ vi file1
:diffthis
:vsplit
CTRL+w + right arrow key
:e file2
:diffthis
-Ramon
On 27/10/2022 00:44, Dale wrote:
I'd like
Ramon Fischer wrote:
> Do you also use "vim" from time to time?
>
> Because it is also able to compare two (or more?) files, similiar to
> "sdiff":
>
> $ vi -d file1 file2
>
> or:
>
> $ vi file1
> :diffthis
> :vsplit
> CTRL+w + right arrow key
> :e file2
> :diffthis
>
> -Ramon
Grant Edwards wrote:
> On 2022-10-26, Dale wrote:
>> Rich Freeman wrote:
>>> If you use an x11-based merge tool then it will also refuse to attempt
>>> an automatic
>>> merge if X11 isn't available. (Obviously you can't actually run the
>>> manual merge if the tool uses X11 and that isn't
On 10/26/22 3:48 PM, Ramon Fischer wrote:
I have created an issue at their Git repository. Maybe there will be
solution for this:
https://github.com/sudo-project/sudo/issues/190
I ... don't know where to begin.
There are so many ways that you can hurt yourself with syntactically
valid
Sure, you cannot cover everything, but mitigating at least a little bit
would be OK or not? :)
-Ramon
On 27/10/2022 01:06, Grant Taylor wrote:
On 10/26/22 3:48 PM, Ramon Fischer wrote:
I have created an issue at their Git repository. Maybe there will be
solution for this:
On 10/26/22 7:27 PM, Ramon Fischer wrote:
Sure, you cannot cover everything, but mitigating at least a little bit
would be OK or not? :)
I don't know. :-/
It's the proverbial problem of spam / virus filtering and a spam / virus
gets through the filters and someone saying "But it's your
52 matches
Mail list logo
