Hi,
I just finished upgrading a 3.8 system to 4.1 and performing a fresh
install on a system that previously had Linux installed on it.
Naturally while performing these upgrades I had to occasionally
consult the OpenBSD documentation (FAQs on installation/upgrading).
The existing documentation wor
Hi,
I don't think this question is really OpenBSD specific per-se but
rather an OpenSSH command.
I'm using public key authentication between my OpenBSD systems
(running ssh-agent) so that I can ssh/sftp between my systems (both
are 4.1) without having to enter a password. As part of some IPSec
pe
Although that solution will make upgrading more difficult without the
change being made in-tree (you'll have to rebuild pfctl after each
upgrade).
On Dec 3, 2007 1:24 PM, MikeM <[EMAIL PROTECTED]> wrote:
> On 12/3/2007 at 7:06 PM Henning Brauer wrote:
>
> |* MikeM <[EMAIL PROTECTED]> [2007-12-03 1
What problem with the existing upgrade procedures is solved with your
new approach?
On 4/4/07, Peter Fraser <[EMAIL PROTECTED]> wrote:
I use an approach to upgrading that I have not seen written
anywhere. It does need additional space in the root partition
but with disks these days that is not n
On 4/4/07, Walter Goulet <[EMAIL PROTECTED]> wrote:
On 4/4/07, Peter Fraser <[EMAIL PROTECTED]> wrote:
> Quoting from http://www.openbsd.org/faq/upgrade41.html
>
> Upgrading is a convenient way to bring your OpenBSD system up to
> the most recent version. However, the res
Hi,
I've recenly installed OpenBSD 3.7 on my Zaurus C3000. While perusing
the afterboot manpage to figure out how to configure my system, I
noticed that the manpage indicated that the /etc/rc.conf.local file was
referred to before the manpage stated that the user had to create this file.
So
On Tue, May 31, 2005 at 10:41:38PM -0500, Walter Goulet wrote:
>> Hi,
>>
>> I've recenly installed OpenBSD 3.7 on my Zaurus C3000. While perusing
>> the afterboot manpage to figure out how to configure my system, I
>> noticed that the manpage indicated t
Hi,
As a relatively new user to OpenBSD on my zaurus, I've spent a bit of
time configuring my prism based wireless network card to work correctly
with my AP using wep etc.
One minor point that befuddled me at first was the fact that ifconfig
and wicontrol use different terms when referring t
et ID (ESSID).
The
.Ar id
can either be any text string up to 32 characters in length,
[EMAIL PROTECTED] wrote:
hi,
On Tue, Jun 07, 2005 at 02:33:35AM -0500, Walter Goulet wrote:
One minor point that befuddled me at first was the fact that ifconfig
and wicontrol use different terms when refe
Hate to keep this thread going, but I have to strongly disagree with the
original poster's assertion on the attitude of the list. I have been
treated well on the list. Additionally, I've been very happy at how
receptive the developers are to discussing issues if you simply do your
homework and
Bram Van Dam wrote:
I quite frankly don't give a rat's arse about how frustrated some of you
are by seeing n00bs post on the list. So what if someone didn't read man
page XYZ? At least tell them to read it. The only thing more disgusting
than people not willing to learn, is people not willing t
man resolv.conf(5)
The resolv.conf.tail file is used to pass extra options to the
resolver. dhclient effectively appends the options in resolv.conf.tail
to the resolv.conf file.
On 7/12/05, Frank Bax <[EMAIL PROTECTED]> wrote:
> I just installed 3.7 twice - once with dhcp and once with static ip
pages must be
-current, because I can find no mention of resolv.conf.tail in any man
pages on my 3.7 (cdrom) system. The -current man pages on openbsd.org
website appear to confirm the behaviour already present in cdrom release.
At 01:25 PM 7/12/05, Walter Goulet wrote:
man resolv.co
I think the UML the OP is referring to is Unified Modeling Language
and Rational Unified Process.
On Wed, May 5, 2010 at 2:25 PM, Lars Nooden wrote:
> On 05/05/2010 10:08 PM, Christiano F. Haesbaert wrote:
>>
>> Sorry for such an out of topic thread, hear my pain:
>>
>> I'm really sick of hearing
14 matches
Mail list logo
