Re: /usr/libexec/ld-elf.so.1: /usr/lib/libutil.so.3: Undefined symbol __stdoutp

2001-12-24 Thread Ruslan Ermilov

On Mon, Dec 24, 2001 at 12:03:34AM -0700, M. Warner Losh wrote:
  Warner, could you please add __stdoutp to the 20010919 entry, and
  a hint to put COMPAT4X=true to /etc/make.conf to the 20010924 entry?
 
 Actually, you only need the first one.  You don't need COMPAT4X=true
 all the time, so I'm a little reluctant to include that.  Lemme know
 how I can improve what I just committed.
 
Not quite true.  COMPAT4X libraries are occasionally get updated,
and if you have 4.x applications to continue running, you'd better
to be safe than sorry, and add COMPAT4X=true to /etc/make.conf, so
that installworld installs them on every run.  The instructions in
20010924 are for manually installing these libraries, and only work
for the i386 arch.  I'd suggest that we put something like this:

: 20010924:
:   The buildworld has been fixed.  You may need to install
:   the 4.x compatibility libraries for some old binaries
:   to work.  Add COMPAT4X=true to your /etc/make.conf to
:   get them installed on every installworld, or execute the
:   following to get them installed only once:
:   cd src/lib/compat/compat4x.arch
:   make all install
:   You will see ``__stdoutp undefined'' until you do this.


Cheers,
-- 
Ruslan Ermilov  Oracle Developer/DBA,
[EMAIL PROTECTED]   Sunbay Software AG,
[EMAIL PROTECTED]  FreeBSD committer,
+380.652.512.251Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Dropping bsd.man.mk support from bsd.kmod.mk

2001-12-24 Thread Ruslan Ermilov

On Mon, Dec 24, 2001 at 12:05:39AM -0700, M. Warner Losh wrote:
  I'd like to drop bsd.man.mk support from bsd.kmod.mk,
  because I was told by someone (peter?) that this is
  the right direction.  :-)
 
 We use it slightly at Timing Solutions, but it is more of a pain than
 a blessing.  More of our module Makefiles have NOMAN than don't, by a
 wide margin.
 
So, does it mean you are objecting or not?  :-)

And now I recall.  Peter told me that at some
point there will be no sys/modules at all.


Cheers,
-- 
Ruslan Ermilov  Oracle Developer/DBA,
[EMAIL PROTECTED]   Sunbay Software AG,
[EMAIL PROTECTED]  FreeBSD committer,
+380.652.512.251Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: 21 in /bin/sh

2001-12-24 Thread 豊永 達人

From: Mike Barcroft [EMAIL PROTECTED]
Subject: Re: 21 in /bin/sh
Date: Mon, 24 Dec 2001 01:42:26 -0500

 KT Sin [EMAIL PROTECTED] writes:
  Just ran make world this morning and 21 fd redirection stopped working
  for /bin/sh.
  
  $ ls /bad/file  /dev/null 21
  ls: /bad/file: No such file or directory
  
  21 is used extensively in the /etc/rc* bootup scripts. Now, the bootup
  screen is cluttered with unwanted messages.
  
  Any idea?
 
 AFAIK, this was fixed.  Check the commit logs for sh(1).
 
According to the CVSROOT/commitlogs/bin, the problematic version of 
redir.c is still in CVS...

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Intel 82544GC Gigabit support?

2001-12-24 Thread Roy Sigurd Karlsbakk

  does anyone know if this is/will be supported?

 I believe it is supported by the em driver, which has been in
 -current for a few weeks and was recently merged into -stable.

Thanks. It works!

--
Roy Sigurd Karlsbakk, MCSE, MCNE, CLS, LCA

Computers are like air conditioners.
They stop working when you open Windows.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Logitech iFeel Optical USB Mouse cannot be attached.

2001-12-24 Thread Raman Ng

The following is the output of usbdevs -v

# usbdevs -v
Controller /dev/usb0:
addr 1: self powered, config 1, UHCI root hub(0x), VIA(0x), rev
0x0100
 port 1 powered
 port 2 powered

Regards,
Raman

