Hey everyone,
I'm trying to be a hurd developer by jumping straight in and trying to
tackle a bug. This may not be a hurd bug, but I only see it with the
hurd version of sudo. I am trying to figure out why I get this message
"visudo: /etc/sudoers busy, try again later" when I run visudo as root.
I
On Tue, 2014-03-11 at 10:29 +0100, Thomas Schwinge wrote:
> You don't happen to be a student willing to do this as a Google Summer of
> Code project? :-)
Yes I am a student hoping to get involved with hurd development through
Google Summer of Code. I saw on the application that I should have
subm
So as the title suggests hurd from git.sv.gnu.org/hurd/ does not compile
for me, but hurd-0.5 from ftp.gnu.org/gnu/ does. The message I am
getting is
~/hurd/exec/exec.c:1173: undefined reference to `task_set_name'
collect2: error: ld returned 1 exit status
make[1]: *** [exec] Error 1
make[1]: Le
On Wed, 2014-03-12 at 11:25 +0100, Samuel Thibault wrote:
> I's actually the Mach headers which need to be upgraded to the version
> which includes task_set_name, and glibc then recompiled against it.
So does this mean I need to compile mach, hurd, and glibc from their
respective development branc
On Tue, 2014-03-11 at 10:15 +0100, Samuel Thibault wrote:
> No, it's rather the locking function which spuriously fails. The
> debian/patches/use-flock-on-hurd.diff patch is supposed to make sudo use
> flock instead of lockf, but that doesn't seem to actually happen. Some
> autoconf patching is pro
The reason the patch was not being applied was
1. The patch was not listed in debian/patches/series so it was not
queued up.
2. The patch was for configure.in it no longer exists for sudo now there
is a configure.ac
So if I just copy paste the the changes to the patch to configure.ac
will that hav
to summerize my experiences with the visudo bug so far,
1. sudo will not build unless umask is something other than 000 even
though /etc/login.defs says the default should be 022. I set the umask
to 002 and 022 in a normal users's .profile and on both occasions sudo
builds.
2. use-flock-on-hurd.di
On Fri, 2014-03-14 at 09:29 +0100, Samuel Thibault wrote:
> Use patch -ur between an unmodified version of sudo and your modified
> version. Send that to debian-h...@lists.debian.org for review, and then
I sent the patch to debian-h...@lists.debian.org does that qualify me
now for google summer of
On Tue, 2014-03-11 at 10:15 +0100, Samuel Thibault wrote:
> Another way is to just fix lockf in glibc (for now it is just returning
> ENOSYS), it seems sudo simply locks the whole file, so it would be the
> simple case to implement.
If I did want to fix lockf in glibc where would I find the lockf
I figured out why sudo was not building, unless I explicitly state a
umask in my .profile that is NOT umask 000, which it seemed like it was.
sudo will fail some permission checks. If put either umask 002 or 022
in .profile sudo will build. So is there another bug with default file
permissions then
10 matches
Mail list logo
