>
> I would recomend calling the port "44bsd-games" and using the NetBSD
> repository as the distfile. NetBSD has even fixed bugs in wargames(6).
Why wouldn't these be broken apart? Perhaps a meta-port?
--
Stephen J. Roznowski([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 9 Oct, David O'Brien wrote:
> On Wed, Oct 09, 2002 at 09:47:12AM -0400, Stephen J. Roznowski wrote:
>> On 9 Oct, Mark Murray wrote:
>> >> I've had a patch in the system (bin/12727) since 1999/07/20 that does
>> >> just this for the NetBS
tbsd.org/pub/NetBSD/security/advisories/NetBSD-SA2002-021.txt.asc
I briefly looked at this and the FreeBSD code appears to be the same.
Of course, I'm not sure what getting a shell with a GID of games really
gets you
My point here, I guess, is that moving these games to ports proba
ce base). I was reacting to
the "rot of the code" comments. I also don't have a (major) problem that
this patch was never committed -- there are other more important things
for the committers to work on. :-)
I would hope that if these are moved to ports, then (at least) these
patches
nBSD's changes would be a
> good place to start. I think rogue, hack, primes, fortune and worm are worth
> keeping, but I don't have the time or patience to maintain them.
I've had a patch in the system (bin/12727) since 1999/07/20 that does
just this for the NetBSD patches. I
what I'm doing wrong?
Thanks,
--
Stephen J. Roznowski([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 17 Apr, Jason wrote:
> I didn't know here to send this, but I thought that other people trying
> to keep current might have had this problem before:
>
> When I run cvsup with the default cvsup file from
> /usr/share/examples/cvsup/cvs-supfile (after putting in the correct cvsup
> server addres
t lines from my boot:
sbc0: at port 0x220-0x22f,0x300-0x301,0x388-0x38b
irq 9 drq 1,5 on isa0
sbc0: setting card to irq 9, drq 1, 5
pcm0: on sbc0
I can provide more info if necessary.
Thanks,
--
Stephen J. Roznowski([EMAIL PROTECTED])
To Unsubscrib
k ] ; then
> echo "${0}: $bak exists and is not a directory, aborting";
> exit 1;
> fi
> fi
Another take on this is to *not* do the backups if the directory doesn't
exist... I'll probably send-pr something like the above however
--
Stephen J. Roznowski([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
fi" to the top
of the files, or
2. Add a "mkdir -p $bak" to the top.
Do others consider this an error, and if so which is the preferred
fix?
Thanks,
--
Stephen J. Roznowski([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscr
10 matches
Mail list logo
