Re: pw_class in _pw_passwd is null if __hashpw() is not called in prior
On Thu, 28 Sep 2000 11:55:55 -0500, "Jacques A. Vidrine" [EMAIL PROTECTED] said: It would also be helpful for us to (semi-)automatically update old binaries installed by ports. (I have been trying this for a couple of days) Jacques Personally I don't want sysinstall or make world to touch my ports. Jacques But a tool to do this would be great. Completely automatic update of installed ports is acutally difficult because we cannot get to know the language or required toolkit from the name of a binary. (eg emulator/wine and japanese/wine, timidity++-xaw and timidity++-tcltk) We can still detect and enumerate the ports that possibly installed old binaries, and decide which of the ports listed up to update. http://people.FreeBSD.org/~tanimura/tools/oldports is a shell script to scan the binaries installed by ports and to list up the name of the ports that installed binaries using libc.so.3 or earlier. -- Seigo Tanimura [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pw_class in _pw_passwd is null if __hashpw() is not called in prior
Seigo Tanimura writes: On Thu, 28 Sep 2000 11:55:55 -0500, "Jacques A. Vidrine" [EMAIL PROTECTED] said: It would also be helpful for us to (semi-)automatically update old binaries installed by ports. (I have been trying this for a couple of days) Jacques Personally I don't want sysinstall or make world to touch my ports. Jacques But a tool to do this would be great. Completely automatic update of installed ports is acutally difficult because we cannot get to know the language or required toolkit from the name of a binary. (eg emulator/wine and japanese/wine, timidity++-xaw and timidity++-tcltk) We can still detect and enumerate the ports that possibly installed old binaries, and decide which of the ports listed up to update. Ah - there's *two* meanings for "old" here. If you were talking about binaries installed by out-of-date ports, that's easy: weekly_status_pkg in the periodic subsystem will do that for you. However, I believe you were talking about binaries that may have been built from a current port against an out-of-date system. Frankly, I'm not really interested in *detecting* such things. A tool that would 1) save tarballs of *all* installed ports; 2) uninstall them all; then 3) rebuild and install them all, with a report about failures would make me happy. That way, I'd know that all the ports were built against the current system, which would make me feel much safer. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(Semi-)automatic update of installed ports (was: Re: pw_class in _pw_passwd is null if __hashpw() is not called in prior)
[cc'ed to -ports] On Sat, 30 Sep 2000 13:35:48 -0500 (CDT), Mike Meyer [EMAIL PROTECTED] said: Mike Seigo Tanimura writes: Completely automatic update of installed ports is acutally difficult because we cannot get to know the language or required toolkit from the name of a binary. (eg emulator/wine and japanese/wine, timidity++-xaw and timidity++-tcltk) We can still detect and enumerate the ports that possibly installed old binaries, and decide which of the ports listed up to update. Mike you. However, I believe you were talking about binaries that may have Mike been built from a current port against an out-of-date system. Mike Frankly, I'm not really interested in *detecting* such things. A tool Mike that would 1) save tarballs of *all* installed ports; 2) uninstall Mike them all; then 3) rebuild and install them all, with a report about Mike failures would make me happy. How do you rebuild a port automatically if you want to hack the configure parameter or make variables of the port? -- Seigo Tanimura [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: (Semi-)automatic update of installed ports (was: Re: pw_class in _pw_passwd is null if __hashpw() is not called in prior)
Seigo Tanimura writes: On Sat, 30 Sep 2000 13:35:48 -0500 (CDT), Mike Meyer [EMAIL PROTECTED] said: Mike Seigo Tanimura writes: Completely automatic update of installed ports is acutally difficult because we cannot get to know the language or required toolkit from the name of a binary. (eg emulator/wine and japanese/wine, timidity++-xaw and timidity++-tcltk) We can still detect and enumerate the ports that possibly installed old binaries, and decide which of the ports listed up to update. Mike Frankly, I'm not really interested in *detecting* such things. A tool Mike that would 1) save tarballs of *all* installed ports; 2) uninstall Mike them all; then 3) rebuild and install them all, with a report about Mike failures would make me happy. How do you rebuild a port automatically if you want to hack the configure parameter or make variables of the port? Since that information isn't currently stored, you have to do it by hand :-(. Of course, you also have to *guess* what port corresponds to an installed package, as the information about which ports collection a package came from is lost as well. It's not clear that the port names are globally uniq, either. If it were easy, I'd've done it myself :-). mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pw_class in _pw_passwd is null if __hashpw() is not called in prior
On Sun, 24 Sep 2000 10:08:12 -0500, "Jacques A. Vidrine" [EMAIL PROTECTED] said: n changing them now. Unless objections come up, I'll commit this change n or something similar with the next nsswitch commit. Here is another possible trouble. While libc.so.4 with nsswitch no longer requires the magic '+' entry, libc.so.3 and earlier still require '+'. What we need before 5.0-RELEASE meets the world is a tool to find binaries linked against libc.so.3 and earlier, and give a warning. It would also be helpful for us to (semi-)automatically update old binaries installed by ports. (I have been trying this for a couple of days) -- Seigo Tanimura [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pw_class in _pw_passwd is null if __hashpw() is not called in prior
On Thu, 28 Sep 2000 22:50:53 +0900, Seigo Tanimura [EMAIL PROTECTED] said: Here is another possible trouble. While libc.so.4 with nsswitch no longer requires the magic '+' entry, libc.so.3 and earlier still require '+'. IMHO, This Is A Bug. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pw_class in _pw_passwd is null if __hashpw() is not called in prior
In the last episode (Sep 28), Garrett Wollman said: On Thu, 28 Sep 2000 22:50:53 +0900, Seigo Tanimura [EMAIL PROTECTED] said: Here is another possible trouble. While libc.so.4 with nsswitch no longer requires the magic '+' entry, libc.so.3 and earlier still require '+'. IMHO, This Is A Bug. Depends on what Seigo meant. If he meant that libc.so.4 and no /etc/nsswitch.conf implicitly adds a "+" to the end of /etc/passwd, that's definitely a bug. If he meant that libc.so.4 and an nsswitch.conf of "passwd: files nis" doesn't require a "+", that's fine. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pw_class in _pw_passwd is null if __hashpw() is not called in prior
On Thu, Sep 28, 2000 at 10:50:53PM +0900, Seigo Tanimura wrote: Here is another possible trouble. While libc.so.4 with nsswitch no longer requires the magic '+' entry, libc.so.3 and earlier still require '+'. If one needs to support applications using libc.so.3, then one needs to use the nsswitch compat mode (which is the default). OTOH, I hope to have nsswitch in 4.2-RELEASE. (I do the develoment on 4-STABLE.) What we need before 5.0-RELEASE meets the world is a tool to find binaries linked against libc.so.3 and earlier, and give a warning. This would be useful in any case. It would also be helpful for us to (semi-)automatically update old binaries installed by ports. (I have been trying this for a couple of days) Personally I don't want sysinstall or make world to touch my ports. But a tool to do this would be great. -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pw_class in _pw_passwd is null if __hashpw() is not called in prior
On Thu, Sep 28, 2000 at 10:24:01AM -0500, Dan Nelson wrote: Depends on what Seigo meant. If he meant that libc.so.4 and no /etc/nsswitch.conf implicitly adds a "+" to the end of /etc/passwd, that's definitely a bug. If you don't have an /etc/nsswitch.conf, then it behaves just like libc.so.3, i.e. only the files are consulted, unless you have a '+' entry. If he meant that libc.so.4 and an nsswitch.conf of "passwd: files nis" doesn't require a "+", that's fine. And that is how it works if you do have an nsswitch.conf like that. -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pw_class in _pw_passwd is null if __hashpw() is not called in prior
On Fri, Sep 29, 2000 at 12:10:39AM +0700, Max Khon wrote: "passwd: compat" should require '+' if I understand it correctly You understand correctly :-) Further, this is the default when there is no /etc/nsswitch.conf. -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pw_class in _pw_passwd is null if __hashpw() is not called in prior
On Sun, Sep 24, 2000 at 11:43:01PM +0900, Seigo Tanimura wrote:
As we are supposed to fill in all of the members in struct passwd
(like Solaris), _pw_passwd should have its initial value other than
zero.
static struct passwd _pw_passwd =
{
"",
"",
(uid_t)0, /* XXX Is zero appropriate? */
(gid_t)0,
(time_t)0,
"",
"",
"",
"",
(time_t)0,
0,
};
I agree -- it bit me while working on some additional nsswitch
backends. Using a pointer to an empty string would be more safe. As
to the XXX comment, those fields have been 0 forever, no point in
changing them now. Unless objections come up, I'll commit this change
or something similar with the next nsswitch commit.
Thanks for the suggestion!
--
Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: pw_class in _pw_passwd is null if __hashpw() is not called in prior
Kris,
I guess once this is committed, the patch I sent you for ssh will no
longer be necessary.
To the cc list: My patch just told ssh to
xstrdup(pw_class ? pw_class : "")
On Sun, Sep 24, 2000 at 11:43:01PM +0900, Seigo Tanimura wrote:
As we are supposed to fill in all of the members in struct passwd
(like Solaris), _pw_passwd should have its initial value other than
zero.
static struct passwd _pw_passwd =
{
"",
"",
(uid_t)0, /* XXX Is zero appropriate? */
(gid_t)0,
(time_t)0,
"",
"",
"",
"",
(time_t)0,
0,
};
I agree -- it bit me while working on some additional nsswitch
backends. Using a pointer to an empty string would be more safe. As
to the XXX comment, those fields have been 0 forever, no point in
changing them now. Unless objections come up, I'll commit this change
or something similar with the next nsswitch commit.
Thanks for the suggestion!
--
Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED]
--
Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org
http://www.Awfulhak.org brian@[uk.]OpenBSD.org
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
