Re: FreeBSD has a politics problem
If politics is when a community had standards it operated by but it showed favoritism not disciplining it's members it thought were more important and allowed them to harass others until they either left or could be accused of breaking not it's rules at time of conflict but this new one they have much more than a political problem. They have a legal problem. They don't own the rights to it's code anymore. Ryan Root Sent from my Verizon, Samsung Galaxy smartphone Original message From: Conrad Meyer Date: 3/3/18 3:25 PM (GMT-08:00) To: John Darrah Cc: freebsd-advoc...@freebsd.org, freebsd-current@freebsd.org Subject: Re: FreeBSD has a politics problem John, A good portion of your original email happens to be inaccurate or misleading. In the spirit of good faith discussion, I'm going to assume you're just accidentally misinformed, and not willfully misrepresenting things. So, some corrections and clarifications follow. If you have further questions about the code of conduct, I suggest reaching out to the drafting committee or core directly. They're nice people, they don't bite, and they're happy to help clarify intent and nuance. Thanks. On Sat, Mar 3, 2018 at 2:30 PM, John Darrah wrote: > FreeBSD recently introduced an updated Code of Conduct that developers and > members must adhere to. There has been much backlash online about it and > about introducing identity politics into a technical OS project in general. > The Code of Conduct was adopted In part, with editorial review and modification by a committee of conscientious project members. > from the "Geek Feminism" wiki's version, > which claims (among other things) that racism against whites doesn't exist, This claim is factually erroneous. The Geek Feminism example anti-harassment policy simply makes no such claim. (Furthermore, criticizing the Geek Feminism document is wholly off-topic for FreeBSD. Our code of conduct is not identical to GF's example policy. The only conduct document relevant to FreeBSD is the one at https://www.freebsd.org/internal/code-of-conduct.html .) > sexism against men doesn't exist, This claim is also objectively absent from the plain language of either document. > and that certain protected classes of > people should not be criticised. Again, this hysterical claim comes from blue sky. > A number of developers, particularly benno@, phk@ and des@, have used racist > and sexist remarks Again, this is a claim made without any evidence. I've briefly re-skimmed the developers discussion on this topic and don't see any examples. (And, this accusation is so far outside of Benno's demeanor as to be completely laughable.) phk@ and des@ have used less conciliatory language but I still do not see any sexist or racist remarks. > against those criticising the far-reaching project policy > change, saying that the concerns about the policy essentially boil down to > "white male privilege" and being "on the wrong side of history". They're entitled to their opinions, as you are. Note that neither des@ nor phk@ sit on or represent the Core team. > Other developers expressed concern about the policy being thrown upon them > with no discussion or debate, as well as The FreeBSD Foundation's choice > to pay an outside person (with donations from the users) to work on the > Code of Conduct's enforcement. The Foundation chooses how to spend donation dollars at its sole discretion. That's the deal with 501(c)(3) charities. If you want to pick and choose how your donated dollars are spent, Linux Foundation is a 501(c)(6). > Said person identifies as a feminist. We don't object to contribution from people who identify as Republican, Catholic, or Pastafarian. Why do you think someone who identifies as a feminist is incapable of doing a good job advising the drafting committee? > Mods on BSD and FreeBSD-related subreddits are censoring posts, removing > threads, and banning users for posting the link. This is a misleading oversimplification. FreeBSD-the-project doesn't control or have any moderation privileges on BSD-topic subreddits. The only active moderator on one of the subreddits (freebsd) isn't even a developer, just some random reddit user who happened to register long ago. Colin Percival happens to have moderation privileges on the other subreddit (BSD), but again, is acting on his personal volition. He does not sit on nor represent the Core team. Most discussions on the code of conduct in both locations have been left in place, despite fairly low quality discussion. (The usual name-calling, spreading of outright FUD, othering, etc etc.) The few posts that have been removed were outright, low-effort trolling. Not any kind of nuanced criticism of the actual code of
Re: PCM freezes the box
> Is anything printed on the console (or the first vty)? > > > Andre Guibert de Bruet | Enterprise Software Consultant > > > Silicon Landmark, LLC. | http://siliconlandmark.com/> Nope. I get complete blackout - I'm unable to switch vtys, move mouse, start a new process, etc. Just like a crash in Windows - only reset button works. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PCM freezes the box
Dear Sirs, I have problems with my 5.1-Release and 5.1-STABLE boxes: they freeze if I play anything different from audio CDs. The cards are ESS 1938, options pcm is in the kernel. If I try to run xmms/mpg123/KDE or any other application related with artsd/esound/audiofile, the machines freeze, leaving not a single chance to escape to shell and kill the process. I have been beating my head for more than two weeks without success. Please give any hints if possible. TIA, DVV ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Best Known Methods for dual booting WinXP + -current
Try GAG-> GAG.SF.NET -> works with charm. I use it to boot Solaris,FreeBSD and Gates crap with minor fixes. Requires restoring Win MBR, not installing a FreeBSD bootloader, if on the same disk. You can set passwords to all ;p Other thing I'm grasping is a guide in OBSD FAQ for multibooting with NT loader. Happy hacking and peace! DVV ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Dummy: PCM causes freezes
Hi!
I got a problem with the pcm driver - on the startup of whatever sound
application by whatever user - root, me, etc it freezes my machine.
I experienced this both on 5.1RElease and 5.1-STABLE(24.07.2003CVSUP). The card
is ESS 1938(SOLO-1) The thing happens over and over again. Here is what I do:
add pcm to the kernel file, make build&&install{kernel}. Reboot,
build+installworld and on the next reboot start KDE,mpg123,etc and face the music.
I googled and found some info that the needed driver must be loaded in
loader.conf like: `snd_es_1938_load="YES"`.
However, even without this, I see my ESS Card attached at pcm0. Can anyone give
hints and help me out bypass this system freeze caused by the pcm?
Attached is my dmesg.boot of my new kernel.
TIA,
Dimitar
dmesg.boot
Description: Binary data
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
OT: X aperture
Hello again! Sorry for trolling. I have just found one more way to have X and seculevel coexisting. It's applicable for desktops mostly.Here's the trick: Start the system with seculevel "-1", run startx and then type '/sbin/sysctl -w kern.securelevel=1' in a terminal. The last requires as all know requires root privileges or sudo. Thanks for your patience, Dimitar Vassilev ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
OT:escaping X barfings
Hello all! CAn you tell me how a procedure how to patch X and kernel to avoid X barfings from securelevel? My release is a FreeBSD 5.1. I looked for patches, unfortunately they're more than a year old.Googled and searched on MARC - nothing new under the sun. Therefore I suppose all works ok in -CURRENT.I'm thinking of: 1) CVSup src and ports to "." 2) adding `options APERTURE` to my kernel 3) make buildkernel && make install kernel && make buildworld 4) reboot and face the music TIA, Dimitar Vassilev - hobbyist and FDP-BG translator ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Belkin USB 2.0 Cardbus card
Has anyone got one of these cards working? I plug it into my laptop with 5.1, cvsupped on Monday or Tuesday (long week), and try to plug this card in. It is recognized the card, but has errors and disables them. I also am trying a Sony DRX-500UL drive. It's recognized in the built-in USB 1.1 ports, and I'm able to mount a CD. Any chance burning on it could happen? CD VCD and DVD +/- RW. Thanks, Paul. -- Paul T. RootCCSA, CCSE, CCNA Qwest CommunicationsPAG: +1 (877) 693-7155 600 Stinson Blvd, Flr 1SWRK: +1 (612) 664-3385 Minneapolis, MN 55413 FAX: +1 (612) 664-4778 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problem with X
On Tue, 28 Jan 2003, joseph wrote: > Try a make build world and see if that version of libc_r works. > It should fix the problem. joseph I tried that... now the error is: Symbol from module /usr/X11R6/lib/modules/fonts/libbitmap.a is unresolved! This is getting old. any other ideas? thanks, Kirk > > On Mon, 2003-01-27 at 13:07, Alexander Pohoyda wrote: > > Charlie ROOT <[EMAIL PROTECTED]> writes: > > > > > root, nor a regular user. Is this a font path problem? > > > > No, it is not. > > > > > > > /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined symbol > > > "__thr_jtable" > > > > This is a problem. Version numbers are OK, though. > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
problem with X
I'm getting the following error when I try and start X. I just built 5.0 and had x working untill I portupgraded gnome2. I have rebuilt wrapper, and freetype2. I have also re-run xf86config. No one can start x, not root, nor a regular user. Is this a font path problem? if so what should I try? Thanks Kirk error message: lorax# xinit XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: FreeBSD 4.7-STABLE i386 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Mon Jan 27 11:41:17 2003 (==) Using config file: "/etc/X11/XF86Config" Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined symbol "__thr_jtable" waiting for X server to shut down To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: only root can startx
On Thu, 23 Jan 2003, Adam Maas wrote: > Your permissions for /var/log are wrong. they are: lorax# ls -l XFree86.0.log -rw-r--r-- 1 root wheel 23375 Jan 23 12:20 XFree86.0.log shouldn't that be correct? > > --Adam > > - Original Message ----- > From: "Charlie ROOT" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, January 23, 2003 1:30 PM > Subject: only root can startx > > > > I am working the kinks out of an upgrade from 4.7 to 5.0-R. So far I see a > > problem starting X. first off xinit does not seem to work. Was that > > removed in 5.0? Second, oly root can startx. When I try as a regular user, > > I get the message: 'Fatal server error connot open log file > > /var/log/XFree86.0.log' > > > > what's going on here? > > > > thanks, > > > > Kirk > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: only root can startx
On Thu, 23 Jan 2003, David Wolfskill wrote: > See /usr/ports/x11/wrapper. I have wrapper installed lorax# pkg_info | grep wrapper fampp-1.1 A C++ wrapper for fam from SGI gtkmm-1.2.8_1 C++ wrapper for gtk, a x11 graphics library javavmwrapper-1.4 Wrapper script for various Java Virtual Machines p5-File-Rsync-0.20 Perl convenience wrapper for the rsync(1) program wrapper-1.0_2 Wrapper for XFree86-4 server do I need to re-buildit? Kirk > > Cheers, > david > -- > David H. Wolfskill[EMAIL PROTECTED] > I have no confidence in results obtained through the use of Microsoft products. > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
only root can startx
I am working the kinks out of an upgrade from 4.7 to 5.0-R. So far I see a problem starting X. first off xinit does not seem to work. Was that removed in 5.0? Second, oly root can startx. When I try as a regular user, I get the message: 'Fatal server error connot open log file /var/log/XFree86.0.log' what's going on here? thanks, Kirk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ia64 tinderbox failure
-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree -- >>> stage 2: rebuilding the object tree -- >>> stage 2: build tools -- >>> stage 3: cross tools -- >>> stage 4: populating >/home/tinderbox/ia64/obj/home/tinderbox/ia64/src/ia64/usr/include -- >>> stage 4: building libraries -- >>> stage 4: make dependencies -- >>> stage 4: building everything.. -- ===> gnu/usr.bin/binutils/libbfd cc1: warnings being treated as errors /home/tinderbox/ia64/src/contrib/binutils/bfd/elf-eh-frame.c: In function `_bfd_elf_discard_section_eh_frame': /home/tinderbox/ia64/src/contrib/binutils/bfd/elf-eh-frame.c:417: warning: comparison between signed and unsigned *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin/binutils/libbfd. *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin. *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ia64 tinderbox failure
-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree -- >>> stage 2: rebuilding the object tree -- >>> stage 2: build tools -- >>> stage 3: cross tools -- >>> stage 4: populating >/home/tinderbox/ia64/obj/home/tinderbox/ia64/src/ia64/usr/include -- >>> stage 4: building libraries -- >>> stage 4: make dependencies -- >>> stage 4: building everything.. -- ===> gnu/usr.bin/binutils/libbfd cc1: warnings being treated as errors /home/tinderbox/ia64/src/contrib/binutils/bfd/elf-eh-frame.c: In function `_bfd_elf_discard_section_eh_frame': /home/tinderbox/ia64/src/contrib/binutils/bfd/elf-eh-frame.c:417: warning: comparison between signed and unsigned *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin/binutils/libbfd. *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin/binutils. *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/usr.bin. *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ia64 tinderbox failure
-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree -- >>> stage 2: rebuilding the object tree -- >>> stage 2: build tools -- >>> stage 3: cross tools -- >>> stage 4: populating >/home/tinderbox/ia64/obj/home/tinderbox/ia64/src/ia64/usr/include -- >>> stage 4: building libraries -- ===> gnu/lib/libgcc /home/tinderbox/ia64/src/contrib/gcc/config/ia64/unwind-ia64.c:242:1: warning: "MIN" redefined In file included from /home/tinderbox/ia64/src/contrib/gcc/config/freebsd-spec.h:157, from tconfig.h:14, from /home/tinderbox/ia64/src/contrib/gcc/config/ia64/unwind-ia64.c:34: /home/tinderbox/ia64/obj/home/tinderbox/ia64/src/ia64/usr/include/sys/param.h:256:1: warning: this is the location of the previous definition In file included from /home/tinderbox/ia64/obj/home/tinderbox/ia64/src/ia64/usr/include/sys/signal.h:47, from /home/tinderbox/ia64/obj/home/tinderbox/ia64/src/ia64/usr/include/sys/param.h:101, from /home/tinderbox/ia64/src/contrib/gcc/config/freebsd-spec.h:157, from tconfig.h:14, from /home/tinderbox/ia64/src/contrib/gcc/libgcc2.c:38: /home/tinderbox/ia64/obj/home/tinderbox/ia64/src/ia64/usr/include/machine/signal.h:114: field `sc_fr' has incomplete type *** Error code 1 Stop in /home/tinderbox/ia64/src/gnu/lib/libgcc. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. *** Error code 1 Stop in /home/tinderbox/ia64/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mysql-server build errors
On Thu, Aug 08, 2002 at 12:05:44PM -0800, Beech Rintoul wrote: > On Thursday 08 August 2002 11:50 am, Dan Nelson wrote: > > In the last episode (Aug 08), Beech Rintoul said: > > > Anyone have a pointer to get this to build? > > > cc -DMYSQL_SERVER > > > -DDEFAULT_MYSQL_HOME="\"/usr/local\"" -fno-exceptions -fno-rtti > > > -DMYSQLD_NET_RETRY_COUNT=100 -c mysqld.cc /usr/include/tcpd.h: In > > > function `void* handle_connections_sockets(void*)': > > > /usr/include/tcpd.h:137: too many arguments to function `void > > > sock_host()' mysqld.cc:2428: at this point in file > > > > It's a bug in the tcpwrappers headers; they declare functions with no > > parameters, and gcc rightfully complains about using them in c++ code. > > Remove the --with-libwrap line from the port Makefile as a workaround. > > Thanks...That worked. Worked=mysql actually compiled? Or it got past that section? Removing --with-libwrap certainly gets past that section but on my system it still spews a lot of errors during the final link: item.o(.gnu.linkonce.d._ZTV9Item_buff+0x8): undefined reference to `__cxa_pure_v irtual' item.o(.gnu.linkonce.d._ZTV17Item_result_field+0x28): undefined reference to `__ cxa_pure_virtual' item.o(.gnu.linkonce.d._ZTV17Item_result_field+0x2c): undefined reference to `__ cxa_pure_virtual' item.o(.gnu.linkonce.d._ZTV17Item_result_field+0x30): undefined reference to `__ cxa_pure_virtual' item.o(.gnu.linkonce.d._ZTV17Item_result_field+0x34): undefined reference to `__ cxa_pure_virtual' item.o(.gnu.linkonce.d._ZTV17Item_result_field+0x38): more undefined references to `__cxa_pure_virtual' follow item_sum.o: In function `Item_sum_count_distinct::~Item_sum_count_distinct()': item_sum.o(.text+0x19c7): undefined reference to `operator delete[](void*)' item_sum.o(.text+0x19dc): undefined reference to `operator delete(void*)' item_sum.o: In function `Item_sum_count_distinct::~Item_sum_count_distinct()': item_sum.o(.text+0x1aa7): undefined reference to `operator delete[](void*)' item_sum.o(.text+0x1abc): undefined reference to `operator delete(void*)' item_sum.o: In function `Item_sum_count_distinct::~Item_sum_count_distinct()': item_sum.o(.text+0x1b87): undefined reference to `operator delete[](void*)' [list goes on for a while] This is with -CURRENT from today (8/8). -Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
C++ troubles continue
Trying to build kdebase3 on the FreeBSD 5.0-CURRENT #7: Mon Jun 17 22:46:16 EDT 2002 [...] gmake[4]: Nothing to be done for `all-am'. gmake[4]: Leaving directory `/ccd/ports/x11/kdebase3/work/kdebase-3.0.1/kappfinder/apps' gmake[3]: Leaving directory `/ccd/ports/x11/kdebase3/work/kdebase-3.0.1/kappfinder/apps' gmake[3]: Entering directory `/ccd/ports/x11/kdebase3/work/kdebase-3.0.1/kappfinder' /bin/sh ../libtool --mode=link --tag=CXX c++ -DNDEBUG -DNO_DEBUG -O2 -O -march=i686 -pipe -fno-exceptions -fno-check-new -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT -DQT_NO_ASCII_CAST-o kappfinder -L/opt/lib -pthread -L/opt/lib -R /opt/lib -R /opt/lib -R /opt/lib -R /opt/lib main.o scanner.o checker.o kappfinder_meta_unload.o -lkdeui c++ -DNDEBUG -DNO_DEBUG -O2 -O -march=i686 -pipe -fno-exceptions -fno-check-new -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT -DQT_NO_ASCII_CAST -o kappfinder -pthread main.o scanner.o checker.o kappfinder_meta_unload.o -L/opt/lib /opt/lib/libkdeui.so /opt/lib/libkdecore.so -L/usr/lib /opt/lib/libDCOP.so /opt/lib/libkdefx.so -lqt-mt -lpng -lz -lXext -lX11 -lSM -lICE -lXrender -lstdc++ -lm -lgcc -Wl,--rpath -Wl,/opt/lib -Wl,--rpath -Wl,/opt/lib checker.o: In function `checkDesktopFile(QString const&, QString)': checker.o(.text+0x536): undefined reference to `cout' checker.o(.text+0x543): undefined reference to `ostream::operator<<(char const*)' checker.o(.text+0x575): undefined reference to `ostream::operator<<(char const*)' checker.o(.text+0x585): undefined reference to `ostream::operator<<(char const*)' checker.o(.text+0x6f1): undefined reference to `cout' checker.o(.text+0x6fe): undefined reference to `ostream::operator<<(char const*)' checker.o(.text+0x706): undefined reference to `endl(ostream&)' checker.o(.text+0x7e1): undefined reference to `cout' checker.o(.text+0x7ea): undefined reference to `ostream::operator<<(char const*)' checker.o(.text+0x7f2): undefined reference to `endl(ostream&)' gmake[3]: *** [kappfinder] Error 1 gmake[3]: Leaving directory `/ccd/ports/x11/kdebase3/work/kdebase-3.0.1/kappfinder' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/ccd/ports/x11/kdebase3/work/kdebase-3.0.1/kappfinder' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/ccd/ports/x11/kdebase3/work/kdebase-3.0.1' gmake: *** [all] Error 2 *** Error code 2 Any clues? The /usr/lib/libstdc++.a has, for example: W std::basic_ostream >& std::endl >(std::basic_ostream >&) B std::cout B std::buf_cout U std::cout U std::buf_cout -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
double panic in todays kernel
Using ``FreeBSD 5.0-CURRENT #1: Wed Feb 27 09:07:28 EST 2002''.
While building some port (-pipe probably played its fatal role)...
-mi
(kgdb) symbol-file kernel.debug
Reading symbols from kernel.debug...done.
(kgdb) exec-file /boot/mi/kernel
(kgdb) core-file /ccd/crash/vmcore.28
IdlePTD at phsyical address 0x004f4000
initial pcb at physical address 0x00418120
panicstr: bwrite: buffer is not busy???
panic messages:
---
Fatal trap 12: page fault while in kernel mode
cpuid = 1; lapic.id =
fault virtual address = 0xa4
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc023ea63
stack pointer = 0x10:0xcf9a0c14
frame pointer = 0x10:0xcf9a0c30
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 23591 (bzip2)
trap number = 12
panic: page fault
cpuid = 1; lapic.id =
boot() called on cpu#1
syncing disks... panic: bwrite: buffer is not busy???
cpuid = 1; lapic.id =
boot() called on cpu#1
Uptime: 51m48s
pfs_vncache_unload(): 8 entries remaining
dumping to dev da0b, offset 131200
dump 319 318 [...] 1 0
---
#0 dumpsys () at /ccd/src/sys/kern/kern_shutdown.c:504
504 if (!dodump)
(kgdb) where
#0 dumpsys () at /ccd/src/sys/kern/kern_shutdown.c:504
#1 0xc0220d54 in boot (howto=260) at /ccd/src/sys/kern/kern_shutdown.c:336
#2 0xc0221245 in panic (fmt=0xc03790b8 "bwrite: buffer is not busy???")
at /ccd/src/sys/kern/kern_shutdown.c:646
#3 0xc0259043 in bwrite (bp=0xc7d1aa34) at /ccd/src/sys/kern/vfs_bio.c:676
#4 0xc025a2ca in vfs_bio_awrite (bp=0xc7d1aa34)
at /ccd/src/sys/kern/vfs_bio.c:1526
#5 0xc01f7168 in spec_fsync (ap=0xcf9a0ad0)
at /ccd/src/sys/fs/specfs/spec_vnops.c:403
#6 0xc01f6d21 in spec_vnoperate (ap=0xcf9a0ad0)
at /ccd/src/sys/fs/specfs/spec_vnops.c:121
#7 0xc02e45d8 in ffs_sync (mp=0xc16d2a00, waitfor=2, cred=0xc102eb80,
td=0xc03d5c00) at vnode_if.h:441
#8 0xc0266212 in sync (td=0xc03d5c00, uap=0x0)
at /ccd/src/sys/kern/vfs_syscalls.c:669
#9 0xc0220980 in boot (howto=256) at /ccd/src/sys/kern/kern_shutdown.c:245
#10 0xc0221245 in panic (fmt=0xc0397dde "%s")
at /ccd/src/sys/kern/kern_shutdown.c:646
#11 0xc032fd16 in trap_fatal (frame=0xcf9a0bd4, eva=164)
at /ccd/src/sys/i386/i386/trap.c:848
#12 0xc032fa3d in trap_pfault (frame=0xcf9a0bd4, usermode=0, eva=164)
at /ccd/src/sys/i386/i386/trap.c:762
#13 0xc032f503 in trap (frame={tf_fs = -1069940712, tf_es = -819986416,
tf_ds = -812187632, tf_edi = -812170240, tf_esi = 4096,
tf_ebp = -811987920, tf_isp = -811987968, tf_ebx = 0,
tf_edx = -812170240, tf_ecx = -811987824, tf_eax = -830089152,
tf_trapno = 12, tf_err = 0, tf_eip = -1071388061, tf_cs = 8,
tf_eflags = 66178, tf_esp = -1069695296, tf_ss = 4096})
at /ccd/src/sys/i386/i386/trap.c:430
#14 0xc023ea63 in pipe_write (fp=0xc20751c0, uio=0xcf9a0c90, cred=0xc2d32a80,
flags=0, td=0xcf974400) at /ccd/src/sys/kern/sys_pipe.c:820
#15 0xc023b834 in dofilewrite (td=0xcf974400, fp=0xc20751c0, fd=1,
buf=0x83ef000, nbyte=4096, offset=-1, flags=0)
at /ccd/src/sys/sys/file.h:191
#16 0xc023b62d in write (td=0xcf974400, uap=0xcf9a0d20)
at /ccd/src/sys/kern/sys_generic.c:337
#17 0xc033015c in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = 134640440, tf_esi = 138342400, tf_ebp = -1077947856,
tf_isp = -811987596, tf_ebx = 134640440, tf_edx = 138342400,
tf_ecx = 134640440, tf_eax = 4, tf_trapno = 0, tf_err = 2,
tf_eip = 134611567, tf_cs = 31, tf_eflags = 663, tf_esp = -1077947884,
tf_ss = 47}) at /ccd/src/sys/i386/i386/trap.c:1044
#18 0xc031f7ed in syscall_with_err_pushed ()
#19 0x805e2ff in ?? ()
#20 0x805db5f in ?? ()
#21 0x805daa9 in ?? ()
#22 0x80488d8 in ?? ()
(kgdb) up 14
#14 0xc023ea63 in pipe_write (fp=0xc20751c0, uio=0xcf9a0c90, cred=0xc2d32a80,
flags=0, td=0xcf974400) at /ccd/src/sys/kern/sys_pipe.c:820
820 PIPE_LOCK(wpipe);
(kgdb) p wpipe
$1 = (struct pipe *) 0x0
(kgdb) l
815 struct pipe *wpipe, *rpipe;
816
817 rpipe = (struct pipe *) fp->f_data;
818 wpipe = rpipe->pipe_peer;
819
820 PIPE_LOCK(wpipe);
821 /*
822 * detect loss of pipe read side, issue SIGPIPE if lost.
823 */
824 if ((wpipe == NULL) || (wpipe->pipe_state & PIPE_EOF)) {
(kgdb) p rpipe
$2 = (struct pipe *) 0x0
(kgdb) p fp
$3 = (struct file *) 0xc20751c0
(kgdb) p fp->f_data
$4 = 0xce85d840 ""
(kgdb) p *fp
$5 = {f_list = {le_next = 0xc256c500, le_prev = 0xc181a700}, f_gcflag = 0,
f_type = 3, f_count = 2, f_msgcount = 0, f_cred = 0xc2d32a80,
f_ops = 0xc03dbec0, f_seqcount = 1, f_nextoff = 0, f_offset = 0,
f_data = 0xce85d840 "", f_flag = 3, f_mtxp = 0xc0417970}
(kgdb) up
#15 0xc023b834 in dofilewrite (td=
kernel threading: the first steps [patch]
Here's a first step.
I've broken the proc structure into 4 structures. At this moment the proc
structure includes
the other three, so there is no problem with allocation, and there is always
a 1:1 correlation between them at this time so this is safe.
SOme of the fields are probably in the wrong structs but it doesn't matter for
his patch.
The aim of this patch is to make people think about which fields go to which
structures and what new fields are needed.
Remarkably the kernel compiles and runs!
The purposes of the structs in this setting are:
1/ The kse struct is known to the scheduler, associated with a CPU and scheduled
whenever there
as a context to run.
2/The ksec is a stored context that is associated with a kse, but for some
reason cannot be running now.
3/The KSEG has a priority, nice value, etc. KSECs tha complete may be reported
back to the
userland scheduler on he next KSE within the same KSEG. Timers are in KSEG
scope.
Signals are in KSEG scope too?
4/Al resorces and permissions are owned by the original proc sruct.
these definitions are open for discussion but they give some grounds to work on
regarding which fields go where
After deciding what the semantics are and assigning fields to structures,
(and how they are linked), we can then work out which functions in the kernel
take which structure as arguments, and them work towards divorcing them so that
the 1:1 relationship is broken.
At that stage we have threads.
thoughts?.
--
__--_|\ Julian Elischer
/ \ [EMAIL PROTECTED]
( OZ) World tour 2000-2001
---> X_.---._/
v
Index: kern/kern_fork.c
===
RCS file: /unused/cvs/freebsd/src/sys/kern/kern_fork.c,v
retrieving revision 1.94
diff -u -r1.94 kern_fork.c
--- kern/kern_fork.c2001/01/24 10:47:14 1.94
+++ kern/kern_fork.c2001/01/27 03:53:12
@@ -371,6 +371,24 @@
bcopy(&p1->p_startcopy, &p2->p_startcopy,
(unsigned) ((caddr_t)&p2->p_endcopy - (caddr_t)&p2->p_startcopy));
+ bzero(&p2->kse0.kse_startzero,
+ (unsigned) ((caddr_t)&p2->kse0.kse_endzero
+ - (caddr_t)&p2->kse0.kse_startzero));
+ bcopy(&p1->kse0.kse_startcopy, &p2->kse0.kse_startcopy,
+ (unsigned) ((caddr_t)&p2->kse0.kse_endcopy
+ - (caddr_t)&p2->kse0.kse_startcopy));
+
+ bzero(&p2->ksec0.ksec_startzero,
+ (unsigned) ((caddr_t)&p2->ksec0.ksec_endzero
+ - (caddr_t)&p2->ksec0.ksec_startzero));
+ bcopy(&p1->ksec0.ksec_startcopy, &p2->ksec0.ksec_startcopy,
+ (unsigned) ((caddr_t)&p2->ksec0.ksec_endcopy
+ - (caddr_t)&p2->ksec0.ksec_startcopy));
+
+ bcopy(&p1->kseg0.kseg_startcopy, &p2->kseg0.kseg_startcopy,
+ (unsigned) ((caddr_t)&p2->kseg0.kseg_endcopy
+ - (caddr_t)&p2->kseg0.kseg_startcopy));
+
mtx_init(&p2->p_mtx, "process lock", MTX_DEF);
p2->p_aioinfo = NULL;
Index: sys/proc.h
===
RCS file: /unused/cvs/freebsd/src/sys/sys/proc.h,v
retrieving revision 1.141
diff -u -r1.141 proc.h
--- sys/proc.h 2001/01/24 09:41:03 1.141
+++ sys/proc.h 2001/01/27 03:52:53
@@ -141,18 +141,157 @@
* m - Giant
* n - not locked, lazy
*/
+struct proc; /* forward decl. */
+
+/*
+ * The schedulable entity that can be given a context to run.
+ * A process may have several of these. Probably one per processor
+ * but posibly a few more. In this universe they are grouped
+ * with a KSEG that contains the priority and niceness
+ * for the group.
+ */
+struct kse {
+ /* individualy set up */
+ struct pstats *kse_stats; /* (bk) Accounting/statistics (CPU). */
+#define kse_startzero kse_estcpu
+ /* start zero */
+ u_int kse_estcpu; /* (jk) Time averaged value of kse_cpticks. */
+ int kse_cpticks;/* (jk) Ticks of cpu time. */
+ fixpt_t kse_pctcpu; /* (jk) %cpu during p_swtime. */
+ u_int64_t kse_uu; /* (jk) Previous user time in microsec. */
+ u_int64_t kse_su; /* (jk) Previous system time in microsec. */
+ u_int64_t kse_iu; /* (jk) Previous interrupt time in microsec. */
+ u_int64_t kse_uticks; /* (jk) Statclock hits in user mode. */
+ u_int64_t kse_sticks; /* (jk) Statclock hits in system mode. */
+ u_int64_t kse_iticks; /* (jk) Statclock hits processing intr. */
+ u_int kse_slptime;/* (jk) Time since last blocked. */
+ u_char kse_oncpu; /* (jk) Which cpu we are on. */
+ charkse_rqindex;/* (jk) Run queue index. */
+ register_t kse_retval[2]; /* (kk) Syscall aux returns. */
+ /* end zero */
+#define kse_endzero kse_priority
+#define kse_startcopy kse_priority
+ /* start copy */
+ u_char kse_priority; /* (jk) Process priority
kyra.unloved.org daily run output
Removing stale files from /var/preserve: Cleaning out old system announcements: Removing stale files from /var/rwho: Backup passwd and group files: kyra.unloved.org passwd diffs: 68d67 < orion:(password):2004:2004::0:0:Orion Server:/home/orion:/usr/local/bin/bash 69a69 > postfix:(password):2001:3024::0:0:Postfix Mail System:/nonexistent:/nonexistent kyra.unloved.org group diffs: 93a94 > postfix:*:3024: Verifying group file syntax: Backing up mail aliases: kyra.unloved.org aliases diffs: --- /var/backups/aliases.bakThu Sep 21 17:28:04 2000 +++ /etc/mail/aliases Mon Jan 22 11:02:55 2001 @@ -1,4 +1,4 @@ -# $FreeBSD: src/etc/mail/aliases,v 1.10.4.1 2000/08/27 17:31:38 gshapiro Exp $ +# $FreeBSD: src/etc/mail/aliases,v 1.10.4.2 2000/12/16 07:03:35 dougb Exp $ # @(#)aliases 5.3 (Berkeley) 5/24/90 # # Aliases in this file will NOT be expanded in the header from @@ -24,8 +24,10 @@ # General redirections for pseudo accounts bin: root +bind: root daemon: root games: root +kmem: root man: root news: root nobody: root @@ -33,6 +35,7 @@ pop: root system: root toor: root +tty: root usenet: news uucp: root xten: root Disk status: Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/ad5s1a19839951629 13089928%/ /dev/ad5s2e 9505261 539884 8204957 6%/data /dev/ad5s1f 8473272 2924146 487126538%/usr /dev/ad5s1e99223918696 894164 2%/var procfs 440 100%/proc Last dump(s) done (Dump '>' file systems): UUCP status: Network interface status: Name Mtu Network AddressIpkts IerrsOpkts Oerrs Coll xl0 1500 00:10:4b:09:ec:f0 49045770 0 84287087 4 0 xl0 1500 62.58.62.160/ kyra49045770 0 84287087 4 0 xl0 1500 jacquie.would jacquie.would.b 49045770 0 84287087 4 0 xl0 1500 my.pussy.gets my.pussy.gets.w 49045770 0 84287087 4 0 xl0 1500 jacquie.loves jacquie.loves.a 49045770 0 84287087 4 0 xl0 1500 twilight.bast twilight.bastar 49045770 0 84287087 4 0 xl0 1500 freebsd.is.be freebsd.is.bett 49045770 0 84287087 4 0 xl0 1500 magic.kablast magic.kablasto. 49045770 0 84287087 4 0 xl0 1500 i.own.decix.n i.own.decix.net 49045770 0 84287087 4 0 xl0 1500 teefers.is.th teefers.is.thra 49045770 0 84287087 4 0 xl0 1500 i.fucked.freu i.fucked.freudi 49045770 0 84287087 4 0 xl0 1500 jacquie.swall jacquie.swallow 49045770 0 84287087 4 0 xl0 1500 unhappy.and/3 unhappy.and 49045770 0 84287087 4 0 xl0 1500 attyz.wants.t attyz.wants.to. 49045770 0 84287087 4 0 xl0 1500 jacquie.is.a. jacquie.is.a.cu 49045770 0 84287087 4 0 xl0 1500 i.am.not.real i.am.not.really 49045770 0 84287087 4 0 xl0 1500 you.need.a.go you.need.a.good 49045770 0 84287087 4 0 xl0 1500 will.never.be will.never.be 49045770 0 84287087 4 0 xl0 1500 vanitywhore.o vanitywhore.org 49045770 0 84287087 4 0 xl0 1500 is.a.masturba is.a.masturbati 49045770 0 84287087 4 0 xl0 1500 works.for.ver works.for.versa 49045770 0 84287087 4 0 xl0 1500 deeply.shallo deeply.shallow. 49045770 0 84287087 4 0 xl0 1500 62.58.48.84/3 62.58.48.84 49045770 0 84287087 4 0 lo0 16384 5114 0 5114 0 0 lo0 16384 127 localhost 5114 0 5114 0 0 Local system status: 3:01AM up 15:55, 1 user, load averages: 0.00, 0.00, 0.00 Mail in local queue: Mail queue is empty Security check: (output mailed separately) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Core dumps on Current Make World this morning
All the machines that I have running Current dumped core at the same place this morning. ===> share/termcap ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder > /dev/null Segmentation fault - core dumped *** Error code 139 Stop in /usr/src/share/termcap. *** Error code 1 For a couple of days now, I haven't been able to use vi because it also dumps core on all the machines except the only one that was able to build world and a new kernel yesterday, just good timing I guess. I haven't seen this on the list. Thanks, ed To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Lucent Orinoco Gold PCCard?
There is definately a trend to lower prices. I just found this. A new intel Intel PRO/Wireless 2011 LAN access point and two pcmcia cards for $699. The access point sounds interesting. I personally would like to use it as a repeater and network bridge. http://www.intel.com/network/products/wireless.htm https://merchant.hibbertco.com/servlet/InteComServlet?SessionID=319728709221315074&OrderID=71803&ItemCnt=1&Adapters=yes ed Doug Ambrisko wrote: > Warner Losh writes: > | In message <[EMAIL PROTECTED]> Doug Ambrisko writes: > | : Well this is what I'm doing with the Aironet stuff. I have a script > | : to flip between modes until it sync's up. I bought the PCMCIA ISA > | : adapter for $25 from a local surplus place. > | > | Does this mean that the an driver can operate in "base station" mode? > > No, just ad-hoc (atleast that's what is published). So on my laptop my > script flips between modes (ad-hoc & infrastructure) until it sync's up > with whatever it can find. I start it out of pccard.conf so it is automatic > on card insertion, reboot or wakeup. > > | : BTW I saw ADDTRON http://www.addtron.com/ has a base station for around > | : $220 that can do 128 bit encryption, has an antenna and is Web administered. > | : I haven't used it but it looks interesting. > | > | I'll have to check this out as well. > > Let us know what you find out. > > Doug A. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
cvs-all@FreeBSD.org
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VIRUS WARNING
WARNING! This mail is generated automatically by virus-scanning software. There was virus found in one or more attachment in e-mail sent by: Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:51 - , with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO M)<=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VIRUS WARNING
WARNING! This mail is generated automatically by virus-scanning software. There was virus found in one or more attachment in e-mail sent by: Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:51 - , with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO M)<=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VIRUS WARNING
WARNING! This mail is generated automatically by virus-scanning software. There was virus found in one or more attachment in e-mail sent by: Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:51 - , with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO M)<=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VIRUS WARNING
WARNING! This mail is generated automatically by virus-scanning software. There was virus found in one or more attachment in e-mail sent by: Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:51 - , with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO M)<=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VIRUS WARNING
WARNING! This mail is generated automatically by virus-scanning software. There was virus found in one or more attachment in e-mail sent by: Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:51 - , with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO M)<=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VIRUS WARNING
WARNING! This mail is generated automatically by virus-scanning software. There was virus found in one or more attachment in e-mail sent by: Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:51 - , with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO M)<=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VIRUS WARNING
WARNING! This mail is generated automatically by virus-scanning software. There was virus found in one or more attachment in e-mail sent by: Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:51 - , with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO M)<=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ALERTE: VIRUS DETECTE DANS UN MESSAGE ENVOYE PAR owner-freebsd-security@FreeBSD.ORG
A L E R T E V I R U S Notre système de détection automatique anti-virus a détecté un virus dans un message qui vous a été envoyé par Peter Wagner <[EMAIL PROTECTED]>. La distribution de ce message a été stoppée. Veuillez vous rapprocher de l'émetteur Peter Wagner <[EMAIL PROTECTED]> pour régler avec lui le problème. *** V I R U S A L E R T Our anti-virus system has detected a virus in an email sent by Peter Wagner <[EMAIL PROTECTED]>. We have stopped the delivery of this email. We invite you to contact Peter Wagner <[EMAIL PROTECTED]> to solve the problem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
VIRUS WARNING
WARNING! This mail is generated automatically by virus-scanning software. There was virus found in one or more attachment in e-mail sent by: Peter Wagner <[EMAIL PROTECTED]> at date: Thu, 2 Nov 2000 09:34:51 - , with subject "US PRESIDENT AND FBI SECRETS =PLEASE VISIT => (http://WWW.2600.CO M)<=". There is list of infected files: Found virus "VBS/LoveLetter.worm" in DOMEO.JPG.vbs Please clean files and resend Your message, Your message was dropped. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
compile failure in current
cd /usr/src/gnu/lib/csu; make depend; make all; make install echo '#include "i386/i386.h"' > tm.h echo '#include "i386/att.h"'>> tm.h echo '#include ' >> tm.h echo '#include "i386/freebsd.h"'>> tm.h echo '#include "i386/perform.h"'>> tm.h rm -f .depend mkdep -f .depend -a-I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I. -DIN_GCC -I/usr/obj/usr/src/i386/usr/include /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c cd /usr/src/gnu/lib/csu; make _EXTRADEPEND cc -Os -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I. -DIN_GCC -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-omit-frame-pointer -I/usr/obj/usr/src/i386/usr/include -g0 -DCRT_BEGIN -c -o crtbegin.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c cc -Os -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I. -DIN_GCC -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-omit-frame-pointer -I/usr/obj/usr/src/i386/usr/include -g0 -DCRT_END -c -o crtend.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c /usr/src/gnu/lib/csu/crtend.c cc: cannot specify -o with -c or -S and multiple compilations *** Error code 1 Stop in /usr/src/gnu/lib/csu. *** Error code 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
(no subject)
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
Subject: Mail::Internet test subject This is a test message that was sent by the test suite of Mail::Internet. Testing. one >From foo four >From bar seven To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
Subject: Mail::Internet test subject This is a test message that was sent by the test suite of Mail::Internet. Testing. one >From foo four >From bar seven To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
Subject: Mail::Internet test subject This is a test message that was sent by the test suite of Mail::Internet. Testing. one >From foo four >From bar seven To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
error in installworld
install -c -s -o root -g wheel -m 4555 -fschg rcp /bin /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" *** Error code 1 Stop in /usr/src/bin/rcp. *** Error code 1 .. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Dr Neuhaus niccy go not recognized
During make of kernel: cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf ../../i4b/layer1/i4b_isic_pnp.c ../../i4b/layer1/i4b_isic_pnp.c:53: warning: #warning "Fix i4b pnp!" Is this a "simple" matter of the right options to config, or does it involve changes to the code? Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #130: Sat Nov 6 18:14:11 CET 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/GINA Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (337.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 67096576 (65524K bytes) avail memory = 61603840 (60160K bytes) Preloaded elf kernel "kernel" at 0xc0357000. VESA: v2.0, 4096k memory, flags:0x1, mode table:0xc00c0e38 (ce38) VESA: S3 Incorporated Trio3D. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: at device 0.0 on pci1 isab0: at device 4.0 on pci0 isa0: on isab0 ata-pci0: at device 4.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 uhci0: irq 9 at device 4.2 on pci0 usb0: on uhci0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ugen0: vendor 0x0553 product 0x0002, rev 1.00/1.00, addr 2 intpm0: at device 4.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped e400 pcm0: irq 5 at device 11.0 on pci0 ed1: irq 10 at device 12.0 on pci0 ed1: address 00:80:ad:50:40:cf, type NE2000 (16 bit) fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 pca0 at port 0x40 on isa0 pca0: PC speaker audio driver unknown0: at port 0x200-0x201,0x202-0x203 irq 11 on isa0 i4b: ISDN call control device attached i4bisppp: 4 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 2 ISDN trace device(s) attached ad0: ATA-4 disk at ata0 as master ad0: 8207MB (16809660 sectors), 16676 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 ad1: ATA-4 disk at ata0 as slave ad1: 6197MB (12692295 sectors), 13431 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 31 depth queue, UDMA33 Creating DISK ad1 Creating DISK wd1 Mounting root from ufs:/dev/wd1s3a To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bsd.lib.mk "@"'s
> Why are many of the build lines in bsd.lib.mk hidden with leading @'s, > so that they don't display in the build? This is useless, it hides > things that go wrong, and hardly belongs here, it seems to me. I like extreme verbosity too, but some don't :-) PMake is supposed to have a .SHELL: pseudo-target that allows one to specify how to make shell commands "quiet". If one could figure out how to use that, it would be trivial to provide a knob for this. I couldn't make .SHELL work though; consult /usr/src/usr.bin/make/job.c if you're interested. I'd like to know how to disable "quiet" commands too... Cheers, Jerry Hicks wghi...@bellsouth.net To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: /var/db/pkg/.mkversion
On Thu, 1 Apr 1999, Chuck Robey wrote: > On Thu, 1 Apr 1999, Richard Wackerbarth wrote: > Your statement "Nobody said cross compilation is easy :-)" By this smiley, I mean to infer that it is far from easy. > you're the ONLY one to demand it. OK, maybe even "demand" is wrong > If you were talking about the FreeBSD sources themselves, everything I > said is out the window, because we *do* have total control I think that you have missed the entire point of what I am advocating. Within the ports Makefiles (and .mk), we DO have control. We SHOULD make certain that we do NOT REPEAT the past errors of using the wrong parameter when we CAN do it correctly. IOW, don't box the future development in by building a mechanism which works ONLY if HOST == TARGET. Provide a mechanism which can provide TARGET independent from HOST, but defaulting to the same value. In the code which we write for the FreeBSD tree, including /usr/ports, use the correct context. I ask this because the mechanism for ports SHOULD be the same mechanism that is used for OS builds. In the realm of OS building, I think that we are making progress toward cross build capability. I would hate to see this thing for ports be a step backward. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Which DHCP client
I do not dispute that he "likes" the WIDE client. However, his choice seems to be based on familarity rather than CURRENT technical evaluation. I have (recently) tried both clients. For the simple case, both work satisfactorily. The ISC client/server (pl10) builds right out of the box. I prefer it because of the additional flexability it provides for the non-trivial case. On Tue, 9 Feb 1999, Jordan K. Hubbard wrote: > I personally am ambivalent about which client is chosen just so > long as *a* client is chosen. I agree that this is the important issue. If someone will agree to commit the files, I'd be happy to supply the pieces for the ISC DHCP2 client to drop in. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
I am glad to see some SOME version of the dhcp client included in base floppies. However, I must take exception to David's choice for any purpose other than single floppy situations. Although it is somewhat larger, the ISC dhcp2 client has significantly more flexability WRT options beyond the bare basics. I would recommend that the default client on HD based systems be the ISC client because of that flexability. Further, the assertion that it is easier to configure the WIDE client is WRONG. The ISC CLIENT requires NO configuration. I don't see how anything can be simpler. :-) Unfortunately, David persists in spreading this mis-information. On, 8 Feb 1999, David O'Brien wrote: > I am planning on adding the Wide-DHCP client to src/contrib/ and > src/sbin/ in a few days. > > I have it bmaked and ready go to. I have choosen the WIDE client because > it is much smaller space-wise than the ISC client and its configuration > is simplier. > > The plan is to make a boot floppy / boot CDROM with a DHCP client on it. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
Remember that the client, relay, and server are all independent items. Each MUST meet the same RFC specification. On Tue, 9 Feb 1999, Andreas Braukmann wrote: > On Mon, Feb 08, 1999 at 02:28:20PM -0800, David O'Brien wrote: > > I am planning on adding the Wide-DHCP client to src/contrib/ and > I'm mostly interested in choosing the server part. In the past I > deployed only the wide-dhcp server from the ports collection; but > only because I somehow decided to test the wide-dhcp before the isc one. > > A few days ago I had a look (triggered by a piece of samba documentation) > at isc-dhcp and found the configuration syntax somewhat more user friendly. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: adding DHCP client to src/contrib/
Wrong! The dhcp client is ESSENTIAL to boot floppies for modern use. As for "bloat", one man's bloat is another's essential material :-( On Mon, 8 Feb 1999, Steve Kargl wrote: > Joe Abley wrote: > > On Mon, Feb 08, 1999 at 02:28:20PM -0800, David O'Brien wrote: > > > I am planning on adding the Wide-DHCP client to src/contrib/ > > Content-Type: text/BLOAT > > These should be left has ports. > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Memory usage weirdness
What would cause more memory to be considered in the active state than
could be accounted for by running processes?
My main machine (running -current as of the afternoon of Jan 25) has
somewhere between 80 and 100 megs of memory listed as used via ps and top
(which, I presume doesn't take in to account shared executable pages, but
does include the 16 megs the X server is mapping on the video card), yet
both top and vmstat show over 170 megs worth of memory being active.
Furthermore, if I kill off my X session and associated processes, active
memory usage doesn't decrease, even after 5 or more minutes. According to
the vmstat manpage, 20 seconds later, the pages released would be
considered inactive.
Since I was curious, I wrote a small program which scanned the contents of
/proc/*/map and added up the amount of memory supposedly being used by
current processes, to make sure top and ps weren't confused. Sure enough,
the figure was far less than the amount that was being listed active at any
given time, by on the order of anywhere between 50% and 75%.
Is this normal, or should I look for some process that's thrashing through
vast amounts of pages in short periods of time?
(For those who wish to look at it, I've attached output from various
commands such as vmstat, top, ps, the contents of /proc/*/map, plus my
kernel config file)
--
/* Dan Root - XTEA cipher */ static unsigned D=0x9E3779B9,l=0xC6EF3720,s;
/* t=64bit text, k=128bit key */ #define m(x,y) ((x<<4^x>>5)+(x^s)+k[s>>y&3])
void enc(int*t,int*k){for(s=0;s!=+l;){t[0]+=m(t[1],0);s+=D;t[1]+=m(t[0],11);}}
void dec(int*t,int*k){for(s=-l;s==0;){t[1]-=m(t[0],11);s-=D;t[0]-=m(t[1],0);}}
Memory statistics by bucket size
Size In Use Free Requests HighWater Couldfree
16 180 76 849191280 0
32 411 4581 325012 640 6290
64 9208 30161154010 320 1103
128 824 6888 184390 160 28831
256 8504152 317570 80939
512 36 4139 40 0
1K 139281 12795 20 1159
2K 41 5451 10165
4K 11 1 1530 5 0
8K5 26 4182 5 3885
16K2 0 2 5 0
32K3 0 3 5 0
64K7 0 7 5 0
128K1 0 1 5 0
Memory usage type by bucket size
Size Type(s)
16 kld, devbuf, temp, proc, sysctl, shm, soname, pcb, vnodes,
ether_multi, routetbl
32 kld, sigio, devbuf, temp, pgrp, subproc, sysctl, SWAP, soname, pcb,
cluster_save buffer, vnodes, ifaddr, ether_multi, routetbl, in_multi,
newblk, bmsafemap, indirdep, freefrag, freefile, diradd, mkdir,
dirrem
64 file, lockf, namecache, devbuf, temp, session, iov, shm, soname, pcb,
cluster_save buffer, vnodes, ifaddr, routetbl, pagedep, allocdirect,
allocindir
128 kld, timecounter, file desc, zombie, namecache, devbuf, temp, proc,
cred, ttys, soname, cluster_save buffer, vnodes, ifaddr, routetbl,
inodedep, freeblks, ZONE
256 file desc, devbuf, temp, subproc, vnodes, routetbl, NFS srvsock,
NFS daemon, newblk, FFS node
512 kld, devbuf, temp, proc, ioctlops, BIO buffer, mount, UFS mount
1K kld, devbuf, temp, BIO buffer, NQNFS Lease
2K devbuf, ttys, pcb, BIO buffer, UFS mount, mbuf
4K kld, devbuf, temp, ioctlops, UFS mount
8K kld, temp, pagedep, indirdep, UFS mount
16K devbuf
32K devbuf, temp, SWAP
64K ISOFS mount, kld, NFS hash, inodedep, UFS ihash, UFS quota,
VM pgdata
128K namecache
Memory statistics by type Type Kern
Type InUse MemUse HighUse Limit Requests Limit Limit Size(s)
ISOFS mount 164K 64K 40960K10 0 64K
kld1679K 84K 40960K 390 0
16,32,128,512,1K,4K,8K,64K
timecounter 5 1K 1K 40960K50 0 128
file desc7210K 12K 40960K619720 0 128,256
file 18312K 15K 40960K 6032450 0 64
sigio 2 1K 1K 40960K 170 0 32
zombie 0 0K 1K 40960K618180 0 128
lockf10 1K 2K 40960K583640 0 64
namecache 8938 688K784K 40960K 2688050 0 64,128,128K
devbuf 252 133K133K 40960K 7030 0
16,32,64,128,256,512,1K,2K,4K,16K,32K
temp 15731K 42K 40960K572700 0
16,32,64,128,256,512,1K,4K,8K,32K
pgrp38 2K 2K 40960K 9330 0 32
session33 3K 3K 40960K 5670 0 64
proc14 2K 2K 40960K 5900 0 16,128,512
subproc77
Re: C++ compliler unable to produce excutables
> > Do you have egcs or gcc-2.8 or anything else installaed that installs > /usr/local/bin/g++? > yes, that's the one I really recently installed I was suspecious about it, but now you confirmed it. > Such extra compilers from ports tend to break. Make sure you use > /usr/bin/g++. > Thanks -- - MAY THE FORCE BE WITH YOU.~o .^. ___ o~ .00 ) Static Email : osiris2...@yahoo.com /| o~ /)( Bouncing Email : r...@isis.dynip.com / | | \ Web Site : http://isis.dynip.com:80 (Frames) ___/ | / \ Anon FTP Site : ftp://isis.dynip.com:21 (anonymous) | /''___/ / | Gopher Site: gopher://isis.dynip.com:70 | /'''/___/| Network News : isis.dynip.com (Read, Post, Xfer) __|/'''/ Mailing Lists : majord...@isis.dynip.com (public) pgp key: finger r...@isis.dynip.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Broken make world
I got the following when trying a new make world (1-17-99): cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/if.c cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/inet.c cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/main.c cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.bin/netstat/mbuf.c /usr/src/usr.bin/netstat/mbuf.c:71: `MT_RTABLE' undeclared here (not in a function) /usr/src/usr.bin/netstat/mbuf.c:71: initializer element for `mbtypes[4].mt_type' is not constant *** Error code 1 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
