hi there,
just a small format correction.
cheers.
alex
Index: usr.bin/elf2aout/elf2aout.1
===
--- usr.bin/elf2aout/elf2aout.1 (revision 203786)
+++ usr.bin/elf2aout/elf2aout.1 (working copy)
@@ -24,7 +24,7 @@
.\"
.\" $FreeBSD$
.\"
owner-freebsd-hack...@freebsd.org wrote:
> Artem Belevich wrote:
>>> Seriously, simply because of curiosity - are MIPS CPUs used in any
>>> kind of "general purpose" machines?
>>
>> I'm not aware of any multi-core general-purpose MIPS box.
>> Low-end MIPS CPUs are ubiquitous in low-end networking
On Fri, Feb 12, 2010 at 02:32:44PM +0100, Alexander Best wrote:
> hi there,
>
> just a small format correction.
Committed to -CURRENT, except I didn't touch ".Dd" and fixed
usage() as well.
Cheers,
--
Ruslan Ermilov
r...@freebsd.org
FreeBSD committer
___
thanks. :)
Ruslan Ermilov schrieb am 2010-02-12:
> On Fri, Feb 12, 2010 at 02:32:44PM +0100, Alexander Best wrote:
> > hi there,
> > just a small format correction.
> Committed to -CURRENT, except I didn't touch ".Dd" and fixed
> usage() as well.
> Cheers,
_
On Thu, Feb 11, 2010 at 08:06, Andrew Brampton
wrote:
> On Thu, Feb 11, 2010 at 2:25 AM, james toy wrote:
>> Hello Hackers,
>>
>> I am working on learning to write FreeBSD drivers; however, I have
>> some practice writing IOKit drivers for MacOSX (they are entirely
>> different I know!). The
little patch to stop gcc from complaining about the implicit declaration of
isalnum().
although this file comes from vendor contributed software (gdtoa) the cause
for the warning is related to local freebsd specific changes in the file which
are not part of the original file shipped by the vendor.
* Rick Macklem (rmack...@uoguelph.ca) wrote:
> > Is it the hostname of the server or the client?
>
> My guess is that hades.panopticon (or something like that:-) is the
Yes, that is the client.
> As John said, it would be nice to try and narrow it down to client or
> server side, too.
I'm pla
* Oliver Fromme (o...@lurza.secnetix.de) wrote:
> This is an excerpt from Solaris' mount_nfs(1M) manpage:
>
> File systems that are mounted read-write or that con-
> tain executable files should always be mounted with
> the hard option. Applications using soft mounted file
>
On Thu, 11 Feb 2010, John Baldwin wrote:
[good stuff snipped]
Case1: single currupted block 3779CF88-3779 (12408 bytes).
Data in block is shifted 68 bytes up, loosing first 68 bytes are
filling last 68 bytes with garbage. Interestingly, among that garbage
is my hostname.
Is it the hostn
On Fri, 12 Feb 2010, Dmitry Marakasov wrote:
* Oliver Fromme (o...@lurza.secnetix.de) wrote:
This is an excerpt from Solaris' mount_nfs(1M) manpage:
File systems that are mounted read-write or that con-
tain executable files should always be mounted with
the hard option. Appl
Dmitry Marakasov wrote:
> * Oliver Fromme (o...@lurza.secnetix.de) wrote:
> > This is an excerpt from Solaris' mount_nfs(1M) manpage:
> >
> > File systems that are mounted read-write or that con-
> > tain executable files should always be mounted with
> > the hard option. A
On Thu, 11 Feb 2010, John Baldwin wrote:
Case1: single currupted block 3779CF88-3779 (12408 bytes).
Data in block is shifted 68 bytes up, loosing first 68 bytes are
filling last 68 bytes with garbage. Interestingly, among that garbage
is my hostname.
Is it the hostname of the server or
On Fri, 12 Feb 2010, Dmitry Marakasov wrote:
I'm planning a massive testing for this weekend, including removing
soft mount option and trying linux client/server.
Btw, I forgot to mention that I'm experiencing other NFS problems from
time to time, including "death" of a mount (that is, all p
* Oliver Fromme (o...@lurza.secnetix.de) wrote:
> I'm sorry for the confusion ... I do not think that it's
> the cause for your data corruption, in this particular
> case. I just mentioned the potential problems with "soft"
> mounts because it could cause additional problems for you.
> (And it's
On Fri, 12 Feb 2010, Dmitry Marakasov wrote:
Interesting, I'll try disabling it. However now I really wonder why
is such dangerous option available (given it's the cause) at all,
especially without a notice. Silent data corruption is possibly the
worst thing to happen ever.
I doubt that th
Dmitry Marakasov wrote:
> Oh, then I really misunderstood. If the curruption implied is
> like when you copy a file via NFS and the net goes down, and in
> case of soft mount you have half of a file (read: corruption), while
> with hard mount the copy process will finish when the net is back u
On Fri, 12 Feb 2010, Dmitry Marakasov wrote:
* Oliver Fromme (o...@lurza.secnetix.de) wrote:
I'm sorry for the confusion ... I do not think that it's
the cause for your data corruption, in this particular
case. I just mentioned the potential problems with "soft"
mounts because it could cau
--- On Fri, 2/12/10, Rick Macklem wrote:
> From: Rick Macklem
> Subject: Re: NFS write corruption on 8.0-RELEASE
> To: "Dmitry Marakasov"
> Cc: freebsd-hackers@freebsd.org, freebsd-sta...@freebsd.org, "John Baldwin"
>
> Date: Friday, February 12, 2010, 11:12 AM
>
>
> On Fri, 12 Feb 2010,
18 matches
Mail list logo
