My apologies if this is not the Right Place to raise this issue.
I just now submitted the following PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=174269
(Please ignore the small typo in the title. That should have been
"bsdinstall/partedit" not "basinstall/partedit".)
Anyway, I wanted to k
In message <20121208120658.4d115...@x220.ovitrap.com>,
Erich Dollansky wrote:
>Hi,
>
>On Fri, 07 Dec 2012 16:18:57 -0800
>"Ronald F. Guilmette" wrote:
>
>> If possibility (c) applies, then I would also like to know if anybody
>> has any suggestions
In message <20121209014547.238...@gmx.com>,
"Dieter BSD" wrote:
>But don't brag about high-end hardware. Â But FreeBSD has dropped support
>for even semi-high-end hardware (DEC Alpha). So I'm stuck running it on
>AMD64. Nothing against AMD, they did what they could to try and make a silk
>purse
In message <20121209091305.238...@gmx.com>,
"Dieter BSD" wrote:
>Ronald writes:
>> the last Alpha to be produced was shipped way back in 2004... eight years
>> ago... with a top speed of 1.3 GHz. Â I now have a cheap little media player
>> thingy sitting on my desk, and _each_ of its two cores
Apparently, I owe everyone an apology.
I found out (a bit too late) that the WD 1 TB "black" drive that had
come to me in sealed anti-static bag with a warning on it about
"Advanced Format" drives (and possible OS incompatability) was not
in fact itself an AF drive. Rather it is a traditional d
In message
Mark Saad wrote:
> I am wondering if anyone has seen this. I pulled down the 9.1-RELEASE
>install media...
That's very interesting. Where did you obtain that?
>From where I am sitting, the freebsd web site is still only offering
version 9.1-RC3.
__
In message
, Adrian Chadd wrote:
>On 12 December 2012 14:04, Ronald F. Guilmette wrote:
>> From where I am sitting, the freebsd web site is still only offering
>> version 9.1-RC3.
>
>The images have to be pushed out to ftp-master and over to the mirrors
>before the r
I have two Seagate ST380011A drives, both in the same single system.
On that system, I boot to the FreeBSD 9.1-RC3 LiveCD.
The resulting dmesg messages indicate the following regarding the two drives:
ada0 at ata0 bus 0 scbus2 target 0 lun 0
ada0: ATA-6 device
ada0: 100.000MB/s transfers (UDM
In message <20121215175447.310...@gmx.com>,
"Dieter BSD" wrote:
>...Some sysadmins want
>the MBR to be read-only for various reasons.
Apparently, at least one sizeable company headquartered in Redmond,
Washington does too. Can't imagine why. :-)
http://www.zdnet.com/linux-foundation-uefi-s
In message <1355691233.1198.126.ca...@revolution.hippie.lan>,
Ian Lepore wrote:
>On Sun, 2012-12-16 at 12:01 -0800, Ronald F. Guilmette wrote:
>> So, um, WTF? One ST380011A is 156299375 sectors big, and the other one
>> is 156301488 big.
>>
>> How exactly
In message
Adrian Chadd wrote:
>Wow, I didn't even know this existed!
My apologies for not replying sooner. It has been a hectic few days.
Anyway, yes, there are two kinds of "hidden" areas that may be present
on a hard drive, Host Protected Area (HPA) and then separately also
the Device Con
Could someone please take a look at this bug report (bin/176713) and
also at the simple patch that I provided to fix the problem?
This is quite a serious problem, and my PR has been pending with no
action since Wed, 6 Mar 2013.
Regards,
rfg
P.S. Please note that in reality, I do not believe
In message
=?ISO-8859-1?Q?Fernando_Apestegu=EDa?= wrote:
>It seems to work for me:
Good.
Just to make sure that we are clear, you are simply confirming what my
bug report (bin/176713) said, i.e. that _without_ my fix, nc can prematurely
truncate the output from some servers, whereas _with_ my
In message <20130721041338.2121.qm...@f5-external.bushwire.net>,
"Mark Delany" wrote:
>> servers running certain protocols. For example, the rules of the SMTP
>> protocol... just to name one... require that a client wait until the
>> server has sent out an initial greeting banner before the cl
In message
Adrian Chadd wrote:
>Wait a second. What's going on under the hood?
>
>You _should_ be able to shutdown the write side of the socket and have
>it not affect reading.
It has been some time now since I filed my PR but I think that the bottom
line is that you need to look at the code (
In message
=?ISO-8859-1?Q?Fernando_Apestegu=EDa?= wrote:
>Yes, that is what I tested. Behavior before (truncated output) and after
>(correct output) applying the patch.
OK, good. Thanks.
>If this is going to be the final version of the patch, i.e. if it is going
>to include the -q flag, then
In message
Adrian Chadd wrote:
> On 21 July 2013 19:02, Ronald F. Guilmette wrote:
>
>> It has been some time now since I filed my PR but I think that the bottom
>> line is that you need to look at the code (of nc) to understand how it is
>> reacting to EOF on st
In message
Adrian Chadd wrote:
>Right. Yes, I had a typo. I meant that it shouldn't die on seeing a
>read EOF after closing the write side of the socket.
>
>So, what you're saying is:
>
>* nc sees EOF on stdin
Yes.
>* nc decides to abort before seeing the rest of the data come in from
>the re
In message
Adrian Chadd wrote:
>Right, and your patch just stops the shutdown(), right?
The shutdown that occurs when EOF is encountered on stdin, yes.
>Rather than
>teaching nc to correctly check BOTH socket states before deciding to
>close things.
In effect, nc *is* currently "checking bot
In message
, you wrote:
>Hi,
>
>Well, I've done this before. More than once. I'm glad that you've
>stuck through helping me understand what nc is doing; I'm
>unfortunately busy doing other things
>
>What you end up doing is:
>
>* tracking the state of the two sockets, both for read EOF and write
In message <1375112533.45247.43.ca...@revolution.hippie.lan>,
Ian Lepore wrote:
>I don't think this accurately summarizes things...
Everyone is entitled to her or her own opinion.
Unfortunately, due to other pressing matters I will no longer be able
to be an active participant in this debate.
It appears to me that the gdb 4.18 port on FreeBSD 3.3 doesn't provide
support for ELF shared libraries.
Am I correct about that, or did I just snag myself on some obscure gdb
bug that was masquerading as ELF shared library non-support?
Anyway, assuming that my supposition is correct, and that
In message <[EMAIL PROTECTED]>, you wrote
:
>How can syscalls be disassembled on BSD?
>
>So far, I tried using ktrace -tc on compiled code using the syscall I
>wanted, but the output from kdump doesn't look like asm. I also tried
>using gdb directly, compiling the source with the -g and -static
In message <[EMAIL PROTECTED]>, you wrote
:
>On FreeBSD 2.2.5 (I know I should change, but it works), gcc 2.7.2.1, gdb
>4.16, typing 'disassemble syscall_as_seen_in_main' I get:
>No function contains specified address.
What the heck is "syscall_as_seen_in_main"?
(Sorry if I'm ignorant, but I h
In message <[EMAIL PROTECTED]>, you wrot
e:
>Hi everyone...
>
>First of all I would like to state that IM not a programmer.
Then you're probably not a `hacker' either.
>Im trying to compile a program and IM getting a errormessage, I have
>included the error message bellow.
>
>viking# cc emsg1.
In message <[EMAIL PROTECTED]>, you wrote:
>Hi,
>
>I posted this on -questions about five days ago and haven't received
>any hints or suggestions. Does anyone here have any ideas?
>
>I use natd and a 56k phone connection to my ISP so that all my
>computers can share one line.
>
>This all works
In message <[EMAIL PROTECTED]>,
Matthew Dillon <[EMAIL PROTECTED]> wrote:
>
>:Has anyone toyed with the idea of implementing a swap-based filesystem
>:similar to Sun's tmpfs?
>:
>:Chuck Youse
>
>I did it a couple of months ago. You simply use the VN device and
>tell it to use swap as b
In message <[EMAIL PROTECTED]>,
Matthew Dillon <[EMAIL PROTECTED]> wrote:
>Mail queue files are persistant enough (upwards of 5 days if a destination
>is down) that you run a real risk of losing something important if
>you crash and wipe. I would not use MFS at all and I would on
In message <[EMAIL PROTECTED]>,
Matthew Dillon <[EMAIL PROTECTED]> wrote:
>So, I think it *IS* possible to make FreeBSD sufficiently bug-free that
>people become 'surprised' when they are able to crash a box running it.
FYI - Part of the reason that _I_ jumped onto the FreeBSD bandwago
My apologies for posting this digression from the usual weighty
matters that are discussed here on -hackers, but I'm really in
a tizzy about this.
Going through my waiting mail this morning (on my personal desktop
system named `segfault.monkeys.com') I found the following message
from the nightl
In message <[EMAIL PROTECTED]>, you
wrote:
>See src/sys/ufs/ffs/README.softupdates, which tells you what you need to get
>them to work
Thank you. I'll definitely be looking at that.
P.S. The other reference you gave:
>http://www.ece.cmu.edu/~ganger/CSE-TR-254-95/
seem to no longer be usef
In message <[EMAIL PROTECTED]>,
Bill Fumerola <[EMAIL PROTECTED]> wrote:
>On Sun, 5 Dec 1999, Ronald F. Guilmette wrote:
>
>> The controller is an AHA-2940U (not wide). The da0 disk is a Quantum
>> Viking 4.5GB SCSI. I have never had any problem with this drive
In message <[EMAIL PROTECTED]>,
"Jordan K. Hubbard" <[EMAIL PROTECTED]> wrote:
>> "... even though I used it on Linux for several months."
>>
>> I read that as meaning "the drive worked despite the fact that it was on
>> Linux".
>
>Well, just to inject a note of reality into this discussion:
>
In message <[EMAIL PROTECTED]>,
Kelly Yancey <[EMAIL PROTECTED]> wrote:
>>
>>3b) Examination of the drive(s) in question for any cooling or
>>mounting deficiencies. Depending on the SCSI errors in question,
>>I might even investigate firmware updates for the drive(s).
>>
In message <[EMAIL PROTECTED]>,
Nick Rogness <[EMAIL PROTECTED]> wrote:
>On Sun, 5 Dec 1999, Archie Cobbs wrote:
>
>> Brian Dean writes:
>> > No dropped packets, but definitely some occasional long delays before
>> > I get the echo. However, I must concede, based on other respondants,
>> > tha
In message <[EMAIL PROTECTED]>,
Martin Hinner <[EMAIL PROTECTED]> wrote:
>Anyway, frankly, I don't think this document would be relevant to
>FreeBSD. Perhaps I'm missing something... what would be the purpose
>of having it?
My two cents:
I happen to think that the HOWTO- system of Linux is ma
The sa(4) man page describes the semantics of the low-order two bits
of the minor device numbers for SCSI tape devices.
Can anyone tell me what the semantics of the next two higher bits of the
minor device number are?
# ls -l /dev/*sa*
crw-rw 2 root operator 14, 2 Oct 25 19:41 /dev/e
In message <[EMAIL PROTECTED]>, you wrot
e:
>> Can anyone interpret this for me:
>>
>> HARDWARE FAILURE asc:0,4
>>
>> What does it mean?
>>
>> It this just the numeric code for ``Buy another tape drive''?
>> :-)
>
>Yes.
Thank you.
P.S. Power cycling _just_ the tape drive seems to have
In message <[EMAIL PROTECTED]>, you wrote:
>What's the practical number of TCP connections per server?
I've gotten over 8,000 at one time on one FreeBSD box.
>Is there an easy guideline for how {much} ram the kernel will be taking per
>connection/route/socket/fd/etc?
Not that I am aware of.
In message <[EMAIL PROTECTED]>, you wrote:
>Speaking of accepting... What's the upper limit on listen queues? Something
>around 64, correct?
I don't know, but why do you ask? Do you have some reason to believe that
the length of listen queues is going to be an issue?
>> Quite a lot of memory
In message <[EMAIL PROTECTED]>,
you wrote:
>
>
>On Sat, 18 Dec 1999, Ronald F. Guilmette wrote:
>
>> # Increase the max # of open sockets, systemwide (use only on older kernels)
>> #/sbin/sysctl -w kern.somaxconn=16384
>
>Regarding the comment, "use
In message <[EMAIL PROTECTED]>,
Alfred Perlstein <[EMAIL PROTECTED]> wrote:
>On Sat, 18 Dec 1999, Kevin Day wrote:
>
>> > The _clean_ way of doing it would be to write your multi-user server using
>> > threads, and to assign one thread to each connection. If you can do that,
>> > then the logic
In message <[EMAIL PROTECTED]>,
Ken Bolingbroke <[EMAIL PROTECTED]> wrote:
>> If you would like to see an example of a very simple multi-connection server
>> that runs as a single process (written in C) as described above, let me know
>.
>
>I'd be very interested in seeing this, if you could po
In message <[EMAIL PROTECTED]>,
David Scheidt <[EMAIL PROTECTED]> wrote:
>On Sat, 18 Dec 1999, Ronald F. Guilmette wrote:
>
>>
>> In a nutshell, teergrubing is the name that has been given to a simple
>> technique that exploits a small but significant k
In message <[EMAIL PROTECTED]>,
"Daniel C. Sobral" <[EMAIL PROTECTED]> wrote:
>"Ronald F. Guilmette" wrote:
>>
>> As I say, my understanding is that FreeBSD still doesn't have real and/or
>> complete thread support in the kernel. So
In message <[EMAIL PROTECTED]>,
John Polstra <[EMAIL PROTECTED]> wrote:
>In article <[EMAIL PROTECTED]>, Daniel C. Sobral
><[EMAIL PROTECTED]> wrote:
>
>> "Ronald F. Guilmette" wrote:
>>
>> > As I say, my understanding is that Fre
In message <[EMAIL PROTECTED]>,
"Richard Seaman, Jr." <[EMAIL PROTECTED]> wrote:
>> I would really be very grateful however if _someone_ would explain to me
>> the actual low level-mechanics of how this works, i.e. how one thread in
>> a ``multi-userland-thread'' process can manage to get contr
In message <[EMAIL PROTECTED]>,
Matthew Dillon <[EMAIL PROTECTED]> wrote:
>:I'd like to just take a second and re-express my growing confusion on
>:this whole topic.
>:
>:Why do you say that this complete-process-blocking effect only takes
>:place in the case of disk reads?? Isn't a read a rea
In message <[EMAIL PROTECTED]>,
"Richard Seaman, Jr." <[EMAIL PROTECTED]> wrote:
>On Sun, Dec 19, 1999 at 01:21:15PM -0800, Ronald F. Guilmette wrote:
>
>> It sounds to me like each and every time there is a thread context switch,
>> some code in th
In message <[EMAIL PROTECTED]>, you wrote:
>
>
>On Thu, 23 Dec 1999 17:14:55 GMT, David Malone wrote:
>
>> Try adding a fpsetmask(fpgetmask()&(~FP_X_OFL)); before the calculation
>> and see what happens.
>
>It still bombs, although fpsetmask(0) does the trick. I'm really
>interested in hearing
In message <[EMAIL PROTECTED]>,
Kent Stewart <[EMAIL PROTECTED]> wrote:
>It also sounds like he isn't getting enough outside air. You can't
>cool if the inside air is hot.
Right!
I have bought three ``slot fans'' now for different systems I own, and I'm
very happy with them. Two I bought fro
In message <[EMAIL PROTECTED]>,
Markus Holmberg <[EMAIL PROTECTED]> wrote:
>IEEE Std 754-1985 (Section 7, paragraph 1) is:
>
>``The default response to an exception shall be to proceed
> without a trap.''
>
>(end quote)
>
>When checking with a simple C program and fpgetmask() I
In message <[EMAIL PROTECTED]>, you wrote:
>
>"Ronald F. Guilmette" <[EMAIL PROTECTED]> writes:
>
>> >Question 1: What is the reason for FreeBSD to differ from other platforms
>> >and not follow the IEEE standard by default?
>> >(Ple
In message <[EMAIL PROTECTED]>,
Ed Hall <[EMAIL PROTECTED]> wrote:
>: I have just upgraded my system to -current w/egcs 2.95.2 and I have
>: several problems with it, especially when using optimizations (-O2 and
>: such)
>
>Have you reported those problems to <[EMAIL PROTECTED]>? Bugs aren't
>
In message <[EMAIL PROTECTED]>,
Ed Hall <[EMAIL PROTECTED]> wrote:
>One of the issues with an alternative compiler is that you'll likely need
>to keep GCC and associated tools around anyway, for ports, kernels, and
>updates. Probably not a problem, but occasionally multiple tool chains
>can be
In message <[EMAIL PROTECTED]>,
Martin Cracauer <[EMAIL PROTECTED]> wrote:
>Hence it is good to trap this and it is a bug in Mozilla, period.
>...
>I think we might discuss lowing the traps so that the softer
>exceptions are disabled. But most cases where people cry about
>FreeBSD's behaviour a
I confess that I didn't look at the original Bugzilla bugreport on this
thing too closely, but...
In message <[EMAIL PROTECTED]>,
Martin Cracauer <[EMAIL PROTECTED]> wrote:
>> #define JSDOUBLE_IS_INT(d, i) (JSDOUBLE_IS_FINITE(d) && \
>> !JSDOUBLE_IS_NEGZERO(d) && ((d) == (i = (jsint)(d)))
In message <[EMAIL PROTECTED]>,
Martin Cracauer <[EMAIL PROTECTED]> wrote:
>In <[EMAIL PROTECTED]>, Ronald F. Guilmette wrote:
>> ...
>> I agree that it appears that the Mozilla code had a serious bug/flaw,
>> and that having the FP traps enabled
In message <[EMAIL PROTECTED]>,
Martin Cracauer <[EMAIL PROTECTED]> wrote:
>Others already said that replacing the system compiler will be
>difficult.
>
>However, you should be able to use any FreeBSD include file that is
>supposed to be used by userlevel code with any ANSI C conforming
>compi
In message <[EMAIL PROTECTED]>,
Martin Cracauer <[EMAIL PROTECTED]> wrote:
>In <[EMAIL PROTECTED]>, Gergely EGERVA
>RY wrote:
>
>> I have just upgraded my system to -current w/egcs 2.95.2 and I have
>> several problems with it, especially when using optimizations (-O2 and
>> such)
>
>When your
In message <[EMAIL PROTECTED]>, you wrote:
> I don't believe the C89 standard doesn't have a way to test for NaN...
That is correct, but most actual C libraries DO provide some function
that will check for that condition.
> ... so, if we're talking portability here - you can't test for NaN.
Y
In message <[EMAIL PROTECTED]>,
Martin Cracauer <[EMAIL PROTECTED]> wrote:
>In <[EMAIL PROTECTED]>, Ronald F. Guilmette wrote:
>> ...
>> Yes, the existing Mozilla code should be fixed to perform the range
>> check in the manner that Martin Cracauer
In message <[EMAIL PROTECTED]>, you wrote:
>> [3] The ANSI C standard, at least, contains the requirement that each
>> individual system include file specified by that standard should
>> be usable all by itself, without the programmer being required to
>> explicitly include any OTHER
In message <[EMAIL PROTECTED]>, you wrote:
>In the last episode (Jan 05), Ronald F. Guilmette said:
>> Martin Cracauer <[EMAIL PROTECTED]> wrote:
>> >
>> >When your code breaks when using -O2 or higher, don't do that, use
>> >just -O!
>&
In message <[EMAIL PROTECTED]>,
Martin Cracauer <[EMAIL PROTECTED]> wrote:
>... If you have examples where it breaks, send them to me, please.
Here is a list of a few system include file problems, in no particular
order. Most of these are ANSI conformance problems.
/usr/include/cam/cam.h:15
In message <[EMAIL PROTECTED]>,
Thomas David Rivers <[EMAIL PROTECTED]> wrote:
rfg> Here is a list of a few system include file problems, in no particular
rfg> order. Most of these are ANSI conformance problems.
rfg> ... {bugz elided} ...
> This begs a question and to help in my understan
In message <[EMAIL PROTECTED]>,
Thomas David Rivers <[EMAIL PROTECTED]> wrote:
>> But pragmatically, it sure would be nice if I (or you) as a programmer
>> developing stuff on FreeBSD could include various of the FreeBSD include
>> files into any program that we happen to be working on, and the
In message <[EMAIL PROTECTED]>, you wrote:
>But I'm not sure I understand the difference between "undefined" and
>"unspecified"? (What a cast from double to int should return when the source
>doesn't fit into the destination).
The C standard talks about "undefined behavior", and when it does, t
In message <[EMAIL PROTECTED]>,
Jim Shankland <[EMAIL PROTECTED]> wrote:
>By the way, I also struck out with DOS fdisk: it took one look
>at the garbage partition table, and wedged. I'll be trying a
>Linux rescue disk next. If that fails, too, then I seem to
>have generated a 1-Gigabyte hock
In message <[EMAIL PROTECTED]>,
James Howard <[EMAIL PROTECTED]> wrote:
>I was playing with a program written for Solaris to see if I could port it
>to FreeBSD (another learning experience thing;). The program uses
>Solaris's libelf to talk to Elf files. It does this quite extensively in
>fac
In message <[EMAIL PROTECTED]>, you wrote:
>On Fri, Jan 14, 2000, Ronald F. Guilmette wrote:
>> (I never asked what the letters B-F-D stood for. I always figured
>> that they had the obvious meaning. :-)
>
> BFD stands for Binary File Descriptor.
Oh sure.
A few weeks ago, I showed up here and was bitching about not being able
to send stuff out to my parallel printer.
I got a bit of heat for saying that I _could_ send data to the printer
from my other system (running Linux).
Well, I just wanted to say that all indications now are that the FreeBSD
My attention has just been called to:
http://immunix.org/StackGuard/mechanism.html
Given all of the buffer overrun vulnerabilities that have been found in
various network daemons over time, this seems like a worthwhile sort of
technique to apply when compiling, in particular, network daemons
73 matches
Mail list logo