- Original Message -
From: Doug White [EMAIL PROTECTED]
To: Jon Parise [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Monday, December 24, 2001 2:24 AM
Subject: Re: Logitech iFeel Optical USB Mouse cannot be attached.


 Dropping -stable crosspost.

 For those of you with this mouse -- we really need the output of 'usbdevs
 -v' with the mouse attached.

 I'm betting that this isn't a standard USB mouse and requires a special,
 proprietary driver. :(

 Doug White|  FreeBSD: The Power to Serve
 [EMAIL PROTECTED] |  www.FreeBSD.org


_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



netstat -f inet broken ?

2001-12-24 Thread Martin Blapp


Hi All,

As we just have noted, there is no output anymore for
netstat -f inet. Has the support been dropped ?

Also there are only unix domain sockets in the normal
netstat output. I cannot see any tpc4 connections anymore.

I noted this in 4.5 PRERELEASE too. It used to work in
4.3 RELEASE and 4.4 RELEASE.

So it got broken trough a MFC between 4.4 and 4.5.

I think this is important for security reasons !

Martin

Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
--
Improware AG, UNIX solution and service provider
Zurlindenstrasse 29, 4133 Pratteln, Switzerland
Phone: +41 061 826 93 00: +41 61 826 93 01
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: netstat -f inet broken ?

2001-12-24 Thread Wilko Bulte

On Mon, Dec 24, 2001 at 02:02:00PM +0100, Martin Blapp wrote:
 
 Hi All,
 
 As we just have noted, there is no output anymore for
 netstat -f inet. Has the support been dropped ?

I also don't get any output.

 Also there are only unix domain sockets in the normal
 netstat output. I cannot see any tpc4 connections anymore.

Well, I do

wb ~: netstat -a
Active Internet connections (including servers)
Proto Recv-Q Send-Q  Local Address  Foreign Address(state)
tcp4   0  0  freebie.1520   mass.dis.org.smtp  SYN_SENT
tcp4   0  0  *.5801 *.*LISTEN
tcp4   0  0  *.5901 *.*LISTEN
tcp4   0  0  *.6001 *.*LISTEN
tcp4   0  0  *.cvspserver   *.*LISTEN
...
udp4   0  0  *.1627 *.*
udp4   0  0  *.1011 *.*


Or do you mean:

wb ~: netstat
Active Internet connections
Proto Recv-Q Send-Q  Local Address  Foreign Address(state)
tcp4   0  0  freebie.1520   mass.dis.org.smtp  SYN_SENT
Active UNIX domain sockets
Address  Type   Recv-Q Send-QInode Conn Refs  Nextref Addr
d6054800 stream  0  00 d60547c000
/tmp/.X11-unix/X0
d60547c0 stream  0  00 d605480000
d6054780 stream  0  00 d60546c000
/tmp/.X11-unix

etc ?

 I noted this in 4.5 PRERELEASE too. It used to work in
 4.3 RELEASE and 4.4 RELEASE.

wb ~: uname -a
FreeBSD freebie.xs4all.nl 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE #1: Sun Dec
23 17:19:34 CET 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FREEBIE
i386

-- 
|   / o / /_  _ email:  [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, The Netherlands 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: netstat -f inet broken ?

2001-12-24 Thread carl

On Mon, Dec 24, 2001 at 02:02:00PM +0100, Martin Blapp wrote:
 Hi All,
 
 As we just have noted, there is no output anymore for
 netstat -f inet. Has the support been dropped ?

Incorrect.

 Also there are only unix domain sockets in the normal
 netstat output. I cannot see any tpc4 connections anymore.

We'll get to that.

 I noted this in 4.5 PRERELEASE too. It used to work in
 4.3 RELEASE and 4.4 RELEASE.

It still works.

 
 So it got broken trough a MFC between 4.4 and 4.5.

No.

 I think this is important for security reasons !

I don't because there is no issue. You need to rebuild your userland because
of changes to the network code. That's all.
-- 
Carl Schmidt

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: netstat -f inet broken ?

2001-12-24 Thread carl

On Mon, Dec 24, 2001 at 02:01:19PM +0100, Wilko Bulte wrote:
 On Mon, Dec 24, 2001 at 02:02:00PM +0100, Martin Blapp wrote:
  
  Hi All,
  
  As we just have noted, there is no output anymore for
  netstat -f inet. Has the support been dropped ?
 
 I also don't get any output.

carbon netstat -f inet
Active Internet connections
Proto Recv-Q Send-Q  Local Address  Foreign Address(state)
tcp4   0  0  Carbon.6667*.*LISTEN
tcp4   0  0  Carbon.http*.*LISTEN
tcp4   0  0  Carbon.smtp*.*LISTEN
tcp4   0  0  Carbon.ssh *.*LISTEN

Etc.

Works fine.

FreeBSD carbon.slackerbsd.org 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE #0: Mon Dec 24 
03:29:03 EST 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CARBON  i386
-- 
Carl Schmidt

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: netstat -f inet broken ?

2001-12-24 Thread Wilko Bulte

On Mon, Dec 24, 2001 at 08:06:06AM -0500, [EMAIL PROTECTED] wrote:
 On Mon, Dec 24, 2001 at 02:01:19PM +0100, Wilko Bulte wrote:
  On Mon, Dec 24, 2001 at 02:02:00PM +0100, Martin Blapp wrote:
   
   Hi All,
   
   As we just have noted, there is no output anymore for
   netstat -f inet. Has the support been dropped ?
  
  I also don't get any output.
 
 carbon netstat -f inet
 Active Internet connections
 Proto Recv-Q Send-Q  Local Address  Foreign Address(state)
 tcp4   0  0  Carbon.6667*.*LISTEN
 tcp4   0  0  Carbon.http*.*LISTEN
 tcp4   0  0  Carbon.smtp*.*LISTEN
 tcp4   0  0  Carbon.ssh *.*LISTEN
 
 Etc.
 
 Works fine.

Nope:

wb ~: netstat -f inet
wb ~: 

but

wb ~: netstat -a
Active Internet connections (including servers)
Proto Recv-Q Send-Q  Local Address  Foreign Address(state)
tcp4   0  0  *.5801 *.*LISTEN
tcp4   0  0  *.5901 *.*LISTEN
tcp4   0  0  *.6001 *.*LISTEN
...

-- 
|   / o / /_  _ email:  [EMAIL PROTECTED]
|/|/ / / /(  (_)  Bulte Arnhem, The Netherlands 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Solved: netstat -f inet broken ?

2001-12-24 Thread Martin Blapp


 Works fine.

Hi,

I guess the world is not 100% up to date. I seems that I just got
this after running a cvsup 2 hours later after the initial one.

Shit happens.

Thanks for the answer and sorry.

Martin




To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Brand New AAA Credit! -oari

2001-12-24 Thread sorby2777
Title: Instantly Get a Brand New AAA Credit Profile in 24 Hours!





Here's How You Can Have
a Brand New
Credit Profile in 24 Hours!
The
Best Part is... It's 100% Legal, 100% Ethical, and Fully GUARANTEED!

Dear Friend,
Do you have bad credit,
judgements, bankruptcies or
any other credit problems?
Does it seem like your bad
credit is holding
you back from qualifying for a major
credit card, car loan,
or even a department store card?
Are you sick of the
embarrassment of being rejected at
your attempts to get
any credit at all? If so... I've got
some extremely good
news for you.


I Will
Show You Precisely How to Get a New, Separate, Clean
Credit
File... and it will be Clear of Any Past Credit History!
And it's
100% LEGAL!





It doesn't
matter, if you have judgements!



It doesn't
matter, if you've filed for bankruptcy!



It doesn't
matter, if you've been foreclosed!



It doesn't
matter, if you have a tax lien!



It doesn't
matter, if have been a slow payer in the past!



It
Doesn't Matter, Because Your Credit File Will Be Completely
New
And Completely Independent Of Any Negative Past File!
With my kit...within
the next 60 days, you will quickly and easily





Get ALL Major Credit Cards



Learn Basic and Advanced
Credit Billing Techniques



Get Bank Loans FAST and
Simple



Get Mortgages NOW



Have AAA Credit on "Your
Brand New File" in 30-60 Days



Get INSTANT Credit From
Real Department Stores



Car Loans FAST and SIMPLE


And much, much more!


CLICK HERE TO LEARN MORE!


This email was sent to you in full compliance with all existing and proposed email legislation.
You may automatically remove yourself from any future mailings by clicking here. The reply address on this email was activeat the time this email was sent.








Re: netstat -f inet broken ?

2001-12-24 Thread Robert Watson


On Mon, 24 Dec 2001, Martin Blapp wrote:

 As we just have noted, there is no output anymore for netstat -f inet.
 Has the support been dropped ? 
 
 Also there are only unix domain sockets in the normal netstat output. I
 cannot see any tpc4 connections anymore. 
 
 I noted this in 4.5 PRERELEASE too. It used to work in 4.3 RELEASE and
 4.4 RELEASE. 
 
 So it got broken trough a MFC between 4.4 and 4.5. 
 
 I think this is important for security reasons ! 

Verify that your userland and kernel are in sync, and let us know if the
problem persists.  A few people ran into this, but it cleared up for all
of them when they re-sync'd userland and kernel.

Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED]  NAI Labs, Safeport Network Services



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Can we use this ? Linux Interrupt Latency benchmark

2001-12-24 Thread Martin Blapp


Hi all,

ftp://ftp.suse.com/pub/people/andrea/lil

Maybe we can port this and use it to see where the
latency actually happens ?

See also this posting:

http://groups.google.com/groups?q=latency+interrupt+linuxhl=enrnum=5selm=Pine.LNX.3.96.980827184103.250A-10%40dragon.bogus


Martin

Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
--
Improware AG, UNIX solution and service provider
Zurlindenstrasse 29, 4133 Pratteln, Switzerland
Phone: +41 061 826 93 00: +41 61 826 93 01
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Add USB mouse to sysinstall

2001-12-24 Thread William Ward

Thanks Joe.  I managed to screw up my first patch posted to any
mailing list.  Hehe.  Maybe it's supposed to work that way.

--- menus.c.old Mon Dec 24 13:54:18 2001
+++ menus.c Mon Dec 24 13:55:49 2001
@@ -387,6 +387,8 @@
dmenuVarCheck, dmenuSetVariable, NULL, VAR_MOUSED_PORT =/dev/cuaa3 },
   { 6 BusMouse,  Logitech, ATI or MS bus mouse (/dev/mse0), 
dmenuVarCheck, dmenuSetVariable, NULL, VAR_MOUSED_PORT =/dev/mse0 },
+  { 7 USBMouse,  USB Mouse (/dev/ums0), 
+   dmenuVarCheck, dmenuSetVariable, NULL, VAR_MOUSED_PORT =/dev/ums0 },
   { NULL } },
 };

