On Fri, May 28, 2010 at 4:51 PM, Marco Peereboom wrote:
> On Fri, May 28, 2010 at 04:28:56PM +0200, Reyk Floeter wrote:
>>
>> So the question is - am I living in a parallel universe?
>
> Simple! yes.
Agreed, in a level IV multiverse at least (before you ask, we need a
very good cosmologist to def
On Wed, May 26, 2010 at 3:24 PM, Vadim Jukov wrote:
>
> Now he'll definitely come here, because you wrote "Linux" instead" of
> religiously correct "GNU/Linux".
Do you mean Apache/BSD/GNU/IPL/MIT/SGI/X11/Linux, right?
On Fri, Apr 16, 2010 at 5:05 AM, VICTOR TARABOLA CORTIANO
wrote:
>> > For them? Maybe the freedom to give copies to their friends whithout
>> > being sued or doing anything illegal.
>>
>> That can easily be applied to any of the free licenses without any
>> other legal obligations.
>>
>
> Yes! Bec
On Sun, Mar 28, 2010 at 6:03 PM, Ingo Schwarze wrote:
>> df /altroot shows: "Mounted on /"
>> (df -h doesn't show /altroot.)
>
> Thus, /altroot is currently not mounted.
As you said before, it shouldn't be usually mounted as it is used by
dd(1). daily.out's output on the first email shows that th
On Sun, Mar 14, 2010 at 5:26 PM, Robert wrote:
>
> There is nothing wrong with cripling an os by deleting files, if one
> isn't hurting enough yet.
> If some random textfile referencing 2.8 helps you achieve what you
> want, go for it.
There are very good reasons to remove files from an operating
On Sun, Mar 14, 2010 at 5:10 PM, Edd Barrett wrote:
> On Sun, Mar 14, 2010 at 2:42 AM, Jason Dixon wrote:
>> https://https.openbsd.org/cgi-bin/order?CD47=1&CD47%2b=Add
>
> Is anyone from openbsd europe on this list? I have some problems with
> my pre-order and the "contact" email page doesnt work
2010/3/8 Miguel Araujo Pirez :
> Do you think if I post the trace and other information on the lists I will
get
> any help? any recommendations?
Usually posting all information available helps when asking for
support on mailing lists. Upgrading to a current snapshot may help
too, as there had been
On Thu, Feb 4, 2010 at 5:42 PM, Miod Vallat wrote:
>
> You do not want to tinker with the firmware. The stock PMON2000 does not
> support these machines, so you'll need to start with the pmon code
> provided by Lemote, and saying that it is in a dire need of cleaning is
> an understatement.
After
On Thu, Feb 4, 2010 at 9:46 AM, Otto Moerbeek wrote:
>
> There are two models. I have the 10" model. It really has a 10"
> screen, but indeed it runs at 800MHz. Also, while a little video hole
> is there, the camera hardware seems to be absent or not connected. The
> 8.9" version does have a worki
On Fri, Dec 18, 2009 at 6:07 AM, David Gwynne wrote:
> On 18/12/2009, at 1:26 PM, Raymond Lillard wrote:
>>
>> Real men use cat. :-)
>
> real men use COPY CON PROGRAM.EXE
real men use EDIT/TECO.
On Tue, Dec 8, 2009 at 12:20 AM, Dorian B|ttner
wrote:
>
> some time ago I had a usb wlan adapter from avaya at hand
> http://old.nabble.com/AVAYA-Wireless-USB-Client-%28Gold%29-td21817914.html
> It turned out, then when opening the cover of the desk stand it was nothing
> more than a pcmcia card
On Tue, Dec 8, 2009 at 7:28 PM, Ted Unangst wrote:
> On Tue, Dec 8, 2009 at 1:12 PM, Mike Small wrote:
>> You might want to try 4.5 and see if that works for you. I have a wi in
>> an old dell laptop too that no longer got detected as of 4.6. If anyone
>> wants to see it for some reason, I can
On Tue, Nov 17, 2009 at 12:28 PM, Pete Vickers wrote:
> alternatively you could run/spawn ftpd from inetd, which will presumably
> mean that all the resources will be 'returned' as soon as the connection
> closes. However significant performance hit on a busy ftp server.
this is not what art@'s s
On Fri, Oct 30, 2009 at 2:31 PM, Dan Harnett wrote:
>
> The kernel you are using predates the iwn changes. B The man page you
> read postdates the changes. B So, yes, use the 5.1 firmware until you
> update to a snapshot after 10/24. B That should match the firmware that
> the iwn manual page incl
2009/10/30 TomC!E! BodE>C!r :
> I'm using snapshots :
>
> $ sysctl kern.version
> kern.version=OpenBSD 4.6-current (GENERIC.MP) #259: Thu Oct 22 20:46:08 MDT
> 2009
> B B dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
>
> $
>
> So I will wait for next one. This is last availabl
2009/10/30 TomC!E! BodE>C!r :
>
> When I use this file
> http://damien.bergamini.free.fr/packages/openbsd/iwn-firmware-5.1p0.tgz
> which was mentioned in older versions of this man page then everything
> is ok.
>
> So is it problem of my card that it can't use 5.2 version of firmware
> or typo in m
On Tue, Oct 13, 2009 at 4:12 PM, Ross Cameron wrote:
>
> Uhm perhaps to provide a better OSPF and BGP implementation to the for an OS
> that is the OS of choice of millions of users and thousands of corporations?
users and corporations should learn how to choose the operating
systems that best fi
On Tue, Aug 25, 2009 at 12:00 PM, Daniel Gracia
Garallar wrote:
> It all depends, as Paraguay has two native languages: spanish and guaranm.
> In spanish, the country name is written as 'Paraguay', and 'Paraguai' in
> guaranm.
>
> I barely, if ever, have read 'Paraguai' in any text, maybe because I
On Tue, Aug 25, 2009 at 11:16 AM, frantisek holop wrote:
> hi there,
>
> Aug 25 Constitution Day in Paragual
>
> shouldn't that be Paraguai?
Indeed, it is a typo. However, is it not a much more usual spelling
"Paraguay"?
On Thu, Aug 20, 2009 at 12:25 PM, Edd Barrett wrote:
> On 8/20/09, Igor Sobrado wrote:
>> we have a few problems here too (using TeX Live in both OpenBSD 4.6
>> and -current, on i386 and amd64); i would suggest sending a detailed
>> bug report to the TeX Live developers
On Thu, Aug 20, 2009 at 4:29 AM, Eric d'Alibut wrote:
>
> I bulled ahead and installed the 2008 texlive from TUG, but still
> errors. Say I do:
[...]
> Thoughts? (Sorry if this is such a sketchy report, but I'm pressed for
> time right now!)
we have a few problems here too (using TeX Live in both
On Sun, Aug 16, 2009 at 12:54 AM, Philip Guenther wrote:
> On Sat, Aug 15, 2009 at 3:44 PM, 4625<4625...@gmail.com> wrote:
>> Is it correct string for /etc/fstab? "/dev/wd2d /altroot ffs xx 0 0"
>
> Assuming /dev/wd2d is the correct partition, yes. (You're looking at
> the daily(8) manpage, right?
On Mon, May 4, 2009 at 12:07 PM, Otto Moerbeek wrote:
> On Mon, May 04, 2009 at 11:46:51AM +0200, David Vasek wrote:
>> Possibly, but you need to get the mentioned license _from Microsoft_, as
>> is written in the license: "...may require an additional license from
>> Microsoft."
>
> the operative
Aaron W. Hsu sacrideo.us> writes:
> I am trying to use the mail(1) p command. According to the help that is
> printed out when running the program, it seems that the p command should
> pipe the message out to LPR and print it. However, it just prints the
> message out to standard output.
>
>
The first Technology Meeting at Isla Cristina city will take place
on April 3rd and 4th, 2008 at Isla Cristina, near Huelva, Spain.
This two days event will be a good oportunity to talk to developers
and users of some of the most important free software projects.
There will be three workshops on th
Check BIOS settings too...
Don't know about the current status of OpenBSD on these fine laptops,
but you will probably need to boot to UKC and disable ahc0. This change
is (was?) required for installation kernels only. GENERIC kernels do
not need this workaround to boot... but you will need to b
Igor Sobrado writes:
>
> I would like to ask if this output for the "machine diskinfo" command
> on the OpenBSD/i386 BOOT release 2.10 is expected:
>
>
> Using drive 0, partition 3.
> Loading...
> probing: pc0 com0 com1 mem[639K 255M a20=on]
> disk:
Hi Lachlan.
What you are looking for is usually called "router on a stick".
Perhaps you can use some binat rules to specify bidirectional
mappings between external netblocks and the internal aliases.
Don't know why you are doing it, however. The only time I made
a "router on a stick" was on my C
Hello.
I have a soekris net4801 embedded computer. This computer currently
runs OpenBSD 4.0. There are two internal drives on it: an enhanced
availability Hitachi Travelstar E7K100 (ready for 24/7 use) and a
SanDisk SDCFB-1024 CF card that is being used as installation media
and net4801 document
Hello!
Joachim. I think that the problem you had with your Thinkpad happened
to the son of a friend I have at Illinois too (on a slightly different
variant). On his laptop (a T20) the display CCF lamp did not turn on.
Indeed, buying at least two similar laptops is a smart idea. That is
the rea
In message <[EMAIL PROTECTED]>, Bob Beck writes:
>
> I have a T30. pretty much everything works on it and very
> well, it suspends and resumes again.
The only concerns I have with OpenBSD are related with APM and ACPI
support (e.g., problem report number 5307/kernel). In fact, APM was
the
Hello.
I am looking for a laptop to replace my old, but excellent,
Dell Latitude CPi R400GT (this computer has a broken hinge right now).
The OpenBSD/i386 laptop page (http://www.openbsd.org/i386-laptop.html)
has a lot of information on Thinkpads (from the earliest models to
the most recent units)
Hello.
This patch removes the -g option from src/etc/skel/dot.cshrc.
The reason I am suggesting this change is that -g "does nothing;
[it is] kept for compatibility with older versions of ls" (source: ls(1));
so this option is superfluous on this alias.
If it is better opening a problem report,
Hi Jason.
Thank you very much for your advice, but I prefer stay at the
software provided in the base system if it is possible (why
choosing an operating system if we do not like the software
it provides?). ksh is a powerful shell and the default
configuration in OpenBSD makes it really useful, n
Well, it seems that the problem related with the V210 system
is a consequence of a lack of documentation provided by Sun
Microsystems. pciide works fine on other sparc64 systems.
As the Geode computers are not designed with I/O performance
in mind, it makes sense thinking on the processor as the
Hello!
I want to say that this thread seems related with this one:
http://marc.theaimsgroup.com/?l=openbsd-misc&m=117027330031702&w=2
Two very different computer architectures (a i386-compatible embedded
computer running a 200 MHz Geode processor and a high-end sparc64 computer)
but both with
ndeed, sometimes mail behaviour is very difficult to understand...
...or believe! :-)
> [2007-01-31 16:27] Igor Sobrado <[EMAIL PROTECTED]> wrote:
> > debug_level++;
> > break;
> > case 'F':
> > +
On Mon, Jan 29, 2007, Jason McIntyre wrote:
> ah, ok. it is not 4 options (-s, -a, -f, and -e), but one (-safe, as in
> "not in danger"). that's why it is described as a "...first (and not
> very reliable) approximation to a ``safe'' version of awk."
>
> you are confusing that with the -f option, w
In a private email, Philip Guenther has observed that awk does not
completely folow the POSIX option guidelines. [-safe] is not
[-s,-a,-f,-e] but a single option!
The right patch is then:
--- main.c.orig Mon Jan 29 15:01:20 2007
+++ main.c Mon Jan 29 15:52:47 2007
@@ -64,7 +64,7 @@
Hi Jason.
Sorry for sending the patches before answering to your email.
As I am not subscribed to this mailing list I have not read
your answer before working on the patches.
I think that the "-f" option requires an argument. The argument
is not optional, though. It seems that the case block th
Hi Jason.
Thank you very much for managing these small bugs so fast.
The first patch is for main.c:
--- main.c Mon Jan 29 15:01:20 2007
+++ main.c Mon Jan 29 15:04:28 2007
@@ -63,8 +63,8 @@
setlocale(LC_NUMERIC, "C"); /* for parsing cmdline & prog */
cmdname = __progna
Jason, you are very fast!
I will download the new main.c as soon as I arrive at home and remove
the case for the "-m" option. I will remove the "f" option in "[-safe]"
as it seems that the argument to it is not optional.
I will submit the patch, based on the updated code, later. Two changes:
Looking carefully at the switch () {...} structure in main.c
it seems that the option "-f" requires an argument: iff the argument
to "-f" is optional I would write:
awk [-sae] [-V] [-d[n]] [-F fs] [-v var=value] [prog | -f [progfile]]
file ...
But it does not look as an optional argument,
Hello.
Just a though... I was writing a simple awk(1) script and looked
at the options supported by this utility in the hope to make the code
cleaner. It seems that there is a big difference between the synopsis
in the manual page:
awk [-safe] [-V] [-d[n]] [-F fs] [-v var=value] [prog | -f pr
In message <[EMAIL PROTECTED]>, Tom Cosgrove writes:
>
> What is happening here is that when you enter
>
> ibase=16
> l(0.1)
>
> you get "0.0" passed to the l() function, which gives -infinity. (I
> would call that the expected result under the circumstances.)
>
> If you enter
>
>
Please, drop my last example about how bc works on Solaris... bc was
on base 16, not on base 10, when run that test... it seems this is a bad
and very long day! :-)
$ bc -l
l(0.0625000)
-2.77258872223978123766
Now all is clear,
Igor.
In message <[EMAIL PROTECTED]>, Otto Moerbeek writes:
>
> On Mon, 29 Jan 2007, Igor Sobrado wrote:
>
> > (I suppose that setting obase=10 after setting the input base to 16d
> > means that the output base is set to 0x10...)
>
> indeed.
>
> In the last e
Hi again.
Of course, Karel Kulhavy is the one to provide feedback on this patch.
But I have tried it too (after upgrading src/usr.bin/bc) and seems to
be working fine for this case (NetBSD and Solaris are running their own
flavours of bc):
For OpenBSD:
$ bc -l
ibase=4
obase=10
scale=100
l(1.031)
In message <[EMAIL PROTECTED]>, Otto Moerbeek writes:
>
> bc hase some more unexpected things for the casual user:
>
> scale=4
> 1/3 produces 0.
> 2/3 produces 0.
Not so unexpected -- a mathematician would work out 0. and 0.6667
respectively, but your excellent example is what we wou
[copied and pasted, I am currently not subscribed to [EMAIL PROTECTED]
On Mon, 29 Jan 2007, Otto Moerbeek wrote:
> Note that some of your tests still
> produce strange results, but that is due to weird handling of
> non-decimal fractions wrt scale:
>
> For example, with ibase=11
> 0.1 produces 0.0
At last, I want to note that the switch structures in sftp.c and ssh.c
related with getopt(3) can be reordered. Currently, its order is
very difficult to understand, at least for me. (perhaps my patch does
not put the "case 'l':" in the right place for that reason, beware!)
and there are some ind
Ok, I have a candidate for a patch:
--- sftp.c Sat Jan 27 08:43:11 2007
+++ sftp.c Sat Jan 27 08:46:45 2007
@@ -1415,8 +1415,8 @@
fprintf(stderr,
"usage: %s [-1Cv] [-B buffer_size] [-b batchfile] [-F ssh_config]\n"
- "[-o ssh_option] [-P sftp_
Hi again!
I am working on the patch for supporting the "-l" option in both ssh
and sftp. Looking at the OpenSSH source code I found some improvements
in the messages returned by sftp and ssh when either the username or
the hostname are not provided. The first patch:
--- sftp.c Sat Jan 27
In message <[EMAIL PROTECTED]>, Christian Ruediger Bahls writes:
>
> to have an -l option for sftp would be really nice
> but perhaps one should argument a little bit differently
>
> your argument would be a lot stronger if it would go like that:
Hi Christian!
Indeed, you are right. Your argum
In message <[EMAIL PROTECTED]>, Stuart Henderson writes:
> On 2007/01/03 16:37, Igor Sobrado wrote:
> > It is certainly better using the "sftp [EMAIL PROTECTED]" syntax, but
> > sometimes
> > I miss the "user@" part on the command line when the logi
Hello.
I would like to ask if there are plans to implement the "-l" option
available in ssh(1) on the secure file transfer program sftp(1).
It is certainly better using the "sftp [EMAIL PROTECTED]" syntax, but sometimes
I miss the "user@" part on the command line when the login name on the
remote
Other missing options in the switch structure are: -b[rev], -I, -M (this
one does nothing by now, but it exists and is undocumented in the usage),
and -tstr. I suppose that these options are just not implemented in
OpenRCS right now.
There is an -e option in the rcs(1)'s usage both with and witho
Hello.
Is the -sstate[:rev] option supported by OpenRCS's rcs(1) in OpenBSD 4.0?
Beware, this computer is not running -stable, just a fresh installation
of OpenBSD 4.0. This is a possible scenario for this error:
$ rcs -s"Rel" test.c
rcs: unknown option -s
usage: rcs [-eIiLqTUV] [-Aoldfile] [-a
> Yes, you can use anything as a transport, probably even pidgeon
> carriers, but you need a receiving end to effect anything.
Indeed, see RFCs 1149 and 2549... two excellent april fools
on avian carriers!
> So, unless
> you fear that someone is able to install a trojan on your OpenBSD
> server b
I am not a member of this mailing list, so I will copy and paste
the comment of Philip Guenther here:
"The 'cpio' format for pax (selected using "-x cpio") handles long file
names in a portable way, as opposed to GNU tar's non-portable
extension for handling file names longer than 100 bytes."
Agr
Hi Uwe.
I see the advantages of your proposal but, as suggested in this thread
and as you did, sed(1) can be very helpful in this matter. Just my
opinion, but one of the best features in the BSD family of operating
systems is that these operating systems are simple. The BSD operating
systems do
D'oh! Of course, the SIMH entry in the FAQ 12 should read
"Instructions can be found _at the_ OpenBSD/vax on SIMH page."
Well... there are people with more appropriate english skills that
will probably suggest a lot of changes like this one.
Igor.
An important note: I missed one of the advices of Tom Cosgrove...
I would replace the "OpenBSD's Flavors" link in the patch with
something like "section 5" (as Tom suggests) or either "FAQ 5, flavors"
as found on other parts of the FAQ. Tom suggestion is more readable,
though. Of course, there ar
Thanks a lot to all the people that provided feedback on this matter.
Attached to this post is a new version of the patch. I did a mistake
downloading the files used previously from the repository. This time,
I choosed the right download method:
$ cvs -d [EMAIL PROTECTED]:/cvs get www/faq
The
In message <[EMAIL PROTECTED]>, Tom Cosgrove writes:
>
> Don't create a bug report for this. This is not a bug. This is a
> change of style that you (and some others) would like to see in the FAQ.
> Nick, myself, and other people who work on the FAQ read misc@; there's
> no point just pi**ing us
sing characters, but
I wanted to fit it in three columns, it was too large.
Now the message:
--- Forwarded Message
Date:Thu, 07 Dec 2006 21:53:51 +0100
From: Igor Sobrado
To: Jeremy Huiskamp
Subject: Re: OpenBSD 4.0 CD Set Package List
In message <[EMAIL PROTECTED]>, Je
Hi Nick.
I read your post after sending the patch. I will do my best to make
these links as short as possible. Don't know your taste on this matter,
but I do not dislike relatively long links if these links make the
text more readable, and it is independent of the format of the document
being us
Attached is the first draft of the patch. Once it has been debugged
I will open a bug report on it. Please, check carefully all the entries
in the patch and do not trust on my English skills. Some suggestions:
- replacing references to threads in the mailing lists (now the
thread subject)
I cannot see why making a patch to change the links is difficult.
I will look at the cvs repository as soon as I get some time and
submit a patch. In any case, I would appreciate a carefully review
of it, just to fit it to the taste of the developers.
Igor.
Hi Jeremy.
There is probably something wrong in the input to "grep -v" as a lot
of the packages that "are not present in the CD" really *are* (e.g.,
xmms, xpdf, abiword...)
Cheers,
Igor.
There are very good reasons to get an original OpenBSD distribution;
packages are only one of these reasons. As you can see, the list
of packages has been carefully choosed to meet the requirements of
both servers and desktops. Hope this information will help you taking
the right decision. The l
Nice to see that the text and PDF releases of the FAQ have finally
been upgraded to 4.0...
Just a suggestion: would it be possible replacing the links of the
class "...can be found here" (e.g., '1.7 of the OpenBSD FAQ) in
the FAQs to more useful descriptions (e.g., "...can be found on the
OpenBSD'
I had been in contact with him too. I sent some errata entries for
his excellent book on pf and he acknowledged these fixes. On november 12,
he mentioned on a private email that these fixes will be added to his
checklist for the 3rd edition of the book.
Never asked him about his health, however.
In message <[EMAIL PROTECTED]>, chefren writes:
> Hello Igor,
Hello Chefren.
> You missed the crux of quite a few important points that Nick tried to
> explain to you.
Indeed, I have carefully read his post. He certainly explains some
important points related with sshd. He is certainly right.
In message <[EMAIL PROTECTED]>, Stuart Henderson writes:
> On 2006/11/23 17:07, Igor Sobrado wrote:
> ...
> > to set up a firewall with an ever-growing list of hostile machines.
> ...
>
> I think you misunderstand me. I mean to restrict direct SSH access
> to only th
In message <[EMAIL PROTECTED]>, Steve Williams writes:
>
> I block brute force attacks using PF. They get a small set of attempts
> before they are blocked. Very trivial.
>
> pass in on $ext_if proto tcp to $ext_if port ssh flags S/SA \
> keep state (max-src-conn-rate 5/40, overload )
In message <[EMAIL PROTECTED]>, chefren writes:
> On 11/23/06 6:35 PM, Igor Sobrado wrote:
>
> > Participate on flamewars is usually not my
> > style and I have certainly more productive ways to waste my time
> > and patience.
>
> Probably not with computer s
In message <[EMAIL PROTECTED]>, Nick Holland writes:
> Igor Sobrado wrote:
> > Hi again.
> >
> > Out of this thread, Mr. Tongson pointed me to an interesting post
> > from march 2005:
> >
> > http://archives.neohapsis.com/archives/openbsd/2005-
In message <[EMAIL PROTECTED]>, Darrin Chandler writes:
> On Thu, Nov 23, 2006 at 12:24:38PM +0100, Igor Sobrado wrote:
> > First of all, I understand that remote root logins can be easily
> > avoided by setting "PermitRootLogin" to "no" in /etc/ssh/ssh
In message <[EMAIL PROTECTED]>, Stuart Henderson writes:
> On 2006/11/23 15:14, Igor Sobrado wrote:
> > 2. There are a lot of brute force attacks from countries like
> > Korea these days. These attacks will be less effective if
> > the intruders get access
Hi again.
Out of this thread, Mr. Tongson pointed me to an interesting post
from march 2005:
http://archives.neohapsis.com/archives/openbsd/2005-03/2808.html
>From this post, it is difficult understanding why disabling remote
root logins is not a good idea; but after reading the entire thread
In message <[EMAIL PROTECTED]>, Anton Karpov writes:
> I'm neither OpenBSD nor an OpenSSH developer, but I think, the main idea of
> enabling root by default in OpenBSD is... protection from weak passwords!
> Just look at this. When you're installing OpenBSD, systems asks for a root
> password. You
Hi again!
I have a question on the default behaviour of OpenSSH. Please, do not
understand that I am complaining on it or trying to change its behaviour
in relation with remote root logins allowed by default on OpenSSH (but
I certainly believe it would be nice, that is the reason I write this
mes
In message <[EMAIL PROTECTED]>, Marc Balmer writes:
>
> This is OpenBSD. We install all configuration files below /etc. Other
> operating systems may use different locations, but here we use /etc.
Indeed, I have just found this behaviour explained on section 15 of the
OpenBSD FAQ. I was writin
Hi Gustavo.
Sorry to know that you have these problems with your soekris.
It is certainly an unusual scenario. I have a net4801 here too
and pxebooting it is very easy and... very fast.
I would suggest looking for the throughput problem on the network
itself. Your network does not look congeste
Hello.
I have just installed OpenBSD 4.0 on my desktop system, but were running
this excellent version of OpenBSD on my soekris for a month or so. As a
difference with the installation on the net4801, my desktop has X.Org,
OpenMotif and Mozilla Firefox:
$ pkg_info
atk-1.10.3p1accessibili
Thanks a lot to all that replied either in private email (Francisco),
or in the misc mailing list (Joachim, Robert, Will, Stuart, Peter,
Damian, Marc and Matthias).
I will try to reply to all in the thread right now. As I am not
a member of this mailing list I have not received a copy of the
emai
Hello.
I have some questions related with the layout of the filesystems
on OpenBSD and hope someone will be able to help me. I must start
saying that I never had problems with this setup, but I certainly
would appreciate some advice on it. To make things clear, I will
try to outline the output o
Thanks to all who answered to my question.
I will not submit the patch then. I agree with all the people that
answered to my question, we must provide man pages easy to read for
first time users but, as Theo said, "man -k" can certainly help.
Even if someone does not know how reading the manual p
Hello,
Can I suggest adding atalk(4), inet6(4), ipsec(4), pf(4), pflog(4),
eon(5), hostapd(8), and tcpdump(8) to the "SEE ALSO" section of
ifconfig(8)? I think that, as these manual pages are being cited
in the ifconfig(8) manual page, they should be added to this section.
Just want to check the
In message <[EMAIL PROTECTED]>, Pedro Martelletto writes:
> On Wed, Sep 06, 2006 at 09:53:43AM +0200, Igor Sobrado wrote:
> > but certainly diverging disklabels can explain the problem I outlined
> > in the first message to this thread
>
> Uh, yes, maybe. I didn'
Ops! I did not added the "-group" switch to repl(1)!!!
Sorry, this message should be directed to the mailing list too.
--- Forwarded Message
Date:Wed, 06 Sep 2006 16:09:18 +0200
From:Igor Sobrado <[EMAIL PROTECTED]>
To: Pedro Martelletto <[EMAIL PROT
In message <[EMAIL PROTECTED]>, Pedro Martelletto writes:
> On Tue, Sep 05, 2006 at 07:24:55PM +0200, Igor Sobrado wrote:
> > Indeed, it is a BSD disklabel related problem not a ffs's one.
>
> It *is* a FFS problem. The superblocks are different.
The BSD disklabel pro
In message <[EMAIL PROTECTED]>, viq writes:
> On Tuesday 05 September 2006 19:24, Igor Sobrado wrote:
> >
> > Thanks a lot for the excellent reference you provided in your email.
> > Indeed, it is a BSD disklabel related problem not a ffs's one. And
> > it se
Hi viq!
Sorry, I have read your message right now (...I am not subscribed to
this mailing list, I was looking at MARC as it seems the most up to
date archive, and found your answer.)
Thanks a lot for the excellent reference you provided in your email.
Indeed, it is a BSD disklabel related problem
In message <[EMAIL PROTECTED]>, Jeff Quast writes:
> On 9/5/06, Igor Sobrado <[EMAIL PROTECTED]> wrote:
> > Hello!
> >
> > I am trying to understand an odd behaviour in the Berkeley Fast File
> > System as implemented in both NetBSD and OpenBSD. My mai
Hello!
I am trying to understand an odd behaviour in the Berkeley Fast File
System as implemented in both NetBSD and OpenBSD. My main concern
is not getting a workaround for this problem (hopefully, I found one)
but understanding if there are hidden issues than can damage files
stored in these sh
97 matches
Mail list logo
