Gustavo V G C Rios wrote:
>
> Hy folks!
>
> I have been playing with FreeBSD for the last 1 year and some time ago i
> decide to give openbsd a try.
>
> I have been loving Free! Now, playing with Open is no trouble.
> Some questions came up:
>
> 1) What are the advantages/disadavantages of usi
On Thursday, 30 March 2000 at 23:19:24 +, Gustavo V G C Rios wrote:
> Matthew Dillon wrote:
>> It's still a bad idea to post this sort of question to both mailing
>> lists.
>
> Sorry, i did not realized that!
> Next time, i'll be carefull!
FWIW, that's Matt's opinion. I don't necessa
Matthew Dillon wrote:
> It's still a bad idea to post this sort of question to both mailing
> lists.
Sorry, i did not realized that!
Next time, i'll be carefull!
--
If you're happy, you're successful.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers"
:Hy folks!
:
:1) What are the advantages/disadavantages of using FreeBSD or OpenBSD?
:..
:
:PS: I am not asking which is the best OS (a kind of question that should
:never be asked).
:I only want to know the good/bad things about both of them, since no
:OS is perfect!
It's still a bad ide
Hy folks!
I have been playing with FreeBSD for the last 1 year and some time ago i
decide to give openbsd a try.
I have been loving Free! Now, playing with Open is no trouble.
Some questions came up:
1) What are the advantages/disadavantages of using FreeBSD or OpenBSD?
2) FreeBSD has proven t
In message
Julian Elischer writes:
: quickest fix would be to make the core-dump routines not follow symlinks.
An even quicker fix would be to disable coredumps in periodic, since
no reboot would be required. :-)
As has been noted in -security, the kernel fix has been committed.
Warner
To Un
In message <19990826184654.a...@ecad.org> crypt0genic writes:
: This was just posted to BUGTRAQ, are the FreeBSD developers aware of this yet?
Yes. We are and have been working to correct the problem. In fact,
there is a kernel patch that has been committed. A quick and dirty
workaround has bee
In message <[EMAIL PROTECTED]> Julian
Elischer writes:
: quickest fix would be to make the core-dump routines not follow symlinks.
An even quicker fix would be to disable coredumps in periodic, since
no reboot would be required. :-)
As has been noted in -security, the kernel fix has been commit
In message <[EMAIL PROTECTED]> crypt0genic writes:
: This was just posted to BUGTRAQ, are the FreeBSD developers aware of this yet?
Yes. We are and have been working to correct the problem. In fact,
there is a kernel patch that has been committed. A quick and dirty
workaround has been posted t
works as advertised for me...
quickest fix would be to make the core-dump routines not follow symlinks.
On Thu, 26 Aug 1999, crypt0genic wrote:
>
> This was just posted to BUGTRAQ, are the FreeBSD developers aware of this yet?
>
> -Emil
>
> --
> Reverse engineering, the most fun and usuall
This was just posted to BUGTRAQ, are the FreeBSD developers aware of this yet?
-Emil
--
Reverse engineering, the most fun and usually the most effective way
to tackle a problem or learn something new.
Public PGP key: http://www.ecad.org/crypt0genic_pgp_key
Website:http:/
works as advertised for me...
quickest fix would be to make the core-dump routines not follow symlinks.
On Thu, 26 Aug 1999, crypt0genic wrote:
>
> This was just posted to BUGTRAQ, are the FreeBSD developers aware of this yet?
>
> -Emil
>
> --
> Reverse engineering, the most fun and usual
This was just posted to BUGTRAQ, are the FreeBSD developers aware of this yet?
-Emil
--
Reverse engineering, the most fun and usually the most effective way
to tackle a problem or learn something new.
Public PGP key: http://www.ecad.org/crypt0genic_pgp_key
Website:http:
13 matches
Mail list logo
