Hi Nick and thanks for the answer.
I have installed openbsd on my laptop and everything works fine,gnome too.
What i haven't uderstand is:
1)I have a Digicom usb wifi with Zydas chipset and i 'vre read it's just
supported...but i don't know to activate (command not found with lsusb and
lspci)
I'm trying to automate getting the sets and source for running -current.
For some reason, this syntax:
ftp -ia ftp://host.domain/pub/OpenBSD/snapshots/architecture/*.tgz
or this:
ftp -ia ftp://host.domain/pub/OpenBSD/snapshots/architecture/bsd.rd
works great from the command line. But not
On Wed, Dec 31, 2008 at 01:58:29AM -0800, lordfabri wrote:
Hi Nick and thanks for the answer.
I have installed openbsd on my laptop and everything works fine,gnome too.
What i haven't uderstand is:
1)I have a Digicom usb wifi with Zydas chipset and i 'vre read it's just
supported...but i
Ed Ahlsen-Girard wrote:
Anybody have an idea of what I'm missing?
How is $PATH set? Do the scripts work if you include the full path?
i.e. /usr/bin/ftp
Regards,
-Lars
this works for me, recheck your install, or otherwise
try to compile ftp again from sources.
-Jesus
Ed Ahlsen-Girard escribis:
I'm trying to automate getting the sets and source for running -current.
For some reason, this syntax:
ftp -ia
Ed Ahlsen-Girard wrote:
I'm trying to automate getting the sets and source for running
-current.
Incase you don't want to reinvent the wheel:
http://www.xs4all.nl/~hanb/software/OpenBSD-binary-upgrade/
# Han
Ed Ahlsen-Girard wrote:
`ftp -ia ftp://host.domain/pub/OpenBSD/snapshots/architecture/*.tgz`;
Using system () does not get any different behavior, whether I pass a
list or a proper array. In all cases I see a connection to the server,
followed by a complaint of an invalid directory, and
I would use authpf and assign them each a unique port number. They
must authenticate with the gateway for the rule to become active.
just a thought ..
-Original Message-
From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org]on Behalf Of
Jonathan Windle
Sent: Tuesday,
I've been running into an error while trying to build 4.4 from source in
preparation for building a release. Both the installation and the
source are plain-vanilla from the CD set. I've been following the steps
in release(8)
http://www.openbsd.org/cgi-bin/man.cgi?query=release
and the
On Tue, Dec 30, 2008 at 12:23:59PM +0100, Henning Brauer wrote:
* Douglas A. Tutty dtu...@vianet.ca [2008-12-30 02:39]:
crappy applications are still crappy applications on OpenBSD, but
worse on pretty much any other OS.
IIUC, with ports right now, to get security fixes you have to run
Just my 1 cent on the perl script
#!/usr/bin/perl
`cd /path-to-dir`:
`rm *`;
will purge your working directory, not /path-to-dir, as each of the `command`
constructs is executed in a process of its own and thus has no influence on
the next command
you would be better of with
#!/usr/bin/perl
That's good thing to know (!)
Christoph Leser le...@sup-logistik.de wrote:
Just my 1 cent on the perl script
#!/usr/bin/perl
`cd /path-to-dir`:
`rm *`;
will purge your working directory, not /path-to-dir, as each of the `command`
constructs is executed in a process of its own
Thanks for the response.
I have considered this however the users who are connecting to the
windows boxes are rather unsophisticated. The user also already has to
authenticate when they connect to the Windows box. Adding another
layer of authentication and software on the users end is
* Douglas A. Tutty dtu...@vianet.ca [2008-12-31 15:56]:
On Tue, Dec 30, 2008 at 12:23:59PM +0100, Henning Brauer wrote:
I'd use the OpenBSD/ff combo over whateverlinux/ff any time, even if
the ff on OpenBSD is older, yes.
Is it older? If its older with backported bug fixes, fine.
And if mixerctl doesn't help you then post a dmesg. It is good
practice here to always send a dmesg when you have a hardware issue.
There is no GUI wifi manager that I know of. There are various scripts
that people have posted to misc@ over time to try to make wifi
management
On Wed, Dec 31, 2008 at 9:42 AM, Christoph Leser le...@sup-logistik.de wrote:
Just my 1 cent on the perl script
#!/usr/bin/perl
`cd /path-to-dir`:
`rm *`;
will purge your working directory, not /path-to-dir, as each of the `command`
constructs is executed in a process of its own and thus
On Wed, Dec 31, 2008 at 9:42 AM, Christoph Leser le...@sup-logistik.de
wrote:
Just my 1 cent on the perl script
#!/usr/bin/perl
`cd /path-to-dir`:
`rm *`;
will purge your working directory, not /path-to-dir, as each of the
`command`
constructs is executed in a process of its
On Wednesday December 31 2008 13:34, you wrote:
On Wed, Dec 31, 2008 at 9:42 AM, Christoph Leser
le...@sup-logistik.de wrote:
#!/usr/bin/perl
`cd /path-to-dir`:
`rm *`;
You shouldn't be using backticks in a perl script. Backtick simply
starts a new process/subshell and runs whatever you have
Opccedil;atilde;o Global deseja Boas Festas a todos os Clientes,
Fornecedores e Amigos.
se nco conseguir visualizar correctamente o contezdo deste e-mail, por favor,
clique aqui.
Para mais informagues acerca dos nossos produtos e servigos, por favor,
contacte-nos:
Rua de Raimundo
19 matches
Mail list logo
