(Just testing after hub was upgraded)
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
ces. I hope you can give me some pointers,
but if not don't worry. Thanks for taking the time to read this.
Peter
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
to stop it
or is it a bug in the USB source for FreeBSD, or just me. Mostly
intrested in the status of this.
Im running FreeBSD 5.1 release #0 with Generic kernel.
Motherboard: Abit KD7
CPU: AMD Baraton
Keyboard: Logitech cordless comfort
With regards
Peter
its my keyboard that is out of sync
with the USB spec since it will add letters when I write like .
"This should read like this" but can end up like "Thisi should reaed
likek this"
Thanks
Peter
- Original Message -
From: "Andre Guibert de Bruet" <[EMAI
rks though.
So I think the letter problem was due to my CNet USB 4 way hub. And I
dont know why am unable to use the keyboard pluged into the USB port
when I install FreeBSD 5.1 but it works when I install FreeBSD 4.8.
Thanks for the help and comments on this. :)
Peter
- Original Mess
Was to quick there, the problem with the letters still exist. But when
I run it with the convertet it works.
Peter
- Original Message -
From: "Peter" <[EMAIL PROTECTED]>
To: "Andre Guibert de Bruet" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Se
in FreeBSDs USB support.
C) A and B in combination.
Or im totaly wrong :) and that happens from time to time.
I hope this info helps.
Peter
- Original Message -
From: "Doug White" <[EMAIL PROTECTED]>
To: "Peter" <[EMAIL PROTECTED]>
Cc: "Andre Guiber
Hi
I receive signals 4, 10, and 11 during my buildworlds. Just put in
another PSU: same problem. Checking memory next...
Christoph Kukulies wrote:
I tried to sync my source tree and build the world. Yesterday
world build failed. Today it seemd to get further but still failed
with signal 4 (SIG
.
During install, in the 'Add Users' part, why is it able to add the new
user 'peter' to a new group 'peter' [the default option], but when I try
to put user 'peter' into a more generic new group 'admin' it says group
does not exist - I fig
cted 'No free space left on device'.
Both times the installer showed 221GB for /data, but one time it still had
907MB left to create a fifth partition - So it rounds down the 221.9GB to
221GB giving a false impression the disk is 100% full.
and yes, when I delete 'p2' and m
Doing a fresh install of 9.0RC2 [amd64].
Add User Accounts -> Yes
[stuff between '*' is my input/answers]
Username: *peter*
Full name: *P*
UID: [default]
Login group [peter]: *admin*
Group admin does not exist!
Login group [peter]: *ENTER*
Login group is peter. Invite peter into
x27; that will overwrite changes made in 'shell' ?
How about adding that option into the last 'Complete' dialog where the
configs are all written and are safe to edit and have three options:
?
]Peter[
Just a complain...errr...tester.
__
est/test.tbz:
File unavailable (e.g., file not found, no access)
pkg_add: unable to fetch
'ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.0-release/Latest/test.tbz'
by URL
]Peter[
___
freebsd-current@freebsd.org mailing list
http://li
> On Thu, Jan 5, 2012 at 2:12 PM, Peter wrote:
>> Hello,
>> Installed 9-RELEASE amd64, svn the latest stable/9 sources,
>> built/installed kernel/world and did pkg_add - It is still by default
>> pointing at -current:
>>
>> pkbsdpkg:#uname -a
>> Free
er, it would make backporting drivers from -current to 3.x a bit of a
problem..
> Bruce
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ating the database...
Read from remote host beast: Operation timed out
Connection to beast closed.
I'll look into this more shortly...
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
, I just don't understand the clustering
well enough yet to fix it.
Speaking of SMP and simple locks, I'd like to turn on the debugging
simplelocks that keep a reference count and check before switching to make
sure that a process doesn't sleep holding a lock. This is a pretty
funda
s the simplelock so that it can sleep
if required etc. The actual implementation of the simplelock routines
is interrupt safe (and has to be).
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Doug Rabson wrote:
> On Sun, 27 Jun 1999, Peter Wemm wrote:
>
> > Matthew Dillon wrote:
> > > Ah, yes, some of us were just discussing this in a small mailing list
.
> > > Hopefully Kirk will pick up on it soon. Ah well.. someone else gets
to b
&g
Doug Rabson wrote:
> On Sun, 27 Jun 1999, Peter Wemm wrote:
>
> > Doug Rabson wrote:
> > > On Sun, 27 Jun 1999, Peter Wemm wrote:
> > >
> > > > Matthew Dillon wrote:
> > > > > Ah, yes, some of us were just discussing this in a small
if (lkp->lk_lockholder != pid &&
> > lkp->lk_lockholder != LK_KERNPROC) /* FALSE */
> > panic("lockmgr: pid %d, not %s %d unlocking
",
> > pid, "ex
it, rather then simply trying to get it ),
> but with the new locks. I do not have time today to do this but I believ
e
> I have given sufficient information for Peter, Kirk, or Alan to make the
> fix.
Actually, I think there is another set if missing BUF_KERNPROC() call
your system swap, netscape will be it. I *think* I fixed
that particular problem in swap_pager about an hour or so ago. The
cluster_wbuild() problem is still lurking though, best advice is to
backtrack a bit.
> Thanks,
>
> Doug
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROT
gument to #10 contains
sys/buf.h:261,
which is just BUF_LOCK.
By the way, can anybody point me to documentation for ddb?
Regards,
--
Peter Holm | mailto:[EMAIL PROTECTED] | http://login.dknet.dk/~pho/
-[ Member of the BSD-Dk User Group / http://www.bsd-dk.dk/ ] -
To Unsubscribe: send mail t
Peter Holm wrote:
> >
> > Date: Mon, 28 Jun 1999 17:22:22 -0400 (EDT)
> > From: Kenneth Wayne Culver <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> >
> >
> > Just to let someone know... I recently (a couple of hours ago) have been
> > having
ge_queues[m->queue].pl is invalid or the tailq corrupt
or something evil along those lines. Or, m->queue is bogus and causing
an out of bounds array lookup. Hmm, do a show registers and record %eax
at this point too.
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ult from a "show registers" (I *realy* do need to
get a null modem cable).
Best regards,
--
Peter Holm | mailto:[EMAIL PROTECTED] | http://login.dknet.dk/~pho/
-[ Member of the BSD-Dk User Group / http://www.bsd-dk.dk/ ] -
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "un
ged some months ago that might have caused this? Is
there a way to have a complete & quiet suspend again?
Thanks in advance,
--
Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know
[EMAIL PROTECTED] | the Netherlands| what I&
k is that 3.x kernels and libraries have
syscalls that do not exist in 2.x and you'll get SIGSYS's etc.
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
he related problems with CURRENT
?
>
> My problems are gone. But I'm not running SMP.
The main place I expect there to be trouble with is the swap-backed-vn device
code. It does it's own clustering, aync/async-aware IO chaining, etc.
> Greg
Cheers,
-Peter
To Unsubscrib
crew things up for fun, but
we're only human. We do try and keep it in fairly good condition
(remember, the developers depend on it working for development), but
mistakes happen..
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Matthew Dillon wrote:
> :This doesn't mean it's OK for committers to screw things up for fun, but
> :we're only human. We do try and keep it in fairly good condition
> :(remember, the developers depend on it working for development), but
> :mistakes happen..
> :
>
ntainer should be
a consideration but isn't a huge deal since it is quite easy to back a
commit out...
Anyway, That's my 2 cents worth on the subject. :-)
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
read the upages from via the procfs
'mem' file.
0xbfbe through 0xbfff are the page tables, page directories etc.
0xc000 onwards is kernel space.
You can also get info from the map file in procfs:
Format: start, end, resident, private resident, vm object, access, refcnt,
shadowco
0x30(%eax),%eax
db>
--
Peter Holm | mailto:[EMAIL PROTECTED] | http://login.dknet.dk/~pho/
-[ Member of the BSD-Dk User Group / http://www.bsd-dk.dk/ ] -
*** src/sys/kern/kern_fork.c~ Sat Jul 3 21:15:58 1999
--- src/sys/kern/kern_fork.cSat Jul 3 21:54:18 1999
***
Peter Holm wrote:
> I don't know is this is of any interest, but a rfork(0) will cause a
> fault. I have included a patch.
Argh!
Thanks, Committed.. (rev 1.63 kern_fork.c)
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current&quo
ey use different ccbs, different backend-specific hooks, etc.
Things like umass, vpo etc have it easy since they basically bulk send the
scsi ccb's to the device as they use the scsi protocol directly. The ATAPI
protocol is similar but would require translation if it used the common top
end drivers. So, it either requires different top end drivers or has to do
translation.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
g is that this is handled in the bus configuration
system already. The driver only has to ask for the handle and tags for the
resource it's activated and can then use that directly for the bus_space
calls.
But, old style drivers don't have access to that as the information is
not avail
en the READDIRPLUS op generates
an oversized reply and it triggers the sanity check.
Change it to 16K and I think it'll work. Otherwise change the panic to a
printf(), but that is sweeping the problem under the carpet and might just
give the client indigestion. It does stop the server cra
Alfred Perlstein wrote:
> On Wed, 7 Jul 1999, Peter Wemm wrote:
>
> > Alfred Perlstein wrote:
> > >
> > > I just cvsup'd today hoping that all the NFS fixes that went in
> > > recently would have alleviated (sp?) the hangs I've been getting
7; by not accessing data through the approved
mechanisms) will lead to fairly obscure panics (the address is
perfectly valid - it's just the wrong segment).
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
directories? Does it consume a whole page or does it do something smarter?
Or does the ubc work apply to read/write only and the filesystem itself
continues to use the buffer cache interfaces for metadata and directories
still? Does the caching part of the bio system still exist?
Cheers,
-Peter
Rabson and
the rest of the Alpha porting crew will have found a lot of these, but
locating race conditions by waiting for them to occur is not the best
solution.
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Doug Rabson wrote:
> On Mon, 12 Jul 1999, Peter Jeremy wrote:
>
> > Mike Haertel <[EMAIL PROTECTED]> wrote:
> > >Um. FYI on x86, even if the compiler generates the RMW
> > >form "addl $1, foo", it's not atomic. If you want it to
> &
exit(1);
@@ -131,7 +199,7 @@
usec = tv2.tv_usec + 100 - tv1.tv_usec + (tv2.tv_sec - tv1.tv_sec - 1) *
100;
- printf("mode %d\t%6.2f ns/loop nproc=%d lcks=%s\n", m, (double)usec * 1000.0 /
(double)LOOPS / (double)nproc, nproc, lcks);
+ printf("mode %2d\t%6.2f ns/loop nproc=%d lcks=%s\n", m, (double)usec * 1000.0
+/ (double)LOOPS / (double)nproc, nproc, lcks);
}
return(0);
}
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
aluable silicon on trying to make
them more efficient (at least as seen by the executing CPU).
[2] Function calls _are_ fairly common, therefore it probably is
worthwhile expending some effort in optimising them - and the
stack updates associated with a leaf subroutine are fairly
easy
would be allowable (and whether the associated silicon
could be justified) for the IA-32.
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
oo much faster - which suggests that the relative costs should stay
fairly similar. At least for a well-designed architecture...
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ficult test cases are
obtained from number-theoretic algorithms developed by Turing Award winner
Prof. W. Kahan, Department of Electrical Engineering and Computer Science,
University of California, Berkeley, as part of ongoing research into test
methods for computer arithmetic.
Peter
To Unsubscribe
making entry and return two or three times faster then
>subroutine calls that make other subroutine calls.
I seem to recall reading somewhere that leaf subroutine performance
is also fairly important for overall performance (though that may
have been before C-compilers learnt how to in-line
thing more recent than
a 386 is fairly expensive. Since the 486 book states `1 clock', but
a real example takes more like 20 clocks, it seems that external
factors outweigh the stated execution timings.
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curre
"Brian F. Feldman" <[EMAIL PROTECTED]> wrote:
>On Tue, 13 Jul 1999, Peter Jeremy wrote:
>> Anyone interested in working on FP emulation (or checking the
>> shortcuts DEC made when then designed the Alpha) might like to
>> check out <http://www
(core/bus cycles) were: 486DX2: 20/10, Pentium: 28/7,
P-II: 34/8.5, P-III 34/7.5.
I suspect that these timings are a combination of inefficient on-chip
implementation of the lock prefix (see above for my reasoning behind
this), together with poor off-chip handling of locked cycles.
Peter
To Unsub
nerally doesn't show up until
run-time - when the results aren't what you expected).
Note that the GNU newlib defines `iprintf()' (and family) as an
integer-only printf() to avoid pulling in all the FP overhead when
it's not really needed.
Peter
To Unsubscribe: send mail to [E
g but only this
one seems
to guaranty recovery.
I have included my changes.
Regards,
--
Peter Holm | mailto:[EMAIL PROTECTED] | http://login.dknet.dk/~pho/
-[ Member of the BSD-Dk User Group / http://www.bsd-dk.dk/ ] -
*** sys/vm/vm_pageout.c~Sun Jul 4 13:53:49 1999
--- sys/vm/vm_pag
TCP SACK issues
http://www.iet.unipi.it/~luigi/sack.html # TCP SACK implementation
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
fully mmap()
a region (the actual parameters were PROT_READ, MAP_SHARED), I should be
able to read the mmap'd region.
Unfortunately, I don't understand the filesystem/vnode layering well
enough to be able to easily identify what's missing.
Peter
To Unsubscribe: send mail
e included from /usr/obj/3.0/cvs/src/tmp/usr/include/g++/new:9,
from
/3.0/cvs/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28:
/usr/obj/3.0/cvs/src/tmp/usr/include/g++/exception:9: syntax error before string
constant
*** Error code 1
Stop.
Peter
To Unsubscribe: se
"Scot W. Hetzel" <[EMAIL PROTECTED]> wrote:
>You'll also want to use:
>
>make world -DWANT_AOUT=YES
>
>to have the a.out libraries built.
You'll also need the a.out X11 libraries, and last time I tried,
they built OK, but wouldn't work.
Peter
n NT or
IRIX client to provoke it. I suspect a 32K mount from a freebsd box will do
it too but (at the time) didn't have one I could afford to crash test with,
and never got around to revisiting it.
I will have another look shortly. Anyway, the clue is that the server
readdirplus routine is the a
as about 680
bytes.
Having the client do a readdir() on a large directory is what triggers it.
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
"David O'Brien" <[EMAIL PROTECTED]> wrote:
>> from
>/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28:
>> /usr/obj/usr/src/tmp/usr/include/g++/exception:9: syntax error before string
>constant
>> *** Error code 1
>
>
>This is due to the Bison->Yacc change. I did b
Kirk seems to be out of touch :-), so I created PR kern/12869.
--
Peter Holm | mailto:[EMAIL PROTECTED] | http://login.dknet.dk/~pho/
-[ Member of the BSD-Dk User Group / http://www.bsd-dk.dk/ ] -
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in t
tion has any effect
on the generated code would take more time than I can justify right
now.
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
n95 for that matter) are doing to make it 100% quiet in suspend
mode? Then I could give it a try to have FreeBSD do the
same. Currently this prevents me from using FreeBSD alas.
Thanks,
--
Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know
[EMAIL PROTECTED] | the Netherlands| what I&#x
>> "MI" == Mitsuru IWASAKI <[EMAIL PROTECTED]> writes:
>> PAO has a small sleep in the apm driver, while -current didn't the
>> last time I looked.
MI> OK, I'll work on this.
MI> To Peter Mutsaers:
MI> Could you try
he problem is not an incomplete suspend, but no suspend at all. It
seems to suspend at first, the led starts flashing, the screen is
blanked, but somehow the computer keeps running.
--
Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know
[EMAIL PROTECTED] | the Netherlands| what I'm doi
argest range, but the lower layers might end up trying to allocate on
rids that the upper layers can't handle.
Cheers,
-Peter
diff -ru3 --exclude=CVS /home/peter/merge/isa/isa_common.c ./isa/isa_common.c
--- /home/peter/merge/isa/isa_common.c Tue Aug 10 20:17:51 1999
+++ ./isa/isa_common.c Sa
but when I hit a key, the console
says (slept 00:00:02) only, and programs in fact continued running
(thus it didn't go or remain in suspend mode at all).
Anyway thanks for you efforts so far.
--
Peter Mutsaers | Abcoude (Utrecht), | Trust me, I kno
ti@home, and it really continued while my computer was
'suspended'. Also a little test program continued running.
--
Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know
[EMAIL PROTECTED] | the Netherlands| what I'm doing.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
erted to revision 1.8.
Sorry for the inconvenience.
Regards,
--
Peter Holm
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ogram continued
>> running.
MS> What you're failing to offer here, and thus why I remain
MS> skeptical, is any evidence that suggests that these programs
MS> were "running" while the system believed itself to be
MS> suspended.
I can see that after
>> "MI" == Mitsuru IWASAKI <[EMAIL PROTECTED]> writes:
MI> Hi,
MI> I got ASUS P2B M/B & ATX case and assembled new box yesterday. With
MI> my patch, new box successfully transit into suspend state. There is
MI> no sounds from CPU fun, chassis fun and IDE HDD spin (powered down b
Followup: I decided to upgrade my P2B BIOS version. I had 1005, went
to 1010. This made a difference!
Now suspend works. However still the disks keep spinning until they
reach their BIOS timeout. In Linux & Windows, there is some hook when
going to suspend mode that spins down the (IDE) disks. Th
imeout or power-button
press.
If I use 'zzz', I have to do the known 'sleep 1; zzz' trick. This is
the difference.
Regards,
--
Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know
[EMAIL PROTECTED] | the Netherlands| what I'm doing.
---+---
-quietenings
If we do import GNU tar 1.13 (which I think is probably a good idea),
we need to make sure all the `invisible' fixes go in (if they're not
there already), as well as the additional options.
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Depending on the implementation, and the layout of struct
sysctl_oid, this could either be ~9.6K (appending both fields)
or ~4.8K (append the pathname pointer, put the 32-bit offset
field into some existing padding).
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
eing to current kernel source please? You need at least rev 1.3
of kern/kern_switch.c.
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I get a
> chance, I will try to look at it. If you want to have another look, the
> code at fault is probably in alpha/alpha/elf_machdep.c and you can get a
> list of relocations in the module with 'objdump --dynamic-reloc foo.ko'.
I thought of that before I went to sleep this
my source tree after cvsupping.
>
> There wasn't one. At least not here. I remember when egcs was imported
> it was the same thing.
Don't sweat, it's just been "un-deleted". David will be doing the transition
over the next week or so via several steps so we don&
nce to the movie web site or something. ;-)
Hmm, do any of the commercial Linux dists distribute the X version?
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
(clobber (scratch:HI))
> ] ) 145 {fix_truncsfsi2+1} (insn_list 293 (nil))
> (expr_list:REG_DEAD (reg:SI 0 %eax)
> (expr_list:REG_UNUSED (scratch:HI)
> (nil))))
> *** Error code 1
>
>
>
>
>
> --
>
> Amancio Hasty
> [EMAIL PROTECTED
sorry but this is
> sufficient information to reproduce the problem.
No, it is not, because we can't *get* XFree86 3.9.xxx -current, so we
cannot reproduce it, can we?
You either need to give us enough to build that part, or provide a
preprocessed file so we can feed the backends direc
us, this means
that you won't be able to build a.out libraries.
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
:56:19 haywire ppp[882]: tun0: Phase: 1: Connect time: 1112 secs: 533725
octets in, 386209 octets out
Dec 29 10:56:19 haywire ppp[882]: tun0: Phase: total 827 bytes/sec, peak 4972
bytes/sec on Wed Dec 29 10:56:19 1999
> -Bryan
>
>
>
> To Unsubscribe: send mail to [EMAI
d GNU'fashion way? Does a purely
> stock GCC 2.95 bomb on this?? If so, it is a GCC problem and the issue
> should be raised with Cygnus.
Yes it is a gcc-2.95.2 bug. It's fixed in the 2.96 snapshot in
ports/lang/gcc-devel.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED];
akefile. I did
actually do a 'make world' immediately prior to the commit, and ifmcstat was
added to usr.sbin/Makefile after the conversion which broke the build.
date: 1999/12/28 02:37:05; author: shin; state: Exp;
Getaddrinfo(), getnameinfo(), and etc support in libc/net.
Several
Last time I checked (I haven't moved to the latest gcc, so I can't
confirm it there), one significant difference between 'cc -E' and
/usr/libexec/cpp was that the latter would read from a pipe, whilst
the former wouldn't. This can make converting to 'cc -E'
cd0 cd1 cd4 -da2 da6-da9
> create cd0, cd1, cd4, da1, da2, da6, da7, da8, da9 ? This would be
> a generic solution that still allows for holes. Not possible because
> of compatibility issues? I'm willing to give it a go.
"Send patches" :-)
Seriously, the ultimate solution
. As several people have pointed out, both
'cc -E -' and 'cc -x c -E /dev/stdin' work. I'll crawl back into
the woodwork for a while :-).
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> manually, which, if anyone has every admin'd majordomo knows, is not a
> requirement.
Just take a look at the last week of bugtraq about majordomo.. if somebody
edited files, it could have been *anyone* with an account on hub - root or
not. That leaves about 296 people who could have logged
The last cvs-cur CTM delta I received was cvs-cur.5961, which arrived
just over 24 hours ago. Is there a problem with the CTM generation?
Peter
--
Peter Jeremy (VK2PJ)[EMAIL PROTECTED]
Alcatel Australia Limited
41 Mandible St Phone: +61 2 9690 5019
modules if you are
tracking -current and rebuilding regularly. It is too easy to shoot
yourself in the foot by getting /modules and the kernel out of sync while
the internal interfaces are still changing.
Using kld's to develop drivers is different.
Cheers,
-Peter
To Unsubscribe: send m
FreeBSD one is the second and is 11743515
sectors. ad2 is dedicated (not dangerously) to FreeBSD and the slice is
2503809 sectors.
Peter
--
Peter Jeremy (VK2PJ)[EMAIL PROTECTED]
Alcatel Australia Limited
41 Mandible St Phone: +61 2 9690 5019
ALEXANDRIA N
16 secs/int, 1 depth queue, DMA
acd0: CDROM drive at ata0 as slave
acd0: read 1723KB/s (1723KB/s), 256KB buffer, DMA
acd0: Reads: CD-R, CD-RW, CD-DA stream
acd0: Audio: play, 16 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: CD-ROM 120mm data disc loaded, unlocked
Mounting root from uf
ero-length request to the underlying driver.
2) The ata-disk driver doesn't check for (and ignore) zero-length
requests, instead passing them onto the disk.
See kern/15956 for details and patches.
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current
n's announcement of a code freeze.
Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 2000-Jan-06 18:38:08 +1100, Soren Schmidt <[EMAIL PROTECTED]> wrote:
>It seems Peter Jeremy wrote:
>> I just discovered that my ATAPI CD-ROM is no longer usable - when I
>> try to mount it, my maching hangs (hard).
...
>> acd0: read 1723KB/s (1
when you've got strange problems like this, be sure
to *not* use '-j' when building as this makes it very hard to see exactly
what happened. The actual failure can be several screens back.
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
;scbus0 at ncr0' and somebody referenced 'scbus?' it would guess that another
'scbus? at ncr?' would be needed. Nothing used this, except the old vax-style
configuration mechanism that never(?) entered 386BSD/FreeBSD. (not newconfig,
I'm talking about the really old oldconf
1 - 100 of 1676 matches
Mail list logo