/William

On Mon, Dec 24, 2001 at 12:17:39PM -0800, Joe Kelsey wrote:
 William Ward writes:
   Is /dev/ums0 ommitted from sysinstall for any particular reason?  This patch
   adds /dev/ums0 to sysinstall::Configure-Mouse-Port.
   
   Patch to /usr/src/release/sysinstall/menus.c.
   
   *** menus.c Mon Dec 24 13:55:49 2001
   --- menus.c.old Mon Dec 24 13:54:18 2001
   ***
   *** 387,394 
   dmenuVarCheck, dmenuSetVariable, NULL, VAR_MOUSED_PORT =/dev/cuaa3 },
   { 6 BusMouse, Logitech, ATI or MS bus mouse (/dev/mse0), 
   dmenuVarCheck, dmenuSetVariable, NULL, VAR_MOUSED_PORT =/dev/mse0 },
   -   { 7 USBMouse, USB Mouse (/dev/ums0), 
   -   dmenuVarCheck, dmenuSetVariable, NULL, VAR_MOUSED_PORT =/dev/ums0 },
   { NULL } },
 };
 
   --- 387,392 
   
 
 Unfortunately, you are apparantly unaware how the diff utility works.
 The patch you posted *removes* /dev/ums0.  The correct way to run diff
 is:
 
 diff -u old new
 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Add USB mouse to sysinstall

