So I'm curious if there's something in OpenBSD that's similar to the
"mount -o bind /dir1 /dir2" to make dir1 appear where dir2 is.
I seem to recall a mount_nullfs but don't see it in the latest
OpenBSD.
Please note that I'm not trying to start a flame war, so there's
no need to make Linux commen
On 2/26/06, vladimir plotnikov <[EMAIL PROTECTED]> wrote:
> Take look on FAQ pages: http://www.openbsd.org/faq/faq14.html#MountImage
Eh? Disk setup?
Anyway, I found 'em, they're called freedt
In /usr/ports/sysutils/freedt
Thanks anyways
--
Security Guru for Hire http://www.lightconsulting.com/
Just curious, I recall hearing there was a clone of daemontools for
OpenBSD, what was it called?
TIA
--
Security Guru for Hire http://www.lightconsulting.com/~travis/ -><-
GPG fingerprint: 9D3F 395A DAC5 5CCC 9066 151D 0A6B 4098 0C55 1484
Hey,
The soekris site says the vpn1401 is fully supported in the latest
release of OpenBSD.
However, mine isn't autoprobing. What do I need to do to get it working?
--
"Cryptography is nothing more than a mathematical framework for discussing
various paranoid delusions." -- Don Alvarez
http://ww
> I'm afraid the driver does not work, unless your machine has 16MB of
> memory (or less). Fixing this is on my list, but real-life issue have
> been in the way.
But it used to work in 2.x; has there been a change underneath, or can
you just use the old code?
I totally understand about not having
Can anyone confirm that an Adaptec AHA-1542 works with anything since
3.6? I found that support for it was silently broken sometime in 3.x,
even though it's listed as supported hardware for x86.
Also, I have 3 PCI Bustek adapters (BT-958D, BT-958, BT-946C) in a
different machine, but booting up
> huh? "Before any rules are evaluated, the filter checks whether the
> packet matches any state. If it does, the packet is passed without
> evaluation of any rules." - pf.conf(5)
Yeah, I neglected stateful matching. I should have said that every
packet that has to run the gauntlet of rules, has
>>In pf nat rules also the first match wins
>>
>>__but__
>>
>>in pf filter rules the __last__ match wins.
>>
>>In fact that is the one thing I don't like in pf, but to have a "first
>>match win" you can use the magic word quick in all your pass and block
>>rules. (e.g "pass in quick")
>And thereby
> So what is the default? It is 022 on all my machines and I have never
> screwed with it and as a result pkg_add works just fine.
I set mine to 077 in .profile.
> Untidy things like that make me wary of code from the same source...
Well, if you think having a paranoid root umask is a bad thing
> And we should have to google, why? I can't be bothered if the author
> can't be bothered to get his own URL correct.
I was typing it by hand from a system which had blocked my homepage's
IP (don't ask me why, I dunno). Momentary lapse of reason. Nice to
see that OpenBSD's culture hasn't change
Hey,
Just letting people know that a dynamic firewall daemon, (sort of a
command shell for the firewall), is available for OpenBSD & pf. It's
called dfd_keeper, and I'm looking for ideas, suggestions, developers,
and testers. You can find it here:
http://www.lightconsulting.com/dfd/dfd_keeper/
> Is not possible to adjust clock under OpenBSD correctly??? I do not
> understand why cmos clock needs to leave at UTC. why?
Just as a tip, it's a bad idea to use the CMOS clock as something
other than UTC. I don't recall all the details, but it is especially
problematic around DST adjustments
Hi, I've spent a fair amount of time minimizing open ports and I have
a cool new program for other people allergic to unnecessary open
ports.
The basic idea is called a dynamic firewall daemon, that provides a
command-line like interface which can execute carefully controlled
modification to your
13 matches
Mail list logo
