> > So far, I haven't seen anyone in this thread seriously
> > argue against either of these points.
>
> I'll seriously argue against the 2nd point above. I don't know of a
> SINGLE person that uses /bin/sh as their interactive shell when
> multi-user. Not ONE. Every Bourne shell'ish user I've
I'm afraid I don't understand the fix... and how it
seems to affect the historical behaviour of srand()/rand().
How does it address the understanding that if I use
srand(28), I will get exactly the same sequence of
numbers srand(28) produced yesterday, last week,
last year?
I have worked with pr
Greg Lehey <[EMAIL PROTECTED]> wrote:
> It has
> three file systems, one of which came up dirty. fsck -y reported
> thousands of errors, and when it was finished, my home directory and
> some other files were gone, and all the subdirectories of my home
> directory were in lost+found, a total of 1.
Harti Brandt <[EMAIL PROTECTED]> wrote:
>
> Yes, of course, but one would assume it to work (I suppose there is a
> large amount of code that assumes it will work).
Not a safe assumption at all. For example, what if the alignment
requirements for `short' and `int' are different (as they frequ
Harti Brandt <[EMAIL PROTECTED]> wrote:
>
>
> Hmm, I though the following would work:
>
> void
> foo(unsigned short *s)
> {
> unsigned short temp;
>
> temp = s[0];
> s[0] = s[1];
> s[1] = temp;
> }
>
> main()
> {
> int i = 0x12345678;
>
> foo(&i);
> p
Harti Brandt <[EMAIL PROTECTED]> wrote:
>
> Well, I just had a long discussion with a collegue about the topic. The
> main problem is in the ISO-C standard, section 6.7 point 4 which states:
>
> All declarations in the same scope that refer to the same object or
> function shall specify compatibl
>
> For the source code below, compiling gcc -O2/-O3 seem to produce
> incorrect code.
>
> ---
> #include
> int main(int argc, char* argv[])
> {
> unsigned int x = 0x12345678;
> unsigned short tmp;
> printf("%x\n", x);
> tmp = ((unsigned short *)&x
Terry Lambert <[EMAIL PROTECTED]> wrote:
>
> Bruce Evans wrote:
> > Isn't this too old and security-holed to use? It stopped being packaged a
> > few releases ago. 4.5R has mainly:
> >
> > /usr/local/lib/netscape-linux/communicator-linux-4.79.bin: ELF 32-bit LSB
>executable, Intel 80386, vers
Terry Lambert <[EMAIL PROTECTED]> wrote:
>
> Martin Blapp wrote:
> > This looks ok to me. And like this we would only have to change one
> > file, Garrett is right.
>
> That's the first thing I said: "Garrett's right".
>
> David O'Brian had the point that there was a tools dependency that
> thi
"David O'Brien" <[EMAIL PROTECTED]> wrote:
>
> On Mon, Jun 17, 2002 at 06:16:45PM -0400, Garrett Wollman wrote:
> > <<[EMAIL PROTECTED]> said:
> >
> > > The correct approach (and, I have to admit to not
> > > glancing at your patch) would be:
> >
> > >#ifndef __cplusplus
> > >typedef
"Marc G. Fournier" <[EMAIL PROTECTED]> wrote:
> Morning all ...
>
> After getting nowhere with the Surecom EP-428X that I picked up, I
> went out today and grabbed one of the Linksys EC2T, figuring it's on the
> list of supported devices I found, and I think I'm s close ...
>
>
Terry Lambert <[EMAIL PROTECTED]> wrote:
> Thomas David Rivers wrote:
> > Well - it's not counter-intuitive on many machines... For example,
> > on the IBM mainframe - there is an instruction to load a character
> > into a register - but not one that loads
Terry Lambert <[EMAIL PROTECTED]> wrote:
>
> Bill Fenner wrote:
> > gcc 3.1 simply defaults to unsigned chars. 127 << 1 = 254; 254 / 2 = 127.
> >
> > My machine is too slow to test this expeditiously, but I'm trying
> > adding "#define DEFAULT_SIGNED_CHAR 1" into freebsd-native.h .
>
> I will
>
> I observed gcc 2.95.4 and gcc 3.1 interpret (or maybe optimize) the
> following code differently (CFLAGS=-O):
>
> int main(void)
> {
> unsigned char i = 127;
> printf("%d\n", ((char)(i << 1)) / 2);
> return 0;
> }
>
> gcc 2.95.4 says it's -1, whereas gcc 3.1 says it's 127. On FreeBSD
On Sun, 11 Feb 2001, Peter Wemm wrote:
> Matt Dillon wrote:
> >
> > :
> > : This is a major change to libc. The library maj must be bumped if you
> > : intend to change the sizeof(FILE), or every single third party applicatio
> n
> > : that uses stdio will break.
> > :
> > :
Alfred Perlstein <[EMAIL PROTECTED]> wrote:
>
> * Tony Johnson <[EMAIL PROTECTED]> [000927 18:26] wrote:
> > OK
> > Well Here is the issue. If I put in the 2 boot floppies I get a page fault
> > 12 after I press Q for "quit" on the visual kernel config. If I can save a
> > crash dump before any
Julian Elischer ([EMAIL PROTECTED]) wrote:
>
> Nik Clayton wrote:
> >
> > Hi guys,
> >
> > For those of you running VMWare (2) on -current, how fast do you expect it to
> > be?
> >
> > I'm running it quite successfully on a 750MHz PIII w/ 128MB RAM, and the
> > following disk controller / dis
>
> Hi,
> I have installed netscape4-navigator and I can't launch its.
> I've got following message:
>
> ld.so failed: Can't find shared library "libXt.so.6.0"
>
> What can I do?
> Piotr Wozniak
You need to install the XFree86 a.out library package. It's
in the packages directory from the 4
Just F.Y.I
I understand that, today, IBM is announcing it will open-source
AFS via the IBM Public Source license..
Some quotes I've seen:
"IBM announced today the open source contribution of a high-performance file
system technology and talent to strengthen collaboration in the enterpri
>
> What about doing the changes on a branch with the understanding that
> the branch will *replace* HEAD when it stabilises ?
>
> This sounds odd at first glance, but it means that others are forced
> to MFC into the smp branch - if they don't they lose.
>
> Anybody that's not confident to b
>
> Brad Knowles wrote:
> >
> > At 10:00 AM -0500 2000/5/2, Dan Nelson wrote:
> >
> > > .. means that a user that wanted to use FreeBSD in a commercial
> > > application would not be able to simply sell his product; he would have
> > > to get a license from Sleepycat.
> >
>
> I asked the K
Peter Jeremy <[EMAIL PROTECTED]> wrote:
>
> On 3/04, John Polstra wrote:
> [don't allocate big structs on kernel stack]
>
> Many years ago, I wrote a tool that analysed stack requirements by
> parsing the assembler output from the compiler. It determined the
> stack frame requirements and buil
>
> And here we are again.
>
> This time on another disk:
>
> dev = #amrd/0x20004, block = 2048, fs = /news/spool
> panic: ffs_blkfree: freeing free block
> Debugger("panic")
> Stopped at Debugger+0x35: movb$0,in_Debugger.372
> db> trace
> Debugger(c01e7ee3) at Debugger+0x35
> panic(c
> seems to work fine,
> except that now we don't have block devices any more
> so every time it gets stuff off disk, it's REALLY SLOW.
>
> I guess a virtual machine is the "App that no-one could put their finger
> on" that really could do with buffered (caching) devices.
Hmmm I wonder what
>
>Nawww... I've tried this on a bunch of different machines.. as a matter
> of fact it replicates with gcc version 2.7.2.1 from December of last
> year. I find it hard to believe that I have 80 machines that all
> exhibit the exact same memory failure... :-)
>
> -John
>
>
>
Yep - othe
>
> Hi,
>
>While I'm at it, a co-worker gave this one to me earlier today.
>
>cc: Internal compiler error: program cc1 got fatal signal 11
>
>4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Dec 20 01:45:25 EST 1999
>
>
>
> FreeBSD(root)/tmp %cc -v
> Using builtin specs.
> gcc version 2.
Adam Strohl <[EMAIL PROTECTED]> wrote:
> On Wed, 15 Dec 1999, Daniel C. Sobral wrote:
>
> > Hey, I like CUI. I'd rather install with a CUI than a GUI, all other
> > things being equal. And besides some quirks here and there, I really
> > like sysinstall.
>
> Its nice, but its not where it should
>
> One potential drawback is that it would probably bloat the
> syscons code slightly.
>
> - Donn
>
Uhh... "slightly"?
- Dave R. -
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
>
> In message <[EMAIL PROTECTED]> Julian
>Elischer writes:
> : more importantly we lost the aha driver for a while.
>
> No we didn't. Well, the aha driver did loose support for the 1542A
> cards, but the aha driver was done so that cam could be committed to
> the tree. Maybe you are confusin
>
> > Just how much code will break?
>
> Boehm-gc, maybe. Modula-3, maybe. I can't remember whether it
> catches both signals or just SIGBUS.
I believe electric-fence would change as well.
- Dave R. -
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current
Marc G. Fournier wrote:
> On Thu, 8 Apr 1999, Brian Handy wrote:
>
> > On 9 Apr 1999, Dag-Erling Smorgrav wrote:
> >
> > >> [4 people said "YES! Add g77!"]
> >
> > >I beg your pardon? You're adding g77 to the system because you know of
> > >four people who would find it useful? Where's the log
31 matches
Mail list logo