2001-12-24 Thread Eric Melville

 Is /dev/ums0 ommitted from sysinstall for any particular reason?  This patch
 adds /dev/ums0 to sysinstall::Configure-Mouse-Port.

This is intentional. In the case of a usb mouse, usbd is responsible for
starting moused.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Add USB mouse to sysinstall

2001-12-24 Thread William Ward

A.  Thanks for the answer.

/William

On Mon, Dec 24, 2001 at 12:27:52PM -0800, Eric Melville wrote:
  Is /dev/ums0 ommitted from sysinstall for any particular reason?  This patch
  adds /dev/ums0 to sysinstall::Configure-Mouse-Port.
 
 This is intentional. In the case of a usb mouse, usbd is responsible for
 starting moused.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Add USB mouse to sysinstall

2001-12-24 Thread David Taylor

On Mon, 24 Dec 2001, William Ward wrote:
 A.  Thanks for the answer.
 
 /William

You know, replying below the quoted post makes it a lot easier to reply to
both peoples replies, without having to be adept at reading backwards...
 
 On Mon, Dec 24, 2001 at 12:27:52PM -0800, Eric Melville wrote:
   Is /dev/ums0 ommitted from sysinstall for any particular reason?  This patch
   adds /dev/ums0 to sysinstall::Configure-Mouse-Port.
  
  This is intentional. In the case of a usb mouse, usbd is responsible for
  starting moused.

