Would you mind posting a patch? I'd like to see if I can get your modifications
to work in my FreeBSD chroot.
Thanks,
---Nathan
On Sun, Jan 20, 2002 at 12:27:23AM +, Matthew Garrett wrote:
> On Thu, Jan 17, 2002 at 04:27:33AM +, Matthew Garrett wrote:
> > Ok, it turns out that t
On Thu, Jan 17, 2002 at 04:27:33AM +, Matthew Garrett wrote:
> Ok, it turns out that this doesn't look too bad. In shadow-foo/lib we have
> a stack of code that performs the actual manipulation of the files, with
> all the utilities using that. There's code there for manipulation of
> dbm-style
On Fri, Jan 18, 2002 at 11:48:59AM -0800, Jeremy C. Reed wrote:
> On Fri, 18 Jan 2002, Jeroen Dekkers wrote:
>
> > On Thu, Jan 17, 2002 at 12:08:00AM +, Matthew Garrett wrote:
> > > I've now uploaded the web page to http://debian-bsd.sf.net and am
>
> > Why do you host it at a site which runs
On Fri, 18 Jan 2002, Jeroen Dekkers wrote:
> On Thu, Jan 17, 2002 at 12:08:00AM +, Matthew Garrett wrote:
> > I've now uploaded the web page to http://debian-bsd.sf.net and am
> Why do you host it at a site which runs non-free software and locks in
> users? For the people who don't know what'
On Fri, Jan 18, 2002 at 05:48:48PM +0100, Jeroen Dekkers wrote:
> On Thu, Jan 17, 2002 at 02:46:29AM +, Matthew Garrett wrote:
> > > That approach gets rid of a lot of hassles associated with upgrading the
> > > sources, and allows people to rebuild their kernel and core system. You
> > > just
On Thu, Jan 17, 2002 at 02:46:29AM +, Matthew Garrett wrote:
> > That approach gets rid of a lot of hassles associated with upgrading the
> > sources, and allows people to rebuild their kernel and core system. You just
> > pull the new sources from CVS, and use the scripts to build debs. A lot
On Thu, Jan 17, 2002 at 12:08:00AM +, Matthew Garrett wrote:
> I've now uploaded the web page to http://debian-bsd.sf.net and am
> redirecting people there from the old location.
Why do you host it at a site which runs non-free software and locks in
users? For the people who don't know what's
On Fri, Jan 18, 2002 at 10:23:24AM +1100, matthew green wrote:
>
>I'm not quite sure what you mean here. passwd, adduser, chfn and so on
>work in as much as they update /etc/passwd (they all use the libshadow
>functions for this even if you don't compile it as a shared library), but
I'm not quite sure what you mean here. passwd, adduser, chfn and so on
work in as much as they update /etc/passwd (they all use the libshadow
functions for this even if you don't compile it as a shared library), but
NetBSD getpwnam will only use the db format files. What I think we
On Thu, Jan 17, 2002 at 12:00:45AM -0500, [EMAIL PROTECTED] wrote:
> Hmm. I was thinking more in terms of a libshadow. I seem to recall that there
> used to be one, back with libc5, and I think that the shadow source package
> still can make one. (If I remember right, it was disabled in the build
On Thu, Jan 17, 2002 at 04:27:33AM +, Matthew Garrett wrote:
> On Wed, Jan 16, 2002 at 09:16:10PM -0500, [EMAIL PROTECTED] wrote:
> > * On the webpage, you mention problems with shadow:
> > I had the exact same problem with FreeBSD, and I see two choices. Either use
> > native passwd, adduser,
I would *much* rather have the non-dependant stuff, of which there is a
whole lot, built as separate packages. Wherever the source comes from, I
don't want to have to rebuild a lot of cruft that isn't actually crucially
out of date, just to get a reasonable kernel. If I rebuild my k
On Thu, Jan 17, 2002 at 03:38:04PM +1100, matthew green wrote:
>
>utilities and libraries NEED to be built together with the kernel. It's a
>feature in the BSD world. It'd be easer to keep them in sync if they're
> built
>
>
> hmm, i wouldn't call it a feature :-) certainly in NetBS
On Thu, Jan 17, 2002 at 03:38:04PM +1100, matthew green wrote:
>
>utilities and libraries NEED to be built together with the kernel. It's a
>feature in the BSD world. It'd be easer to keep them in sync if they're
> built
>
>
> hmm, i wouldn't call it a feature :-) certainly in NetBS
utilities and libraries NEED to be built together with the kernel. It's a
feature in the BSD world. It'd be easer to keep them in sync if they're built
hmm, i wouldn't call it a feature :-) certainly in NetBSD we've done a
lot of work to remove these sorts of issues... and the trend is
On Thu, Jan 17, 2002 at 02:46:29AM +, Matthew Garrett wrote:
> On Wed, Jan 16, 2002 at 09:16:10PM -0500, [EMAIL PROTECTED] wrote:
> > * About packaging from /usr/src:
> > I had been planning on writing something similar to kernel-package for
> > FreeBSD.
> > The basic idea was to do a make bui
On Wed, Jan 16, 2002 at 09:16:10PM -0500, [EMAIL PROTECTED] wrote:
> * On the webpage, you mention problems with shadow:
> I had the exact same problem with FreeBSD, and I see two choices. Either use
> native passwd, adduser, etc. or get the shadow package to build a library (I
> believe it can, bu
On a related note, FreeBSD's Makefiles use "make" sometimes where they should
use "${MAKE}", so I put the BSD make into /usr/bsd/bin. Then I mangle $PATH
before running make from debian/rules, so that the FreeBSD Makefiles always
get BSD make rather than GNU. Sounds like NetBSD has
On Wed, Jan 16, 2002 at 09:16:10PM -0500, [EMAIL PROTECTED] wrote:
> * About packaging from /usr/src:
> I had been planning on writing something similar to kernel-package for
> FreeBSD.
> The basic idea was to do a make buildworld against the regular FreeBSD source
> tree, and then make multiple p
On Thu, Jan 17, 2002 at 12:08:00AM +, Matthew Garrett wrote:
> I've now uploaded the web page to http://debian-bsd.sf.net and am
> redirecting people there from the old location. It's also reminded me that
> there's currently several libs in the chroot that are just copied in there
> rather tha
I've now uploaded the web page to http://debian-bsd.sf.net and am
redirecting people there from the old location. It's also reminded me that
there's currently several libs in the chroot that are just copied in there
rather than packaged - packaging them shouldn't be too difficult. What I'm
doing fo
21 matches
Mail list logo
