All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aurélien Aptel" <aaptel@suse.com>
To: Calvin Chiang <calvin.chiang@gmail.com>
Cc: linux-cifs@vger.kernel.org
Subject: Re: Unable to find pw entry for uid
Date: Thu, 06 May 2021 23:19:35 +0200	[thread overview]
Message-ID: <871rajv9ug.fsf@suse.com> (raw)
In-Reply-To: <CAEVyU89=egaEAdvCD=FVkLwP4akzY3y8q=0hFW-hSryq0sxnxg@mail.gmail.com>

Calvin Chiang <calvin.chiang@gmail.com> writes:
> I guess after i make the change in the cifs.upcall.c file i need to
> autoreconf /config /make /make install ?
> is it correct that this will overwrite all the files from the
> cifs-utils package on my machine?

Yes you need to make sure you have all the dependencies required to
build cifs.upcall (your package manager of your distro might provide a
way to get 'build dependencies' of a package). If it's missing some the
configure script might disable the build of cifs.upcall so make sure it
is built. You can run

as regular user:

   autoreconf -i
   ./configure
   make

Check where is installed your current cifs.upcall ($ whereis
cifs.upcall) usually it's in /usr/sbin/. I would recommend keeping a
copy of the old one.

as root (or sudo):

make backup once:

    cp /usr/sbin/cifs.upcall{,.backup}

then to build and use new one (rm is to make sure it is rebuilt):

     rm -f cifs.upcall && make && sudo cp cifs.upcall /usr/sbin/

Good luck

Cheers,
-- 
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97  8C99 03C8 A49B 521B D5D3
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)


  reply	other threads:[~2021-05-06 21:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04  7:49 Unable to find pw entry for uid Calvin Chiang
2021-05-06 12:42 ` Aurélien Aptel
2021-05-06 13:40   ` Calvin Chiang
2021-05-06 21:19     ` Aurélien Aptel [this message]
2021-05-11 10:39       ` Calvin Chiang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871rajv9ug.fsf@suse.com \
    --to=aaptel@suse.com \
    --cc=calvin.chiang@gmail.com \
    --cc=linux-cifs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.