However, perhaps sysinstall should tell the user that if they have a USB
mouse, they need do nothing, insetad of think 'Uhh, I don't recognise any of
these, lets try this one'  and getting it wrong.

-- 
David Taylor
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Add USB mouse to sysinstall

2001-12-24 Thread Eric Melville

 However, perhaps sysinstall should tell the user that if they have a USB
 mouse, they need do nothing, insetad of think 'Uhh, I don't recognise any of
 these, lets try this one'  and getting it wrong.

Before this menu is presented, sysinstall asks if there is a usb mouse or
not. I suppose it could be a bit more verbose about what it is doing and
why, but if the questions are simply answered as they are presented the
user will end up with what they need.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: KSE changes available

2001-12-24 Thread Glenn Gombert


 In case anyone is in interested I have put a patched set of source files
from the latest changes below on my FreeBSD Web page at:

  freebsd.imatowns.com/kse3 

 There is the latest set of 'diffs' from the link below broken out for
each  individual file too, along with the 'unpatched' source files in
three different directories:

  /unpatched-src
  /patches/
  /patched-src

 I have not tried to compile these yet, just have got the soruces code
patches finished :)

Glenn G.

 Julian Elischer [EMAIL PROTECTED] wrote:
 The latest round of KSE changes are available from
 
 http://www.freebsd.org/~julian/thediff
 
 These changes represent a work in progress.
 Basically the state is:
 
 GENERIC compiles
 (I don't know yet if it runs but I doubt it.)
 The following changes have been made:
 The 'thread' structure is no longer a built-in part of the proc structure.
 There is an infrastructure to independently crfeate and reap threads.
 The infrastructure is used to create and destroy the 'usual' single
 thread
 associated with each process. It should eventually be used to create
 more
 threads per process..
 The 'state' variable associated with the process has been raped and
 
 now each thread, and process and KSE has it's own state.
 
 This last part is the bit that is broken because a LOT of the kernel
 doesn't expect the state of a thread to be spread across several
 structures.
 
 For example:
  switch (p-p_stat) {
   case SRUN:
 ...
   case SSTOP:
 ..
 
 has to be completely rewritten because
 SRUN is a per-thread property
 and is accessed as:
   FOREACH_THREAD_IN_PROC(p, td) {
   switch(td-td_state) {
   case TDS_RUNNING:
   case TDS_RUNQ:
   case TDS_SLP:
   ...
   }
   ...
   }
 
 wheras STOP is still a per-process state.
 
 obviously any code that tries to assume the same scope for these tow
 states will break violently in the new code.
 
 I have replaced some of the logic where there seems to be a simple
 answer,
 but there are plenty of places where the answer is not clear.
 
 Such places include signal delivery,
 selection of process (thread?) to deliver a signal to,
 collection of scheduling statistics, 
 handling FORK run by one of several threads,
 handling EXIT run by one of several threads,
 handling when the user types ^Z and suspends the process.
 
 If anyone is feeling adventurous they can stat with the code that is
 there 
 and start fixing things :-)
 send me patches but let me know ahead of time what you will be doing
 so we don't duplicate, and so I can send you notes on where I'm going
 in
 that part..
 
 I'll be working on the scheduler for the next few days I think.
 
 Note: if ((p-p_flag  P_KSES) == 0) a process should act exactly as
 it
 does now.. :-)
 
 REGARDS JULIAN
 (bloody capslock key)
 
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
 

__
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: KSE changes available

2001-12-24 Thread Robert Watson

For those of us that live in P4-land already, it's just the head of the
KSE branch?  Also, for those that don't, this is also available via
cvsup10.

Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED]  NAI Labs, Safeport Network Services

