Collecting waiting statistics (simulation question)
Can anybody help me with a project I am working on? I am trying to simulate different memory allocation policies for a discrete event simulation course. Being the guy I am, I decided to collect some real statistics from a real system. The difficulty I've encountered is that I can't find how to make them accessible! Is there a way that I can log a large amount of statistics regarding kernel memory allocator activity and make that accessible to a user process? (Something like Solaris' crash(1m) and kmalog) Thanks in advance for any comments! -Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Collecting waiting statistics (simulation question)
* Jeff Rhyason [EMAIL PROTECTED] [000814 00:14] wrote: Can anybody help me with a project I am working on? I am trying to simulate different memory allocation policies for a discrete event simulation course. Being the guy I am, I decided to collect some real statistics from a real system. The difficulty I've encountered is that I can't find how to make them accessible! Is there a way that I can log a large amount of statistics regarding kernel memory allocator activity and make that accessible to a user process? (Something like Solaris' crash(1m) and kmalog) Thanks in advance for any comments! Using sysctls is probably the easiest way of doing it. -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Collecting waiting statistics (simulation question)
Using sysctls is probably the easiest way of doing it. OK. Is there any example code that uses sysctls in this way? Thanks ;) -Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: limit processes that a user can 'see'
Maxime Henrion wrote: Hello, I have an idea that I would love to see applied in FreeBSD source code, but as I'm not skilled enough to code it, I post it to see if you think it makes sense, and if someone would be interested in coding this. It is a security measure regarding 'ps' command. By using the 'ps' command, any user logged in the system can view all the running processes, including root's one and processes of other users. My idea is to limit a bit this behaviour. Through a sysctl variable, the root could restrict the list of "readable" processes. By readable, I mean that it can be viewed. For example, a value of 0 could mean no restriction, 1 would hide root processes, 2 would restrict the visible processes to the processes owned by users in the same group as the current user, and finally, 3 would restrict the processes list to those owned by the current user (this is the way I'd have done it if I was able to). Of course, there would be no limitation for the superuser. The modification must be done at a low enough level so that a user won't be able to bypass this security measure by compiling another 'ps' so patching 'ps' doesn't suffise (in fact, if it was, I would have done it :-). What do you all think of this ? Best regards, Maxime Henrion To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message I think it is fascist, butit's your system. Have Fun, Sends Steve P.S.Known to to run wth at.deny and cron.deny set to known one with no trouble. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does sio have a maintainer?
Hi folks, Does the sio driver have a maintainer? There are two PR's open that contain patches to provide support for new devices, but I can't find anyone to pin them on. :-) I thought bde looked after sio.c... Dunno if he reads this list. -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Collecting waiting statistics (simulation question)
* Jeff Rhyason [EMAIL PROTECTED] [000814 00:45] wrote: Using sysctls is probably the easiest way of doing it. OK. Is there any example code that uses sysctls in this way? A lot of sysctls implement some sort of statistics mechanism such as counters. Do a 'sysctl -a' and you'll see various sysctls being used for counters/stats. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: IPC, shared memory, syncronization AND threads...
John Polstra wrote: Jonas Bulow wrote Maybe I havn't been thinking enough but wouldn't this lock mechanism be a good choice to use for mmaped:memory accessed by multiple processes? It depends on the amount of contention you expect. The code in lockdflt.c was designed for a very low-contention situation (usually no contention at all). It also had to work in a very restrictive environment where the threads package was unknown and could be practically anything. Also it was designed to do locking between two threads running in the same process, which is not the problem you're trying to solve. Your environment is much more controlled, so you can probably do better. I think I'm trying to solve the threading-problem too. The overall architecture is a preforked server where there is a need to share information between all threads in all preforked processes. The solution below seems to be good if flock doesn't block all threads in a process, that is. I think the ideal solution would first try to lock the test-and-set lock, maybe spinning on it just a few times. If that failed it would fall back to using a system-call lock such as flock() which would allow the process to block without spinning. But I don't have any code to do that. (If you write some, could I have a copy?) I am about to. I don't know it it's bad design to have rtld.c export lockdflt_init in the same way as dlopen, what di you think? /jonas To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
freebsd and non-preemtive threads
I'm trying to build a preforked and threaded server. When it comes to the threading part it seems that non-preemtive threads have a lot of benefits if the server is a statefull-server. What I'm trying to say is that the server is not going to do a lot of computation for each request. The server will simply update it's state and respond about it's success. In this situation preemtive threads creats more harm than good becuase of the fact that the thread don't know when the next context switch will happen and therefor must do locking and stuff for the resources it uses. I have found two packages for non-preemtive threads: "State Threads Library for Internet Applications", http://oss.sgi.com/projects/state-threads/ and GNU-Pth. Is there anyone who has any experience of these or have any comment about these? Is it possible to have the FreeBSD pthreads to be non-preemtive? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ELF rtld and environment variables...
Ollivier Robert wrote: According to Julian Stacey: 4.1-release produces no /sbin/mount_cfs, man mount give no hint, If you have patches to test, I volunteer to test on 4.1 or 3.4 :-) It is a port. I'd love to import it into CURRENT though. Some friends running vile Micro$oft asked me if BSD offers an encrypting file system, it would be just too horrible to say "No", [though wether src/ or ports/ is best, I'm not now informed to comment] How do I get my hands on your sources ? :-) I'm running 4.0 on my laptop, was going to 4.1, but will go stable or current instead if necessary. Julian - Julian Stacey http://bim.bsn.com/~jhs/ Munich Unix Consultant. Free BSD Unix with 3600 packages sources. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: COMPAT_43 and kernel compiles.
On Sun, Aug 13, 2000 at 06:19:37PM +1000, Darren Reed wrote: Darren Reed wrote: Is it meant to be possible to compile a kernel *without* COMPAT_43 ? Has anyone else tried this recently ? For me, it seems to break the compile in (at least) kern_sig.c I doing this for a while, and I think the last signal interface change broke not being able to compile a kernel without COMPAT_43. This was a while back, and someone was supposed to be working on it to fix it. I might be able to dig some more info up if anyone wants it. From /sys/i386/conf/NOTES: # # Implement system calls compatible with 4.3BSD and older versions of # FreeBSD. You probably do NOT want to remove this as much current code # still relies on the 4.3 emulation. # options COMPAT_43 If it is to not be an option, then it should be deprecated as an option and all of that removed. FWIW, I tested NetBSD-current without this option and it compiles cleanly (not that I used it). Seems like someone needs to make a decision one way or the other about COMPAT_43 and FreeBSD. It used to be possible to compile and run kernels with COMPAT_43 undefined. -Mike -- Mike Pritchard [EMAIL PROTECTED] or [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: limit processes that a user can 'see'
In message [EMAIL PROTECTED], Maxime Henrion writes: Hello, I have an idea that I would love to see applied in FreeBSD source code, but as I'm not skilled enough to code it, I post it to see if you think it makes sense, and if someone would be interested in coding this. It is a security measure regarding 'ps' command. By using the 'ps' command, any user logged in the system can view all the running processes, including root's one and processes of other users. My idea is to limit a bit this behaviour. You can possibly make jail(8) do this for you... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Bootstrapping ? (was Re: Installation Problems on Dell PowerEdge 6100/200 )
Hiho, Mike Smith wrote on Sat, Aug 12, 2000 at 12:24:55AM +: [..] Ok, once you have this setting in place, re-install and verify that the disk geometry is xxx/255/63. Any other value will cause the system to fail to boot. I suspect that the point at which you tried this you already had the system installed with a totally bogus geometry. This was in fact, the hint I needed. The geometry was set to strange values, resetting it to 522/255/63 (for a 4G drive), solved the problem. After that, the system did boot correctly, and I could move on to the next problem (getting the SMP kernel running, which finally succeeded, as well). I'm still wondering if the wrong geometry settings could result from the prior solaris installation, or from unsuccessful installation attempts ? I always thought geometry settings are sort of alway right with scsi disks ... So thanks a lot for your help. Best regards, Daniel -- IRCnet: Mr-Spock - Truth lies in the eye of the beholder - *Daniel Lang * [EMAIL PROTECTED] * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
how to support adaptec 29160 ?
Hello ALL! Please, give me some info about support adaptec 29160 with FreeBSD Kernel during installation doesn't recognise this adapter Best regards, Kazennov mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Does sio have a maintainer?
In message [EMAIL PROTECTED] Brian Somers writes: : Does the sio driver have a maintainer? There are two PR's open that : contain patches to provide support for new devices, but I can't find : anyone to pin them on. :-) : : I thought bde looked after sio.c... Dunno if he reads this list. bde does maintain sio, for the most part. I also maintain the pci modem part of sio and am looking at one of the PRs right now which adds support for simple multiport serial ports attached to a pci bus (at bde's prodding). bde has some pending changes to sio as well in his queue. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
library name conflict problem
Howdy!
I've run into a situation where I need to have two differing
implementations of a library (both are from the ports collection)
installed on the same machine... by default both implementations get
installed with the same name (but in different locations) which causes a
library-name-resolution problem: the one appearing first in the hints
database is the only one that gets used. This, of course, breaks
applications that need the other version of the library.
Does anyone have any recommendations about how this should best be
resolved? Should one of the two libraries be given a different name
altogether (which then would require any ports that need this library to
be adjusted to link to the new name)... or is there a better approach?
This is actually a reposting... I made the mistake of including the word
'perldap' in the original posting which may have pushed it below the
radar of most. Below is the original text which provides further
background.
Thanks!
Charles Owens
--- Original Posting:
I 've encountered a problem which I could see affecting other LDAP
hackers as
well: the libldap and libber libraries from openldap and from the
Mozilla
ldap-sdk (${PORTSDIR}/net/ldapsdk) get installed with the same names and
version numbers (but not in the same directories... the mozilla libs get
put
in /usr/local/mozilla/directory/lib). Thus when running programs
written for
either library set the libraries that actually get invoked are whichever
set
is listed first in the dynamic linker's "hints" database. This is very
annoying! What is the appropriate solution? Some thoughts that come to
mind:
* change the version number that gets used for either library set...
and
then change all corresponding ports (if any) to use that verion
number
* somehow compile stuff (PerLDAP, for example) so it goes directly to
the
Mozilla libraries, despite the fact that the openldap libs are in
the
hints database first. I'm sure this could be accomplished via
static
linking, but that doesn't seem ideal.
I'm not exactly sure how to accomplish either approach. Any hints?
(hah! a
weak pun!)
Thanks,
--
-
Charles N. Owens Email: [EMAIL PROTECTED]
http://www.enc.edu/~owensc
Network Systems Administrator
Information Technology Services "Outside of a dog, a book is a man's
Eastern Nazarene College best friend. Inside of a dog it's
too dark to read." - Groucho Marx
-
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Does sio have a maintainer?
Warner Losh writes: In message [EMAIL PROTECTED] Brian Somers writes: : Does the sio driver have a maintainer? There are two PR's open that : contain patches to provide support for new devices, but I can't find : anyone to pin them on. :-) : : I thought bde looked after sio.c... Dunno if he reads this list. bde does maintain sio, for the most part. I also maintain the pci modem part of sio and am looking at one of the PRs right now which adds support for simple multiport serial ports attached to a pci bus (at bde's prodding). bde has some pending changes to sio as well in his queue. Greetings!, Without going into too much detail, I am using isa Byterunner 6-port cards at present (AST Multiport compat) and wish to use their pci version cards *when* a pci driver exists;-) I would gladly donate this pci style card if it would help in the development of the driver. I'd also volunteer to do any testing of new drivers for this as well. Thanks, John J. Rieser [EMAIL PROTECTED] PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Roadx327 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: how to support adaptec 29160 ?
On Mon, Aug 14, 2000 at 07:25:42PM +0400, Kazennov Vladimir wrote: Please, give me some info about support adaptec 29160 with FreeBSD Kernel during installation doesn't recognise this adapter What version of FreeBSD? It should be supported in 4.1. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ELF rtld and environment variables...
Julian Stacey wrote:
Ollivier Robert wrote:
According to Julian Stacey:
4.1-release produces no /sbin/mount_cfs, man mount give no hint,
If you have patches to test, I volunteer to test on 4.1 or 3.4 :-)
It is a port. I'd love to import it into CURRENT though.
Some friends running vile Micro$oft asked me if BSD offers an encrypting file
system, it would be just too horrible to say "No",
[though wether src/ or ports/ is best, I'm not now informed to comment]
How do I get my hands on your sources ? :-) I'm running 4.0 on my laptop,
was going to 4.1, but will go stable or current instead if necessary.
My relatively recent 4.1 laptop has it in ports/security/cfs. The package
description reads:
This is CFS, Matt Blaze's Cryptographic File System. It provides
transparent encryption and decryption of selected directory trees.
It is implemented as a user-level NFS server and thus does not
require any kernel modifications.
For an overview of how to use it, read "${PREFIX}/share/doc/cfs/notes.ms"
and the manual pages. There is a paper describing CFS at:
ftp://research.att.com/dist/mab/cfs.ps
Under FreeBSD, the mount command for the CFS tree must include
"-o port=3049,nfsv2".
John Polstra [EMAIL PROTECTED]
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
[EMAIL PROTECTED] http://softweyr.com/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
dma to userland address
lets say, hypothetically, that i have an ioctl interface to my device
driver that takes a buffer that looks something like:
struct {
int length;
char *buf;
} mystruct;
and lets say, hypothetically, that i wanted to dma directly
to/from 'buf'. how would i do that?
i've tried doing vtophys on buf, but that doesn't seem to work.
i've tried doing vtophys on a kernel-allocated block and the mmapping it
through /dev/mem in userland, but that doesn't seem to work either (this
may have a bug, though - it worked under linux, but was about 10x slower
than just leaving the kernel/user copy in there).
so what am i missing here?
- j
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: dma to userland address
Look at what physio does.
On Mon, 14 Aug 2000, Bill Clinton wrote:
lets say, hypothetically, that i have an ioctl interface to my device
driver that takes a buffer that looks something like:
struct {
int length;
char *buf;
} mystruct;
and lets say, hypothetically, that i wanted to dma directly
to/from 'buf'. how would i do that?
i've tried doing vtophys on buf, but that doesn't seem to work.
i've tried doing vtophys on a kernel-allocated block and the mmapping it
through /dev/mem in userland, but that doesn't seem to work either (this
may have a bug, though - it worked under linux, but was about 10x slower
than just leaving the kernel/user copy in there).
so what am i missing here?
- j
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
code question...
I am getting a warning from a program I wrote: lined in free(): warning: chunk is already free. Is there anyway I can figure out where exactly this is happening, maybe cause a core or something. - Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: code question...
In the last episode (Aug 14), Chris Ptacek said: I am getting a warning from a program I wrote: lined in free(): warning: chunk is already free. Is there anyway I can figure out where exactly this is happening, maybe cause a core or something. Man malloc, see the "DEBUGGING MALLOC PROBLEMS" section. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: code question...
On Mon, Aug 14, 2000 at 02:10:16PM -0700, Chris Ptacek wrote: I am getting a warning from a program I wrote: lined in free(): warning: chunk is already free. Is there anyway I can figure out where exactly this is happening, maybe cause a core or something. From 'man free', which you did read twice, right? (in reference to malloc.conf...) A All warnings (except for the warning about unknown flags being set) become fatal. The process will call abort(3) in these cas- es. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ipfw drop packets based on SYN TTL
Is this similar to the following kernel configuration? options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN Thanks! Bruce. __ FREE Personalized Email at Mail.com Sign up at http://www.mail.com/?sr=signup To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: code question...
This is happening in a call to free() ;; the memory being freed is either not actually allocated or is somewhere that your programs memory does not contain (ie address out of range). Use mxgdb, ddd, or gdb to show all things things and step through the executiong. * Philip M. Gollucci E-mail : [EMAIL PROTECTED] [EMAIL PROTECTED] Phone : 301.249.6261 Major : Computer Science Electrical Engineering Current Job : Co Science, Discovery, the Universe Webmaster * On Mon, 14 Aug 2000, Chris Ptacek wrote: I am getting a warning from a program I wrote: lined in free(): warning: chunk is already free. Is there anyway I can figure out where exactly this is happening, maybe cause a core or something. - Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Collecting waiting statistics (simulation question)
On Mon, 14 Aug 2000, Jeff Rhyason wrote: A lot of sysctls implement some sort of statistics mechanism such as counters. Do a 'sysctl -a' and you'll see various sysctls being used for counters/stats. Aah. This isn't quite what I lust for: Is it possible to get a *log* of allocation requests rather than aggregate sums or averages? The reason is so I can calculate the distribution of the data. For example: the kind of information I would like to have from kern_malloc for each invocation is: - time of the allocation - size - time spent in asleep - return value The same thing can be done with kern_free and from there the time the memory was used can be calculated. So write it. It wouldn't be terribly difficult. I don't think it'd be terribly popular (so you won't be able to talk someone here into doing it for you) but you could grab an idea for the communications logging from syslog (using a daemon a socket) and just instrument the right parts of the kernel to write to the socket. You'd have to write the daemon write a bit of code in the kernel. It would be a reasonably simple project. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED]| electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ipfw drop packets based on SYN TTL
On Mon, Aug 14, 2000 at 06:44:28PM -0400, Bruce Petro wrote: Is this similar to the following kernel configuration? options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN Not at all. The original poster is looking to drop all packets with a certain tcp syn#, where the TCP_DROP_SYNFIN option (and you must turn on the corresponding sysctl for it to be enabled) drops all packets with both the "syn" and "fin" flags set. functionally equivalent to: ipfw add drop tcp from any to any tcpflags syn,fin -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Updating /etc/passwd and /etc/master.passwd
I am about to migrate from a 2.2.8-STABLE box to a 4.1-STABLE box and beofre I try was wondering is there anything special I have to do do migrate my passwd file over their with my accounts. TIA -- -- Ron Rosson... and a UNIX user said ... The InSaNe Onerm -rf * [EMAIL PROTECTED]and all was /dev/null and *void() -- You are the Senate. You have the power to Filibuster. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ipfw drop packets based on SYN TTL
No, TTL is in IP header while SYN FIN are TCP flags. On Mon, 14 Aug 2000, Bruce Petro wrote: Is this similar to the following kernel configuration? options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN Thanks! Bruce. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
linux expo san jose tomorrow
hey, is there gonna be a freebsd or bsd booth there tomorrow in san jose for that linux expo thing? I may go if there is a bsd booth... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: linux expo san jose tomorrow
hey, is there gonna be a freebsd or bsd booth there tomorrow in san jose for that linux expo thing? I may go if there is a bsd booth... There will be a BSDi booth at the show. Look for the usual black monolith with the daemon on it. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CVS question
In article [EMAIL PROTECTED], Archie Cobbs [EMAIL PROTECTED] wrote: Hmm.. sounds like we should do one or both of these things.. 1/ Fix the bug in CVS that caused the import to set two different dates I finally got around to checking, and the bug doesn't exist in the current version of CVS that we use. I think it probably got fixed a couple of years ago when they stopped running "rcs" and started doing all the RCS operations directly themselves. Some things _have_ gotten better since 1993. :-) 2/ Modify this cvs file to set the dates to be the same Yep, good idea. It's only a 1-second difference. I've done that now. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: how to support adaptec 29160 ?
On Mon, 14 Aug 2000, Kazennov Vladimir wrote: Hello ALL! Please, give me some info about support adaptec 29160 with FreeBSD Kernel during installation doesn't recognise this adapter Works fine for me, just using the ahc driver (endless thanks to Justin Gibbs!) I have a dualbussed 7895 controller on my motherboard, so the 29160 became my ahc2. I only have one of the my drives up yet, but my hints file looks like: hint.da.3.at="scbus2" hint.da.3.target="0" hint.da.4.at="scbus2" hint.da.4.target="1" (scbus0 1 already used up with the 7895). The config file just needs the single "device ahc", no count required. The dmesg so far (with only one of my two drives up): ahc2: Adaptec 29160 Ultra160 SCSI adapter port 0xf000-0xf0ff mem 0xfecfd000-0x da3 at ahc2 bus 0 target 6 lun 0 da3: IBM DDYS-T18350N S80D Fixed Direct Access SCSI-3 device da3: 160.000MB/s transfers (80.000MHz, offset 63, 16bit) da3: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) Bonnie tells me: ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 100 16798 98.2 27256 63.6 10974 35.3 15611 99.2 29266 45.0 366.9 7.3 Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED]| electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: linux expo san jose tomorrow
On 15-Aug-00 Jordan K. Hubbard wrote: hey, is there gonna be a freebsd or bsd booth there tomorrow in san jose for that linux expo thing? I may go if there is a bsd booth... There will be a BSDi booth at the show. Look for the usual black monolith with the daemon on it. - Jordan And A BSDi BOF later in the day! see www.daemonnews.org Nicole To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message [EMAIL PROTECTED] |\ __ /| (`\ http://www.unixgirl.com/ [EMAIL PROTECTED] | o_o |__ ) ) http://www.dangermouse.org/ // \\ ---(((---(((- -- Powered by Coka-Cola and FreeBSD -- -- Strong enough for a man - But made for a Woman -- -- OWNED? MS: Who's Been In/Virused Your Computer Today? -- --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Collecting waiting statistics (simulation question)
So write it. It wouldn't be terribly difficult. I don't think it'd be terribly popular (so you won't be able to talk someone here into doing it for you) but you could grab an idea for the communications logging from syslog (using a daemon a socket) and just instrument the right parts of the kernel to write to the socket. You'd have to write the daemon write a bit of code in the kernel. It would be a reasonably simple project. OK I will get started. Can I hassle you for help? -Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Collecting waiting statistics (simulation question)
On Mon, 14 Aug 2000, Jeff Rhyason wrote: So write it. It wouldn't be terribly difficult. I don't think it'd be terribly popular (so you won't be able to talk someone here into doing it for you) but you could grab an idea for the communications logging from syslog (using a daemon a socket) and just instrument the right parts of the kernel to write to the socket. You'd have to write the daemon write a bit of code in the kernel. It would be a reasonably simple project. OK I will get started. Can I hassle you for help? Occaisonally, but you'd do better hitting this list in general. I'm on a new job and I'm giving it a LOT of hours; you might wait a week for me to find time to generate an answer. It depends on your questions, too. If you demonstrate by your question's topic and focus that you've made a *hard* effort to answer it on yourself, *loads* of folks will help. If it looks like just another person looking for a free ride (and there's so many of those that we get a bit defensive) then you wouldn't expect too much. Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED]| electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
fam and fmon?
Does anyone have fam working with fmon yet? The sgi page has a few mentions of it but they're a few months old. -Brandon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
