You should be mounting devfs in that directory. For convenience you can use
a null mount to achieve that.
Also, I'm currently working on a huge update of linuxulator, so if it
doesn't work, it might well be worth waiting a while or so for me to commit
the whole mess.
Cheers,
Alex
:
Am 08.03.2010 14:57, schrieb Saifi Khan:
Since the boot manager displays information on the basis of
partition ID, DragonFlyBSD is shown as FreeBSD !
In DragonFly's boot0? It must be really old then, since I changed it to
DF/FBSD back in 2005. Not that this helps you any better but it's all
On Monday 08 March 2010 08:26:05 Alex Hornung wrote:
You should be mounting devfs in that directory. For convenience you can use
a null mount to achieve that.
Hm, there's an hda in there; DFly calls that ad0 (although the hda is a
symlink to a nonexistent wd0d).
Also, I'm currently working
: Hm, there's an hda in there; DFly calls that ad0 (although the hda is a
: symlink to a nonexistent wd0d).
If the point is to have something called hda, linking to ad0, you can do
exactly that, link it.
: Great! I look forward to it. Could you include sed and awk in one of
: the suse
:
I got curious about BSD (DragonFly, specifically) security and
wondered why there wasn't a security process that processed all
security-relevant error messages which could then be used to
block IPs, disable user accounts, and kill processes. At least
it'd be a step to automating *some* obvious
Walter wrote:
I got curious about BSD (DragonFly, specifically) security and
wondered why there wasn't a security process that processed all
security-relevant error messages which could then be used to
block IPs, disable user accounts, and kill processes.
Because
a) such a mechanism could be
On Monday 08 March 2010 15:33:11 Walter wrote:
I got curious about BSD (DragonFly, specifically) security and
wondered why there wasn't a security process that processed all
security-relevant error messages which could then be used to
block IPs, disable user accounts, and kill processes. At
How would you write a program to process error messages and decide which user
accounts to disable?
As to blocking repeated login failures, there are such things.
I agree with you that blocking the ip is better than blocking a login,
that could be easily abused to lock out accounts. Password
Jonas Trollvik schrieb:
How would you write a program to process error messages and decide which user
accounts to disable?
As to blocking repeated login failures, there are such things.
I agree with you that blocking the ip is better than blocking a login,
that could be easily abused to