On Fri, 21 Dec 2001, Julian Elischer wrote:

 The latest round of KSE changes are available from
 
 http://www.freebsd.org/~julian/thediff
 
 These changes represent a work in progress.
 Basically the state is:
 
 GENERIC compiles
 (I don't know yet if it runs but I doubt it.)
 The following changes have been made:
 The 'thread' structure is no longer a built-in part of the proc structure.
 There is an infrastructure to independently crfeate and reap threads.
 The infrastructure is used to create and destroy the 'usual' single thread
 associated with each process. It should eventually be used to create more
 threads per process..
 The 'state' variable associated with the process has been raped and 
 now each thread, and process and KSE has it's own state.
 
 This last part is the bit that is broken because a LOT of the kernel
 doesn't expect the state of a thread to be spread across several
 structures.
 
 For example:
  switch (p-p_stat) {
   case SRUN:
 ...
   case SSTOP:
 ..
 
 has to be completely rewritten because
 SRUN is a per-thread property
 and is accessed as:
   FOREACH_THREAD_IN_PROC(p, td) {
   switch(td-td_state) {
   case TDS_RUNNING:
   case TDS_RUNQ:
   case TDS_SLP:
   ...
   }
   ...
   }
 
 wheras STOP is still a per-process state.
 
 obviously any code that tries to assume the same scope for these tow
 states will break violently in the new code.
 
 I have replaced some of the logic where there seems to be a simple answer,
 but there are plenty of places where the answer is not clear.
 
 Such places include signal delivery,
 selection of process (thread?) to deliver a signal to,
 collection of scheduling statistics, 
 handling FORK run by one of several threads,
 handling EXIT run by one of several threads,
 handling when the user types ^Z and suspends the process.
 
 If anyone is feeling adventurous they can stat with the code that is there 
 and start fixing things :-)
 send me patches but let me know ahead of time what you will be doing
 so we don't duplicate, and so I can send you notes on where I'm going in
 that part..
 
 I'll be working on the scheduler for the next few days I think.
 
 Note: if ((p-p_flag  P_KSES) == 0) a process should act exactly as it
 does now.. :-)
 
 REGARDS JULIAN
 (bloody capslock key)
 
 
 
 
 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: KSE changes available

2001-12-24 Thread Julian Elischer

What is at the head of the branch in P4 is a little incomplete while what
is in thepatch file was taken at a moment just before I broke it all again
:)


On Mon, 24 Dec 2001, Robert Watson wrote:

 For those of us that live in P4-land already, it's just the head of the
 KSE branch?  Also, for those that don't, this is also available via
 cvsup10.
 
 Robert N M Watson FreeBSD Core Team, TrustedBSD Project
 [EMAIL PROTECTED]  NAI Labs, Safeport Network Services
 
 On Fri, 21 Dec 2001, Julian Elischer wrote:
 
  The latest round of KSE changes are available from
  
  http://www.freebsd.org/~julian/thediff
  
  These changes represent a work in progress.
  Basically the state is:
  
  GENERIC compiles
  (I don't know yet if it runs but I doubt it.)
  The following changes have been made:
  The 'thread' structure is no longer a built-in part of the proc structure.
  There is an infrastructure to independently crfeate and reap threads.
  The infrastructure is used to create and destroy the 'usual' single thread
  associated with each process. It should eventually be used to create more
  threads per process..
  The 'state' variable associated with the process has been raped and 
  now each thread, and process and KSE has it's own state.
  
  This last part is the bit that is broken because a LOT of the kernel
  doesn't expect the state of a thread to be spread across several
  structures.
  
  For example:
   switch (p-p_stat) {
  case SRUN:
  ...
  case SSTOP:
  ..
  
  has to be completely rewritten because
  SRUN is a per-thread property
  and is accessed as:
  FOREACH_THREAD_IN_PROC(p, td) {
  switch(td-td_state) {
  case TDS_RUNNING:
  case TDS_RUNQ:
  case TDS_SLP:
  ...
  }
  ...
  }
  
  wheras STOP is still a per-process state.
  
  obviously any code that tries to assume the same scope for these tow
  states will break violently in the new code.
  
  I have replaced some of the logic where there seems to be a simple answer,
  but there are plenty of places where the answer is not clear.
  
  Such places include signal delivery,
  selection of process (thread?) to deliver a signal to,
  collection of scheduling statistics, 
  handling FORK run by one of several threads,
  handling EXIT run by one of several threads,
  handling when the user types ^Z and suspends the process.
  
  If anyone is feeling adventurous they can stat with the code that is there 
  and start fixing things :-)
  send me patches but let me know ahead of time what you will be doing
  so we don't duplicate, and so I can send you notes on where I'm going in
  that part..
  
  I'll be working on the scheduler for the next few days I think.
  
  Note: if ((p-p_flag  P_KSES) == 0) a process should act exactly as it
  does now.. :-)
  
  REGARDS JULIAN
  (bloody capslock key)
  
  
  
  
  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: KSE changes available

