Ok, please stop that now. Those pseudo-witty replies are getting quite
annoying.
Thanks.
Hi,
I just tried to rebuild the stable userland yesterday night. There seems
to be something (I know, a bit vague) wrong with that banner stuff. Due
to the CVS-logs, nobody changed a thing here recently.
Does anybody see the same error or should I blame my box for that:
cc -O2 -pipe-c /usr/s
Hi,
I've got a D-Link DWL-G650 (H/W C2, F/W 3.1.6) PCMCIA wifi-card lying
around here for some time. I haven't had tested it by now, but out of
curiousity I was searching for some info yesterday why it wouldn't work
on OpenBSD (though it seemed to be recognized as ath1, AR5212, but not
registered
Uwe Dippel wrote:
>
> What I cannot reproduce, though, is the boot problem. Here it installs and
> boots properly (what do you mean with 'Installing the BIOS' ??); also in
> the case with active partition #0. Without any additional biosboot or
> whatsoever.
> Maybe you made a mistake at your offse
Uwe Dippel wrote:
> On Mon, 02 Jan 2006 14:06:52 +0100, M. Schatzl wrote:
>
>
>>Now that I switched to a 60G disk (cloned the other 2 partitions and the
>>Windows bootsector, then installed OpenBSD anew from the same
>>floppy/mirror as before), OpenBSD won't
Hi,
I've got a strange problem here; maybe some of you have a better
understanding of the issue:
Machine:Thinkpad X40
Disks: 40G, 60G
Partitions: 7.5G NTFS : OpenBSD : Free Space : 4G CompaqRescue
Installing OpenBSD on the original disk (40G) made no problems at all.
Everything worked j
The easiest way would be to look for a file $USER.key in /home. If it
exists, look for a corresponding $USER.img file somewhere and mount it
on /home/$USER. This way you won't have to do anything special for a
certain user except changing his login-facility used. And you don't
twist semantics.
As
>>oh, like putting it in the gecos field? that'd be kinda cool.
I like that idea..
But what are you doing if you want to transfer your crypted dir to
another machine? Will be definitely harder to squeeze the bits out of
the gecos. And you probably get a high probability of funny terminal
behaving
David Coppa wrote:
> So basically what I ask is: which atheros chipsets are known to work?
> For what I've understood only AR5210 and AR5211 are safe bets.
Ever looked at man ath?
/M
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Philip S. Schulz wrote:
> Could be your BIOS' fault. Try sth like
>
> machine mem [EMAIL PROTECTED]
Thanks a lot. That was it.
All the best,
/Markus
iD8DBQFDIrtRV/arRO6fNWsRA4SlAJ0XtJKuLo2/eDlEAJweg/IuFiJY/QCePTVt
GtcaSp4NTD8KMBMVcdRDu5s=
=mq2K
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
900K ... hell; I meant that only the 16 MB onboard are recognized.
/M
iD8DBQFDIquaV/arRO6fNWsRAzE2AKDdRfRlaaXPwUx0FHenEKV0HOMIAQCfZIbi
gPO6DGem371ykTgtJV3g48Q=
=YBPq
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hi Gang,
probably a bit of a ridiculous question, but I ever noticed that one
of my machines I occasionally use for testing (Pentium MMX, 133 MHz)
is generally a bit slow and swaps out a lot. I didn't care, though,
until now.
I just looked at th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Damien Miller wrote:
> Just use "tail -f" as the source of your pipe and all your problems go
> away.
You're right. Thanks for reminding.
>> In this case, its a script scanning for invalid ssh-logins invoked by
>> auth.info. It then appends the IP to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi list,
is there a reason why the OpenBSD-shipped syslogd cannot write
directly into a pipe? This would come in quite handy for just-in-time
log-processing.
In this case, its a script scanning for invalid ssh-logins invoked by
auth.info. It then app
14 matches
Mail list logo