2001-12-24 Thread Julian Elischer

what is currently there will probably not compile
well, it might compile but I'd be amazed if it ran..


On Mon, 24 Dec 2001, Glenn Gombert wrote:

 
  In case anyone is in interested I have put a patched set of source files
 from the latest changes below on my FreeBSD Web page at:
 
   freebsd.imatowns.com/kse3 
 
  There is the latest set of 'diffs' from the link below broken out for
 each  individual file too, along with the 'unpatched' source files in
 three different directories:
 
   /unpatched-src
   /patches/
   /patched-src
 
  I have not tried to compile these yet, just have got the soruces code
 patches finished :)
 
 Glenn G.
 
  Julian Elischer [EMAIL PROTECTED] wrote:
  The latest round of KSE changes are available from
  
  http://www.freebsd.org/~julian/thediff
  
  These changes represent a work in progress.
  Basically the state is:
  
  GENERIC compiles
  (I don't know yet if it runs but I doubt it.)
  The following changes have been made:
  The 'thread' structure is no longer a built-in part of the proc structure.
  There is an infrastructure to independently crfeate and reap threads.
  The infrastructure is used to create and destroy the 'usual' single
  thread
  associated with each process. It should eventually be used to create
  more
  threads per process..
  The 'state' variable associated with the process has been raped and
  
  now each thread, and process and KSE has it's own state.
  
  This last part is the bit that is broken because a LOT of the kernel
  doesn't expect the state of a thread to be spread across several
  structures.
  
  For example:
   switch (p-p_stat) {
  case SRUN:
  ...
  case SSTOP:
  ..
  
  has to be completely rewritten because
  SRUN is a per-thread property
  and is accessed as:
  FOREACH_THREAD_IN_PROC(p, td) {
  switch(td-td_state) {
  case TDS_RUNNING:
  case TDS_RUNQ:
  case TDS_SLP:
  ...
  }
  ...
  }
  
  wheras STOP is still a per-process state.
  
  obviously any code that tries to assume the same scope for these tow
  states will break violently in the new code.
  
  I have replaced some of the logic where there seems to be a simple
  answer,
  but there are plenty of places where the answer is not clear.
  
  Such places include signal delivery,
  selection of process (thread?) to deliver a signal to,
  collection of scheduling statistics, 
  handling FORK run by one of several threads,
  handling EXIT run by one of several threads,
  handling when the user types ^Z and suspends the process.
  
  If anyone is feeling adventurous they can stat with the code that is
  there 
  and start fixing things :-)
  send me patches but let me know ahead of time what you will be doing
  so we don't duplicate, and so I can send you notes on where I'm going
  in
  that part..
  
  I'll be working on the scheduler for the next few days I think.
  
  Note: if ((p-p_flag  P_KSES) == 0) a process should act exactly as
  it
  does now.. :-)
  
  REGARDS JULIAN
  (bloody capslock key)
  
  
  
  
  To Unsubscribe: send mail to [EMAIL PROTECTED]
  with unsubscribe freebsd-current in the body of the message
  
 
 __
 FREE voicemail, email, and fax...all in one place.
 Sign Up Now! http://www.onebox.com
 
 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Dropping bsd.man.mk support from bsd.kmod.mk

2001-12-24 Thread M. Warner Losh

: And now I recall.  Peter told me that at some
: point there will be no sys/modules at all.

I'm not objecting.  We don't use sys/modules, but do use bsd.kmod.mk
to build our drivers outside of the sys tree.  Any successor to
sys/modules must allow this (ideally with the same makefiles we have
now, or very similar).

Warner

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message