From owner-freebsd-hackers Sun Jul 28 01:27:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA07044 for hackers-outgoing; Sun, 28 Jul 1996 01:27:42 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA07036 for ; Sun, 28 Jul 1996 01:27:39 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id DAA06937 for hackers@freebsd.org; Sun, 28 Jul 1996 03:27:34 -0500 (EST) From: "John S. Dyson" Message-Id: <199607280827.DAA06937@dyson.iquest.net> Subject: Got an idea about ccd To: hackers@freebsd.org Date: Sun, 28 Jul 1996 03:27:34 -0500 (EST) Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just noticed that ccd doesn't set the b_bufsize field of the (struct buf). There are various parts of the system that can get confused given that. I have absolutely NO way to test it, but I suggest that the b_bufsize field be set to be the same as b_bcount page rounded (or perhaps the same exactly.) John From owner-freebsd-hackers Sun Jul 28 09:57:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA00504 for hackers-outgoing; Sun, 28 Jul 1996 09:57:11 -0700 (PDT) Received: from cps.cmich.edu (cps201.cps.cmich.edu [141.209.20.201]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA00479; Sun, 28 Jul 1996 09:57:06 -0700 (PDT) Received: from cps200.cps.cmich.edu (cps200 [141.209.20.200]) by cps.cmich.edu (8.7.5/8.7.3) with SMTP id MAA27780; Sun, 28 Jul 1996 12:53:30 -0400 (EDT) Date: Sun, 28 Jul 1996 12:53:28 -0400 (EDT) From: Mail Archive To: Jim Dennis cc: terry@lambert.org, jnoetzel@intermind.com, freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Netscape Commerce Servers In-Reply-To: <199607152054.NAA02840@starshine> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 15 Jul 1996, Jim Dennis wrote: > > > > On Mon, 10 Jun 1996, Terry Lambert wrote: > > > > > > Does anyone know about FreeBSD ports of the Commerce server and the News > > > > server? I know we've got Navigator ports, but I'd like to get a couple > > > > server ports as well if we have them available. > > > The BSDI commerce server runs (but didn't Netscape just drop BSDI > > > so the can concentrate on the NT platform where Microsoft has > > > already won?). > > Well actually Netscape is dropping support for all non-threaded OS's for their > > servers.. > > > Matthew S. Bailey > > I was at a party hanging out with three or four of Netscape's > developement team over the weekend -- I didn't get the impression > that they were doing either of these things. > > Granted we chatted more about the client side and business > model issues -- mostly about Java and JavaScript which is what this > particularly crew are working on most. I suggested that > JavaScript (a.k.a. LiveScript take on one feature -- > that the > > (to get rid of that atrocious code-embedded-in-comments hack). > > (He said they'll look at it for version 4.x). > > So, Matthew, what's the source of your info? I'd like to see > more about this. > Sorry for such a late response work has been getting to me here :) I got that information for the mirror mailing list (we were one of netscape mirror sites) and from netscape sales about 3 months ago, however I called them friday and asked the same question as before and what I gather is they have done a total rewrite and support for non-threaded OS's is forthcomming but it very slow. Matthew S. Bailey mbailey@cps.cmich.edu From owner-freebsd-hackers Sun Jul 28 13:04:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07571 for hackers-outgoing; Sun, 28 Jul 1996 13:04:56 -0700 (PDT) Received: from neuron.bsd.uni-passau.de (ith6.extern.inet-nb.de [194.121.36.167]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA07548; Sun, 28 Jul 1996 13:04:35 -0700 (PDT) Received: (from moos@localhost) by neuron.bsd.uni-passau.de (8.6.12/8.6.12) id WAA00702; Sun, 28 Jul 1996 22:00:08 +0200 From: Darius Moos Message-Id: <199607282000.WAA00702@neuron.bsd.uni-passau.de> Subject: FreeBSD-2.1-pppd/pap <-> Linux-2.x-PPP => VERY BIG problem To: questions@FreeBSD.org Date: Sun, 28 Jul 1996 22:00:08 +0200 (MET DST) Cc: hackers@FreeBSD.org X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi all, i'm having hell on earth configuring pppd (kernel-ppp) to work with PAP. Maybe someone could help me with this problem. First: I'm running FreeBSD-2.1(R) I have already run kernel-ppp succesfully to a FreeBSD-box (2.1R) and a Linux-box (1.x). I've also connected to the FreeBSD-box with CHAP. No problem. Next: I'm initiating the whole process from a bash-script with a case-statement: case $1 in . . deg) /usr/sbin/pppd -d connect "~/.ppp.deg.up " \ file ~/.ppprc.deg 0.0.0.0: /dev/cuaa1 ;; . . esac ~/.ppp.deg.up is also a bash-script for chat-dial: chat -v -t 90 "" atz0 OK atd$1 CONNECT "" ~/.ppprc.deg is the optionsfile specific to this connection: user moos name moos +pap -chap ipcp-accept-remote ~/.ppprc includes options common to all my personal connections: defaultroute /etc/ppp/options includes everytime-options for pppd: netmask 255.255.255.248 crtscts modem /etc/ppp/pap-secrets includes the client-server-password-data: moos * Misc: My provider offers dial-in-lines for PPP using PAP-authentication with dynamic IPs running Linux (2.x). My username is moos. I don't know the server-name for the authentication, therefor i've put a '*' in the pap-secrets-file. He gave me the secret and it stands where i've written . The HORRORSHOW: When i start the dialing-process nothing happens. No error on console. Here is the relevant part of the pppd-log-file: Jul 28 20:42:11 neuron pppd[556]: pppd 2.1.2 started by moos, uid 30001 Jul 28 20:42:35 neuron pppd[557]: Connected... Jul 28 20:42:36 neuron pppd[557]: Using interface ppp0 Jul 28 20:42:36 neuron pppd[557]: Connect: ppp0 <--> /dev/cuaa1 Jul 28 20:42:36 neuron pppd[557]: sent [LCP ConfReq id=0x1 ] Jul 28 20:42:39 neuron pppd[557]: sent [LCP ConfReq id=0x1 ] Jul 28 20:42:39 neuron pppd[557]: rcvd [LCP ConfReq id=0x0 ] Jul 28 20:42:39 neuron pppd[557]: sent [LCP ConfRej id=0x0 ] Jul 28 20:42:39 neuron pppd[557]: rcvd [LCP ConfRej id=0x1 ] Jul 28 20:42:39 neuron pppd[557]: sent [LCP ConfReq id=0x2 ] Jul 28 20:42:40 neuron pppd[557]: rcvd [LCP TermReq id=0x1 00 00 02 dc] Jul 28 20:42:40 neuron pppd[557]: sent [LCP TermAck id=0x1] Jul 28 20:42:42 neuron pppd[557]: sent [LCP ConfReq id=0x2 ] Jul 28 20:43:07 neuron last message repeated 8 times Jul 28 20:43:10 neuron pppd[557]: LCP: timeout sending Config-Requests Jul 28 20:43:10 neuron pppd[557]: Connection terminated. Jul 28 20:43:10 neuron pppd[557]: Exit. More horror: - I've also tried using the auth-option. The result: Jul 27 15:19:03 neuron pppd[1024]: pppd 2.1.2 started by moos, uid 30001 Jul 27 15:19:27 neuron pppd[1025]: Connected... Jul 27 15:19:28 neuron pppd[1025]: Using interface ppp0 Jul 27 15:19:28 neuron pppd[1025]: Connect: ppp0 <--> /dev/cuaa1 Jul 27 15:19:28 neuron pppd[1025]: sent [LCP ConfReq id=0x1 ] Jul 27 15:19:31 neuron pppd[1025]: sent [LCP ConfReq id=0x1 ] Jul 27 15:19:31 neuron pppd[1025]: rcvd [LCP ConfReq id=0x0 ] Jul 27 15:19:31 neuron pppd[1025]: sent [LCP ConfNak id=0x0 ] Jul 27 15:19:31 neuron pppd[1025]: rcvd [LCP ConfAck id=0x1 ] Jul 27 15:19:31 neuron pppd[1025]: rcvd [LCP ConfReq id=0x1 ] Jul 27 15:19:31 neuron pppd[1025]: sent [LCP ConfRej id=0x1 ] Jul 27 15:19:31 neuron pppd[1025]: rcvd [LCP TermReq id=0x2 00 00 02 dc] Jul 27 15:19:31 neuron pppd[1025]: sent [LCP TermAck id=0x2] Jul 27 15:19:34 neuron pppd[1025]: sent [LCP ConfReq id=0xff ] Jul 27 15:20:01 neuron last message repeated 9 times Jul 27 15:20:04 neuron pppd[1025]: LCP: timeout sending Config-Requests Jul 27 15:20:04 neuron pppd[1025]: Connection terminated. Jul 27 15:20:04 neuron pppd[1025]: Exit. - I've tried without the options "auth [+-]pap [+-]chap". No success. - I've tried "* * " in pap-secrets. No success. - I've tried "+ua " with user and password in . No success. - I've tried using CHAP. The result: Jul 27 15:33:24 neuron pppd[1071]: pppd 2.1.2 started by moos, uid 30001 Jul 27 15:33:47 neuron pppd[1072]: Connected... Jul 27 15:33:48 neuron pppd[1072]: Using interface ppp0 Jul 27 15:33:48 neuron pppd[1072]: Connect: ppp0 <--> /dev/cuaa1 Jul 27 15:33:48 neuron pppd[1072]: sent [LCP ConfReq id=0x1 ] Jul 27 15:33:51 neuron pppd[1072]: sent [LCP ConfReq id=0x1 ] Jul 27 15:33:51 neuron pppd[1072]: rcvd [LCP ConfReq id=0x0 ] Jul 27 15:33:51 neuron pppd[1072]: sent [LCP ConfNak id=0x0 ] Jul 27 15:33:52 neuron pppd[1072]: rcvd [LCP ConfRej id=0x1 ] Jul 27 15:33:52 neuron pppd[1072]: sent [LCP ConfReq id=0x2 ] Jul 27 15:33:52 neuron pppd[1072]: rcvd [LCP ConfReq id=0x1 ] Jul 27 15:33:52 neuron pppd[1072]: sent [LCP ConfRej id=0x1 ] Jul 27 15:33:52 neuron pppd[1072]: rcvd [LCP ConfAck id=0x2 ] Jul 27 15:33:52 neuron pppd[1072]: rcvd [LCP TermReq id=0x2 00 00 02 dc] Jul 27 15:33:52 neuron pppd[1072]: sent [LCP TermAck id=0x2] Jul 27 15:33:55 neuron pppd[1072]: sent [LCP ConfReq id=0xff ] Jul 27 15:34:22 neuron last message repeated 9 times Jul 27 15:34:25 neuron pppd[1072]: LCP: timeout sending Config-Requests Jul 27 15:34:25 neuron pppd[1072]: Connection terminated. Jul 27 15:34:25 neuron pppd[1072]: Exit. - I've tried making changes to /usr/src/usr.sbin/pppd/chap.h (I know this is NOT the right way to solve the problem): I changed #define CHAP_DIGEST_MD5 5 to #define CHAP_DIGEST_MD5 128 compiled and installed pppd. The result: Jul 27 17:49:21 neuron pppd[2428]: pppd 2.1.2 started by moos, uid 30001 Jul 27 17:49:44 neuron pppd[2429]: Connected... Jul 27 17:49:45 neuron pppd[2429]: Using interface ppp0 Jul 27 17:49:45 neuron pppd[2429]: Connect: ppp0 <--> /dev/cuaa1 Jul 27 17:49:45 neuron pppd[2429]: sent [LCP ConfReq id=0x1 ] Jul 27 17:49:48 neuron pppd[2429]: sent [LCP ConfReq id=0x1 ] Jul 27 17:49:49 neuron pppd[2429]: rcvd [LCP ConfReq id=0x0 ] Jul 27 17:49:49 neuron pppd[2429]: sent [LCP ConfAck id=0x0 ] Jul 27 17:49:49 neuron pppd[2429]: rcvd [LCP ConfRej id=0x1 ] Jul 27 17:49:49 neuron pppd[2429]: sent [LCP ConfReq id=0x2 ] Jul 27 17:49:49 neuron pppd[2429]: rcvd [LCP ConfAck id=0x2 ] Jul 27 17:49:51 neuron pppd[2429]: rcvd [CHAP Challenge id=0x66 <7c4b5d06001cf056>, name = ""] Jul 27 17:49:51 neuron pppd[2429]: sent [CHAP Response id=0x66 <872c2f92d6c4ae3fb6fe9067860b8ac5>, name = ""] Jul 27 17:49:53 neuron pppd[2429]: rcvd [CHAP Challenge id=0x67 <12dfdce9c94b6340>, name = ""] Jul 27 17:49:53 neuron pppd[2429]: sent [CHAP Response id=0x67 <660020266cb6c283d19162396bc37fda>, name = ""] . . . Jul 27 17:50:05 neuron pppd[2429]: rcvd [CHAP Challenge id=0x6d , name = ""] Jul 27 17:50:05 neuron pppd[2429]: sent [CHAP Response id=0x6d <342b335f88174593703049bc0f6bcf1b>, name = ""] Jul 27 17:50:07 neuron pppd[2429]: rcvd [LCP TermReq id=0x1 00 00 02 ce] Jul 27 17:50:07 neuron pppd[2429]: LCP terminated at peer's request Jul 27 17:50:07 neuron pppd[2429]: sent [LCP TermAck id=0x1] Jul 27 17:50:10 neuron pppd[2429]: Connection terminated. Jul 27 17:50:10 neuron pppd[2429]: Exit. Conclusion: No end of the HORROR-show. Maybe there is someone on the net, who knows what's going on who knows where the problem is who knows a solution or workaround who would help me who knows that FreeBSD-2.1(R)-pppd and Linux-2.x-PPP can NOT work together I don't have the option of upgrading to FreeBSD-2.1.5(R) If upgrading would solve my problem, would it be possible to run a statically compiled pppd of FreeBSD-2.1.5 under FreeBSD-2.1 ? Please help me with this damned problem; i can't solve it on my own. Any help is appreciated. Many thanks in advance, bye Darius. email: moos@degnet.baynet.de moos@ithnet.com P.S.: Sorry for this mail being so long and thaks for reading it to this point. From owner-freebsd-hackers Sun Jul 28 13:09:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA07833 for hackers-outgoing; Sun, 28 Jul 1996 13:09:42 -0700 (PDT) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA07826 for ; Sun, 28 Jul 1996 13:09:29 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id QAA28027 for hackers@freebsd.org; Sun, 28 Jul 1996 16:09:23 -0400 From: Bill Paul Message-Id: <199607282009.QAA28027@skynet.ctr.columbia.edu> Subject: Request for comments: NIS+ database design To: hackers@freebsd.org Date: Sun, 28 Jul 1996 16:09:22 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings: Lately I've been eroding my sanity by trying to put together an NIS+ implementation for FreeBSD. After going over the man pages, RPC protocol definitions and other available headers a few times, I decided to start at the bottom by building an NIS+ database backend library. Briefly, with NIS+, databases are managed entirely by the server, rpc.nisd. This includes creating, destroying and populating tables: all the NIS+ tools send requests to rpc.nisd, which in turn updates the database files and keeps a log of changes. The log is used by slaves (or replicas, as Sun now calls them) to stay in sync with the master server by carrying out the changes as specified in the log rather than snarfing an entire copy of the updated database, which is what NIS v2 does. Furthermore, NIS+ uses a relational database system rather than the (relatively) simple key/value database system used by NIS v2. With NIS+, you're allowed to make queries such as: "find me all the entries in the passwd table where uid=0 and shell=/bin/csh", whereas with NIS v2 you're only allowed to say: "give me the data associated with the key 'foouser' in the map 'passwd.byname'." (Note that this assumes that the 'passwd' table has been created with the uid and shell columns marked as searchable. Normally this is not the case: only the name and uid columns are searchable.) This (IMHO) is where most of the complexity in NIS+ comes from. With NIS v2, it's fairly easy to just bolt on an interface to Berkeley DB, ndbm, GDBM or whatever and leave it at that. With NIS+, you have to be more creative. Anyway. I managed to concoct a workable libnisdb prototype, but not being a database expert I'm not terribly confident in its design. I want to briefly explain how it works then ask for comments, criticisms, screams of terror or any other input anyone would care to offer. I apologize if this seems a bit too far off topic for this list. I don't know how many of you actually care about this stuff, but since it is likely to end up in the tree eventually it deserves some discussion somewhere. The NIS+ database backend consists of a handful of public functions such as db_create_table(), db_destroy_table(), db_add_entry(), db_remove_entry(), db_list_entry(), db_next_entry(), db_reset_next_entry(), db_checkpoint(), db_standby(), db_unload_table() and db_free_result(). Some of these return just a single enum value (status code) while others return a db_result structure containing the results of queries. db_free_result() returns void. (Note that there were a few extra functions added between Solaris 2.3, whent he NIS+ and nis_db.h specifications were released and Solaris 2.5. I decided to implement the functions outlined as of Solaris 2.5.) The Sun implementation uses something described in the nis_db(3n) man page as the 'Structured Storage Manager (SMM).' I also know that the Sun libnisdb is written, at least in part, in C++ (in fact I think a lot of Sun's NIS+ implementation is written in C++). I also think that it handles some of the transaction logging. My library doesn't do logging, but when time comes to do rpc.nisd, I may decide to merge it in if it seems practical. First of all, I decided to use the Berkeley DB btree method as the underlying database format. With ypserv I used the hash method. The one downside to the hash method is that the R_CURSOR flag doesn't work, which makes it hard to arbitrarily set a 'pointer' to a given place in the database. I worked around this with ypserv, but I decided I needed it to work correctly this time, so I switched to btree. Second, the actual 'database' is stored in two files. One contains the actual entries, and the other contains the relations that describe the entries. When an entry is added, it is first XDR-encoded into a buffer using xdrmem_create() in order to transform it into an opaque form. This buffer is then passed to a hash function which generates a 32-bit hash value that describes the entry. This hash value is used as the 'key' in the 'entries' database, and the XDR'ed buffer is the data. I call these 32-bit hash values 'tags.' Assuming one knows the 32-bit 'tag' for a particular entry, one can just do a (db->get) on the database using the tag as the key and get back the XDR'ed buffer. The original entry_obj structure can then be recreated just by passing the buffer through the XDR filter again. When the (db->put) operation is performed, I can tell immediately if I've been handed a duplicate entry since Berkeley DB will notice the key collision and return an error (if you use the R_NOOVERWRITE flag, which I do). If this happens, the caller gets back a DB_NOTUNIQUE error. Next, a set of relations are derived from the entry, and the 32-bit tag is associated with each relation. For example, if I have a 'passwd' table with seven total columns, two of which are searchable (name and uid), I would have two relations for each entry: name= and uid=. These would each be stored in the second database file as keys with the 32-bit tag derived from the entry as data. With passwd databases, the name field is meant to be unique, therefore each name= relation will likely only be related to a single tag. However, uids are often not unique, which means that a single uid= relation may yield several tags. If I find that a uid= key already exists, I update it by adding the new tag to the list of tags already stored. So as more entries are added that have the same uid= relation, the list of tags gets bigger. Let's say I do a simple query: find me all entries where name=wpaul. I would use db_list_entries() for this. First, I would use [name=wpaul] as a key for searching the 'relations' database for the passwd table. Assuming there is an entry that matches this criteria, I'll get back a datum that contains the 32-bit tag for the desired entry. I then use this tag as a key for searching the 'entries' database for the passwd table and get back the entry buffer, which I convert back into an entry_obj structure and pass back to the caller. Now let's say I do a more complex query that yields several entries as a result: find me all entries where uid=0 and shell=/bin/csh. Let's say there are three entries where uid=0 but only two where shell=/bin/csh. Doing a (db->get) from the 'relations' database with [uid=0] as the key yields three tags, but [shell=/bin/csh] yields only two. In this case, we take the smallest of the two tag lists (uid=0) and check to see if each one exists in the other relations' list. If we find that one of the tags in the smaller list doesn't appear in the larger list, it's eliminated from the query. (When there are more than two attributes, a tag is eliminated if it fails to appear in any of the larger lists.) Once we know which tags appear in both sets of lists, we retrieve the corresponding entries and pass them back the caller. Lastly, the 'entries' database has one special record in it which actually contains an XDR'ed table_obj that describes the table. When the database is initialized, each table is opened and this record is read into a cache which the various functions can then used for sanity checking. This record also describes the access rights associated with the various columns in the table. (Note that the database itself does not care about the access rights; only the server (rpc.nisd) concerns itself with them.) Along with all this, there are two circular queues of table handles. One of them contains a single entry for each known table and is loaded when the database library is initialized. The second queue is used to hold special descriptors used by the db_first_entry() and db_next_entry() functions. These database handles are positioned to particular locations within the btree databases using the (db->seq) function in Berkeley DB. This is somewhat analagous to the database handle cache in ypserv. The db_reset_next_entry() is used to close down one of these table handles when the caller is finished with them. The reason I decided to store the 'entries' and 'relations' separately was to save a little time in db_next_entry(). If both types of keys/data where stored in one database, I would have to check the type of data retrieved on each (db->seq) to make sure it was of the correct type and do a second retrieval if it wasn't (or a third, or a fourth, if I encountered a series of the wrong type of data). By putting the relations in a seperate database, I can step through the entries quickly without worrying about encountering uninteresting records. That's about it really. The idea here was to make the retrieval process quick in exchange for making the storage process more complex since the overwhelming majority of queries received by the server are likely to be for lookups. At the moment I have a completed library with all the functions from the Solaris nis_db(3n) man page and header implemented. I still need to make a couple of cleanup passes and write my own man page (not to mention run some comparison tests against the Solaris libnisdb), after which I'll put the whole mess up for FTP somewhere so people can look at it, point their fingers and laugh. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "If you're ever in trouble, go to the CTR. Ask for Bill. He will help you." ============================================================================= From owner-freebsd-hackers Sun Jul 28 13:31:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA08727 for hackers-outgoing; Sun, 28 Jul 1996 13:31:27 -0700 (PDT) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA08704; Sun, 28 Jul 1996 13:31:19 -0700 (PDT) Received: from venus.mcs.com (root@Venus.mcs.com [192.160.127.92]) by Kitten.mcs.com (8.7.5/8.7.5) with SMTP id PAA11047; Sun, 28 Jul 1996 15:31:18 -0500 (CDT) Received: by venus.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Sun, 28 Jul 96 15:31 CDT Message-Id: Subject: Re: PPro Question To: mark@quickweb.com (Mark Mayo) Date: Sun, 28 Jul 1996 15:31:16 -0500 (CDT) From: "Karl Denninger, MCSNet" Cc: hackers@freebsd.org, current@freebsd.org In-Reply-To: from "Mark Mayo" at Jul 26, 96 03:49:50 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Hi there - I was wondering if many people have experience with PPro > servers running FreeBSD. I just picked up a Digital Celebris XL 6150 > Pentium Pro (150MHz), and I installed FreeBSD 2.1R - no problems with the > install, the DEC uses an NCR on-board SCSI Bios / COntroller, and > everthing worked fine (the Celebris line use daughter cards to hold the > CPU and Ram so you can switch between ALpha's and PPro's..) > > I was wondering if the following 'time' result is reasonable (for a kernel > rebuild, all options - seemed like a good benchmark to me :-)). The > machine only has 16 MB of RAM. The reason I ask is that I'm curious if a > "normal" pentium 200 with SRAM would be faster.. > > Anyways, the results: > > $ time make > . > . > 183.8u 32.6s 5:20.20 67.9% 989+1207K 1380+59565io 61pf + 0w > > > Any experience/opinions of the Pentium Pro's would be greatly appreciated. We just picked up two PPro 200s, one with 64MB RAM, the other with 128MB. They "feel" about 2x as fast as a P166 with otherwise identical equipment. One of them is in production use as a news server, the other as our "codebase" machine (yes, we finally went out and built one). People who want to grab a -CURRENT release build can get it from codebase.mcs.net, log in as "FTP"; you'll be at the top of the "make release" tree. The normal "grab" files are under "R/ftp" from there. We'll normally keep a "snapshot" type build ("make release") in there and update it every few days, but I *cannot* promise that it will be there at any given point in time. I can also set up a SUP server for the CVS tree if people are interested. Would this help folks? We have *lots* of free cycles and net bandwidth, so we're not constrained at all. What I don't think I will be able to do right now though is keep all the other packages online (at least I can't *promise* they will be there). Functionally, I'm not even sure what I have to sup over here to get a "Complete" set of distributions if I want to be a mirror. Anyone? Give me a list and amount of disk required (will it fit on a 4G drive?) and I'll go grab it. No big deal; 4G disks are only about a kilobuck these days, and I have a bunch of them available to me. Dedicating a machine to serving sups and builds doesn't bother me at all; as long as it doesn't get plastered *too* badly I'll be happy to make it available to the world. If it does we'll have to figure out a way to choke it off to the point that I can still build my kernels and distributions for internal use. CAUTION! The 2.1.anything floppy boot images want a "root.flp" file in the release which IS NOT THERE on a 2.2 build. DO NOT ATTEMPT TO LOAD A 2.2 RELEASE WITH A 2.1.ANYTHING BOOT FLOPPY! IT WILL NOT WORK! Grab the current 2.2 "boot.flp"; that image will work properly. I found this out the hard way... -- -- Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity http://www.mcs.net/~karl | T1 from $600 monthly; speeds to DS-3 available | 23 Chicagoland Prefixes, 13 ISDN, much more Voice: [+1 312 803-MCS1] | Email to "info@mcs.net" WWW: http://www.mcs.net/ Fax: [+1 312 248-9865] | Home of Chicago's only FULL Clarinet feed! From owner-freebsd-hackers Sun Jul 28 14:11:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA10947 for hackers-outgoing; Sun, 28 Jul 1996 14:11:59 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA10927; Sun, 28 Jul 1996 14:11:52 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id OAA03149; Sun, 28 Jul 1996 14:11:23 -0700 (PDT) To: "Karl Denninger, MCSNet" cc: mark@quickweb.com (Mark Mayo), hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: PPro Question In-reply-to: Your message of "Sun, 28 Jul 1996 15:31:16 CDT." Date: Sun, 28 Jul 1996 14:11:23 -0700 Message-ID: <3147.838588283@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I can also set up a SUP server for the CVS tree if people are interested. > Would this help folks? We have *lots* of free cycles and net bandwidth, so > we're not constrained at all. What I don't think I will be able to do right That's be great - sup2 being down since Paul moved jobs has really hurt us since none of the others were ever as reliable as sup2, and now everyone's back to swamping freefall again. If I can ever get John to finally release cvsup, we could also deploy that on the box and serve cvs, -current and -stable all from the single repository and with no need to cvs update a checked-out tree, as we do now for -sup. I was actually just in the process of creating another sup2 with Paul Vixie, who'll site the server at DEC's NAP, but 3 "major" [cv]sup servers would be even better than 2, so please don't let that stop you. > Anyone? Give me a list and amount of disk required (will it fit on a > 4G drive?) and I'll go grab it. No big deal; 4G disks are only about a > kilobuck these days, and I have a bunch of them available to me. Dedicating Heck, if you can make the machine generally accessible to me via ssh, I'll set it all up myself. I was already planning to do this in Paul's case, and if I can set the 2 machines up fairly identically it would make these resources even easier to manage in the future. Jordan From owner-freebsd-hackers Sun Jul 28 14:41:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA12094 for hackers-outgoing; Sun, 28 Jul 1996 14:41:33 -0700 (PDT) Received: from pdx1 (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA12089; Sun, 28 Jul 1996 14:41:27 -0700 (PDT) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1 (8.6.9/8.6.9) with ESMTP id OAA06725; Sun, 28 Jul 1996 14:42:36 -0700 Received: (proff@localhost) by suburbia.net (8.7.4/Proff-950810) id HAA24022; Mon, 29 Jul 1996 07:40:35 +1000 From: Julian Assange Message-Id: <199607282140.HAA24022@suburbia.net> Subject: Re: PPro Question To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 29 Jul 1996 07:40:34 +1000 (EST) Cc: karl@mcs.com, mark@quickweb.com, hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <3147.838588283@time.cdrom.com> from "Jordan K. Hubbard" at Jul 28, 96 02:11:23 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I was actually just in the process of creating another sup2 with Paul > Vixie, who'll site the server at DEC's NAP, but 3 "major" [cv]sup > servers would be even better than 2, so please don't let that stop you. > > Heck, if you can make the machine generally accessible to me via ssh, > I'll set it all up myself. I was already planning to do this in > Paul's case, and if I can set the 2 machines up fairly identically it > would make these resources even easier to manage in the future. > > Jordan Vixie may want to have a wee chat to Randal first ;\ -- "Of all tyrannies a tyranny sincerely exercised for the good of its victims may be the most oppressive. It may be better to live under robber barons than under omnipotent moral busybodies, The robber baron's cruelty may sometimes sleep, his cupidity may at some point be satiated; but those who torment us for own good will torment us without end, for they do so with the approval of their own conscience." - C.S. Lewis, _God in the Dock_ +---------------------+--------------------+----------------------------------+ |Julian Assange RSO | PO Box 2031 BARKER | Secret Analytic Guy Union | |proff@suburbia.net | VIC 3122 AUSTRALIA | finger for PGP key hash ID = | |proff@gnu.ai.mit.edu | FAX +61-3-98199066 | 0619737CCC143F6DEA73E27378933690 | +---------------------+--------------------+----------------------------------+ From owner-freebsd-hackers Sun Jul 28 15:44:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA15255 for hackers-outgoing; Sun, 28 Jul 1996 15:44:21 -0700 (PDT) Received: from relay-2.mail.demon.net (disperse.demon.co.uk [158.152.1.77]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA15242 for ; Sun, 28 Jul 1996 15:44:17 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-2.mail.demon.net id ah05925; 28 Jul 96 23:44 +0100 Received: from salokin.demon.co.uk ([194.222.5.136]) by relay-3.mail.demon.net id aa27472; 28 Jul 96 23:42 +0100 Message-ID: <31FBECE5.865@salokin.demon.co.uk> Date: Sun, 28 Jul 1996 23:42:45 +0100 From: Nicholas Metcalfe Organization: Hangabout X-Mailer: Mozilla 2.02 (Win95; I) MIME-Version: 1.0 To: vote@imdb.com Subject: Form posted from Mozilla Content-type: text/plain Content-Disposition: inline; form-data Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk VOTES= vote 5 Twister (1996) From owner-freebsd-hackers Sun Jul 28 15:58:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA15968 for hackers-outgoing; Sun, 28 Jul 1996 15:58:45 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA15957 for ; Sun, 28 Jul 1996 15:58:43 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id RAA00322; Sun, 28 Jul 1996 17:58:25 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Sun, 28 Jul 1996 17:58:24 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu To: Doug Rabson cc: Dmitry Khrustalev , hackers@freefall.freebsd.org, hasty@rah.star-gate.com Subject: Re: NFS crash In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 25 Jul 1996, Doug Rabson wrote: > On Wed, 24 Jul 1996, Dmitry Khrustalev wrote: > > > Yes. solaris 2.5 uses readdirplus and it is broken in freebsd. > > Look at VOP_VGET in nfs_serv.c:2913. > > This patch should fix readdirplus: This patch did the trick for on OSF/1 client mounting my freebsd server. :-) -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-hackers Sun Jul 28 16:35:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA17548 for hackers-outgoing; Sun, 28 Jul 1996 16:35:52 -0700 (PDT) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA17543 for ; Sun, 28 Jul 1996 16:35:50 -0700 (PDT) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id TAA19640; Sun, 28 Jul 1996 19:35:18 -0400 Date: Sun, 28 Jul 1996 19:35:17 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: FreeBSD hackers Subject: Re: -T appears to be a can of worms: In-Reply-To: <199607270913.LAA28959@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 27 Jul 1996, J Wunsch wrote: > As Ron G. Minnich wrote: > > p0 63% cc -o zclient -T 4096 zclient.o ../lib/libzounds.a > > p0 64% nm zclient > > Segmentation fault (core dumped) > You are not supposed to use -T loadaddr unless you know what you're > doing... (e.g. when you're linking a kernel). Yup you're right it was pilot error. I needed to get the code/text/etc. running up at a high address and thought that this might be possible on xxxbsd or linux. No dice. I've used other os'es that let you do this, so read too much into the various man pages. ah well. I got to the needed capability a different way. Thanks! ron From owner-freebsd-hackers Sun Jul 28 17:58:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA21436 for hackers-outgoing; Sun, 28 Jul 1996 17:58:00 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA21429 for ; Sun, 28 Jul 1996 17:57:56 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id TAA00731; Sun, 28 Jul 1996 19:57:50 -0500 (EST) From: "John S. Dyson" Message-Id: <199607290057.TAA00731@dyson.iquest.net> Subject: Re: -T appears to be a can of worms: To: rminnich@Sarnoff.COM (Ron G. Minnich) Date: Sun, 28 Jul 1996 19:57:50 -0500 (EST) Cc: freebsd-hackers@freebsd.org In-Reply-To: from "Ron G. Minnich" at Jul 28, 96 07:35:17 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Yup you're right it was pilot error. I needed to get the code/text/etc. > running up at a high address and thought that this might be possible on > xxxbsd or linux. No dice. I've used other os'es that let you do this, so read > too much into the various man pages. ah well. I got to the needed > capability a different way. > Try mmap'ing the image in. Our a.out format doesn't afford the info for mapping the image with the existing image-activator stuff, but mmaping an image and jumping to it -- must just work. John From owner-freebsd-hackers Sun Jul 28 18:43:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA23422 for hackers-outgoing; Sun, 28 Jul 1996 18:43:59 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA23417 for ; Sun, 28 Jul 1996 18:43:55 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id UAA00805; Sun, 28 Jul 1996 20:43:17 -0500 (EST) From: "John S. Dyson" Message-Id: <199607290143.UAA00805@dyson.iquest.net> Subject: Re: -T appears to be a can of worms: To: toor@dyson.iquest.net (John S. Dyson) Date: Sun, 28 Jul 1996 20:43:17 -0500 (EST) Cc: rminnich@Sarnoff.COM, freebsd-hackers@freebsd.org In-Reply-To: <199607290057.TAA00731@dyson.iquest.net> from "John S. Dyson" at Jul 28, 96 07:57:50 pm X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Try mmap'ing the image in. Our a.out format doesn't afford the > info for mapping the image with the existing image-activator > stuff, but mmaping an image and jumping to it -- must just work. ^^^^ I meant might. > From owner-freebsd-hackers Sun Jul 28 19:23:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA24874 for hackers-outgoing; Sun, 28 Jul 1996 19:23:26 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA24846; Sun, 28 Jul 1996 19:23:19 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id TAA03622; Sun, 28 Jul 1996 19:21:49 -0700 (PDT) To: Julian Assange cc: karl@mcs.com, mark@quickweb.com, hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: PPro Question In-reply-to: Your message of "Mon, 29 Jul 1996 07:40:34 +1000." <199607282140.HAA24022@suburbia.net> Date: Sun, 28 Jul 1996 19:21:49 -0700 Message-ID: <3620.838606909@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Vixie may want to have a wee chat to Randal first ;\ Huh? Jordan From owner-freebsd-hackers Sun Jul 28 23:21:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA04779 for hackers-outgoing; Sun, 28 Jul 1996 23:21:44 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA04774 for ; Sun, 28 Jul 1996 23:21:39 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA06986; Mon, 29 Jul 1996 08:20:56 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA07568; Mon, 29 Jul 1996 08:20:55 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id IAA02345; Mon, 29 Jul 1996 08:04:01 +0200 (MET DST) From: J Wunsch Message-Id: <199607290604.IAA02345@uriah.heep.sax.de> Subject: Re: -T appears to be a can of worms: To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Mon, 29 Jul 1996 08:04:01 +0200 (MET DST) Cc: rminnich@Sarnoff.COM (Ron G. Minnich) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Ron G. Minnich" at "Jul 28, 96 07:35:17 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Ron G. Minnich wrote: > > You are not supposed to use -T loadaddr unless you know what you're > > doing... (e.g. when you're linking a kernel). > > Yup you're right it was pilot error. I needed to get the code/text/etc. > running up at a high address and thought that this might be possible on > xxxbsd or linux. Btw., it's perhaps possible with ELF. Have you tried this? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Jul 29 01:42:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA13075 for hackers-outgoing; Mon, 29 Jul 1996 01:42:23 -0700 (PDT) Received: from hp.com (hp.com [15.255.152.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA13070 for ; Mon, 29 Jul 1996 01:42:20 -0700 (PDT) Received: from fakir.india.hp.com by hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA241199732; Mon, 29 Jul 1996 01:42:16 -0700 Received: from localhost by fakir.india.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA225279874; Mon, 29 Jul 1996 14:14:35 +0530 Message-Id: <199607290844.AA225279874@fakir.india.hp.com> To: hackers@freebsd.org Subject: Q: How to create lint libs? Date: Mon, 29 Jul 1996 14:14:34 +0530 From: A JOSEPH KOSHY Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I wasn't able to figure out the procedure to create lint libs for the system. The default `lint' target is quiet no-op. I frequently run my code against lint and occasionally I do wade in and cleanup the 1001 warnings too :-), so I would like to build these by default. Could some kind soul send me the right incantations? I'm running -current as of the last weekend. Thanks, Koshy From owner-freebsd-hackers Mon Jul 29 02:26:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA15567 for hackers-outgoing; Mon, 29 Jul 1996 02:26:09 -0700 (PDT) Received: from mail.ca2.so-net.or.jp (mail.ca2.so-net.or.jp [202.238.95.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA15562 for ; Mon, 29 Jul 1996 02:26:06 -0700 (PDT) Received: from chiota (ppp724d.pppp.ap.so-net.or.jp [202.238.114.77]) by mail.ca2.so-net.or.jp (8.7.5/3.4W396052919) with SMTP id SAA78892; Mon, 29 Jul 1996 18:25:55 +0900 Received: from localhost (localhost [127.0.0.1]) by chiota (8.6.12/) with SMTP id SAA00390; Mon, 29 Jul 1996 18:24:57 +0900 Message-Id: <199607290924.SAA00390@chiota> To: hackers@freebsd.org Cc: shigio@ca2.so-net.or.jp Subject: Unix source code tour by global 1.3 and patched vi. Date: Mon, 29 Jul 1996 18:24:57 +0900 From: Shigio Yamaguchi Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, this is Yamaguchi. I put the source code of GLOBAL version1.3 for FreeBSD 2.1R at http://ux01.so-net.or.jp/~shigio/freebsd/emain.html GLOBAL is a command which find the locations of specified function in C source files. This includes the patch for VI(nvi/nex 1.34) to use global within the editor. NEW FEATURE in VERSION 1.3: ~~~~~~~~~~~~~~~~~~~~~~~~~~~ o Global search in not only a source tree but also library paths specified by environment variable GTAGSLIBPATH. Example: % cd /develop/src/mh % gtags <- make tag file % global mhl uip/mhlsbr.c <- mhl() found in the source tree % global strlen <- strlen() not found % cd /usr/src/lib % gtags <- make library tag % cd /usr/src/sys % gtags <- make system call tag % setenv GTAGSLIBPATH /usr/src/lib:/usr/src/sys % cd /develop/src/mh % global strlen ../../../usr/src/lib/libc/string/strlen.c <- strlen() is found in library % global access ../../../usr/src/sys/kern/vfs_syscalls.c <- access() is found in kernel OTHER FEATURES: ~~~~~~~~~~~~~~~ o Global can find the locations of specified function very quickly. o Global can locate not only function definitions but also function references. o Global can treat a source tree containing subdirectories and you can get relative path of objects from anywhere within the tree. o Global allow duplicate entries. o Global can understand perl's regular expression. o Global can be executed from vi's tag commands.(nvi/nex 1.34 only) The new version of nvi/nex(1.61 and later) supports duplicate entries in tags file. You can use patched ctags in this this package with the nvi/nex. If you cannot get items, please send E-mail to me. Please enjoy. -- Shigio Yamaguchi E-Mail: shigio@ca2.so-net.or.jp Home Page: http://ux01.so-net.or.jp/~shigio/ From owner-freebsd-hackers Mon Jul 29 04:20:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA20050 for hackers-outgoing; Mon, 29 Jul 1996 04:20:37 -0700 (PDT) Received: from sam.networx.ie (dublin-ts11-222.indigo.ie [194.125.133.222]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA20045 for ; Mon, 29 Jul 1996 04:20:23 -0700 (PDT) Received: from mip1.networx.ie (mip1.networx.ie [194.9.12.1]) by sam.networx.ie (8.6.12/8.6.12) with SMTP id MAA04019; Mon, 29 Jul 1996 12:08:56 +0100 X-Organisation: I.T. NetworX Ltd X-Business: Network Consultancy and Training X-Address: 67 Merrion Square, Dublin 2, Ireland X-Voice: +353-1-676-8866 X-Fax: +353-1-676-8868 Received: from mike.networx.ie by mip1.networx.ie Date: Mon, 29 Jul 1996 12:00:25 BST From: Michael Ryan Reply-To: mike@NetworX.ie Subject: hackers-digest V1 #1337 (pppd and PAP) To: Darius Moos Cc: freebsd-hackers-digest@FreeBSD.ORG Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Darius, You say you've connected to the other fsbd box using CHAP. Have you connected to it using PAP? If not, here's my config to connect to another fbsd box using PAP. Maybe it's not perfect, but it does work. Client: ------ # cd /etc/ppp # cat options modem crtscts # cat options.client lock user mike remotename sam 1.2.3.4:1.2.3.5 connect "chat -f /etc/ppp/chat.client" # cat pap-secrets mike sam password.for.mike Server (hostname "sam"/"sam.networx.ie"): ---------------------------------------- # cd /etc/ppp # cat options modem crtscts # cat options.server lock auth +pap usehostname 1.2.3.5:1.2.3.4 # cat pap-secrets mike sam.networx.ie password.for.mike 1.2.3.4 In the above, remember "mike" is a user and "sam" is a host. Hope this helps, Mike --- From owner-freebsd-hackers Mon Jul 29 04:59:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA21973 for hackers-outgoing; Mon, 29 Jul 1996 04:59:33 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA21968 for ; Mon, 29 Jul 1996 04:59:30 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id LAA28717 for ; Mon, 29 Jul 1996 11:59:27 GMT Date: Mon, 29 Jul 1996 20:59:27 +0900 (JST) From: Michael Hancock To: hackers@FreeBSD.ORG Subject: kernel assertions In-Reply-To: <199607290924.SAA00390@chiota> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Any comments on introducing an assertion macro for kernel code that panics if the expression is false and does nothing otherwise. It would also be very cool to preprocess it out with something like a -NDEBUG flag. It could be called KASSERT or KERN_ASSERT. Benefits: 1) You write most of your code assuming the parameters are correct. This would get rid of a few if ... then ... else's. 2) You define your function requirements clearly to callers of your function. An example follows below: Original version ---------------- /* * remove the buffer from the appropriate free list */ void bremfree(struct buf * bp) { int s = splbio(); if (bp->b_qindex != QUEUE_NONE) { TAILQ_REMOVE(&bufqueues[bp->b_qindex], bp, b_freelist); bp->b_qindex = QUEUE_NONE; } else { panic("bremfree: removing a buffer when not on a queue"); } splx(s); } KERN_ASSERT version --------------- /* * remove the buffer from the appropriate free list */ void bremfree(struct buf * bp) { int s = splbio(); KERN_ASSERT(bp->b_qindex != QUEUE_NONE) TAILQ_REMOVE(&bufqueues[bp->b_qindex], bp, b_freelist); bp->b_qindex = QUEUE_NONE; splx(s); } This was a simple example but I'm sure it could make code a lot less intricate in other places. Confident performance freaks can preprocess away a few clock cycles. This could add up for frequently called functions. -- Mike Hancock From owner-freebsd-hackers Mon Jul 29 05:02:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA22107 for hackers-outgoing; Mon, 29 Jul 1996 05:02:26 -0700 (PDT) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA22098 for ; Mon, 29 Jul 1996 05:02:20 -0700 (PDT) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id IAA22316; Mon, 29 Jul 1996 08:01:14 -0400 Date: Mon, 29 Jul 1996 08:01:14 -0400 (EDT) From: "Ron G. Minnich" X-Sender: rminnich@terra To: "John S. Dyson" cc: freebsd-hackers@freebsd.org Subject: Re: -T appears to be a can of worms: In-Reply-To: <199607290057.TAA00731@dyson.iquest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 28 Jul 1996, John S. Dyson wrote: > Try mmap'ing the image in. Our a.out format doesn't afford the > info for mapping the image with the existing image-activator > stuff, but mmaping an image and jumping to it -- must just work. yeah i'm doing that now. Got some problems with it. I'll let you know how it goes. I did compile -fpic and -static for this attempt. ron From owner-freebsd-hackers Mon Jul 29 06:35:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA25273 for hackers-outgoing; Mon, 29 Jul 1996 06:35:09 -0700 (PDT) Received: from pancake.remcomp.fr (root@pancake.remcomp.fr [194.51.30.247]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA25081 for ; Mon, 29 Jul 1996 06:33:38 -0700 (PDT) Received: from zapata.omnix.fr.org (zapata [128.127.10.1]) by zapata.omnix.fr.org (8.6.12/8.6.9) with SMTP id PAA13831 for ; Mon, 29 Jul 1996 15:17:14 +0200 Date: Mon, 29 Jul 1996 15:17:14 +0200 (MET DST) From: didier@omnix.fr.org To: hackers@freebsd.org Subject: not directly related to freebsd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk do you know where I could find a demagnetizer for hard disks (oven that heat to the curie point are ok) thanks for your help -- Didier Derny | My computer is Microsoft Free... didier@omnix.fr.org | FreeBSD 2.1-STABLE site From owner-freebsd-hackers Mon Jul 29 06:43:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA25657 for hackers-outgoing; Mon, 29 Jul 1996 06:43:05 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA25649; Mon, 29 Jul 1996 06:43:00 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id PAA00534; Mon, 29 Jul 1996 15:43:16 +0200 (MET DST) To: Michael Hancock cc: hackers@FreeBSD.ORG Subject: Re: kernel assertions In-reply-to: Your message of "Mon, 29 Jul 1996 20:59:27 +0900." Date: Mon, 29 Jul 1996 15:43:16 +0200 Message-ID: <532.838647796@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Any comments on introducing an assertion macro for kernel code that panics >if the expression is false and does nothing otherwise. It would also be >very cool to preprocess it out with something like a -NDEBUG flag. It >could be called KASSERT or KERN_ASSERT. I like this idea. How about: in we put: #if defined(DIAGNOSTIC) || defined(WITH_ASSERTS) #define ASSERT(cond, expl) if (cond) panic expl ; else ; #else #define ASSERT(cond, expl) /* nothing */ #endif In our code: void foo(char *buf, int i { ASSERT(buf,("foo(%p, %d): buf is zero",buf,i)); ... } -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hackers Mon Jul 29 06:47:30 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA26043 for hackers-outgoing; Mon, 29 Jul 1996 06:47:30 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA26026; Mon, 29 Jul 1996 06:47:26 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id PAA00562; Mon, 29 Jul 1996 15:47:43 +0200 (MET DST) To: didier@omnix.fr.org cc: hackers@FreeBSD.ORG Subject: Re: not directly related to freebsd In-reply-to: Your message of "Mon, 29 Jul 1996 15:17:14 +0200." Date: Mon, 29 Jul 1996 15:47:43 +0200 Message-ID: <560.838648063@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message , didi er@omnix.fr.org writes: > >do you know where I could find a demagnetizer for hard disks >(oven that heat to the curie point are ok) how about the local waste-disposal facility ? We used that a lot here in .dk You drive up there with your disk, drop it into a special hole they have for that kind of services, and after 5 seconds in free fall, your goods are in a very nice 1500 C environment that satisfies most if not all NATO requirements for destruction of data. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hackers Mon Jul 29 06:58:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA26980 for hackers-outgoing; Mon, 29 Jul 1996 06:58:44 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA26975 for ; Mon, 29 Jul 1996 06:58:42 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id GAA26833; Mon, 29 Jul 1996 06:58:31 -0700 (PDT) Message-Id: <199607291358.GAA26833@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Michael Hancock cc: hackers@FreeBSD.ORG Subject: Re: kernel assertions In-reply-to: Your message of "Mon, 29 Jul 1996 20:59:27 +0900." From: David Greenman Reply-To: dg@root.com Date: Mon, 29 Jul 1996 06:58:31 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >This was a simple example but I'm sure it could make code a lot less >intricate in other places. ...and a lot less informative. I prefer the existing model. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Jul 29 07:00:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA27143 for hackers-outgoing; Mon, 29 Jul 1996 07:00:58 -0700 (PDT) Received: from neuron.bsd.uni-passau.de (ith7.extern.inet-nb.de [194.121.36.168]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA27135 for ; Mon, 29 Jul 1996 07:00:42 -0700 (PDT) Received: (from moos@localhost) by neuron.bsd.uni-passau.de (8.6.12/8.6.12) id PAA01003 for hackers@freebsd.org; Mon, 29 Jul 1996 15:55:00 +0200 From: Darius Moos Message-Id: <199607291355.PAA01003@neuron.bsd.uni-passau.de> Subject: RE: hackers-digest V1 #1337 (pppd and PAP) To: hackers@freebsd.org Date: Mon, 29 Jul 1996 15:55:00 +0200 (MET DST) Reply-To: moos@degnet.baynet.de X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Mike, thanks for your reply, but it does NOT work. > You say you've connected to the other fsbd box using CHAP. Yes > Have you connected to it using PAP? Nope. I want to connect a Linux-box-2.x using PAP. Sorry if this was not clear in my mailing. BTW i've tried your configuration. No success. Horror-show continues. Result of pppd-logging: Jul 29 14:31:56 neuron pppd[324]: pppd 2.1.2 started by moos, uid 30001 Jul 29 14:32:21 neuron pppd[325]: Connected... Jul 29 14:32:22 neuron pppd[325]: Using interface ppp0 Jul 29 14:32:22 neuron pppd[325]: Connect: ppp0 <--> /dev/cuaa1 Jul 29 14:32:22 neuron pppd[325]: sent [LCP ConfReq id=0x1 ] Jul 29 14:32:25 neuron pppd[325]: sent [LCP ConfReq id=0x1 ] Jul 29 14:32:25 neuron pppd[325]: rcvd [LCP ConfReq id=0x0 ] Jul 29 14:32:25 neuron pppd[325]: sent [LCP ConfRej id=0x0 ] Jul 29 14:32:25 neuron pppd[325]: rcvd [LCP ConfAck id=0x1 ] Jul 29 14:32:25 neuron pppd[325]: rcvd [LCP TermReq id=0x1 00 00 02 dc] Jul 29 14:32:25 neuron pppd[325]: sent [LCP TermAck id=0x1] Jul 29 14:32:28 neuron pppd[325]: sent [LCP ConfReq id=0xff ] Jul 29 14:32:55 neuron last message repeated 9 times Jul 29 14:32:58 neuron pppd[325]: LCP: timeout sending Config-Requests Jul 29 14:32:58 neuron pppd[325]: Connection terminated. Jul 29 14:32:58 neuron pppd[325]: Exit. Please look at the line Jul 29 14:32:25 neuron pppd[325]: sent [LCP ConfRej id=0x0 ] ^^^^^^^^^^^ so my pppd is rejecting to authenticate. BUT when trying to authenticate with CHAP (options: auth -pap +chap) i'm getting following result: Jul 29 15:42:04 neuron pppd[948]: pppd 2.1.2 started by moos, uid 30001 Jul 29 15:42:28 neuron pppd[949]: Connected... Jul 29 15:42:29 neuron pppd[949]: Using interface ppp0 Jul 29 15:42:30 neuron pppd[949]: Connect: ppp0 <--> /dev/cuaa1 Jul 29 15:42:30 neuron pppd[949]: sent [LCP ConfReq id=0x1 ] Jul 29 15:42:33 neuron pppd[949]: sent [LCP ConfReq id=0x1 ] Jul 29 15:42:33 neuron pppd[949]: rcvd [LCP ConfReq id=0x0 ] Jul 29 15:42:33 neuron pppd[949]: sent [LCP ConfRej id=0x0 ] Jul 29 15:42:33 neuron pppd[949]: rcvd [LCP ConfRej id=0x1 ] Jul 29 15:42:33 neuron pppd[949]: sent [LCP ConfReq id=0x2 ] Jul 29 15:42:33 neuron pppd[949]: rcvd [LCP TermReq id=0x1 00 00 02 dc] Jul 29 15:42:33 neuron pppd[949]: sent [LCP TermAck id=0x1] Jul 29 15:42:36 neuron pppd[949]: sent [LCP ConfReq id=0x2 ] Jul 29 15:43:00 neuron last message repeated 8 times Jul 29 15:43:03 neuron pppd[949]: LCP: timeout sending Config-Requests Jul 29 15:43:03 neuron pppd[949]: Connection terminated. Jul 29 15:43:03 neuron pppd[949]: Exit. Have a look at the lines: Jul 29 15:42:33 neuron pppd[949]: sent [LCP ConfReq id=0x1 ] Jul 29 15:42:33 neuron pppd[949]: rcvd [LCP ConfReq id=0x0 ] Jul 29 15:42:33 neuron pppd[949]: sent [LCP ConfRej id=0x0 ] Jul 29 15:42:33 neuron pppd[949]: rcvd [LCP ConfRej id=0x1 ] So my pppd wants to authenticate using [chap 05] and the linux-ppp wants to use [chap 80]. The strange thing is, that my provider says explicitly, "the authentication is PAP" !!! The other thing is, that Win-95 has no problems connecting to my provider. When dialing, i just write username and password in the appropriate textfields and everything is fine. (Shit ... don't want to use Win-95; i want and have to use FreeBSD !!!) Please send me more replies, help, info, pointers, patches, ... Thanks in advance. Bye, Darius. From owner-freebsd-hackers Mon Jul 29 07:01:37 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA27185 for hackers-outgoing; Mon, 29 Jul 1996 07:01:37 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA27179 for ; Mon, 29 Jul 1996 07:01:35 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id HAA26854; Mon, 29 Jul 1996 07:01:23 -0700 (PDT) Message-Id: <199607291401.HAA26854@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Poul-Henning Kamp cc: Michael Hancock , hackers@FreeBSD.ORG Subject: Re: kernel assertions In-reply-to: Your message of "Mon, 29 Jul 1996 15:43:16 +0200." <532.838647796@critter.tfs.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 29 Jul 1996 07:01:23 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >In our code: > void > foo(char *buf, int i > { > ASSERT(buf,("foo(%p, %d): buf is zero",buf,i)); > ... > } Blech. Macros are evil unless they actually do something real to improve the code. Please, let's NOT adopt this practice. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Jul 29 07:09:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA27585 for hackers-outgoing; Mon, 29 Jul 1996 07:09:50 -0700 (PDT) Received: from relay.hp.com (relay.hp.com [15.255.152.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA27579 for ; Mon, 29 Jul 1996 07:09:47 -0700 (PDT) Received: from fakir.india.hp.com by relay.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA249269377; Mon, 29 Jul 1996 07:09:41 -0700 Received: from localhost by fakir.india.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA255919517; Mon, 29 Jul 1996 19:41:57 +0530 Message-Id: <199607291411.AA255919517@fakir.india.hp.com> To: Poul-Henning Kamp Cc: Michael Hancock , hackers@FreeBSD.ORG Subject: Re: kernel assertions In-Reply-To: Your message of "Mon, 29 Jul 1996 15:43:16 +0200." <532.838647796@critter.tfs.com> Date: Mon, 29 Jul 1996 19:41:56 +0530 From: A JOSEPH KOSHY Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>>>>> "mh" == "Michael Hancock", "phk" == "Poul Henning-Kamp" >>>>> mh>Any comments on introducing an assertion macro for kernel code that panics ... mh>could be called KASSERT or KERN_ASSERT. phk> I like this idea. Its been my experience that judicious use of ASSERTs goes a long way in assuring code quality. Even better is of course a thorough code review :-). However, some of these checks should probably remain even in a production kernel since pathological situations do arise, and its better to abort than corrupt user data silently. So we probably have two kinds of asserts here: one kind is thorough but expensive (which could be removed using -DNDEBUG or whatever) and the other that is minimal and cheap. Koshy From owner-freebsd-hackers Mon Jul 29 07:24:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA28597 for hackers-outgoing; Mon, 29 Jul 1996 07:24:21 -0700 (PDT) Received: from etinc.com (etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA28590 for ; Mon, 29 Jul 1996 07:24:15 -0700 (PDT) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id KAA02782 for ; Mon, 29 Jul 1996 10:28:22 -0400 Date: Mon, 29 Jul 1996 10:28:22 -0400 Message-Id: <199607291428.KAA02782@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: hackers@freebsd.org From: dennis@etinc.com (Dennis) Subject: IPX (NS) stuff Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tcpdump seems to decode ipx packets, but you cant do a tcpdump -i ed1 if there is is only an xns address associated with ed1, and you can't do tcpdump -proto ipx is this correct? Dennis ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous Communications Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD and LINUX From owner-freebsd-hackers Mon Jul 29 07:29:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA28921 for hackers-outgoing; Mon, 29 Jul 1996 07:29:10 -0700 (PDT) Received: from etinc.com (etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA28909 for ; Mon, 29 Jul 1996 07:29:07 -0700 (PDT) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id KAA02814 for ; Mon, 29 Jul 1996 10:33:09 -0400 Date: Mon, 29 Jul 1996 10:33:09 -0400 Message-Id: <199607291433.KAA02814@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: hackers@freebsd.org From: dennis@etinc.com (Dennis) Subject: Re: HSSI ? Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J. Dixon writes.... >Is anyone out there using FreeBSD to handle WAN traffic at DS3 data >rates? Or to put the question differently: is anyone actually using a >PCI HSSI card with FreeBSD? Building a T3/HSSI card is much easier than figuring out how to get unix to consistently and reliably route 86Mb/s without dropping a lot of traffic :( Dennis ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous Communications Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD and LINUX From owner-freebsd-hackers Mon Jul 29 08:00:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA02183 for hackers-outgoing; Mon, 29 Jul 1996 08:00:21 -0700 (PDT) Received: from apollo.it.hq.nasa.gov (apollo.it.hq.nasa.gov [131.182.119.87]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA02155; Mon, 29 Jul 1996 08:00:12 -0700 (PDT) Received: from wirehead.it.hq.nasa.gov (wirehead.it.hq.nasa.gov [131.182.119.88]) by apollo.it.hq.nasa.gov (8.6.12/8.6.12) with ESMTP id PAA27215; Mon, 29 Jul 1996 15:00:12 GMT Received: from localhost (cshenton@localhost) by wirehead.it.hq.nasa.gov (8.6.12/8.6.12) with SMTP id OAA01389; Mon, 29 Jul 1996 14:58:09 GMT Message-Id: <199607291458.OAA01389@wirehead.it.hq.nasa.gov> X-Authentication-Warning: wirehead.it.hq.nasa.gov: cshenton owned process doing -bs X-Authentication-Warning: wirehead.it.hq.nasa.gov: Host localhost didn't use HELO protocol To: lithium@cia-g.com Cc: hardware@freebsd.org, hackers@freebsd.org Subject: Re: Fatal trap 12: page fault while in kernel mode In-Reply-To: Your message of "Fri, 26 Jul 1996 16:13:08 -0600 (MDT)" References: X-Mailer: Mew version 1.03 on Emacs 19.31.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 29 Jul 1996 10:58:05 -0400 From: Chris Shenton Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 26 Jul 1996 16:13:08 -0600 (MDT) Stephen Fisher wrote: lithium> (This is running 2.1.5R, I had the same problems with 2.1R). lithium> Sometimes the machine will even "Freeze" and reboot in the lithium> middle of doing something with no warning..:] lithium> lithium> Fatal tral 12: page fault while in kernel mode lithium> Fault virtual address = 0xfc7 lithium> Fault code = supervisor read, page not present lithium> Instruction pointer = 0x8:0xf0181de2 lithium> Code segment = base 0x0, limit 0xfffff, type 0x1b lithium> DPL 0, pres 1, def32 1, gran 0 lithium> Processor eflags = interrupt enabled, resume, IOPL = 0 lithium> Current process = 249 (cpp) lithium> Interrupt mask = lithium> panic: page fault lithium> lithium> As I said it almost always happens on the same instruction lithium> pointer. The process can be anything but it usually occurs lithium> with gcc (such as when compiling the kernel, I can't even get lithium> a minute or two into the compile). lithium> lithium> Hardware: 16meg of parity ram, AMD DX4/100, SiS 85c471 lithium> chipset motherboard (ick!) with VLB bus, Adaptec 284x SCSI lithium> controller, S3 video card, etc. I just brought up 2.1.5R on an AMD486-100 and got a very similar problem after rebuilding the kernel. It spat out this kind of error -- in random processes like sh and inetd -- and failed to boot. At the time I was trying to compile in support for a GUS MAX and PC Audio devices. I also noticed I was getting file corruption, as if my disk was dying or some such, so I suspect that possibly the kernel file also had corruption, causing a bogus instruction to be executed. I just re-installed on a new disk, so if this disappears, I'll blame the drive. If not, I'm not sure :-( From owner-freebsd-hackers Mon Jul 29 08:03:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA02609 for hackers-outgoing; Mon, 29 Jul 1996 08:03:15 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA02599; Mon, 29 Jul 1996 08:03:11 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id RAA00675; Mon, 29 Jul 1996 17:03:28 +0200 (MET DST) To: dg@Root.COM cc: Michael Hancock , hackers@FreeBSD.ORG Subject: Re: kernel assertions In-reply-to: Your message of "Mon, 29 Jul 1996 06:58:31 PDT." <199607291358.GAA26833@root.com> Date: Mon, 29 Jul 1996 17:03:27 +0200 Message-ID: <673.838652607@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199607291358.GAA26833@root.com>, David Greenman writes: >>This was a simple example but I'm sure it could make code a lot less >>intricate in other places. > > ...and a lot less informative. I prefer the existing model. I think that they supplement each other, they are certainly not exclusive. I still think it's a good idea. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hackers Mon Jul 29 08:09:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA03140 for hackers-outgoing; Mon, 29 Jul 1996 08:09:02 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA03135 for ; Mon, 29 Jul 1996 08:08:56 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id PAA29597; Mon, 29 Jul 1996 15:08:41 GMT Date: Tue, 30 Jul 1996 00:08:41 +0900 (JST) From: Michael Hancock To: David Greenman cc: Poul-Henning Kamp , hackers@FreeBSD.ORG Subject: Re: kernel assertions In-Reply-To: <199607291401.HAA26854@root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Jul 1996, David Greenman wrote: > >In our code: > > void > > foo(char *buf, int i > > { > > ASSERT(buf,("foo(%p, %d): buf is zero",buf,i)); > > ... > > } > > Blech. Macros are evil unless they actually do something real to improve > the code. Please, let's NOT adopt this practice. They can reduce conceptual pollution. A conscientious programmer might integrate various checks into code that is trying to do something else and as a side-effect makes the code more complicated for readers and even compiler optimizers. Assertions are the most under-rated software engineering tool I can think of. If you want more information, stringify the expression in the assertion failure message or add a description parameter. At least give us the benefit of the doubt and try applying this to some random sample of code to see the difference it makes. I can think of 3 types of programmers who don't use assertions: 1) The god who writes all the code with zero bugs and doesn't need assertions. 2) The conscientious defensive programmer who integrates a lot of code checks in his code. The code has lots of nested structures and is complicated to read. 3) The programmer who gives up on the writing the checks because it's hell. His code is probably the source of very hard to find bugs. Assertions are simple to use and let's you write code for the problem at hand. There's no question as to where the responsibilities of the caller or callee lie. Mike Hancock From owner-freebsd-hackers Mon Jul 29 08:17:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04089 for hackers-outgoing; Mon, 29 Jul 1996 08:17:34 -0700 (PDT) Received: from apollo.it.hq.nasa.gov (apollo.it.hq.nasa.gov [131.182.119.87]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA04084 for ; Mon, 29 Jul 1996 08:17:31 -0700 (PDT) Received: from wirehead.it.hq.nasa.gov (wirehead.it.hq.nasa.gov [131.182.119.88]) by apollo.it.hq.nasa.gov (8.6.12/8.6.12) with ESMTP id PAA27337 for ; Mon, 29 Jul 1996 15:17:41 GMT Received: from localhost (cshenton@localhost) by wirehead.it.hq.nasa.gov (8.6.12/8.6.12) with SMTP id PAA01486 for ; Mon, 29 Jul 1996 15:15:39 GMT Message-Id: <199607291515.PAA01486@wirehead.it.hq.nasa.gov> X-Authentication-Warning: wirehead.it.hq.nasa.gov: cshenton owned process doing -bs X-Authentication-Warning: wirehead.it.hq.nasa.gov: Host localhost didn't use HELO protocol To: hackers@freefall.freebsd.org Subject: 2.1.5R sysinstall comments In-Reply-To: Your message of "Fri, 26 Jul 1996 15:38:49 -0700 (PDT)" References: <199607262238.PAA11270@freefall.freebsd.org> X-Mailer: Mew version 1.03 on Emacs 19.31.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 29 Jul 1996 11:15:39 -0400 From: Chris Shenton Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I recently installed 2.1.5R -- twice, but that's another story -- on a machine and had a couple comments/suggestions. I like some of the new features, especially the status at the bottom of what packages its getting and the transfer rate. MULTI-USER SYSINSTALL DISK/PARTITION PROBLEM: The second time I installed, it was because my first disk appeared to be getting corrupted. So I installed a second SCSI drive along with the first and ran sysinstall from multiuser. Answered the questions, and told it to label the partitions, which generated a core dump. Tried again and didn't label them, did the COMMIT, and it started downloading, but installing it on my currently-running disk in /, /usr, etc, blowing away perfectly good copies of stuff like sh! I tried again, labeling the partitions /new, /new/usr, /net/var on sd1 but it did the same thing. Finally, I downloaded the boot.flp, pulled the running drive out so it could only write to the new drive. RESTART WANTED: While downloading, my !#$@ing ISP dropped my PPP link. The download failed. I had to start from ground-zero. This is really painful at 28.8. It would be really cool if you could say "RESTART" on some menu, and it would examine what was already fetched versus what you wanted installed, and pickup from where it left off. Perhaps retrieval by sup would be a good thing. SAVED INSTALL CONFIG WANTED: I'd really like it if when you say COMMIT, it wrote a little config file to disk which said what partitions were where, what the network config parameters were, what packages were requested for installation. This way, if the install fails, you can start over (or restart!) without having to go through all the specifications again. PORTS CD/DIR CONFUSED, NO CANCEL OPTION: After sysinstalling, one of the menus asks if I want to install some ports. I said yes, and it told me that I need to insert CDROM-2; kinda difficult when I'm installing over PPP :-). I hit CONTINUE, cuz that's the only choice it gives me (*everything* should have a CANCEL option which backs you out), and it then talks to the ftpN.freebsd.org server, fails, and repeats its demands for the CD. After a couple iterations, it appears to give up, demands CDROM-1 this time, connects, fails, and eventually leads me back to the main sysinstall menu. Fortunately. Not sure why it isn't aware that I'm installing from ftp, not CD. It does go to the net to do something, but looks like maybe it wasn't finding the proper ports directly -- not sure. If I'm confused, let me know. Otherwise, I think this went pretty well and is an improvement over previous versions. PS: why don't you change the name of "boot4.flp" to "boot4mb.flp" to make it more obvious? just a suggestion. From owner-freebsd-hackers Mon Jul 29 08:22:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04717 for hackers-outgoing; Mon, 29 Jul 1996 08:22:22 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA04707 for ; Mon, 29 Jul 1996 08:22:17 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id PAA29645; Mon, 29 Jul 1996 15:22:09 GMT Date: Tue, 30 Jul 1996 00:22:09 +0900 (JST) From: Michael Hancock To: David Greenman cc: hackers@FreeBSD.ORG Subject: Re: kernel assertions In-Reply-To: <199607291358.GAA26833@root.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Jul 1996, David Greenman wrote: > >This was a simple example but I'm sure it could make code a lot less > >intricate in other places. > > ...and a lot less informative. I prefer the existing model. I think they are more informative when used to specify the parameter requirements immediately after the function is defined. Forget that a MACRO is being used to implement it and imagine that it was an integral part of the C language from the beginning. Mike Hancock From owner-freebsd-hackers Mon Jul 29 09:02:30 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA07345 for hackers-outgoing; Mon, 29 Jul 1996 09:02:30 -0700 (PDT) Received: from casparc.ppp.net (casparc.ppp.net [194.64.12.35]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA07312 for ; Mon, 29 Jul 1996 09:02:21 -0700 (PDT) Received: from ernie by casparc.ppp.net with uucp (Smail3.1.28.1 #1) id m0ukulq-000Hz6C; Mon, 29 Jul 96 18:02 MET DST Received: by ernie.kts.org (Smail3.1.29.1 #4) id m0uktbD-00001gC; Mon, 29 Jul 96 16:47 MET DST Message-Id: From: hm@kts.org (Hellmuth Michaelis) Subject: LAPD code with BSD copyright ? To: freebsd-hackers@freebsd.org Date: Mon, 29 Jul 1996 16:47:11 +0200 (MET DST) Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk before i write one myself, is there code available which handles LAPD and has BSD copyright attached to it ? (Yes, i know there is LAPB code in the netccitt source directory) hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe (A)bort, (R)etry, (I)nstall BSD ? From owner-freebsd-hackers Mon Jul 29 09:23:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA08257 for hackers-outgoing; Mon, 29 Jul 1996 09:23:26 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA08250 for ; Mon, 29 Jul 1996 09:23:22 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id JAA12583; Mon, 29 Jul 1996 09:22:45 -0700 (PDT) Received: from shrimp.whistle.com(207.76.205.74) by whistle.com via smap (V1.3) id sma012581; Mon Jul 29 09:22:17 1996 Received: (from julian@localhost) by shrimp.whistle.com (8.6.12/8.6.12) id JAA15299; Mon, 29 Jul 1996 09:22:16 -0700 From: Julian Elischer Message-Id: <199607291622.JAA15299@shrimp.whistle.com> Subject: Re: IPX (NS) stuff To: dennis@etinc.com (Dennis) Date: Mon, 29 Jul 1996 09:22:16 -0700 (PDT) Cc: hackers@freebsd.org In-Reply-To: <199607291428.KAA02782@etinc.com> from "Dennis" at Jul 29, 96 10:28:22 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It wouldn't surprise me.. ipx was put in in a rush > > > Tcpdump seems to decode ipx packets, but you cant do a > > tcpdump -i ed1 > > if there is is only an xns address associated with ed1, and you can't do > > tcpdump -proto ipx > > is this correct? > > Dennis > ---------------------------------------------------------------------------- > Emerging Technologies, Inc. http://www.etinc.com > > Synchronous Communications Cards and Routers For > Discriminating Tastes. 56k to T1 and beyond. Frame > Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD > and LINUX > > From owner-freebsd-hackers Mon Jul 29 11:04:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA13073 for hackers-outgoing; Mon, 29 Jul 1996 11:04:33 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA13068 for ; Mon, 29 Jul 1996 11:04:30 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id SAA00356; Mon, 29 Jul 1996 18:04:17 GMT Date: Tue, 30 Jul 1996 03:04:16 +0900 (JST) From: Michael Hancock To: Poul-Henning Kamp cc: hackers@FreeBSD.ORG Subject: Re: kernel assertions In-Reply-To: <532.838647796@critter.tfs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Jul 1996, Poul-Henning Kamp wrote: > >Any comments on introducing an assertion macro for kernel code that panics > >if the expression is false and does nothing otherwise. It would also be > >very cool to preprocess it out with something like a -NDEBUG flag. It > >could be called KASSERT or KERN_ASSERT. > > I like this idea. > > How about: > > in we put: > > #if defined(DIAGNOSTIC) || defined(WITH_ASSERTS) > #define ASSERT(cond, expl) if (cond) panic expl ; else ; > #else > #define ASSERT(cond, expl) /* nothing */ > #endif I think it's better to have ASSERTs on by default. When a stable snapshot is identified performance people can turn them off with something like NO_KERN_ASSERTS. You could also have the preprocessor generate the filename and line number. > > In our code: > void > foo(char *buf, int i > { > ASSERT(buf,("foo(%p, %d): buf is zero",buf,i)); > ... > } Even a simple ... ASSERT(buf, "Buf is zero"); would be very beneficial. There are other types of assertions, but I've found that the parameter checking assertions helped us spot around 80% of the problems found by assertions. The others types include: func decl ( arg decl ) [Argument assertions] [embedded assertions] [Return value assertions] Since the primary benefit was in the Argument checks we often just made the Return value assertions just comments. The embedded assertions were invariants that we needed to check for in more complex code. Thorough checks should probably be done as it is now with the DDB stuff as I've seen in a few places. #ifdef DDB Do thorough check() #endif #ifdef DDB #endif -- Mike Hancock From owner-freebsd-hackers Mon Jul 29 11:59:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15929 for hackers-outgoing; Mon, 29 Jul 1996 11:59:57 -0700 (PDT) Received: from tippy.cybernet.com (tippy.cybernet.com [192.245.33.86]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA15906 for ; Mon, 29 Jul 1996 11:59:47 -0700 (PDT) Received: (from pcobb@localhost) by tippy.cybernet.com (8.6.12/8.6.12) id OAA05031; Mon, 29 Jul 1996 14:53:41 -0400 Message-ID: X-Mailer: XFMail 0.4-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 29 Jul 1996 11:15:51 -0400 (EDT) Reply-To: pcobb@cybernet.com From: "Paul N. Cobb" To: Mark Mayo Subject: RE: PPro Question Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On 26-Jul-96 Mark Mayo wrote: >>Hi there - I was wondering if many people have experience with PPro >servers running FreeBSD. I just picked up a Digital Celebris XL 6150 >Pentium Pro (150MHz), and I installed FreeBSD 2.1R - no problems with the >install, the DEC uses an NCR on-board SCSI Bios / COntroller, and >everthing worked fine (the Celebris line use daughter cards to hold the >CPU and Ram so you can switch between ALpha's and PPro's..) > >I was wondering if the following 'time' result is reasonable (for a kernel >rebuild, all options - seemed like a good benchmark to me :-)). The >machine only has 16 MB of RAM. The reason I ask is that I'm curious if a >"normal" pentium 200 with SRAM would be faster.. > >Anyways, the results: > >$ time make >>. >>. >183.8u 32.6s 5:20.20 67.9% 989+1207K 1380+59565io 61pf + 0w > >Any experience/opinions of the Pentium Pro's would be greatly appreciated. > >-Mark > I got a kernel build time of just under 4 minutes on a new ASUS P6 200 Mhz. This has a 440 Intel chipset in it. On another Intel motherboard P6 200 Mhz with an Intel 450 KX chipset the kernel build time was 4:43. They both have 32 Megs o f ram. Obviously not all motherboards are equal. What I'm really curious about though is whether or not anyone has been using the pgcc optimized compiler for the P6 yet and what are the performance enhancements? ----------------------------------------------------------------- Paul Cobb Research Engineer pcobb@cybernet.com Cybernet Systems Corp. (313)668-2567 Ann Arbor, MI 'Is this a special moment or should we be disturbed?' - The Tick ----------------------------------------------------------------- From owner-freebsd-hackers Mon Jul 29 13:03:07 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA19025 for hackers-outgoing; Mon, 29 Jul 1996 13:03:07 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA18997 for ; Mon, 29 Jul 1996 13:02:57 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA08062; Mon, 29 Jul 1996 21:53:28 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA23390; Mon, 29 Jul 1996 21:53:28 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id VAA03905; Mon, 29 Jul 1996 21:52:32 +0200 (MET DST) From: J Wunsch Message-Id: <199607291952.VAA03905@uriah.heep.sax.de> Subject: Re: Q: How to create lint libs? To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Mon, 29 Jul 1996 21:52:32 +0200 (MET DST) Cc: koshy@india.hp.com (A JOSEPH KOSHY) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607290844.AA225279874@fakir.india.hp.com> from A JOSEPH KOSHY at "Jul 29, 96 02:14:34 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As A JOSEPH KOSHY wrote: > I wasn't able to figure out the procedure to create lint libs for the > system. The default `lint' target is quiet no-op. I think there is a default inference rule. Try ``make llib-${libname}.ln''. However, be warned, our libc is still not lintable (i.e., it won't create any lint lib at all, since there is at least one type conflict, struct pmap is defined twice in different contexts), so lint is not of much use. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Jul 29 13:37:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA20822 for hackers-outgoing; Mon, 29 Jul 1996 13:37:09 -0700 (PDT) Received: from saluki-mail.fiber2.siu.edu (SALUKI-MAIL.FIBER2.SIU.EDU [131.230.252.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA20795 for ; Mon, 29 Jul 1996 13:36:40 -0700 (PDT) Received: from [131.230.16.14] by saluki-mail.fiber2.siu.edu (AIX 3.2/UCB 5.64/4.03) id AA27778; Mon, 29 Jul 1996 15:33:53 -0500 Message-Id: <31FD213E.911@siu.edu> Date: Mon, 29 Jul 1996 15:38:22 -0500 From: Nathan Denny X-Mailer: Mozilla 2.0 (WinNT; I) Mime-Version: 1.0 To: hackers@freebsd.org Subject: Token Ring Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I noticed that all the network drivers are for ethernet cards. Is this because Ethernet is more popular, or because their is some Unix limitation on network protocols? ie. Is it possible to have a token ring card in a FreeBSD machine? Nate:SCHCATS! From owner-freebsd-hackers Mon Jul 29 14:57:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA25759 for hackers-outgoing; Mon, 29 Jul 1996 14:57:56 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA25741 for ; Mon, 29 Jul 1996 14:57:42 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id BAA14426; Tue, 30 Jul 1996 01:01:48 +0300 Date: Tue, 30 Jul 1996 01:01:48 +0300 (EET DST) From: Narvi To: Nathan Denny cc: hackers@FreeBSD.ORG Subject: Re: Token Ring In-Reply-To: <31FD213E.911@siu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Jul 1996, Nathan Denny wrote: > I noticed that all the network drivers are for ethernet cards. Is this because > Ethernet is more popular, or because their is some Unix limitation on network > protocols? ie. Is it possible to have a token ring card in a FreeBSD machine? > Ethernet is not only more popular, there are also no FreeBSD drivers for token-ring cards. As soon as someone writes a driver, you can not only have a token-ring card in you computer but also use it for networking. Sander > Nate:SCHCATS! > From owner-freebsd-hackers Mon Jul 29 15:14:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA26644 for hackers-outgoing; Mon, 29 Jul 1996 15:14:50 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA26629 for ; Mon, 29 Jul 1996 15:14:30 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA11575 for ; Tue, 30 Jul 1996 00:14:22 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA02733 for freebsd-hackers@freebsd.org; Tue, 30 Jul 1996 00:14:21 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id WAA04122 for freebsd-hackers@freebsd.org; Mon, 29 Jul 1996 22:04:51 +0200 (MET DST) From: J Wunsch Message-Id: <199607292004.WAA04122@uriah.heep.sax.de> Subject: Re: kernel assertions To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Mon, 29 Jul 1996 22:04:51 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Michael Hancock at "Jul 30, 96 00:08:41 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Michael Hancock wrote: > > Blech. Macros are evil unless they actually do something real to improve > > the code. Please, let's NOT adopt this practice. > Assertions are the most under-rated software engineering tool I can think > of. But also the IMHO most misnamed tool in the standard. It's (at least for me as a non-native speaker) absolutely unobvious what happens for which condition. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Jul 29 16:44:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA00478 for hackers-outgoing; Mon, 29 Jul 1996 16:44:32 -0700 (PDT) Received: from main.gbdata.com (GB2.Brewich.COM [207.90.222.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA00472 for ; Mon, 29 Jul 1996 16:44:28 -0700 (PDT) Received: (from gclarkii@localhost) by main.gbdata.com (8.7.5/8.6.9) id SAA12032; Mon, 29 Jul 1996 18:44:40 -0500 (CDT) From: Gary Clark II Message-Id: <199607292344.SAA12032@main.gbdata.com> Subject: Re: Token Ring To: narvi@haldjas.folklore.ee (Narvi) Date: Mon, 29 Jul 1996 18:44:40 -0500 (CDT) Cc: SCHCATS@siu.edu, hackers@FreeBSD.ORG In-Reply-To: from Narvi at "Jul 30, 96 01:01:48 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Narvi wrote: > On Mon, 29 Jul 1996, Nathan Denny wrote: >>I noticed that all the network drivers are for ethernet cards. Is this because >>Ethernet is more popular, or because their is some Unix limitation on network >>protocols? ie. Is it possible to have a token ring card in a FreeBSD machine? > > Ethernet is not only more popular, there are also no FreeBSD > drivers for token-ring cards. As soon as someone writes a driver, you can > not only have a token-ring card in you computer but also use it for > networking. > Ethernet is NOT Token-Ring. A bigger problem is the lack up the bottom end protocols instead of just the lack of a card driver. Do a search of the Archives and you should find atleast a couple of articles by Terry Lambert on what is needed to get TR working. > Sander > >> Nate:SCHCATS! > Gary -- Gary Clark II (N5VMF) | I speak only for myself and "maybe" my company gclarkii@GBData.COM | Member of the FreeBSD Doc Team Providing Internet and ISP startups mail info@GBData.COM for information FreeBSD FAQ at ftp://ftp.FreeBSD.ORG/pub/FreeBSD/docs/freebsd-faq.ascii From owner-freebsd-hackers Mon Jul 29 17:25:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA02297 for hackers-outgoing; Mon, 29 Jul 1996 17:25:13 -0700 (PDT) Received: from mole.mole.org (marmot.mole.org [204.216.57.191]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA02292; Mon, 29 Jul 1996 17:25:09 -0700 (PDT) Received: (from mail@localhost) by mole.mole.org (8.6.12/8.6.12) id AAA06655; Tue, 30 Jul 1996 00:24:17 GMT Received: from meerkat.mole.org(206.197.192.110) by mole.mole.org via smap (V1.3) id sma006653; Tue Jul 30 00:24:05 1996 Received: (from mrm@localhost) by meerkat.mole.org (8.6.11/8.6.9) id RAA02198; Mon, 29 Jul 1996 17:24:05 -0700 Date: Mon, 29 Jul 1996 17:24:05 -0700 From: "M.R.Murphy" Message-Id: <199607300024.RAA02198@meerkat.mole.org> To: cshenton@it.hq.nasa.gov, lithium@cia-g.com Subject: Re: Fatal trap 12: page fault while in kernel mode Cc: hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [...] > lithium> Fatal tral 12: page fault while in kernel mode [...] > lithium> Hardware: 16meg of parity ram, AMD DX4/100, SiS 85c471 > lithium> chipset motherboard (ick!) with VLB bus, Adaptec 284x SCSI > lithium> controller, S3 video card, etc. > > I just brought up 2.1.5R on an AMD486-100 and got a very similar > problem after rebuilding the kernel. It spat out this kind of error -- > in random processes like sh and inetd -- and failed to boot. > > At the time I was trying to compile in support for a GUS MAX and PC > Audio devices. > > I also noticed I was getting file corruption, as if my disk was dying > or some such, so I suspect that possibly the kernel file also had > corruption, causing a bogus instruction to be executed. I just > re-installed on a new disk, so if this disappears, I'll blame the > drive. If not, I'm not sure :-( > Try disabling the external cache. From experience :-( -- Mike Murphy mrm@Mole.ORG +1 619 598 5874 Better is the enemy of Good From owner-freebsd-hackers Mon Jul 29 17:27:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA02448 for hackers-outgoing; Mon, 29 Jul 1996 17:27:40 -0700 (PDT) Received: from etinc.com (etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA02440 for ; Mon, 29 Jul 1996 17:27:37 -0700 (PDT) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id UAA00779; Mon, 29 Jul 1996 20:31:11 -0400 Date: Mon, 29 Jul 1996 20:31:11 -0400 Message-Id: <199607300031.UAA00779@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 2 (High) To: Gary Clark II From: dennis@etinc.com (Dennis) Subject: Re: Token Ring Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Narvi wrote: >> On Mon, 29 Jul 1996, Nathan Denny wrote: >>>I noticed that all the network drivers are for ethernet cards. Is this because >>>Ethernet is more popular, or because their is some Unix limitation on network >>>protocols? ie. Is it possible to have a token ring card in a FreeBSD machine? >> > > Ethernet is not only more popular, there are also no FreeBSD > drivers for token-ring cards. As soon as someone writes a driver, you can > not only have a token-ring card in you computer but also use it for > networking. > Token Ring? Whats that? :-) db From owner-freebsd-hackers Mon Jul 29 18:19:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA04660 for hackers-outgoing; Mon, 29 Jul 1996 18:19:11 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA04655 for ; Mon, 29 Jul 1996 18:19:09 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id BAA03141 for ; Tue, 30 Jul 1996 01:19:07 GMT Date: Tue, 30 Jul 1996 10:19:07 +0900 (JST) From: Michael Hancock To: FreeBSD hackers Subject: Re: kernel assertions In-Reply-To: <199607292004.WAA04122@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Jul 1996, J Wunsch wrote: > As Michael Hancock wrote: > > > Assertions are the most under-rated software engineering tool I can think > > of. > > But also the IMHO most misnamed tool in the standard. It's (at least > for me as a non-native speaker) absolutely unobvious what happens for > which condition. I had a French professor who decided to call them, REQUIRE and ENSURE. [Function declaration] [REQUIRE: Don't give me bogus arguments or I'll stop] [REAL CODE] ... [ENSURE: I'll guarantee this or I'll stop] [End] From owner-freebsd-hackers Mon Jul 29 18:21:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA04777 for hackers-outgoing; Mon, 29 Jul 1996 18:21:21 -0700 (PDT) Received: from cesium.clock.org (cesium.clock.org [17.255.4.43]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA04772 for ; Mon, 29 Jul 1996 18:21:20 -0700 (PDT) Received: by cesium.clock.org id <119170-16661>; Mon, 29 Jul 1996 18:20:57 -0800 From: Sean Doran To: dennis@etinc.com, gclarkii@main.gbdata.com Subject: Re: Token Ring Cc: hackers@FreeBSD.org Message-Id: <96Jul29.182057pdt.119170-16661+63@cesium.clock.org> Date: Mon, 29 Jul 1996 18:20:56 -0800 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Token Ring? Whats that? :-) Slow FDDI. Sean. From owner-freebsd-hackers Mon Jul 29 19:55:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA10024 for hackers-outgoing; Mon, 29 Jul 1996 19:55:27 -0700 (PDT) Received: from mail.think.com (Mail1.Think.COM [131.239.33.245]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA10017 for ; Mon, 29 Jul 1996 19:55:23 -0700 (PDT) Received: from Early-Bird.Think.COM (Early-Bird-1.Think.COM [131.239.146.105]) by mail.think.com (8.7.5/m3) with ESMTP id WAA19246; Mon, 29 Jul 1996 22:55:09 -0400 (EDT) Received: from compound.Think.COM ([206.147.16.34]) by Early-Bird.Think.COM (8.7.5/e1) with ESMTP id WAA08819; Mon, 29 Jul 1996 22:55:04 -0400 (EDT) Received: (from alk@localhost) by compound.Think.COM (8.7.5/8.7.3) id VAA28307; Mon, 29 Jul 1996 21:56:18 -0500 (CDT) Date: Mon, 29 Jul 1996 21:56:18 -0500 (CDT) From: Tony Kimball Message-Id: <199607300256.VAA28307@compound.Think.COM> To: michaelh@cet.co.jp Cc: hackers@freebsd.org Subject: kernel assertions Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Quoth Michael Hancock on Mon, 29 July: : Any comments on introducing an assertion macro for kernel code that panics : if the expression is false and does nothing otherwise. It would also be : very cool to preprocess it out with something like a -NDEBUG flag. It : could be called KASSERT or KERN_ASSERT. Assertions should take different forms in order to support different goals. A single form should not be overloaded to provide all facilities. - There may be some assertions which should never be removed, because they provide protection against catastrophic failures. There is no need for a macro in such cases. - Certainly, some assertions should only be removed when a high-confidence configuration is used, for which utmost performance is pivotal. (Global macro candidate, first form.) - Others may be removed unless a debug kernel is being built. (Global macro candidate, second form.) - Finally, some are of use primarily if not exclusively in active development. These should be defined ad hoc appropriately to the task at hand, and limited in scope. In principle, I personally prefer inline functions, defined static in header files, with #ifdef'd bodies. They can be stepped, for example. But neither ANSI nor K&R C provide inlines, so this is probably not acceptable. From owner-freebsd-hackers Mon Jul 29 20:59:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA13927 for hackers-outgoing; Mon, 29 Jul 1996 20:59:36 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA13920 for ; Mon, 29 Jul 1996 20:59:33 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id DAA04014; Tue, 30 Jul 1996 03:59:24 GMT Date: Tue, 30 Jul 1996 12:59:24 +0900 (JST) From: Michael Hancock Reply-To: Michael Hancock To: Tony Kimball cc: hackers@freebsd.org Subject: Re: kernel assertions In-Reply-To: <199607300256.VAA28307@compound.Think.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 29 Jul 1996, Tony Kimball wrote: > Assertions should take different forms in order to support different > goals. A single form should not be overloaded to provide all facilities. > > - There may be some assertions which should never be removed, because > they provide protection against catastrophic failures. There is no > need for a macro in such cases. If ... else ... > - Certainly, some assertions should only be removed when a > high-confidence configuration is used, for which utmost performance is > pivotal. (Global macro candidate, first form.) REQUIRE1(cond, desc) ENSURE1(cond, desc) (less frequently used) > - Others may be removed unless a debug kernel is being built. (Global > macro candidate, second form.) REQUIRE2(cond, desc) ENSURE2(cond, desc) (more commonly used) > - Finally, some are of use primarily if not exclusively in active > development. These should be defined ad hoc appropriately to the task > at hand, and limited in scope. #ifdef DDB ... #endif I'd settle for Poul's ASSERT, or an ASSERT1/ASSERT2, if people don't like the REQUIRE and ENSURE names. Mike Hancock From owner-freebsd-hackers Mon Jul 29 23:21:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA23069 for hackers-outgoing; Mon, 29 Jul 1996 23:21:33 -0700 (PDT) Received: from sam.networx.ie (dublin-ts2-69.indigo.ie [194.125.133.69]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA23058 for ; Mon, 29 Jul 1996 23:21:28 -0700 (PDT) Received: from mip1.networx.ie (mip1.networx.ie [194.9.12.1]) by sam.networx.ie (8.6.12/8.6.12) with SMTP id TAA06964; Mon, 29 Jul 1996 19:18:50 +0100 X-Organisation: I.T. NetworX Ltd X-Business: Network Consultancy and Training X-Address: 67 Merrion Square, Dublin 2, Ireland X-Voice: +353-1-676-8866 X-Fax: +353-1-676-8868 Received: from mike.networx.ie by mip1.networx.ie Date: Mon, 29 Jul 1996 19:10:20 BST From: Michael Ryan Reply-To: mike@NetworX.ie Subject: RE: hackers-digest V1 #1337 (pppd and PAP) To: Darius Moos Cc: freebsd-hackers-digest@FreeBSD.org Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Darius said: >thanks for your reply, but it does NOT work. It does not work for you; it DOES work for me. >I want to connect a Linux-box-2.x using PAP. Sorry if this was not clear >in my mailing. It was clear; I just wanted to know if you had gotten PAP working at all, to anything... I notice the following: (a) You use "auth". This means "require the peer to authenticate". You want to authenticate yourself to the peer, not the other way around. (b) You use "-pap". This means "don't agree to authenticate using PAP". But you *do* want to authenticate using PAP. (c) You use "+chap". This means "require the peer to authenticate using CHAP". See my comments for (a). (d) The peer wants to authenticate using CHAP regardless of what your ISP is saying. Regards, Mike --- From owner-freebsd-hackers Mon Jul 29 23:53:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA25382 for hackers-outgoing; Mon, 29 Jul 1996 23:53:10 -0700 (PDT) Received: from relay.philips.nl (ns.philips.nl [130.144.65.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA25377 for ; Mon, 29 Jul 1996 23:53:07 -0700 (PDT) Received: (from smap@localhost) by relay.philips.nl (8.6.9/8.6.9-950414) id IAA05129 for ; Tue, 30 Jul 1996 08:52:33 +0200 Received: from unknown(192.26.173.32) by ns.philips.nl via smap (V1.3+ESMTP) with ESMTP id sma004951; Tue Jul 30 08:51:21 1996 Received: from aonc01.nym.sc.philips.com (aonc01.nym.sc.philips.com [130.144.70.193]) by smtp.nl.cis.philips.com (8.6.10/8.6.10-0.9z-02May95) with ESMTP id IAA16831 for ; Tue, 30 Jul 1996 08:53:44 +0200 Received: from NLNMG01.nym.sc.philips.com (nlnmg01 [130.144.80.6]) by aonc01.nym.sc.philips.com (8.6.10/8.6.10-0.993a-08Jan96) with ESMTP id IAA17734 for ; Tue, 30 Jul 1996 08:48:50 +0200 Received: from NLNMG01/MAILQUEUE by NLNMG01.nym.sc.philips.com (Mercury 1.21); 30 Jul 96 08:51:42 +0100 Received: from MAILQUEUE by NLNMG01 (Mercury 1.21); 30 Jul 96 08:51:37 +0100 From: "Kees Jan Koster" Organization: Philips Semiconductors Nijmegen To: hackers@freebsd.org Date: Tue, 30 Jul 1996 08:51:34 GMT+0100 Subject: Re: kernel assertions Reply-to: Kees.Koster@nym.sc.philips.com Priority: normal X-mailer: Pegasus Mail v3.22 Message-ID: <6DBC786E34@NLNMG01.nym.sc.philips.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hmm. It seems to me gcc has those neat `inline' keywords. I've been using them in my C++ code, but since FreeBSD is using other gcc extensions to C, might as well use inline too. Ever tried compiling your kernel with -ansi? That's fun :-) Just a thought... Kees Jan From owner-freebsd-hackers Tue Jul 30 01:40:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA00303 for hackers-outgoing; Tue, 30 Jul 1996 01:40:10 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA00298 for ; Tue, 30 Jul 1996 01:40:07 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id BAA08578; Tue, 30 Jul 1996 01:39:52 -0700 (PDT) To: Chris Shenton cc: hackers@freefall.freebsd.org Subject: Re: 2.1.5R sysinstall comments In-reply-to: Your message of "Mon, 29 Jul 1996 11:15:39 EDT." <199607291515.PAA01486@wirehead.it.hq.nasa.gov> Date: Tue, 30 Jul 1996 01:39:50 -0700 Message-ID: <8565.838715990@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > MULTI-USER SYSINSTALL DISK/PARTITION PROBLEM: > > The second time I installed, it was because my first disk appeared to > be getting corrupted. So I installed a second SCSI drive along with > the first and ran sysinstall from multiuser. Answered the questions, > and told it to label the partitions, which generated a core > dump. Tried again and didn't label them, did the COMMIT, and it Hmmmm. Bleah. :-( I have about 2 problems like this on my "to look at" queue, I've simply been saving them for the end since it kind of involves sacrificing a box during the debugging, and that takes time. > RESTART WANTED: > > While downloading, my !#$@ing ISP dropped my PPP link. The download > failed. I had to start from ground-zero. This is really painful at > 28.8. It would be really cool if you could say "RESTART" on some menu, Unfortunately, the intermediate files never touch your disk (and this makes certain minimal installs even possible) - keeping a checkpoint file wouldn't do me a lot of good, except perhaps to avoid extracting what was already extracted? You'd still need to restart the transfer at the beginning anyway, so it wouldn't save you anything where you want it most. > SAVED INSTALL CONFIG WANTED: > > I'd really like it if when you say COMMIT, it wrote a little config > file to disk which said what partitions were where, what the network > config parameters were, what packages were requested for > installation. This way, if the install fails, you can start over (or > restart!) without having to go through all the specifications again. Yeah, that's been on my wish list for awhile.. :-) My real problem is that I'm basically Really Sick of sysinstall and adding nifty little features like this goes pretty low on my priority list. It's not that I don't think they're good investments of time (and I occasionally rouse myself enough to add some little goodie, like the transfer rate hack), I've just spent too damn much time looking at that code. It could really use a fresh pair of eyes or three. :-) > PORTS CD/DIR CONFUSED, NO CANCEL OPTION: > > After sysinstalling, one of the menus asks if I want to install some > ports. I said yes, and it told me that I need to insert CDROM-2; kinda > difficult when I'm installing over PPP :-). I hit CONTINUE, cuz that's Hmmmm! That's really... Unique... I'll see if I can reproduce it. Jordan From owner-freebsd-hackers Tue Jul 30 04:28:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA11362 for hackers-outgoing; Tue, 30 Jul 1996 04:28:17 -0700 (PDT) Received: from cyclone.degnet.baynet.de (root@cyclone.degnet.baynet.de [194.95.214.129]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA11355 for ; Tue, 30 Jul 1996 04:28:00 -0700 (PDT) Received: from neuron.bsd.uni-passau.de (ppp3 [194.95.214.133]) by cyclone.degnet.baynet.de (8.6.12/8.6.9) with SMTP id NAA25478; Tue, 30 Jul 1996 13:30:16 +0200 Message-ID: <31FE0C90.36AB@degnet.baynet.de> Date: Tue, 30 Jul 1996 13:22:24 +0000 From: Darius Moos Reply-To: moos@degnet.baynet.de X-Mailer: Mozilla 3.0b5aGold (Win95; I) MIME-Version: 1.0 To: mike@NetworX.ie CC: freebsd-hackers Subject: Re: hackers-digest V1 #1337 (pppd and PAP) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi, > >I want to connect a Linux-box-2.x using PAP. Sorry if this was not clear > >in my mailing. > > It was clear; I just wanted to know if you had gotten PAP working at all, > to anything... YES got it; here's the pppd-log: Jul 30 11:46:47 neuron pppd[535]: pppd 2.1.2 started by moos, uid 30001 Jul 30 11:47:15 neuron pppd[536]: Connected... Jul 30 11:47:16 neuron pppd[536]: Using interface ppp0 Jul 30 11:47:16 neuron pppd[536]: Connect: ppp0 <--> /dev/cuaa1 Jul 30 11:47:16 neuron pppd[536]: Remote message: Login ok Jul 30 11:47:16 neuron pppd[536]: local IP address 192.168.250.5 Jul 30 11:47:16 neuron pppd[536]: remote IP address 10.1.2.1 > > I notice the following: > > (a) You use "auth". > (b) You use "-pap". > (c) You use "+chap". > (d) The peer wants to authenticate using CHAP regardless of I've tried all combinations of this three options !!! Really !!! I did not succeed with the Linux-2.x-box BUT i succeded on the first try with another FreeBSD-2.1-box (see log of pppd above). Darius. > > Regards, > Mike > > --- From owner-freebsd-hackers Tue Jul 30 06:20:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA15293 for hackers-outgoing; Tue, 30 Jul 1996 06:20:06 -0700 (PDT) Received: from ccs.sogang.ac.kr (ccs.sogang.ac.kr [163.239.1.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA15283 for ; Tue, 30 Jul 1996 06:20:01 -0700 (PDT) Received: from cslsun10.sogang.ac.kr by ccs.sogang.ac.kr (8.7.5/Sogang) id WAA03894; Tue, 30 Jul 1996 22:16:47 +0900 (KST) Received: from localhost by cslsun10.sogang.ac.kr (4.1/SMI-4.1) id AA02716; Tue, 30 Jul 96 22:18:58 KST Date: Tue, 30 Jul 1996 22:18:57 +0900 (KST) From: Heo Sung-Gwan X-Sender: heo@cslsun10 To: freebsd-hackers@FreeBSD.ORG Subject: Manpages 9 Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk VFS interface manpages by Doug Rabson was wonderful. (ftp://freefall.freebsd.org/pub/incoming/vopdoc-960727.tar.gz) Those was exactly what I need. Thank for his effort. Is there more manpages 9 that explains kernel functions? Now I use 2.1.0-RELEASE, is there manpages 9 in 2.1.5-RELEASE? Heo Sung-Gwan -- E-mail: heo@cslsun10.sogang.ac.kr From owner-freebsd-hackers Tue Jul 30 07:12:53 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA18398 for hackers-outgoing; Tue, 30 Jul 1996 07:12:53 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA18378; Tue, 30 Jul 1996 07:12:41 -0700 (PDT) Received: from localhost (dfr@localhost) by minnow.render.com (8.6.12/8.6.9) with SMTP id PAA14575; Tue, 30 Jul 1996 15:15:03 +0100 Date: Tue, 30 Jul 1996 15:15:03 +0100 (BST) From: Doug Rabson To: freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org Subject: More VFS manpages Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk More manpages in ftp://freefall.freebsd.org/incoming/vopdoc-960730.tar.gz. This completes the VOP_*.9 set. Next will be vnode.9, VFS.9 and VFS_*.9. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-hackers Tue Jul 30 08:43:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA05308 for hackers-outgoing; Tue, 30 Jul 1996 08:43:39 -0700 (PDT) Received: from jabber.paco.odessa.ua (jabber.paco.odessa.ua [193.124.52.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA03707 for ; Tue, 30 Jul 1996 08:37:17 -0700 (PDT) Received: (from igor@localhost) by jabber.paco.odessa.ua (8.7.1/8.6.10/01) id SAA11447 for freebsd-hackers@freebsd.org; Tue, 30 Jul 1996 18:34:14 +0300 (UKD) From: Igor Khasilev Message-Id: <199607301534.SAA11447@jabber.paco.odessa.ua> Subject: incorect (?) execution of gziped executable To: freebsd-hackers@freebsd.org Date: Tue, 30 Jul 1996 18:34:14 +0300 (UKD) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi everybody! Is it right that code become writeable in gziped executable? I tried such program: -------8<-------------------- sub() { printf("sub\n"); } main() { printf("before: %x\n",*(int*)&sub); *(int*)&sub = 0; printf("after: %x\n", *(int*)&sub); sub(); } -------8<-------------------- when compiled and executed normally (before gziping executable file) it produce normal output: bash$ ./x before: 68e58955 Bus error (core dumped) bash$ gdb display that program was terminated with signal 10 at line *(int*)&sub = 0; Nothing unusual... But... bash$ gzip x gzip: x.gz already exists; do you wish to overwrite (y or n)? y bash$ ./x.gz before: 68e58955 after: 0 Segmentation fault (core dumped) bash$ I become able to write to code? Or i misunderstand something? Regads! Igor. From owner-freebsd-hackers Tue Jul 30 09:09:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA10658 for hackers-outgoing; Tue, 30 Jul 1996 09:09:50 -0700 (PDT) Received: from inner.cortx.com (root@inner.cortx.com [205.197.61.8]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA10653 for ; Tue, 30 Jul 1996 09:09:48 -0700 (PDT) Received: (from root@localhost) by inner.cortx.com (8.6.12/8.6.12) id MAA19484; Tue, 30 Jul 1996 12:12:41 GMT Date: Tue, 30 Jul 1996 12:12:41 +0000 () From: Charlie ROOT To: hackers@freebsd.org Subject: /etc/group Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am having a problem with groups in FreeBSD. I have a group 'user' and i seem to have broke it. I think itsbecause the line buffer in /etc/group cannot exceed 1024 characters. So i tried adding a new group called 'user' also, with different GID but i get an error when i run the adduser script along wiht other errors. ex... inner /home/staff/costa>adduser (c) Copyright 1995 Wolfram Schneider Use option ``-silent'' if you don't want see all warnings & questions. Check /etc/shells Check /etc/master.passwd User news: illegal shell: ``/nonexistent'' User xten: illegal shell: ``/nonexistent'' User ftp: illegal shell: ``/dev/null'' Check /etc/group Groupname exist twice: user:1109 -> user:101 How do i resolve the problem? Right now i addusers into their own group (jim:*:1239:jim) and its OK. How do i clean up this mess?? Thanks in advance! Costa ==================C=O=R=T=E=X==C=O=M=M=U=N=I=C=A=T=I=O=N=S================== Costa J Morris - Partner Full Service Internet Access http://www.cortx.com Interactive CGI Scripting costa@cortx.com Internet Consulting 201-567-2297 Web Design ============================================================================ From owner-freebsd-hackers Tue Jul 30 09:34:41 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA15586 for hackers-outgoing; Tue, 30 Jul 1996 09:34:41 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA15580 for ; Tue, 30 Jul 1996 09:34:39 -0700 (PDT) Received: from orion.webspan.net (scanner@orion.webspan.net [206.154.70.41]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id MAA18203; Tue, 30 Jul 1996 12:34:28 -0400 (EDT) Date: Tue, 30 Jul 1996 12:34:27 -0400 (EDT) From: Scanner To: Charlie ROOT cc: hackers@FreeBSD.ORG Subject: Re: /etc/group In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Jul 1996, Charlie ROOT wrote: > I am having a problem with groups in FreeBSD. I have a group 'user' and > i seem to have broke it. I think itsbecause the line buffer in > /etc/group cannot exceed 1024 characters. > > So i tried adding a new group called 'user' also, with different GID but > i get an error when i run the adduser script along wiht other errors. Have you tried going into /etc/groups and DELETING the users after users:*:1001:john1, john2 etc.. delete the users john1, john2 etc.. sicne they are already added they dont neeed to be in the groups file sicne they already have the GID of users in the password file. So delete the users in the groups file and your set and good to go. Chris -- ===================================| Webspan Inc., ISP Division. FreeBSD 2.1.5 is available now! | Phone: 908-367-8030 ext. 126 -----------------------------------| 500 West Kennedy Blvd., Lakewood, NJ-08701 Turning PCs into Workstations | E-Mail: scanner@webspan.net http://www.freebsd.org | SysAdmin / Network Engineer / Security ===================================| Member BSDNET team! http://www.bsdnet.org From owner-freebsd-hackers Tue Jul 30 10:00:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA18307 for hackers-outgoing; Tue, 30 Jul 1996 10:00:13 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA18145 for ; Tue, 30 Jul 1996 09:58:10 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id UAA03692; Tue, 30 Jul 1996 20:01:15 +0300 Date: Tue, 30 Jul 1996 20:01:15 +0300 (EET DST) From: Narvi To: Charlie ROOT cc: hackers@freebsd.org Subject: Re: /etc/group In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Jul 1996, Charlie ROOT wrote: > I am having a problem with groups in FreeBSD. I have a group 'user' and > i seem to have broke it. I think itsbecause the line buffer in > /etc/group cannot exceed 1024 characters. > > So i tried adding a new group called 'user' also, with different GID but > i get an error when i run the adduser script along wiht other errors. > > ex... > inner /home/staff/costa>adduser > (c) Copyright 1995 Wolfram Schneider > Use option ``-silent'' if you don't want see all warnings & questions. > > Check /etc/shells > Check /etc/master.passwd > User news: illegal shell: ``/nonexistent'' > User xten: illegal shell: ``/nonexistent'' > User ftp: illegal shell: ``/dev/null'' > Check /etc/group > Groupname exist twice: user:1109 -> user:101 Of course it should complain if there are two groups with the same name - the mapping between names and IDs should be one to one. > > How do i resolve the problem? Right now i addusers into their own group > (jim:*:1239:jim) and its OK. And you don't want it to stay that way? It does sometimes have some plusses... > Why do you want to keep the users in only one group anyways? How about spliting them between several groups (users1, users2, ...)? Sander > How do i clean up this mess?? > > Thanks in advance! > Costa > > > ==================C=O=R=T=E=X==C=O=M=M=U=N=I=C=A=T=I=O=N=S================== > Costa J Morris - Partner Full Service Internet Access > http://www.cortx.com Interactive CGI Scripting > costa@cortx.com Internet Consulting > 201-567-2297 Web Design > ============================================================================ > > > > From owner-freebsd-hackers Tue Jul 30 11:25:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA24287 for hackers-outgoing; Tue, 30 Jul 1996 11:25:34 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA24282 for ; Tue, 30 Jul 1996 11:25:30 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA00292; Tue, 30 Jul 1996 11:21:45 -0700 From: Terry Lambert Message-Id: <199607301821.LAA00292@phaeton.artisoft.com> Subject: Re: Ethernet-like loopback & IPX To: louie@TransSys.COM (Louis A. Mamakos) Date: Tue, 30 Jul 1996 11:21:45 -0700 (MST) Cc: babkin@hq.icb.chel.su, jhay@mikom.csir.co.za, hackers@FreeBSD.org In-Reply-To: <199607230410.AAA24684@whizzo.transsys.com> from "Louis A. Mamakos" at Jul 23, 96 00:10:32 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > > > ... > > > > > > > > > > By the way, I have fixed the bug (in my opinion) in IPX. It allowed > > > > > only one link-level (i.e. Ethernet) address for all interfaces. > > > > > Was it a real bug or feature ? > > > > > > > > > > > > > It is a leftover from its XNS days. If you send me the patches for > > > > IPX, I will look it over and commit it. > > > > > > It's not a bug, but a feature. Having a single address for your > > > end-station make quite a few other weirdnesses in the protocol stack > > > and application just go away. > > > > But if you have a single address you need to set it for all > > Ethernet cards or they will not accept the packets with this > > address. The current implementation does not do this and I > > think that it's not a very good idea. > > Sure, it's true that the current drivers do not allow the MAC address > to be set on the various LAN interfaces, but this would argue for > fixing the device drivers, and not the protocol design. > > While you may believe that the single address per IPX host is an > error, it is fundamental to the protocol's design. I wouldn't > characterize changing this as "fixing" it, unless it's the same way a > veteranarian "fixes" something. You are mistaken. Probably, you don't know about "internal net addresses", which were introduced in NetWare 3.x. Each NetWare server from 3.x onward (and thus each router) has the concept of an internal net address. This is basically an internal virtual network interface. The destination is the internal interconnect address, which is not a real hardware address. Conceptually, it looks like this: Server address | o--x---x-------------------x--------------------x--o | | | | | | Ethernet 1 Ethernet 2 Ethernet 3 The destination address specified is "Server address" in all cases. Each ethernet interface has a logical name. This logical name is the same for each IPX machine's attachment to that interface. The practical effect is that the hop limit is reduced by one (from a default 16 to a default 15) by the addition of the routing from the internal to the external net interfaces. Thus you have a unique "server address" and you have a unique net address per card, but each card's net address is not unique. This is pretty obvious if you look at the interface configuration on the IPX stack on a UnixWare box, or on a NetWare 3.x/4.x server. You should contact Jim Freeman of Caldera, since he worked on the IPX stack which was shipped in UnixWare, if you don't believe this. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 30 11:59:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA28643 for hackers-outgoing; Tue, 30 Jul 1996 11:59:15 -0700 (PDT) Received: from tetsuo.communique.net (Tetsuo.Communique.Net [204.27.64.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA28637; Tue, 30 Jul 1996 11:59:12 -0700 (PDT) Received: from yama.communique.net (Yama.Communique.Net [204.27.65.102]) by tetsuo.communique.net (8.6.12/8.6.12) with SMTP id NAA42259; Tue, 30 Jul 1996 13:59:03 -0500 Date: Tue, 30 Jul 1996 13:57:37 -0500 (CDT) From: Raul Zighelboim To: hardware@freebsd.org cc: hackers@freebsd.org Subject: Best Ethernet Card / Best Drivers for ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We are building a server for the office. We want to make this server as solid as possible. So, the question is: What is the best supported Ethernet Card for FreeBSD 2.1.5 ? Thanks. From owner-freebsd-hackers Tue Jul 30 12:43:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01145 for hackers-outgoing; Tue, 30 Jul 1996 12:43:15 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA01140; Tue, 30 Jul 1996 12:43:13 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id OAA23114; Tue, 30 Jul 1996 14:42:39 -0500 From: Joe Greco Message-Id: <199607301942.OAA23114@brasil.moneng.mei.com> Subject: Re: Best Ethernet Card / Best Drivers for ? To: mango@communique.net (Raul Zighelboim) Date: Tue, 30 Jul 1996 14:42:39 -0500 (CDT) Cc: hardware@freebsd.org, hackers@freebsd.org In-Reply-To: from "Raul Zighelboim" at Jul 30, 96 01:57:37 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > We are building a server for the office. > We want to make this server as solid as possible. > > So, the question is: > > What is the best supported Ethernet Card for FreeBSD 2.1.5 ? Do you want PCI, VLB, EISA, or ISA? Do you want 10Mbps or 100Mbps? Do you want 10base2, 10baseT, AUI, 100baseXX? If you are building a system from scratch, I suspect that your best option is to go PCI, and get a DEC 21x40 based card. I personally like the Kingston 10baseT cards because they're like $50. The SMC EtherPower 10/100's are pretty cool too, but are more like $150. ... JG From owner-freebsd-hackers Tue Jul 30 12:53:30 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01870 for hackers-outgoing; Tue, 30 Jul 1996 12:53:30 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA01865 for ; Tue, 30 Jul 1996 12:53:28 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.6.12/8.6.12) with SMTP id MAA25807 for ; Tue, 30 Jul 1996 12:53:26 -0700 Date: Tue, 30 Jul 1996 12:53:26 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org Subject: So what's the word on quotas in -current or 2.1.5? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Stable? Usable? Seems I recall reading about some breakage, and I'm putting in a new box for our userbase. If quotas are broke, I have to install BSD/OS, if they aren't, then it's FreeBSD all the way... From owner-freebsd-hackers Tue Jul 30 13:13:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA03113 for hackers-outgoing; Tue, 30 Jul 1996 13:13:08 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA03105 for ; Tue, 30 Jul 1996 13:13:03 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA00436; Tue, 30 Jul 1996 13:11:44 -0700 From: Terry Lambert Message-Id: <199607302011.NAA00436@phaeton.artisoft.com> Subject: Re: your mail To: hasty@rah.star-gate.com (Amancio Hasty) Date: Tue, 30 Jul 1996 13:11:44 -0700 (MST) Cc: davidg@Root.COM, heo@cslsun10.sogang.ac.kr, freebsd-hackers@FreeBSD.org In-Reply-To: <199607191258.FAA00407@rah.star-gate.com> from "Amancio Hasty" at Jul 19, 96 05:58:14 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > From The Desk Of David Greenman : > > > 4) How can user process access the file in ufs filesystem through raw disk? > > > > You can't unless you write a user-mode UFS/FFS that does it's I/O through > > the raw device. I couldn't imagine why you'd want to do this, however. > > > > My guess is that his assumption is that accessing the files via a > "raw disk mode" will be faster than going thru the normal file > access mechanism. I wish I knew what is he up to so we can help him or > better yet his justification for taking such approach . You can more efficiently traverse a directory this way; specifically, you avoid the system call boundry push problem when you have blocks of crap file names that don't match the pattern you are looking for. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 30 13:30:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA04532 for hackers-outgoing; Tue, 30 Jul 1996 13:30:28 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA04400 for ; Tue, 30 Jul 1996 13:29:38 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA20070; Tue, 30 Jul 1996 22:27:56 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA24616; Tue, 30 Jul 1996 22:27:55 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id WAA11579; Tue, 30 Jul 1996 22:01:09 +0200 (MET DST) From: J Wunsch Message-Id: <199607302001.WAA11579@uriah.heep.sax.de> Subject: Re: Manpages 9 To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Tue, 30 Jul 1996 22:01:09 +0200 (MET DST) Cc: heo@cslsun10.sogang.ac.kr (Heo Sung-Gwan) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Heo Sung-Gwan at "Jul 30, 96 10:18:57 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Heo Sung-Gwan wrote: > Is there more manpages 9 that explains kernel functions? j@uriah 141% ls /usr/share/man/man9 /usr/share/man/man9: copy.9.gz fubyte.9.gz subyte.9.gz copyin.9.gz fuswintr.9.gz suswintr.9.gz copyinstr.9.gz fusword.9.gz susword.9.gz copyout.9.gz fuword.9.gz suword.9.gz copystr.9.gz i386/ timeout.9.gz devfs_add_devsw.9.gz intro.9.gz tsleep.9.gz devfs_add_devswf.9.gz sleep.9.gz untimeout.9.gz devfs_link.9.gz store.9.gz wakeup.9.gz fetch.9.gz style.9.gz > Now I use 2.1.0-RELEASE, is there manpages 9 in 2.1.5-RELEASE? It's not in 2.1.5, since (as you can see above), it's still fairly incomplete. I've got slice(9) (with alot of input from Bruce) and spl(9) in my personal queue. I wish more people would contribute to this effort. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jul 30 13:30:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA04560 for hackers-outgoing; Tue, 30 Jul 1996 13:30:33 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA04479; Tue, 30 Jul 1996 13:30:15 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA00470; Tue, 30 Jul 1996 13:27:59 -0700 From: Terry Lambert Message-Id: <199607302027.NAA00470@phaeton.artisoft.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: rnordier@iafrica.com (Robert Nordier) Date: Tue, 30 Jul 1996 13:27:59 -0700 (MST) Cc: jkh@time.cdrom.com, pst@shockwave.com, hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199607221808.UAA00225@eac.iafrica.com> from "Robert Nordier" at Jul 22, 96 08:08:11 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The FAT fs primitives are done and tested and I'm currently working > on VFAT support. > > Microsoft is shortly to be introducing a FAT32 filesystem to Windows > 95 which will increase maximum filesystem size from 2 (or 4, for > NT) gigabytes to 2 terabytes. The new filesystem makes use of > 32-bit (as opposed to 12-bit and 16-bit) FAT entries and will > require a fundamentally different handling of boot record, FATs, > and root directory, so I'm busy on provision for this also. I have a beta copy of this in house right now. It is intended solely for the OEM market. I think it will require a reinstall to share the disk in any case, since FIPS/PARTED/etc. doesn't understand the disk layout. In general, you will only ever see it on preinstalled systems. > The changes required for FAT32 support would probably be rather > difficult to graft onto the msdosfs at this stage: possibly another > factor supporting the decision to re-implement DOS/Win filesystem > support on FreeBSD. A reimplementation of the current/NetBSD code would be necessary to handle VFAT32. It is not *that* different than FAT, since it has to support Drivespace compression, which under Windows95 uses an undocumented ioctl() to get a block list back for a file (that's how their swap file is allowed to be non-contiguous, as well). > FAT32 is supposedly due for public release in the fall. I'm > currently working towards a similar release date for the new > filesystem. I think it's ready now. The limiting factor is going to be MS's OEM release date. Don't expect to install VFAT32 yourself, since NT can't mount VFAT32 partitions, and MS wants everyone to move to NT (Windows95 has always been billed as a transition product). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 30 13:33:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA04879 for hackers-outgoing; Tue, 30 Jul 1996 13:33:55 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA04872; Tue, 30 Jul 1996 13:33:49 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA00494; Tue, 30 Jul 1996 13:32:27 -0700 From: Terry Lambert Message-Id: <199607302032.NAA00494@phaeton.artisoft.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Tue, 30 Jul 1996 13:32:27 -0700 (MST) Cc: rnordier@iafrica.com, bde@zeta.org.au, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <3900.838135055@critter.tfs.com> from "Poul-Henning Kamp" at Jul 23, 96 05:17:35 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > DRIVE DOS START DOS END > > cyl head sect || cyl head sect cyl head sect size > >------------------------------------------------------------------- > >wd0 | 525 | 64 | 63 || 0 | 1 | 1 | 126 | 63 | 63 | 512001 > >wd0 | 2099 | 64 | 63 || 0 | 1 | 1 | 189 | 63 | 63 | 766017 > > same drive || 250 | 0 | 1 | 523 | 63 | 63 | 1104768 > >wd0 | 788 | 64 | 63 || 0 | 1 | 1 | 787 | 63 | 63 | 3177153 > >wd0 | 621 | 64 | 63 || 0 | 1 | 1 | 619 | 63 | 63 | 2499777 > > This could be because the drives in question have a version of then > "OnTrack" diskmanager that we don't recognize". I don't think so... there are several other vendors doing the same thing. One issue is that you would see only one partition on such a drive -- and the partition ID would identify the software to itself. Since there is more than one partition listed, this can't be the problem. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 30 13:57:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA06307 for hackers-outgoing; Tue, 30 Jul 1996 13:57:39 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA06294 for ; Tue, 30 Jul 1996 13:57:31 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA00558; Tue, 30 Jul 1996 13:56:44 -0700 From: Terry Lambert Message-Id: <199607302056.NAA00558@phaeton.artisoft.com> Subject: Re: X.25 revisited To: dennis@etinc.com (Dennis) Date: Tue, 30 Jul 1996 13:56:44 -0700 (MST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199607251436.KAA12979@etinc.com> from "Dennis" at Jul 25, 96 10:36:57 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >> 2) Is there a terminal server type application available for that interface > >> so X.25 users dialing into a network could access the FreeBSD system, > >> or does this need to be built? > > > >I believe you are looking for an X.29 PAD. > > Well, not really....a PAD more describes the caller end rather than the > server end. I'm looking more to service PAD callers from some sort of > emulator. Our (old) SCO driver simulated async ttys and used the > standard gettys...there are several ways to do it. > > Just what IS in the ISODE stuff that anyone might want? Circuit switching via X.29, for one thing. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 30 14:14:12 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA07334 for hackers-outgoing; Tue, 30 Jul 1996 14:14:12 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA07304; Tue, 30 Jul 1996 14:13:45 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA00605; Tue, 30 Jul 1996 14:13:20 -0700 From: Terry Lambert Message-Id: <199607302113.OAA00605@phaeton.artisoft.com> Subject: Re: Union mounts and other mounts To: michaelh@cet.co.jp (Michael Hancock) Date: Tue, 30 Jul 1996 14:13:20 -0700 (MST) Cc: freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Michael Hancock" at Jul 26, 96 00:24:03 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Terry, are you out there? Yes, I'm here. I broke my back two weeks ago last Thursday, and have been pretty much laid up and starving for network access. 8-(. > Please upload your mega patches. I'm sure someone will take a look and > maybe we can at least start with getting the locks fixed. > > Or do we just have to dream about the possibilities? I will not be able to get to this until this weekend. Basically, it's nothing more than a CVS diff on my machine, or I can upload the full /sys directory (like Poul wanted). I can't give him direct access because all incoming connections are firewalled by the corporate gateway. > I want to mount my home source directory on top of a FreeBSD CD and > compile as if the CD were writable. Me too. > I want to start working on a non-itar restricted crypto-fs layer. This would be cool. > I want to see a gzip layer. Two of John's students have already implemented one of these; I have the code here, but only on the condition that it not be redistributed. I like the idea of block compression better than file compression. It goes a long way towards using the character set as a compression attribute (ie: an ISO-8859-1 character set is a "compressed" ISO-10646/16 character set, assuming you use only ISO-8859-1 characters... etc.). You may wish to check with John directly re compression layer code. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 30 14:17:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA07736 for hackers-outgoing; Tue, 30 Jul 1996 14:17:27 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA07716; Tue, 30 Jul 1996 14:17:00 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA00621; Tue, 30 Jul 1996 14:16:07 -0700 From: Terry Lambert Message-Id: <199607302116.OAA00621@phaeton.artisoft.com> Subject: Re: Union mounts and other mounts To: toor@dyson.iquest.net (John S. Dyson) Date: Tue, 30 Jul 1996 14:16:07 -0700 (MST) Cc: michaelh@cet.co.jp, freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199607251559.KAA00163@dyson.iquest.net> from "John S. Dyson" at Jul 25, 96 10:59:19 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Terry, are you out there? > > > > Please upload your mega patches. I'm sure someone will take a look and > > maybe we can at least start with getting the locks fixed. > > > I want to consider including Terry's stuff. Even though I do filesystem > hacking from time to time, I think that we need to get agreement from > other's (on the team) on the changes. The changes have significant > architectural implications. > > At least, in certain areas, Terry is on the right track... We need to > get consensus on the changes. The last batch of changes don't fix all > of the problems, and Jeffery Hsu's stuff should be reviewed and appropriately > included also. I actually think that we are stagnating in this area a "little > bit." But again, I don't feel qualified to make wholesale changes in that > (the VFS) section of the kernel, without agreement from others... Anybody > have any ideas on this impasse? Jeffrey's mount changes are my mount code with some of the edges knocked off... he's done a good job on it. It happens to work around a couple of known problems in the Lite2 code, so he included them. The other changes are less seperable, which is why Poul has asked for a source tree copy (as in previous message: I will try for this weekend). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 30 14:20:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA07968 for hackers-outgoing; Tue, 30 Jul 1996 14:20:43 -0700 (PDT) Received: from eac.iafrica.com (196-7-192-139.iafrica.com [196.7.192.139]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA07939; Tue, 30 Jul 1996 14:20:08 -0700 (PDT) Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id XAA00293; Tue, 30 Jul 1996 23:17:47 +0200 From: Robert Nordier Message-Id: <199607302117.XAA00293@eac.iafrica.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: terry@lambert.org (Terry Lambert) Date: Tue, 30 Jul 1996 23:17:46 +0200 (SAT) Cc: hackers@freebsd.org, current@freebsd.org In-Reply-To: <199607302027.NAA00470@phaeton.artisoft.com> from "Terry Lambert" at Jul 30, 96 01:27:59 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > > Microsoft is shortly to be introducing a FAT32 filesystem to Windows > > 95 which will increase maximum filesystem size from 2 (or 4, for > > NT) gigabytes to 2 terabytes. The new filesystem makes use of > > 32-bit (as opposed to 12-bit and 16-bit) FAT entries and will > > require a fundamentally different handling of boot record, FATs, > > and root directory, so I'm busy on provision for this also. > > I have a beta copy of this in house right now. It is intended > solely for the OEM market. I think it will require a reinstall > to share the disk in any case, since FIPS/PARTED/etc. doesn't > understand the disk layout. In general, you will only ever see > it on preinstalled systems. [...] > > I think it's ready now. The limiting factor is going to be MS's OEM > release date. > > Don't expect to install VFAT32 yourself, since NT can't mount VFAT32 > partitions, and MS wants everyone to move to NT (Windows95 has always > been billed as a transition product). Good to have your comments, Terry. Would it be correct to say you consider VFAT32 support not worth the effort, or am I reading too much between the lines? -- Robert Nordier From owner-freebsd-hackers Tue Jul 30 14:28:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA08439 for hackers-outgoing; Tue, 30 Jul 1996 14:28:39 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA08412; Tue, 30 Jul 1996 14:28:07 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA00658; Tue, 30 Jul 1996 14:26:47 -0700 From: Terry Lambert Message-Id: <199607302126.OAA00658@phaeton.artisoft.com> Subject: Re: Union mounts and other mounts To: phk@critter.tfs.com (Poul-Henning Kamp) Date: Tue, 30 Jul 1996 14:26:47 -0700 (MST) Cc: toor@dyson.iquest.net, michaelh@cet.co.jp, freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <1028.838313231@critter.tfs.com> from "Poul-Henning Kamp" at Jul 25, 96 06:47:11 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Jeff's changes have higher priority for me than Terrys, because they > bring us closer to the codebase Kirk is hacking away on, and he has > some nice things brewing too. Yes; I was under the impression that one of the things Kirk was doing was soft updates. Matt Day already has an FFS integration of soft updates against the FreeBSD FS code, as ported to Windows 95. I dislike the idea of seperately retrofitting each FS code base (in the BSD case, it means seperate UFS chunks for FFS and LFS and ... unless Kirk is retrofitting all of the FS's. Finding out where soft updates go in a given FS is a graph reduction problem. The way Ganger and Patt solved the problem hides the graph reduction, and so is very FFS specific. I think this is a design error, but it was expedient, since you would otherwise have to consider each FS as a set of event points in an acyclic graph of event dependencies mixed in with POSIX semantics. Considering FS's as event/trigger/processing sets is not really an easy thing, given how the code is arranged. Eventually, I'd like to see the FS defined in terms of events and reactions to events. With an up-front graph, you could establish a node/callback chain when the FS is instantiated, and then do I/O in the context of event nodes. This would let you have a single engine for doing soft updates, which is referenced by all FS's, instead of having to hack the soft updates into each FS on a case-by-case basis. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 30 14:20:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA07969 for hackers-outgoing; Tue, 30 Jul 1996 14:20:45 -0700 (PDT) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA07908 for ; Tue, 30 Jul 1996 14:20:03 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.7.5/8.7.3) with SMTP id RAA03424; Tue, 30 Jul 1996 17:18:46 -0400 (EDT) Message-Id: <199607302118.RAA03424@whizzo.transsys.com> X-Authentication-Warning: whizzo.transsys.com: Host localhost.transsys.com [127.0.0.1] didn't use HELO protocol To: Terry Lambert cc: babkin@hq.icb.chel.su, jhay@mikom.csir.co.za, hackers@FreeBSD.org From: "Louis A. Mamakos" Subject: Re: Ethernet-like loopback & IPX References: <199607301821.LAA00292@phaeton.artisoft.com> In-reply-to: Your message of "Tue, 30 Jul 1996 11:21:45 PDT." <199607301821.LAA00292@phaeton.artisoft.com> Date: Tue, 30 Jul 1996 17:18:46 -0400 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I said: > > Sure, it's true that the current drivers do not allow the MAC address > > to be set on the various LAN interfaces, but this would argue for > > fixing the device drivers, and not the protocol design. > > > > While you may believe that the single address per IPX host is an > > error, it is fundamental to the protocol's design. I wouldn't > > characterize changing this as "fixing" it, unless it's the same way a > > veteranarian "fixes" something. And Terry said: > You are mistaken. > > Probably, you don't know about "internal net addresses", which were > introduced in NetWare 3.x. > > Each NetWare server from 3.x onward (and thus each router) has the > concept of an internal net address. This is basically an internal > virtual network interface. I think that we're in violent agreement. First, IPX != Novell, more or less. Second, a NetWare 3.x file server I really view as a Novell router with this internal interface to a file server virtual host. When entities communicate with the file server, they use only the internal network number, and not the hardware interface addresses/network numbers. The file server "host" has only a single address. My part of the discussion was to discourage "fixing" the IPX stack to allow a multihomed host to have distinct addresses. I believe that this violates a premise of IPX and how entities are addressed. I believe that the Novell file server instances is really a different animal, and not just a host with multiple addresses. louie From owner-freebsd-hackers Tue Jul 30 14:38:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09241 for hackers-outgoing; Tue, 30 Jul 1996 14:38:19 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA09198; Tue, 30 Jul 1996 14:37:37 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA00697; Tue, 30 Jul 1996 14:35:51 -0700 From: Terry Lambert Message-Id: <199607302135.OAA00697@phaeton.artisoft.com> Subject: Re: Union mounts and other mounts To: michaelh@cet.co.jp (Michael Hancock) Date: Tue, 30 Jul 1996 14:35:50 -0700 (MST) Cc: gibbs@freefall.freebsd.org, dfr@render.com, phk@critter.tfs.com, toor@dyson.iquest.net, freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Michael Hancock" at Jul 26, 96 09:45:44 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > >Is Kirk going to attack some of the same issues as Terry is talking about? > > >To improve my own understanding of the interface, I just started writing > > >manpages for the VFS entry points and VOP_LOOKUP makes me feel ill :-). > > > > Last I heard, Kirk was incorperating the recent work on soft metadata > > updates into the 4.4Lite2 code base. > > I also heard he was working on delayed ordered writes which might mean a > lot of changes per fs. > > Can anyone confirm the any of the above? I can confirm that USL has a patent on delayed ordered writes. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 30 14:36:24 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA09113 for hackers-outgoing; Tue, 30 Jul 1996 14:36:24 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA08995; Tue, 30 Jul 1996 14:35:47 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA00682; Tue, 30 Jul 1996 14:33:41 -0700 From: Terry Lambert Message-Id: <199607302133.OAA00682@phaeton.artisoft.com> Subject: Re: Union mounts and other mounts To: dfr@render.com (Doug Rabson) Date: Tue, 30 Jul 1996 14:33:41 -0700 (MST) Cc: phk@critter.tfs.com, toor@dyson.iquest.net, michaelh@cet.co.jp, freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Doug Rabson" at Jul 25, 96 07:42:10 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Is Kirk going to attack some of the same issues as Terry is talking about? > To improve my own understanding of the interface, I just started writing > manpages for the VFS entry points and VOP_LOOKUP makes me feel ill :-). Join the club. 8-). > Does anyone else have any documentation on our VFS interface? "The Magic Garden Explained" comes close, ignoring the stacking aspects, and the fact that we don't have getpage/putpage. Substitute "VN_" for "VOP_". > Does anyone feel like reviewing my efforts? I have seen the pdf postings elsewhere, but won't be able to look for some time. Do you have ASCII or otherwise non-PDF versions? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 30 14:49:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA10502 for hackers-outgoing; Tue, 30 Jul 1996 14:49:49 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA10472; Tue, 30 Jul 1996 14:49:40 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA00719; Tue, 30 Jul 1996 14:48:55 -0700 From: Terry Lambert Message-Id: <199607302148.OAA00719@phaeton.artisoft.com> Subject: Re: Union mounts and other mounts To: michaelh@cet.co.jp (Michael Hancock) Date: Tue, 30 Jul 1996 14:48:55 -0700 (MST) Cc: phk@critter.tfs.com, toor@dyson.iquest.net, freebsd-fs@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: from "Michael Hancock" at Jul 26, 96 10:17:09 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I understand that Jeff's Lite2 work needs to be incorporated before > any fs commits can be made. Yes. They are the baseline. Kirk's work is somewhat of a monkey wrench, since it will change the baseline, perhaps significantly: I don't know how he is going about the soft update integration. I exchanged some email with Ganger right after the paper came out, and he seemed reluctant to go for a generic implementation using graph reduction theory. I don't know whether to blame it on graph theory, group theory, and topology being ...ahem... rather esoteric, or that once you have an FFS that has it, you shouldn't need any other FS. 8-). > I think we're a ways off from any fs commits anyway. There's been very > little analysis on this mailing list of the direction the file systems > might be taking. Actually, there's been quite a lot of stuff on this, at least for local storage. What's been missing is distribution and replication. The "WebNFS" modification is an easy hack. As I stated on Usenet, it's pretty obvious that it's for downloading to embeded systems without local storage -- ie: set top boxes. Vendor | FS | For download of ----------------+---------------+------------------------ Microsoft | CIFS (SMB) | ActiveX (OLE) controls Sun | WebNFS (NFS) | JAVA Applets ----------------+---------------+------------------------ I don't think this is a direction we need to worry about for quite a while. More interesting is transactioning, reliability, and multifile idempotentence (Tuxedo-like capabilities for transaction interdependence). Other directions include componentization (one FS quota module, etc.), hosted metadata for interoperability (one hosting module, ala UMSDOSFS), and event notification to user space processes (ie: "file browser, the directory whose icons are presently being displayed, has changed") to get rid of polling and go more towards a user interactive model, etc.. Transient connectedness and replication are already being looked at by the Japanese "Nomads" group. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 30 14:53:03 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA10851 for hackers-outgoing; Tue, 30 Jul 1996 14:53:03 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA10843 for ; Tue, 30 Jul 1996 14:52:55 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA00735; Tue, 30 Jul 1996 14:52:35 -0700 From: Terry Lambert Message-Id: <199607302152.OAA00735@phaeton.artisoft.com> Subject: Re: patch for the 'sgetrune' of EUC encoding To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Date: Tue, 30 Jul 1996 14:52:35 -0700 (MST) Cc: mihoko@pa.yokogawa.co.jp, freebsd-hackers@FreeBSD.org In-Reply-To: <199607260346.HAA01313@nagual.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Jul 26, 96 07:46:26 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > That is, The library function 'mblen(3)' doesn't return the error > > when the second byte is not set MSB. > > I make the following patch for this problem. > > ... > > > + /* '0x80-0x9f' are control codes */ > > + if ((c = (unsigned char)*string++) < 0xa0) { > > I dislike this hardcoded assumption, because it makes sgetrune > very charset-depended without proper configuration knobs. > I.e. if it plans to sense control codes, it must be iscntrl() > instead. > Could you change this thing? Hee hee! 8-). I wondered how long this would last before the KOI-8 people cake out against it... if only they were using the ISO standard for Coptic languages instead... }B-}. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 30 15:00:12 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA11216 for hackers-outgoing; Tue, 30 Jul 1996 15:00:12 -0700 (PDT) Received: from etinc.com (etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA11181 for ; Tue, 30 Jul 1996 15:00:01 -0700 (PDT) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id SAA00355; Tue, 30 Jul 1996 18:02:21 -0400 Date: Tue, 30 Jul 1996 18:02:21 -0400 Message-Id: <199607302202.SAA00355@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Terry Lambert From: dennis@etinc.com (Dennis) Subject: Re: Ethernet-like loopback & IPX Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry writes... >> While you may believe that the single address per IPX host is an >> error, it is fundamental to the protocol's design. I wouldn't >> characterize changing this as "fixing" it, unless it's the same way a >> veteranarian "fixes" something. > >You are mistaken. > >Probably, you don't know about "internal net addresses", which were >introduced in NetWare 3.x. > >Each NetWare server from 3.x onward (and thus each router) has the >concept of an internal net address. This is basically an internal >virtual network interface. > This is true, as long as the "address" that you chose is not the same as one of the cards in the box. Netware server's have their own network address, which makes routing more sane. Dennis ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous Communications Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD and LINUX From owner-freebsd-hackers Tue Jul 30 15:05:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA11626 for hackers-outgoing; Tue, 30 Jul 1996 15:05:25 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA11605 for ; Tue, 30 Jul 1996 15:05:18 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id PAA29462 for ; Tue, 30 Jul 1996 15:05:02 -0700 (PDT) Prev-Resent: Tue, 30 Jul 1996 15:05:02 -0700 Prev-Resent: "hackers@freebsd.org " Received: from freefall.freebsd.org (jkh-sl0-o.cdrom.com [204.216.27.193]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id NAA26985 for ; Tue, 30 Jul 1996 13:21:50 -0700 (PDT) Received: from wc.cdrom.com (wc.cdrom.com [204.216.28.155]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA03831 for ; Tue, 30 Jul 1996 13:22:02 -0700 (PDT) Received: (from r3cgm@localhost) by wc.cdrom.com (8.6.12/8.6.12) id NAA28476 for jkh; Tue, 30 Jul 1996 13:21:31 -0700 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by wc.cdrom.com (8.6.12/8.6.12) with SMTP id RAA01175 for ; Tue, 23 Jul 1996 17:53:51 -0700 Message-Id: <199607240053.RAA01175@wc.cdrom.com> X-Authentication-Warning: wc.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: r3cgm@cdrom.com Subject: Re: bug in driver In-reply-to: Your message of "Mon, 22 Jul 1996 16:38:30 +0200." <199607221438.QAA21299@dutian.twi.tudelft.nl> Date: Tue, 23 Jul 1996 17:53:51 -0700 From: Order Information Resent-To: hackers@freebsd.org Resent-Date: Tue, 30 Jul 1996 15:05:02 -0700 Resent-Message-ID: <29460.838764302@time.cdrom.com> Resent-From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Send this to whoever is supposed to see it. -Info "J.M.W. Kooijman" said... >Dear Sirs, >I recently downloaded the ide/cdrom-driver from your FreeBSD(stable)- >directory (files ../src/sys/i386/isa/wd.c, atapi.c and wcd.c c.a.). >I discovered several bugs when trying to include the driver in the >kernel. In the first place the code that checks free IDE drives in >wdattach() in wd.c never reaches the atapi_attach()-call in normal >circumstances. Consequently, the cdrom-device, that is a slave to the >ide-controller is never attached. This is because of the goto-jump >(Dykstra apparently lived in vain, warning about this). I wrote >the following replacement-code: > >#ifdef ATAPI > /* > * Probe all free IDE units, searching for ATAPI drives. > */ > for (unit=0; unit<2; ++unit) { > for (lunit=0; lunit if (!(wddrives[lunit]->dk_ctrlr == dvp->id_unit && > wddrives[lunit]->dk_unit == unit)){ > printf("Attempt atapi_attach ctlr %d unit %d\n",dvp->id_unit, > unit); > if (!atapi_attach (dvp->id_unit, unit, dvp->id_iobase, > &kdc_wdc[dvp->id_unit])) > printf("Attempt atapi_attach not succeeded\n"); > } > else { > printf("ctrlr %d unit %d not free\n",dvp->id_unit,unit); > } > } >next: printf("End of probe of free IDE units\n"); >#endif > >This works, provided the incorrect switches around ATAPI_STATIC in >atapi.c and atapi.h (which now cause the wrong parts of the source >to be compiled) are corrected. >I was amazed that you allow this stuff on your website. Has no one >else complained? >Sincerely, >Joe Kooijman >kooijman@dutian.twi.tudelft.nl From owner-freebsd-hackers Tue Jul 30 15:05:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA11698 for hackers-outgoing; Tue, 30 Jul 1996 15:05:57 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA11677 for ; Tue, 30 Jul 1996 15:05:51 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA00765; Tue, 30 Jul 1996 15:00:11 -0700 From: Terry Lambert Message-Id: <199607302200.PAA00765@phaeton.artisoft.com> Subject: Re: Asynchronous IO - Posix AIO To: dchapes@zeus.leitch.com (Dave Chapeskie) Date: Tue, 30 Jul 1996 15:00:11 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199607261922.PAA01514@ale.zeus.leitch.com> from "Dave Chapeskie" at Jul 26, 96 03:22:01 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have need of an AIO subsystem and have been thinking about how I > might do a partial Posix AIO implementation under FreeBSD. Has > anyone else given this any thoughts? > > Would this best be done via a user side library, via new system > calls, via a mix of both, etc. Any thoughts on this would be greatly > appreciated. I think the correct thing to do is create an alternate call gate and aiowait/aiocancel calls, plus kernel context records, and add a flag to each system call to indicate that it is potentially blocking or not. Then "aioread" is "read using async call gate" and "aiowrite" is "write using async call gate". The reasoning is that things other than read/write can also block, and you might want to trade the block for queue + context switch (the POSIX AIO was originally for support of SunOS LWP ALA the University of Washington paper on "SPARC Register Windows and User Space Threading"). This would also let you write "team" in one process... 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 30 15:11:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA12305 for hackers-outgoing; Tue, 30 Jul 1996 15:11:40 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA12294 for ; Tue, 30 Jul 1996 15:11:33 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id PAA29570; Tue, 30 Jul 1996 15:11:01 -0700 (PDT) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-hackers@FreeBSD.ORG (FreeBSD hackers), heo@cslsun10.sogang.ac.kr (Heo Sung-Gwan) Subject: Re: Manpages 9 In-reply-to: Your message of "Tue, 30 Jul 1996 22:01:09 +0200." <199607302001.WAA11579@uriah.heep.sax.de> Date: Tue, 30 Jul 1996 15:11:01 -0700 Message-ID: <29567.838764661@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > j@uriah 141% ls /usr/share/man/man9 > /usr/share/man/man9: > copy.9.gz fubyte.9.gz subyte.9.gz > copyin.9.gz fuswintr.9.gz suswintr.9.gz > copyinstr.9.gz fusword.9.gz susword.9.gz > copyout.9.gz fuword.9.gz suword.9.gz > copystr.9.gz i386/ timeout.9.gz > devfs_add_devsw.9.gz intro.9.gz tsleep.9.gz > devfs_add_devswf.9.gz sleep.9.gz untimeout.9.gz > devfs_link.9.gz store.9.gz wakeup.9.gz > fetch.9.gz style.9.gz Hmmmmmm. A good 60% of these aren't even committed - you holdin' back on us there, pardner? :-) > I've got slice(9) (with alot of input from Bruce) and spl(9) in my > personal queue. I wish more people would contribute to this effort. Well, making the effort which is currently underway more VISIBLE might have a way of spawning more imitators. :-) Jordan From owner-freebsd-hackers Tue Jul 30 15:13:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA12454 for hackers-outgoing; Tue, 30 Jul 1996 15:13:44 -0700 (PDT) Received: from etinc.com (etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA12446 for ; Tue, 30 Jul 1996 15:13:37 -0700 (PDT) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id SAA00430; Tue, 30 Jul 1996 18:16:07 -0400 Date: Tue, 30 Jul 1996 18:16:07 -0400 Message-Id: <199607302216.SAA00430@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Terry Lambert From: dennis@etinc.com (Dennis) Subject: Re: X.25 revisited Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >> 2) Is there a terminal server type application available for that interface >> >> so X.25 users dialing into a network could access the FreeBSD system, >> >> or does this need to be built? >> > >> >I believe you are looking for an X.29 PAD. >> >> Well, not really....a PAD more describes the caller end rather than the >> server end. I'm looking more to service PAD callers from some sort of >> emulator. Our (old) SCO driver simulated async ttys and used the >> standard gettys...there are several ways to do it. >> >> Just what IS in the ISODE stuff that anyone might want? > >Circuit switching via X.29, for one thing. X.29 is just a tiny command protocol for controlling a PAD...its not very usefuly by itself....... where would one find this stuff.....to look at (not to install). Dennis ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous Communications Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD and LINUX From owner-freebsd-hackers Tue Jul 30 15:25:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA13272 for hackers-outgoing; Tue, 30 Jul 1996 15:25:04 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA13249; Tue, 30 Jul 1996 15:24:58 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA00825; Tue, 30 Jul 1996 15:23:50 -0700 From: Terry Lambert Message-Id: <199607302223.PAA00825@phaeton.artisoft.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: rnordier@iafrica.com (Robert Nordier) Date: Tue, 30 Jul 1996 15:23:50 -0700 (MST) Cc: terry@lambert.org, hackers@freebsd.org, current@freebsd.org In-Reply-To: <199607302117.XAA00293@eac.iafrica.com> from "Robert Nordier" at Jul 30, 96 11:17:46 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I have a beta copy of this in house right now. It is intended > > solely for the OEM market. I think it will require a reinstall > > to share the disk in any case, since FIPS/PARTED/etc. doesn't > > understand the disk layout. In general, you will only ever see > > it on preinstalled systems. > [...] > > > > I think it's ready now. The limiting factor is going to be MS's OEM > > release date. > > > > Don't expect to install VFAT32 yourself, since NT can't mount VFAT32 > > partitions, and MS wants everyone to move to NT (Windows95 has always > > been billed as a transition product). > > Good to have your comments, Terry. > > Would it be correct to say you consider VFAT32 support not worth the > effort, or am I reading too much between the lines? The installation I have will "upgrade" an existing system. Whether VFAT32 becomes rampant will depend on whether they give it as an option. Right now, an upgrade kills NT, and the sector-based allocation table that replaces the partition table kills NT on dual-boot systems. I believe that they would have to release or announce NT support before they would be willing to let people use the version I have. The current estimate for Windows95's life cycle is 2 years before there is a unification of NT/95 to get a single Win32 based OS. If they release the VFAT32 for 95 without releasing it for NT, then the life cycle for Windows95 grows to 2 years + (the "+" being the delay in the NT release to allow upgrades). NT already has a problem with DriveSpace drives, and there are a lot of shops running NT on FAT FS's because FAT is actually *faster* than NTFS. I don't think Microsoft will kill NT on purpose. On the other hand, support for it can't hurt. The replacement for the partition table is bound to make it into NT even if nothing else does. I think the partition translation problem is logically seperate from the FAT FS itself (I think it will go into physical-to-logical device mapping in DEVFS), so it would be possible to support it without supporting the VFAT32 FS proper. Expect to need support for it in no less than a year, if ever. If I were writing a VFATFS, I would macro the calls to do the actual reads/writes and stick device range checking in a function layer that you can expect to go away in a later incarnation. Return "EINVAL" and do the logical to physical offset translation in your layer. All new FS's should expect to work on a "device" that is totally committed to the FS and looks like it starts at offset 0, and return EINVAL or EFAULT for out of range operations on the device. If this were there now, then the MSDOSFS would be incapable of corrupting non-MSDOSFS disk areas with the current code. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 30 15:31:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA13705 for hackers-outgoing; Tue, 30 Jul 1996 15:31:04 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA13699 for ; Tue, 30 Jul 1996 15:31:01 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA00868; Tue, 30 Jul 1996 15:29:47 -0700 From: Terry Lambert Message-Id: <199607302229.PAA00868@phaeton.artisoft.com> Subject: Re: So what's the word on quotas in -current or 2.1.5? To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Tue, 30 Jul 1996 15:29:47 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: from "Jaye Mathisen" at Jul 30, 96 12:53:26 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Stable? Usable? Seems I recall reading about some breakage, and I'm > putting in a new box for our userbase. If quotas are broke, I have to > install BSD/OS, if they aren't, then it's FreeBSD all the way... Don't put quota's on root. Eventually, quotas will be a mount-over VOP stacking option, and will apply to all FS's equally. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 30 15:34:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA13993 for hackers-outgoing; Tue, 30 Jul 1996 15:34:15 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA13988 for ; Tue, 30 Jul 1996 15:34:13 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA00916; Tue, 30 Jul 1996 15:33:32 -0700 From: Terry Lambert Message-Id: <199607302233.PAA00916@phaeton.artisoft.com> Subject: Re: X.25 revisited To: dennis@etinc.com (Dennis) Date: Tue, 30 Jul 1996 15:33:32 -0700 (MST) Cc: terry@lambert.org, hackers@freebsd.org In-Reply-To: <199607302216.SAA00430@etinc.com> from "Dennis" at Jul 30, 96 06:16:07 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> Just what IS in the ISODE stuff that anyone might want? > > > >Circuit switching via X.29, for one thing. > > X.29 is just a tiny command protocol for controlling a PAD...its not > very usefuly by itself....... > > > where would one find this stuff.....to look at (not to install). Beats me. I always look up "ISODE" via Yahoo, or I go to an older FreeBSD CDROM (before the ISO stuff was deleted from the tree). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Tue Jul 30 15:34:53 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA14033 for hackers-outgoing; Tue, 30 Jul 1996 15:34:53 -0700 (PDT) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA14028 for ; Tue, 30 Jul 1996 15:34:51 -0700 (PDT) Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id AAA09756 for ; Wed, 31 Jul 1996 00:36:54 +0200 Received: by uni4nn.iaf.nl with UUCP id AA13078 (5.67b/IDA-1.5 for FreeBSD-hackers@freebsd.org); Wed, 31 Jul 1996 00:36:18 +0200 Received: by iafnl.es.iaf.nl with UUCP id AA22196 (5.67b/IDA-1.5 for FreeBSD-hackers@freebsd.org); Wed, 31 Jul 1996 00:07:16 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.6) id AAA00206 for FreeBSD-hackers@freebsd.org; Wed, 31 Jul 1996 00:03:58 +0200 From: Wilko Bulte Message-Id: <199607302203.AAA00206@yedi.iaf.nl> X-Organisation: Private FreeBSD site - Arnhem - The Netherlands Subject: comments on panic message? To: FreeBSD-hackers@freebsd.org (FreeBSD hackers list) Date: Wed, 31 Jul 1996 00:03:58 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi there Any comments on: Jul 30 21:39:00 yedi last message repeated 4 times Jul 31 00:01:19 yedi /kernel: vnode_pager_input: unexpected missing page: firsta ddr: -1, foff: 98304, vnp_size: 147456 Jul 31 00:01:19 yedi /kernel: panic: vnode_pager_input:... Jul 31 00:01:19 yedi /kernel: Jul 31 00:01:19 yedi /kernel: syncing disks... 2 2 2 2 2 2 2 2 2 2 1 done ? This is 2.1R on a Asus XE P100 with 32Mb. Disk is a NCR810 with a 2Gb Quantum. Wilko _ ____________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------- From owner-freebsd-hackers Tue Jul 30 15:51:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA15278 for hackers-outgoing; Tue, 30 Jul 1996 15:51:21 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA15249; Tue, 30 Jul 1996 15:51:08 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA23619; Wed, 31 Jul 1996 00:51:05 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA26726; Wed, 31 Jul 1996 00:51:05 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id WAA12158; Tue, 30 Jul 1996 22:42:40 +0200 (MET DST) From: J Wunsch Message-Id: <199607302042.WAA12158@uriah.heep.sax.de> Subject: Re: Best Ethernet Card / Best Drivers for ? To: mango@communique.net (Raul Zighelboim) Date: Tue, 30 Jul 1996 22:42:40 +0200 (MET DST) Cc: hardware@FreeBSD.org, hackers@FreeBSD.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Raul Zighelboim at "Jul 30, 96 01:57:37 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Raul Zighelboim wrote: > > We are building a server for the office. > We want to make this server as solid as possible. > > So, the question is: > > What is the best supported Ethernet Card for FreeBSD 2.1.5 ? Mainly depends on the bus system. For ISA buses, the WD/SMC cards (SMC 8013) are fine. For PCI, get something with the DEC 21040 chip. They are built by many vendors. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jul 30 15:52:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA15475 for hackers-outgoing; Tue, 30 Jul 1996 15:52:44 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA15466 for ; Tue, 30 Jul 1996 15:52:35 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA23611; Wed, 31 Jul 1996 00:51:01 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id AAA26719; Wed, 31 Jul 1996 00:51:01 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id WAA12296; Tue, 30 Jul 1996 22:50:06 +0200 (MET DST) From: J Wunsch Message-Id: <199607302050.WAA12296@uriah.heep.sax.de> Subject: Re: So what's the word on quotas in -current or 2.1.5? To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Tue, 30 Jul 1996 22:50:06 +0200 (MET DST) Cc: mrcpu@cdsnet.net (Jaye Mathisen) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Jaye Mathisen at "Jul 30, 96 12:53:26 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Jaye Mathisen wrote: > Stable? Usable? sax.sax.de runs with them under FreeBSD 2.1R, as a login server for a small non-commercial ISP. The machine is not as stable as i wish it were, but it's also not the very best kind of hardware at all. I can't directly hold the quotas responsible for the crashes or hangs, they appear randomly all over the place (mostly page faults, in case i've got a core dump), and we're seeing too many logs of sig 11's as well, so i tend to blame hardware. (However, upgrading from 2.0.5 to 2.1 made it surprisingly more stable.) The important thing is that you _must_ put the quota control file into the same partition. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jul 30 16:39:24 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA17671 for hackers-outgoing; Tue, 30 Jul 1996 16:39:24 -0700 (PDT) Received: from palin.cc.monash.edu.au (palin.cc.monash.edu.au [130.194.2.87]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA17662 for ; Tue, 30 Jul 1996 16:39:18 -0700 (PDT) Received: (peter@localhost) by palin.cc.monash.edu.au (8.7.3/8.6.4) id JAA18594; Wed, 31 Jul 1996 09:39:16 +1000 Date: Wed, 31 Jul 1996 09:39:16 +1000 From: Peter Hawkins Message-Id: <199607302339.JAA18594@palin.cc.monash.edu.au> To: hackers@freebsd.org, root@inner.cortx.com Subject: Re: /etc/group Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I understood that you could have multiple lines with the same GID and group name. Peter From owner-freebsd-hackers Tue Jul 30 17:09:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA19407 for hackers-outgoing; Tue, 30 Jul 1996 17:09:48 -0700 (PDT) Received: from frig.mt.cs.keio.ac.jp (frig.mt.cs.keio.ac.jp [131.113.32.7]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA19377; Tue, 30 Jul 1996 17:09:38 -0700 (PDT) Received: (from hosokawa@localhost) by frig.mt.cs.keio.ac.jp (8.6.12+2.4W/3.4Wbeta3) id JAA26576; Wed, 31 Jul 1996 09:09:34 +0900 Date: Wed, 31 Jul 1996 09:09:34 +0900 Message-Id: <199607310009.JAA26576@frig.mt.cs.keio.ac.jp> To: announce@FreeBSD.org, mobile@FreeBSD.org, hackers@FreeBSD.org Cc: cyf00575@niftyserve.or.jp Reply-To: mobile@FreeBSD.org Subject: [PCMCIA] PAO-960731 is now available! From: hosokawa@mt.cs.keio.ac.jp (HOSOKAWA Tatsumi) X-Mailer: mnews [version 1.18PL3] 1994-08/01(Mon) Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk New version of PAO (FreeBSD PC-card and APM package) is now available! Important changes: o 2.1.5-RELEASE support I put it at ftp://ryukyu.mt.cs.keio.ac.jp/pub/FreeBSD/PAO-960731.tar.gz BTW, this ftp site will be down from today's evening :-) through August 8 and I'm away from net until August 8. So I also put this file at ftp://freefall.freebsd.org/incoming/PAO-960731.tar.gz If you have something to tell me urgently, please e-mail me at "cyf00575@niftyserve.or.jp". Enjoy! -- HOSOKAWA, Tatsumi E-mail: hosokawa@mt.cs.keio.ac.jp WWW homepage: http://www.mt.cs.keio.ac.jp/person/hosokawa.html Department of Computer Science, Keio University, Yokohama, Japan From owner-freebsd-hackers Tue Jul 30 17:10:41 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA19528 for hackers-outgoing; Tue, 30 Jul 1996 17:10:41 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA19520 for ; Tue, 30 Jul 1996 17:10:39 -0700 (PDT) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id RAA00471; Tue, 30 Jul 1996 17:08:47 -0700 (PDT) Message-Id: <199607310008.RAA00471@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: Terry Lambert cc: davidg@Root.COM, heo@cslsun10.sogang.ac.kr, freebsd-hackers@FreeBSD.org Subject: Re: your mail In-reply-to: Your message of "Tue, 30 Jul 1996 13:11:44 PDT." <199607302011.NAA00436@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Jul 1996 17:08:45 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Unless he has a creative way of handling lots of mpeg files , then I doubt that he needs such a mechanism for transversing directories. I believe what the original poster was after is to eliminate caching mpeg files in memory which doesn't bother me that much. I supposed that for mpeg2 , to conserve memory or a video server this is important;however, for mpeg1 requiring a 150KB stream is hardly worth doing. The first thing I would try to do is to spec out the system: 1. cost 2. cpu 3. memory 4. disks / controllers 5. mpeg decoder 6. server or standalone unit >From The Desk Of Terry Lambert : > > From The Desk Of David Greenman : > > > > 4) How can user process access the file in ufs filesystem through raw d isk? > > > > > > You can't unless you write a user-mode UFS/FFS that does it's I/O thro ugh > > > the raw device. I couldn't imagine why you'd want to do this, however. > > > > > > > My guess is that his assumption is that accessing the files via a > > "raw disk mode" will be faster than going thru the normal file > > access mechanism. I wish I knew what is he up to so we can help him or > > better yet his justification for taking such approach . > > You can more efficiently traverse a directory this way; specifically, > you avoid the system call boundry push problem when you have blocks > of crap file names that don't match the pattern you are looking for. > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. From owner-freebsd-hackers Tue Jul 30 18:05:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA22038 for hackers-outgoing; Tue, 30 Jul 1996 18:05:54 -0700 (PDT) Received: from wugate.wustl.edu (wugate.wustl.edu [128.252.120.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA22031 for ; Tue, 30 Jul 1996 18:05:51 -0700 (PDT) Received: from michelob.wustl.edu (michelob.wustl.edu [128.252.130.10]) by wugate.wustl.edu (8.7.5/8.7.3) with SMTP id UAA13750 for ; Tue, 30 Jul 1996 20:06:31 -0500 test-header: [newton@michelob.wustl.edu] Received: from slug-ppp16.wustl.edu by michelob.wustl.edu (4.1/SMI-4.1) id AA04411; Tue, 30 Jul 96 19:44:50 CDT Message-Id: <31FECCF2.55CD@michelob.wustl.edu> Date: Tue, 30 Jul 1996 20:03:14 -0700 From: Newton Love Reply-To: newton@michelob.wustl.edu Organization: St. Louis UNIX Users' Group X-Mailer: Mozilla 3.0b5aGold (Win16; I) Mime-Version: 1.0 To: freebsd-hackers@freefall.FreeBSD.org Subject: You're there Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk So, you are listed in the site below. We are also part of Yahoo's /computers.../OS/UNIX/ Usersgroups/Index follow the lead, (not an exact path reference) Web Wide UNIX ---> http://dark.wustl.edu/~newton/othr_uug.html St. Louis UUG ---> http://dark.wustl.edu/ -- "Everyone's got something to hide, except for me an my monkey" (and he's not giving out our pgp key. Hey! Talk to him!) From owner-freebsd-hackers Tue Jul 30 22:51:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA07769 for hackers-outgoing; Tue, 30 Jul 1996 22:51:36 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA07714 for ; Tue, 30 Jul 1996 22:51:11 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id HAA01674 for ; Wed, 31 Jul 1996 07:50:57 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA01459 for freebsd-hackers@freebsd.org; Wed, 31 Jul 1996 07:50:57 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id HAA14269 for freebsd-hackers@freebsd.org; Wed, 31 Jul 1996 07:39:57 +0200 (MET DST) From: J Wunsch Message-Id: <199607310539.HAA14269@uriah.heep.sax.de> Subject: Re: Manpages 9 To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Wed, 31 Jul 1996 07:39:56 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <29567.838764661@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 30, 96 03:11:01 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Jordan K. Hubbard wrote: > > j@uriah 141% ls /usr/share/man/man9 > > /usr/share/man/man9: ... > Hmmmmmm. A good 60% of these aren't even committed - you holdin' back > on us there, pardner? :-) Hardly. Have you tried an `ls' on your own machine? A good 60 % are hard links to other pages, yep. > > I've got slice(9) (with alot of input from Bruce) and spl(9) in my > > personal queue. I wish more people would contribute to this effort. > > Well, making the effort which is currently underway more VISIBLE might > have a way of spawning more imitators. :-) Sadly not. The existing pages in section 9 are lurking there for rather long time already, but the only one who volunteerely came up with more stuff for this section by now is Doug Rabson. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Jul 30 22:55:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA08202 for hackers-outgoing; Tue, 30 Jul 1996 22:55:59 -0700 (PDT) Received: from pdx1 (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA08197 for ; Tue, 30 Jul 1996 22:55:57 -0700 (PDT) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1 (8.6.9/8.6.9) with ESMTP id WAA24856; Tue, 30 Jul 1996 22:57:45 -0700 Received: (proff@localhost) by suburbia.net (8.7.4/Proff-950810) id PAA14097; Wed, 31 Jul 1996 15:54:57 +1000 From: Julian Assange Message-Id: <199607310554.PAA14097@suburbia.net> Subject: Re: X.25 revisited To: terry@lambert.org (Terry Lambert) Date: Wed, 31 Jul 1996 15:54:57 +1000 (EST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199607302233.PAA00916@phaeton.artisoft.com> from "Terry Lambert" at Jul 30, 96 03:33:32 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > >> Just what IS in the ISODE stuff that anyone might want? > > > > > >Circuit switching via X.29, for one thing. > > > > X.29 is just a tiny command protocol for controlling a PAD...its not > > very usefuly by itself....... > > > > > > where would one find this stuff.....to look at (not to install). > Is there any way to drive an X.29 connection? (x.25 over a regular modem from)? Often used in dial-on-demand NUA's. -- "Of all tyrannies a tyranny sincerely exercised for the good of its victims may be the most oppressive. It may be better to live under robber barons than under omnipotent moral busybodies, The robber baron's cruelty may sometimes sleep, his cupidity may at some point be satiated; but those who torment us for own good will torment us without end, for they do so with the approval of their own conscience." - C.S. Lewis, _God in the Dock_ +---------------------+--------------------+----------------------------------+ |Julian Assange RSO | PO Box 2031 BARKER | Secret Analytic Guy Union | |proff@suburbia.net | VIC 3122 AUSTRALIA | finger for PGP key hash ID = | |proff@gnu.ai.mit.edu | FAX +61-3-98199066 | 0619737CCC143F6DEA73E27378933690 | +---------------------+--------------------+----------------------------------+ From owner-freebsd-hackers Tue Jul 30 23:00:18 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA08383 for hackers-outgoing; Tue, 30 Jul 1996 23:00:18 -0700 (PDT) Received: from pdx1 (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA08376 for ; Tue, 30 Jul 1996 23:00:17 -0700 (PDT) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1 (8.6.9/8.6.9) with ESMTP id XAA24957; Tue, 30 Jul 1996 23:01:40 -0700 Received: (proff@localhost) by suburbia.net (8.7.4/Proff-950810) id PAA14132; Wed, 31 Jul 1996 15:59:38 +1000 From: Julian Assange Message-Id: <199607310559.PAA14132@suburbia.net> Subject: Re: Manpages 9 To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 31 Jul 1996 15:59:38 +1000 (EST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <29567.838764661@time.cdrom.com> from "Jordan K. Hubbard" at Jul 30, 96 03:11:01 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > fetch.9.gz style.9.gz > > Hmmmmmm. A good 60% of these aren't even committed - you holdin' back > on us there, pardner? :-) > > > I've got slice(9) (with alot of input from Bruce) and spl(9) in my > > personal queue. I wish more people would contribute to this effort. > > Well, making the effort which is currently underway more VISIBLE might > have a way of spawning more imitators. :-) > > Jordan Hnmm. Thinking of man pages, I was thinking of writing a "mman" or "meta man". That will search /usr/share/* for a matching document and run the approprimate document viewer (info, lynx, ghostview, etc). Comments? -- "Of all tyrannies a tyranny sincerely exercised for the good of its victims may be the most oppressive. It may be better to live under robber barons than under omnipotent moral busybodies, The robber baron's cruelty may sometimes sleep, his cupidity may at some point be satiated; but those who torment us for own good will torment us without end, for they do so with the approval of their own conscience." - C.S. Lewis, _God in the Dock_ +---------------------+--------------------+----------------------------------+ |Julian Assange RSO | PO Box 2031 BARKER | Secret Analytic Guy Union | |proff@suburbia.net | VIC 3122 AUSTRALIA | finger for PGP key hash ID = | |proff@gnu.ai.mit.edu | FAX +61-3-98199066 | 0619737CCC143F6DEA73E27378933690 | +---------------------+--------------------+----------------------------------+ From owner-freebsd-hackers Tue Jul 30 23:07:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA08716 for hackers-outgoing; Tue, 30 Jul 1996 23:07:19 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA08711 for ; Tue, 30 Jul 1996 23:07:16 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id GAA12493 for ; Wed, 31 Jul 1996 06:07:14 GMT Date: Wed, 31 Jul 1996 15:07:14 +0900 (JST) From: Michael Hancock To: FreeBSD Hackers Subject: kernel assertions (Rev. 1) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is a more concrete example of code specifications via assertions with changes based on the discussions earlier. Global Macros ------------- The assertion macros can have levels associated with them to allow the code author to choose which assertions go into the production build. ASSERT_LEVEL == 0 - All assertions are preprocessed out. ASSERT_LEVEL == 1 - Level 1 assertions are applied. (default) REQUIRE1, ENSURE1 ASSERT_LEVEL == 2 - Level 2 assertions are additionally applied REQUIRE1, ENSURE1 REQUIRE2, ENSURE2 Example ... /* * remove the buffer from the appropriate free list */ void bremfree(struct buf * bp) { int s = splbio(); REQUIRE2(bp, "Expected bp to point to something") REQUIRE1(bp->b_qindex != QUEUE_NONE, "Expected a buffer on a queue"); TAILQ_REMOVE(&bufqueues[bp->b_qindex], bp, b_freelist); bp->b_qindex = QUEUE_NONE; ENSURE2(bp->b_qindex == QUEUE_NONE, "Buffer should no longer be on a queue"); splx(s); } Since the ASSERTION_LEVEL is 1, only the original assertion check is actually compiled into the code. We were able to add specifications REQUIRE2 and ENSURE2 without adding any overhead except when running diagnostics. Note REQUIRE and ENSURE do the same thing. They are named differently for conceptual reasons. The ENSURE2 looks redundant in the above example, but for larger functions without multiple exits and with easily defined resulting states the assertion is useful. Though I've found that the REQUIRE assertions are more important. I personally don't care if they are called REQUIRE, ENSURE or just plain ASSERT. The REQUIRE and ENSURE names, borrowed from Eiffel, do help make things clearer. The REQUIRE2 stuff can replace the #ifdef DIAGNOSTICS if (expr) panic(expl); #endif stuff I've seen in the code. Assertion failures can print out the following: A stringified expr The description Filename Line number Mike Hancock From owner-freebsd-hackers Tue Jul 30 23:40:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA10182 for hackers-outgoing; Tue, 30 Jul 1996 23:40:45 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA10177 for ; Tue, 30 Jul 1996 23:40:36 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id XAA02552; Tue, 30 Jul 1996 23:40:06 -0700 (PDT) Message-Id: <199607310640.XAA02552@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Michael Hancock cc: FreeBSD Hackers Subject: Re: kernel assertions (Rev. 1) In-reply-to: Your message of Wed, 31 Jul 96 15:07:14 +0900. Date: Tue, 30 Jul 1996 23:40:05 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >The REQUIRE2 stuff can replace the > >#ifdef DIAGNOSTICS > if (expr) > panic(expl); >#endif I prefer asserts to call "Debugger()", rather than "panic()", and that's how I write my assertion macros. How are you supposed to debug something if it panics? ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-hackers Tue Jul 30 23:48:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA10686 for hackers-outgoing; Tue, 30 Jul 1996 23:48:32 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA10681 for ; Tue, 30 Jul 1996 23:48:30 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id XAA22916; Tue, 30 Jul 1996 23:48:09 -0700 (PDT) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: Manpages 9 In-reply-to: Your message of "Wed, 31 Jul 1996 07:39:56 +0200." <199607310539.HAA14269@uriah.heep.sax.de> Date: Tue, 30 Jul 1996 23:48:08 -0700 Message-ID: <22914.838795688@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hardly. Have you tried an `ls' on your own machine? A good 60 % > are hard links to other pages, yep. Shucks. I was looking at the sources, not the install directory. :-) Mea culpa. > Sadly not. The existing pages in section 9 are lurking there for > rather long time already, but the only one who volunteerely came up > with more stuff for this section by now is Doug Rabson. Hmmmmm. Rah! Rah! C'mon kernel hackers! Go team go! Docs! Docs! Docs! Olayyyy-olay-olay-olayyyyyyy! [rushes to the door and looks over his shoulder - everyone is still sitting down, looking at him with highly quizzical expressions]. You're right, that doesn't work at all. Hmmmm. Any suggestions, anyone? :-) Jordan From owner-freebsd-hackers Wed Jul 31 02:23:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA17480 for hackers-outgoing; Wed, 31 Jul 1996 02:23:40 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA17449 for ; Wed, 31 Jul 1996 02:23:35 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id BAA01128 for ; Wed, 31 Jul 1996 01:24:44 -0700 (PDT) Received: from gvr.win.tue.nl by mail.crl.com with SMTP id AA04670 (5.65c/IDA-1.5 for ); Wed, 31 Jul 1996 01:23:54 -0700 Received: by gvr.win.tue.nl (8.6.13/1.53) id KAA24842; Wed, 31 Jul 1996 10:21:50 +0200 From: guido@gvr.win.tue.nl (Guido van Rooij) Message-Id: <199607310821.KAA24842@gvr.win.tue.nl> Subject: Re: "login classes" To: sef@kithrup.com (Sean Eric Fagan) Date: Wed, 31 Jul 1996 10:21:49 +0200 (MET DST) Cc: hackers@FreeBSD.ORG In-Reply-To: <199607140659.XAA02107@kithrup.com> from Sean Eric Fagan at "Jul 13, 96 11:59:36 pm" X-Mailer: ELM [version 2.4ME+ PL17 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > (Basicly, the reason I want this is because I want to be able to use S/Key. > However, I don't like having a seperate account name for that. The login > classes allow you to specify something like, "sef:skey" at the login: > prompt, and login will then use S/Key instead of the default mechanism. It > also removes all password and/or authentication from the login program > proper, relying on /usr/libexec/auth_* -- e.g., /usr/libexec/auth_passwd and > /usr/libexec/auth_skey.) > This would break the current way of dealing with skeys: now you can specify when ppl are obligated to use S/Keys. With your scheme it will no longer be possible (at least I think so). Have you made your `normal' authentication in such a way that somehow the etc/skey.access file is still horoured? -Guido From owner-freebsd-hackers Wed Jul 31 02:23:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA17474 for hackers-outgoing; Wed, 31 Jul 1996 02:23:39 -0700 (PDT) Received: from minnow.render.com (render.demon.co.uk [158.152.30.118]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA17446 for ; Wed, 31 Jul 1996 02:23:35 -0700 (PDT) Received: from localhost (dfr@localhost) by minnow.render.com (8.6.12/8.6.9) with SMTP id KAA17195; Wed, 31 Jul 1996 10:23:53 +0100 Date: Wed, 31 Jul 1996 10:23:52 +0100 (BST) From: Doug Rabson To: "Jordan K. Hubbard" cc: Joerg Wunsch , FreeBSD hackers , Heo Sung-Gwan Subject: Re: Manpages 9 In-Reply-To: <29567.838764661@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Jul 1996, Jordan K. Hubbard wrote: > > j@uriah 141% ls /usr/share/man/man9 > > /usr/share/man/man9: > > copy.9.gz fubyte.9.gz subyte.9.gz > > copyin.9.gz fuswintr.9.gz suswintr.9.gz > > copyinstr.9.gz fusword.9.gz susword.9.gz > > copyout.9.gz fuword.9.gz suword.9.gz > > copystr.9.gz i386/ timeout.9.gz > > devfs_add_devsw.9.gz intro.9.gz tsleep.9.gz > > devfs_add_devswf.9.gz sleep.9.gz untimeout.9.gz > > devfs_link.9.gz store.9.gz wakeup.9.gz > > fetch.9.gz style.9.gz > > Hmmmmmm. A good 60% of these aren't even committed - you holdin' back > on us there, pardner? :-) I recognise most of them. copy*.9 are links to copy.9 fu*.9 to fetch.9 and su*.9 to store.9 so you won't see a list this large in /usr/src/share/man/man9. -- Doug Rabson, Microsoft RenderMorphics Ltd. Mail: dfr@render.com Phone: +44 171 251 4411 FAX: +44 171 251 0939 From owner-freebsd-hackers Wed Jul 31 02:24:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA17644 for hackers-outgoing; Wed, 31 Jul 1996 02:24:09 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA17573; Wed, 31 Jul 1996 02:23:56 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id BAA01243 ; Wed, 31 Jul 1996 01:44:40 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id SAA12179; Wed, 31 Jul 1996 18:37:27 +1000 Date: Wed, 31 Jul 1996 18:37:27 +1000 From: Bruce Evans Message-Id: <199607310837.SAA12179@godzilla.zeta.org.au> To: rnordier@iafrica.com, terry@lambert.org Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >All new FS's should expect to work on a "device" that is totally >committed to the FS and looks like it starts at offset 0, and return >EINVAL or EFAULT for out of range operations on the device. If >this were there now, then the MSDOSFS would be incapable of >corrupting non-MSDOSFS disk areas with the current code. It's always been there. Broken code can only write outside the range by corrupting the device number. Bruce From owner-freebsd-hackers Wed Jul 31 06:49:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA29563 for hackers-outgoing; Wed, 31 Jul 1996 06:49:05 -0700 (PDT) Received: from ra.ibr.cs.tu-bs.de (ra.ibr.cs.tu-bs.de [134.169.246.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA29496; Wed, 31 Jul 1996 06:48:09 -0700 (PDT) Received: from achill.ibr.cs.tu-bs.de [134.169.34.18] by ra.ibr.cs.tu-bs.de (8.6.10/tubsibr) with ESMTP id PAA08534; Wed, 31 Jul 1996 15:47:41 +0200 Received: from petri@localhost by achill.ibr.cs.tu-bs.de (8.6.10/tubsibr) id PAA02285; Wed, 31 Jul 1996 15:47:40 +0200 Date: Wed, 31 Jul 1996 15:47:40 +0200 From: Stefan Petri Message-Id: <199607311347.PAA02285@achill.ibr.cs.tu-bs.de> To: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: IPv6 / IPng? Reply-to: petri@ibr.cs.tu-bs.de Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! For my curiosity: What is the state of IPv6 or IPng for FreeBSD? is anyone working on it? Stefan From owner-freebsd-hackers Wed Jul 31 07:35:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA02473 for hackers-outgoing; Wed, 31 Jul 1996 07:35:13 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA02409; Wed, 31 Jul 1996 07:34:56 -0700 (PDT) Received: from localhost (trefor@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id PAA26280; Wed, 31 Jul 1996 15:36:57 +0100 (BST) Date: Wed, 31 Jul 1996 15:36:56 +0100 (BST) From: "Trefor S." To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, freebsd-chat@freebsd.org Subject: FreeBSD Accounts Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If anyone is interested in accounts on FreeBSD systems take a look at this url: http://www.flevel.co.uk/services/netaccs.html Regards, Trefor S. From owner-freebsd-hackers Wed Jul 31 07:50:43 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA03941 for hackers-outgoing; Wed, 31 Jul 1996 07:50:43 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA03936 for ; Wed, 31 Jul 1996 07:50:40 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id OAA15102 for ; Wed, 31 Jul 1996 14:50:38 GMT Date: Wed, 31 Jul 1996 23:50:38 +0900 (JST) From: Michael Hancock To: FreeBSD Hackers Subject: Re: kernel assertions (Rev. 1) In-Reply-To: <199607310640.XAA02552@MindBender.HeadCandy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Jul 1996, Michael L. VanLoon -- HeadCandy.com wrote: > >The REQUIRE2 stuff can replace the > > > >#ifdef DIAGNOSTICS > > if (expr) > > panic(expl); > >#endif > > I prefer asserts to call "Debugger()", rather than "panic()", and > that's how I write my assertion macros. How are you supposed to debug > something if it panics? I'd be happy either way. The point I was trying to make was that REQUIRE2 could replace the "tentative looking" argument checking in the code that often manifests itself in the form above. REQUIRE2 would also hopefully induce people to consistently do simple argument checking, because there is no overhead in the production code. The REQUIRE1 assertions would remove the argument checking that's integrated with the real code, just leaving REAL code. They would then be reinstated at the top where they belong. These are level I checks because obviously the author thought they were important enough to integrate the argument checking logic with the code doing the real work. Let's go for HIGHER QUALITY!!! nuff, said. Regards, Mike Hancock From owner-freebsd-hackers Wed Jul 31 08:27:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA05989 for hackers-outgoing; Wed, 31 Jul 1996 08:27:10 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA05982 for ; Wed, 31 Jul 1996 08:26:58 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id IAA05309; Wed, 31 Jul 1996 08:26:41 -0700 (PDT) Message-Id: <199607311526.IAA05309@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Michael Hancock cc: FreeBSD Hackers Subject: Re: kernel assertions (Rev. 1) In-reply-to: Your message of Wed, 31 Jul 96 23:50:38 +0900. Date: Wed, 31 Jul 1996 08:26:37 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I'd be happy either way. The point I was trying to make was that REQUIRE2 >could replace the "tentative looking" argument checking in the code that >often manifests itself in the form above. > >REQUIRE2 would also hopefully induce people to consistently do simple >argument checking, because there is no overhead in the production code. [...] >Let's go for HIGHER QUALITY!!! I agree 125%. My production code at work is literally filled with asserts. However, programmers first have to change their mindset from "I will assume most code is non-buggy, and I will find the few bugs that creep in when they happen" to "I will assume code has bugs, always, and I will write my code in a way that helps me find bugs, even when I'm not looking for them". Asserts (whatever they are called) are an exceptionally helpful tool for that, and as you say, they only slow down the machine when you actually turn them on. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-hackers Wed Jul 31 09:14:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA08591 for hackers-outgoing; Wed, 31 Jul 1996 09:14:32 -0700 (PDT) Received: from etinc.com (etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA08586 for ; Wed, 31 Jul 1996 09:14:24 -0700 (PDT) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id MAA06897; Wed, 31 Jul 1996 12:18:03 -0400 Date: Wed, 31 Jul 1996 12:18:03 -0400 Message-Id: <199607311618.MAA06897@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Ulf Zimmermann From: dennis@etinc.com (Dennis) Subject: Re: Question about Cisco 2503i price Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >The 2503i is a mission critical version, it directly includes the software, >which disables the serial port. You can later buy the full version ($1200 >list price) to upgrade and use the serial ports. Does that include the (required) memory upgrade? So your talking $3000. for a box with 2 serial ports, an ISDN connection and a '386-speed processor? Eeek! db >Ulf. > >> make shure that includes the grand or so of software. >> >> >> On Tue, 30 Jul 1996, Ulf Zimmermann wrote: >> >> > Hi everyone. >> > >> > I am looking into buying a Cisco 2503i router and have a quote of >> > $1866 with IP feature set. Is this a good price ? >> > >> > Regards, Ulf. >> > >> > --------------------------------------------------------------------- >> > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 >> > Lamb Art Internet Services || http://www.Lamb.net/ >> > >> >> Geoffrey Deasey / / /\ / / / \/ >> Netpath/Stratonet /__ / / \/ /__/ /\ >> 910-226-0425 Forever ! >> >> >> > >--------------------------------------------------------------------- >Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 >Lamb Art Internet Services || http://www.Lamb.net/ > > ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous Communications Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD and LINUX From owner-freebsd-hackers Wed Jul 31 10:21:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA11238 for hackers-outgoing; Wed, 31 Jul 1996 10:21:36 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA11231 for ; Wed, 31 Jul 1996 10:21:35 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA02301; Wed, 31 Jul 1996 10:20:27 -0700 From: Terry Lambert Message-Id: <199607311720.KAA02301@phaeton.artisoft.com> Subject: Re: kernel assertions (Rev. 1) To: michaelv@HeadCandy.com (Michael L. VanLoon -- HeadCandy.com) Date: Wed, 31 Jul 1996 10:20:26 -0700 (MST) Cc: michaelh@cet.co.jp, Hackers@FreeBSD.ORG In-Reply-To: <199607310640.XAA02552@MindBender.HeadCandy.com> from "Michael L. VanLoon -- HeadCandy.com" at Jul 30, 96 11:40:05 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >The REQUIRE2 stuff can replace the > > > >#ifdef DIAGNOSTICS > > if (expr) > > panic(expl); > >#endif > > I prefer asserts to call "Debugger()", rather than "panic()", and > that's how I write my assertion macros. How are you supposed to debug > something if it panics? By having: #ifdef DIAGNOSTICS Debugger(exp1); return; #endif /* DIAGNOSTICS*/ In panic? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jul 31 10:31:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA11638 for hackers-outgoing; Wed, 31 Jul 1996 10:31:28 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA11632; Wed, 31 Jul 1996 10:31:23 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA02343; Wed, 31 Jul 1996 10:29:46 -0700 From: Terry Lambert Message-Id: <199607311729.KAA02343@phaeton.artisoft.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: bde@zeta.org.au (Bruce Evans) Date: Wed, 31 Jul 1996 10:29:45 -0700 (MST) Cc: rnordier@iafrica.com, terry@lambert.org, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <199607310837.SAA12179@godzilla.zeta.org.au> from "Bruce Evans" at Jul 31, 96 06:37:27 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > >All new FS's should expect to work on a "device" that is totally > >committed to the FS and looks like it starts at offset 0, and return > >EINVAL or EFAULT for out of range operations on the device. If > >this were there now, then the MSDOSFS would be incapable of > >corrupting non-MSDOSFS disk areas with the current code. > > It's always been there. Broken code can only write outside the range > by corrupting the device number. The sd and od strategy rotutines do not error out. I am not sure I trust dscheck() entirely (since corruption occurs). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jul 31 11:03:01 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA13970 for hackers-outgoing; Wed, 31 Jul 1996 11:03:01 -0700 (PDT) Received: from cd.iidpwr.com ([204.33.177.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA13965 for ; Wed, 31 Jul 1996 11:02:58 -0700 (PDT) Received: from cd.iidpwr.com (cd.iidpwr.com [204.33.177.3]) by cd.iidpwr.com (8.7.5/8.6.12) with SMTP id LAA03456 for ; Wed, 31 Jul 1996 11:03:30 -0700 (PDT) Message-ID: <31FF9FF1.167EB0E7@cd.iidpwr.com> Date: Wed, 31 Jul 1996 11:03:29 -0700 From: Tony Tam Organization: Imperial Irrigation District X-Mailer: Mozilla 3.0b5aGold (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Real Audio Player Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Did anybody try the Real Audio Player for FreeBSD? I cannot get it to work. All I got is static noise. I have the Sound Blaster (sb), Yamaha OPL-2 and OPL-3 FM (opl) compiled with my kernel. I also have VoxWare 3.0 Beta Driver compiled with my kernel too. I know my Sound Blaster work. Because it works with au and midi files. -- Yours truly, Tony Tam +------------------------------+--------------------------------+ | Tony Tam | Imperial Irrigation District | | Imperial Irrigation District | 333 E. Barioni Blvd. | | email: tam@cd.iidpwr.com | P.O. BOX 937 | | tel: (619) 339 9454 | Imperial, CA 92251 | | fax: (619) 339 9189 | U.S.A. | +------------------------------+--------------------------------+ From owner-freebsd-hackers Wed Jul 31 11:32:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA15357 for hackers-outgoing; Wed, 31 Jul 1996 11:32:27 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA15337; Wed, 31 Jul 1996 11:32:23 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA02458; Wed, 31 Jul 1996 11:29:45 -0700 From: Terry Lambert Message-Id: <199607311829.LAA02458@phaeton.artisoft.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: rnordier@iafrica.com (Robert Nordier) Date: Wed, 31 Jul 1996 11:29:44 -0700 (MST) Cc: jkh@time.cdrom.com, pst@shockwave.com, hackers@freebsd.org, current@freebsd.org In-Reply-To: <199607221808.UAA00225@eac.iafrica.com> from "Robert Nordier" at Jul 22, 96 08:08:11 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The FAT fs primitives are done and tested and I'm currently working > on VFAT support. Before you get too far on that, I have the algorithm it uses to avoid short name name space collisions. It's not pretty, but it works, and I think that was all Microsoft really cared about. Unfortunately, since the struct nameidata is not yet treated as an opaque object in a lot of places, it's not possible to do the lookup in multiple name spaces correctly in the vfs_lookup.c, where it belongs. I'm also not sure about the long name space storage which is in ISO-10646/16 (16 bit Unicode), since it is not possible to pass Unicode across the lookup interface (this will be a problem for any NTFS as well -- Linux is unfortunately way ahead of BSD here). The long names are case sensitive on storage and case insensitive on lookup. I don't know how you could emulate this for a DOS client (for instance) reading for a BSD mounted FS mapped to a DOS drive letter by the emulator. My opinion is that lookup changes are required, including adding a bit priority vector and name space identifier parameter to the VOP_LOOKUP. I can't help with the Unicode stuff given the current state of the BSD VFS; my suggestion is to punt, and treat the high byte as zero in all cases, converting it to ISO-8859-1 (Latin 1). This will damage utility for anyone outside the Latin 1 scope, but that can't be helped without the underlying VFS changes (appologies to non-Latin 1 using countries up front). If you get to where you need to work on name collision, let me know, and I can describe the algorithm in a couple of pages. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jul 31 11:59:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA16582 for hackers-outgoing; Wed, 31 Jul 1996 11:59:45 -0700 (PDT) Received: from novell.com (prv-mail20.IS.Provo.Novell.COM [137.65.40.4]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA16569 for ; Wed, 31 Jul 1996 11:59:43 -0700 (PDT) Received: from INET-PRV-Message_Server by novell.com with Novell_GroupWise; Wed, 31 Jul 1996 12:59:21 -0600 Message-Id: X-Mailer: Novell GroupWise 4.1 Date: Wed, 31 Jul 1996 13:06:59 -0600 From: Darren Davis To: tam@cd.iidpwr.com, hackers@FreeBSD.org Subject: Real Audio Player - Reply Encoding: 29 Text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Yes, I have the Real Audio Player working just fine on my Dell Optiplex XM 5100 with a Sound Blaster Pro card. I am currently running FreeBSD 2.1.5-current and it works fine for me. Darren R. Davis Senior Software Engineer Novell >>> Tony Tam 7/31 12:03pm >>> Did anybody try the Real Audio Player for FreeBSD? I cannot get it to work. All I got is static noise. I have the Sound Blaster (sb), Yamaha OPL-2 and OPL-3 FM (opl) compiled with my kernel. I also have VoxWare 3.0 Beta Driver compiled with my kernel too. I know my Sound Blaster work. Because it works with au and midi files. -- Yours truly, Tony Tam +------------------------------+--------------------------------+ | Tony Tam | Imperial Irrigation District | | Imperial Irrigation District | 333 E. Barioni Blvd. | | email: tam@cd.iidpwr.com | P.O. BOX 937 | | tel: (619) 339 9454 | Imperial, CA 92251 | | fax: (619) 339 9189 | U.S.A. | +------------------------------+--------------------------------+ From owner-freebsd-hackers Wed Jul 31 12:21:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA17843 for hackers-outgoing; Wed, 31 Jul 1996 12:21:26 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA17838; Wed, 31 Jul 1996 12:21:21 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id SAA03982; Wed, 31 Jul 1996 18:24:28 +0200 (MET DST) To: Igor Khasilev cc: freebsd-hackers@freebsd.org Subject: Re: incorect (?) execution of gziped executable In-reply-to: Your message of "Tue, 30 Jul 1996 18:34:14 +0300." <199607301534.SAA11447@jabber.paco.odessa.ua> Date: Wed, 31 Jul 1996 18:24:27 +0200 Message-ID: <3980.838830267@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199607301534.SAA11447@jabber.paco.odessa.ua>, Igor Khasilev writes: >Hi everybody! > >Is it right that code become writeable in gziped executable? > [...] >I become able to write to code? Or i misunderstand something? Consider it a feature :-) It would be easy to change if it mattered... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hackers Wed Jul 31 12:26:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA18386 for hackers-outgoing; Wed, 31 Jul 1996 12:26:26 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA18360 for ; Wed, 31 Jul 1996 12:26:23 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id FAA25171; Thu, 1 Aug 1996 05:21:36 +1000 Date: Thu, 1 Aug 1996 05:21:36 +1000 From: Bruce Evans Message-Id: <199607311921.FAA25171@godzilla.zeta.org.au> To: michaelv@HeadCandy.com, terry@lambert.org Subject: Re: kernel assertions (Rev. 1) Cc: Hackers@FreeBSD.ORG, michaelh@cet.co.jp Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> >The REQUIRE2 stuff can replace the >> > >> >#ifdef DIAGNOSTICS >> > if (expr) >> > panic(expl); >> >#endif >> >> I prefer asserts to call "Debugger()", rather than "panic()", and >> that's how I write my assertion macros. How are you supposed to debug >> something if it panics? >By having: >#ifdef DIAGNOSTICS > Debugger(exp1); > return; >#endif /* DIAGNOSTICS*/ panic() is declared __dead2 (i.e., __attribute__((noreturn))), so this should fail to compile. panic() already calls Debugger(), so it is easy to return by hand (set $eip to the return address, etc.). Bruce From owner-freebsd-hackers Wed Jul 31 12:38:01 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA19564 for hackers-outgoing; Wed, 31 Jul 1996 12:38:01 -0700 (PDT) Received: from axp5.physik.fu-berlin.de (axp5.fddi5B.fu-berlin.de [160.45.5.75]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA19536 for ; Wed, 31 Jul 1996 12:37:53 -0700 (PDT) Received: from mordillo (lislip.physik.fu-berlin.de [160.45.33.82]) by axp5.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id VAA07018 for ; Wed, 31 Jul 1996 21:37:37 +0200 (MET DST) Received: (from graichen@localhost) by mordillo (8.6.12/8.6.12) id VAA01052 for hackers@FreeBSD.org; Wed, 31 Jul 1996 21:30:15 +0200 From: Thomas Graichen Message-Id: <199607311930.VAA01052@mordillo> Subject: tcp/ip over lp0 To: hackers@FreeBSD.org Date: Wed, 31 Jul 1996 21:30:14 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk are there any parameters to play with for getting tcp/ip over the parallel port working - i tried it with two FreeBSD machines - one 2.1.0 and one -current but i only get very few packets through the line - here's what i get from ping -f and netstat: 2874 packets transmitted, 241 packets received, 91% packet loss round-trip min/avg/max = 9.805/11.167/17.566 ms root@mordillo:~> netstat -ain Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ed0 1500 00.00.c0.19.fa.ae 566 0 640 0 0 ed0 1500 10 10.0.0.1 566 0 640 0 0 lp0 1500 1019 1 1165 2490 0 lp0 1500 10 10.0.0.3 1019 1 1165 2490 0 the other side: 4308 packets transmitted, 617 packets received, 85% packet loss round-trip min/avg/max = 11.202/15.700/30.719 ms root@prospero:~> netstat -ain Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ed0 1500 00.80.ad.13.bc.7a 638 0 566 0 0 ed0 1500 10/24 10.0.0.2 638 0 566 0 0 lp0 1500 1165 4 1019 3846 0 lp0 1500 10/24 10.0.0.4 1165 4 1019 3846 0 there do these errors come from ? - is there any timing i may change to get it working or is it the hardware (i had it working between the two machines some time ago - but now some parts of them have changed - and the cable was different) ? - or can it be that the cable is too long (it's really long - about 5 meters or so) ? does anyone have any ideas ? nate ? - thanks in advance t -- thomas graichen graichen@mail.physik.fu-berlin.de graichen@FreeBSD.org perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away antoine de saint-exupery From owner-freebsd-hackers Wed Jul 31 12:42:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA20093 for hackers-outgoing; Wed, 31 Jul 1996 12:42:33 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA20086 for ; Wed, 31 Jul 1996 12:42:24 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id NAA12892; Wed, 31 Jul 1996 13:41:52 -0600 (MDT) Message-Id: <199607311941.NAA12892@rover.village.org> To: "Jordan K. Hubbard" Cc: hackers@freebsd.org Subject: Re: Manpages 9 In-reply-to: Your message of Tue, 30 Jul 1996 23:48:08 PDT Date: Wed, 31 Jul 1996 13:41:52 -0600 From: Warner Losh Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : You're right, that doesn't work at all. Hmmmm. Any suggestions, : anyone? :-) Yes, but aren't use of manacles, spiked chambers and branding irons against the Geneva conventions? Your best bet: Pay a tech writer (or find some sucker to volunteer) to fly to each of the hacker's home towns. Buy them a beer or three (or sushi or whatever their poison is) and get them babbling about the interfaces, possibly in their native language. Record this on tape, and take notes. Then, have that person massage the results into man pages. Take those man pages and pass them back by the original authors, or people that would know for corrections. It is much easier to correct something than it is to write it from scratch (unless it is so wrong that it has to be completely rewritten). Warner From owner-freebsd-hackers Wed Jul 31 13:04:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA21831 for hackers-outgoing; Wed, 31 Jul 1996 13:04:39 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA21824 for ; Wed, 31 Jul 1996 13:04:36 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id NAA05086; Wed, 31 Jul 1996 13:04:18 -0700 (PDT) To: Tony Tam cc: hackers@FreeBSD.org Subject: Re: Real Audio Player In-reply-to: Your message of "Wed, 31 Jul 1996 11:03:29 PDT." <31FF9FF1.167EB0E7@cd.iidpwr.com> Date: Wed, 31 Jul 1996 13:04:18 -0700 Message-ID: <5083.838843458@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Did anybody try the Real Audio Player for FreeBSD? Yep! Works great for me, though I'm using a GUS MAX. Jordan From owner-freebsd-hackers Wed Jul 31 13:46:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA24615 for hackers-outgoing; Wed, 31 Jul 1996 13:46:13 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA24601 for ; Wed, 31 Jul 1996 13:46:09 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.7.5/8.7.3) id QAA00943; Wed, 31 Jul 1996 16:46:02 -0400 (EDT) Date: Wed, 31 Jul 1996 16:46:02 -0400 (EDT) From: Charles Henrich Message-Id: <199607312046.QAA00943@crh.cl.msu.edu> To: jkh@time.cdrom.com, freebsd-hackers@freebsd.org Subject: Re: Real Audio Player Newsgroups: lists.freebsd.hackers References: <4tofvb$iri@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In lists.freebsd.hackers you write: >> Did anybody try the Real Audio Player for FreeBSD? >Yep! Works great for me, though I'm using a GUS MAX. Works fine here on a 2.2-960612-SNAP system with the 2.1 compatability libs.. Now if only Xing would get streamworks ported! Streamworks is only about 15000x better than Real(Bad)Audio :) -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Wed Jul 31 13:50:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA25005 for hackers-outgoing; Wed, 31 Jul 1996 13:50:10 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA24992 for ; Wed, 31 Jul 1996 13:50:05 -0700 (PDT) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id NAA02049; Wed, 31 Jul 1996 13:49:22 -0700 (PDT) Message-Id: <199607312049.NAA02049@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: "Jordan K. Hubbard" cc: Tony Tam , hackers@FreeBSD.ORG Subject: Re: Real Audio Player In-reply-to: Your message of "Wed, 31 Jul 1996 13:04:18 PDT." <5083.838843458@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 31 Jul 1996 13:49:21 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of "Jordan K. Hubbard" : > > Did anybody try the Real Audio Player for FreeBSD? > > Yep! Works great for me, though I'm using a GUS MAX. > > Jordan > I have a GUS PnP and a modified version of the sound driver 3.5 . raplayer seems to work over here;however, upon startup it displays on a pop up window "execlp not found" however I just click okay and the player is able to run. I noticed that the frequency on some occassions changes during playback not sure if this is the recording or the decoder side of real audio player. This happens on 28.8 audio streams. It is a cute audio player 8) Amancio From owner-freebsd-hackers Wed Jul 31 13:56:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA25477 for hackers-outgoing; Wed, 31 Jul 1996 13:56:10 -0700 (PDT) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA25426 for ; Wed, 31 Jul 1996 13:55:42 -0700 (PDT) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id QAA19816; Wed, 31 Jul 1996 16:52:47 -0400 From: Bill Paul Message-Id: <199607312052.QAA19816@skynet.ctr.columbia.edu> Subject: Re: /etc/group To: peter@palin.cc.monash.edu.au (Peter Hawkins) Date: Wed, 31 Jul 1996 16:52:46 -0400 (EDT) Cc: hackers@freebsd.org In-Reply-To: <199607302339.JAA18594@palin.cc.monash.edu.au> from "Peter Hawkins" at Jul 31, 96 09:39:16 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Of all the gin joints in all the towns in all the world, Peter Hawkins had to walk into mine and say: > I understood that you could have multiple lines with the same > GID and group name. > Peter Show me the man page where it says that. Having slogged through the getgrent(3) code a few times, I feel fairly confident in saying that you're mistaken. There's a line limit of 1024 characters and a limit of 200 members per group. Both these limits are hard-coded (though they can be changed by modifying a coupld of #defines). Getgrent(3) has a static array of pointers to char * called 'members' which is only large enough to hold MAXGRP (200) pointers. The grscan() function reads the comma seeparated list of members from /etc/group, replaces the commas with NULs, then sets the pointers in the array to point at the first character of each member name. Each time grscan() reads a new line from /etc/group, it clobbers its input buffer so the old member list from the previous line is destroyed. The member array is also repopulated starting from the top again. There is therefore no way for two consecutive /etc/group entries to be combined (unless you hack the code to support it). Furthermore, if you use NIS/YP, you won't be able to create a second group entry with the same name/gid in the first place since the yp_mkdb(8) utility will reject records with duplicate keys. (NIS does not support the notion of having two entries in a map with the same key. NIS+ does in a twisted fashion, but that's beside the point.) You can't cascade group entries either. Only a user can be a member of a group. A group can not be a member of another group. You can cascade netgroups, but you can't do with netgroups all the things you can do with groups. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "If you're ever in trouble, go to the CTR. Ask for Bill. He will help you." ============================================================================= From owner-freebsd-hackers Wed Jul 31 13:59:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA25760 for hackers-outgoing; Wed, 31 Jul 1996 13:59:04 -0700 (PDT) Received: from mole.mole.org (marmot.mole.org [204.216.57.191]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA25754 for ; Wed, 31 Jul 1996 13:59:00 -0700 (PDT) Received: (from mail@localhost) by mole.mole.org (8.6.12/8.6.12) id UAA01079; Wed, 31 Jul 1996 20:58:56 GMT Received: from meerkat.mole.org(206.197.192.110) by mole.mole.org via smap (V1.3) id sma001076; Wed Jul 31 20:58:45 1996 Received: (from mrm@localhost) by meerkat.mole.org (8.6.11/8.6.9) id NAA07944; Wed, 31 Jul 1996 13:58:45 -0700 Date: Wed, 31 Jul 1996 13:58:45 -0700 From: "M.R.Murphy" Message-Id: <199607312058.NAA07944@meerkat.mole.org> To: graichen@axp5.physik.fu-berlin.de, hackers@FreeBSD.ORG Subject: Re: tcp/ip over lp0 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > there do these errors come from ? - is there any timing i may change to get it > working or is it the hardware (i had it working between the two machines some > time ago - but now some parts of them have changed - and the cable was > different) ? - or can it be that the cable is too long (it's really long - > about 5 meters or so) ? > > does anyone have any ideas ? nate ? - thanks in advance > TCP over parallel port worked fine for me with a 486DX2/66 laptop to a p5/133. Very different speed cpu's in that case, and about 50Kbytes/sec. I think you're on the right track with the cable. Mine was an 8ft commercial molded cable. -- Mike Murphy mrm@Mole.ORG +1 619 598 5874 Better is the enemy of Good From owner-freebsd-hackers Wed Jul 31 14:09:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA28326 for hackers-outgoing; Wed, 31 Jul 1996 14:09:59 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA28297 for ; Wed, 31 Jul 1996 14:09:50 -0700 (PDT) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id OAA02315; Wed, 31 Jul 1996 14:08:53 -0700 (PDT) Message-Id: <199607312108.OAA02315@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: Charles Henrich cc: jkh@time.cdrom.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Real Audio Player In-reply-to: Your message of "Wed, 31 Jul 1996 16:46:02 EDT." <199607312046.QAA00943@crh.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 31 Jul 1996 14:08:53 -0700 From: Amancio Hasty Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of Charles Henrich : > Now if only Xing would get streamworks ported! Streamworks is only about > 15000x better than Real(Bad)Audio :) Oh, Xing's are hard core linux fanatics . Perhaps they have started "porting" their software to *BSD systems;however , back in November when I talked to their president it didn't look good . Basically, I broadcasted a concert and Xing's server was not working so I had a nice long chat with their president who got the Xing server going that nite. Regards, Amancio From owner-freebsd-hackers Wed Jul 31 14:20:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA00871 for hackers-outgoing; Wed, 31 Jul 1996 14:20:56 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA00851 for ; Wed, 31 Jul 1996 14:20:49 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id PAA03869; Wed, 31 Jul 1996 15:20:38 -0600 (MDT) Date: Wed, 31 Jul 1996 15:20:38 -0600 (MDT) Message-Id: <199607312120.PAA03869@rocky.mt.sri.com> From: Nate Williams To: Thomas Graichen Cc: hackers@freebsd.org Subject: Re: tcp/ip over lp0 In-Reply-To: <199607311930.VAA01052@mordillo> References: <199607311930.VAA01052@mordillo> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > are there any parameters to play with for getting tcp/ip over the parallel > port working None that I'm aware of. > 4308 packets transmitted, 617 packets received, 85% packet loss That anything gets through implies that at least the software is setup correctly, so the remaining factor is hardware. > time ago - but now some parts of them have changed - and the cable was > different) ? - or can it be that the cable is too long (it's really long - > about 5 meters or so) ? That's a *really* long cable. Also, *MAKE SURE* that neither machine has another device using it's interrupt, and that there is a driver for all hardware that generate interrupts. If you happen to use the commonly-used IRQ 7 for the parallel port and something other than the parallel port either generates interrupts on 7 or one another unregistered port you'll have lots of problems. Make sure both machines have don't have IRQ conflicts and shorten the cable. Nate From owner-freebsd-hackers Wed Jul 31 16:20:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA12016 for hackers-outgoing; Wed, 31 Jul 1996 16:20:16 -0700 (PDT) Received: from iidpwr.com ([204.33.177.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA12010 for ; Wed, 31 Jul 1996 16:20:13 -0700 (PDT) Received: by mail.iidpwr.com id <15360>; Wed, 31 Jul 1996 16:22:08 -0700 Date: Wed, 31 Jul 1996 16:22:12 -0700 From: Tony Tam Reply-To: ttam@mail.iidpwr.com Organization: Imperial Irrigation District X-Mailer: Mozilla 3.0b5aGold (WinNT; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: [Fwd: Re: Real Audio Player] Content-Type: multipart/mixed; boundary="------------5EF747DE1D15" Message-Id: <96Jul31.162208pdt.15360@mail.iidpwr.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. --------------5EF747DE1D15 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit -- Yours truly, Tony Tam Imperial Irrigation District P.O. BOX 937 Imperial, CA 92251 USA Tel: 619-339-9454 FAX: 619-339-9189 E-Mail: ttam@iidpwr.com --------------5EF747DE1D15 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-ID: <31FFE626.5C40@iidpwr.com> Date: Wed, 31 Jul 1996 16:03:02 -0700 From: Tony Tam Reply-To: ttam@iidpwr.com Organization: Imperial Irrigation District X-Mailer: Mozilla 3.0b5aGold (WinNT; I) MIME-Version: 1.0 To: "Jordan K. Hubbard" Subject: Re: Real Audio Player References: <5083.838843458@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jordan K. Hubbard wrote: > > > Did anybody try the Real Audio Player for FreeBSD? > > Yep! Works great for me, though I'm using a GUS MAX. Yep! I got it working too, after I compiled my kernel with sbxvi (sound blaster 16 dsp) and sbmidi (sound blaster 16 midi) drivers. Thank You. By the way, could you tell me what is the difference between sb, sbxvi, and sbmidi drivers. I just upgraded my FreeBSD 2.1.0-RELEASE to 2.1.5-RELEASE. It seems Netscape 3.0 is running faster now. Any significant change I should know? One thing I would like to have is a hard-disk-adding utility. The utility would let the users to partition, label, and make file system for any hard disks. The sysinstall is closed; however, it only let the users work on the bootable disk. -- Yours truly, Tony Tam Imperial Irrigation District P.O. BOX 937 Imperial, CA 92251 USA Tel: 619-339-9454 FAX: 619-339-9189 E-Mail: ttam@iidpwr.com --------------5EF747DE1D15-- From owner-freebsd-hackers Wed Jul 31 16:28:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA12627 for hackers-outgoing; Wed, 31 Jul 1996 16:28:09 -0700 (PDT) Received: from eac.iafrica.com (196-7-192-148.iafrica.com [196.7.192.148]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA12610 for ; Wed, 31 Jul 1996 16:28:03 -0700 (PDT) Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id BAA00549; Thu, 1 Aug 1996 01:25:59 +0200 From: Robert Nordier Message-Id: <199607312325.BAA00549@eac.iafrica.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: terry@lambert.org (Terry Lambert) Date: Thu, 1 Aug 1996 01:25:57 -2200 (SAT) Cc: hackers@freebsd.org In-Reply-To: <199607311829.LAA02458@phaeton.artisoft.com> from "Terry Lambert" at Jul 31, 96 11:29:44 am X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: [...] (Still digesting other comments. :) > I can't help with the Unicode stuff given the current state of the BSD > VFS; my suggestion is to punt, and treat the high byte as zero in all > cases, converting it to ISO-8859-1 (Latin 1). This will damage utility > for anyone outside the Latin 1 scope, but that can't be helped without > the underlying VFS changes (appologies to non-Latin 1 using countries > up front). Agreed. For completeness, any thoughts on how to handle the following? Directory containing 3 single-character DOS filenames 0xc3..0xc5: SFN LFN c3 251c c4 2500 c5 253c AFAIK, DOS filenames containing characters >= 0x80 have never been much used, or had much practical value. So extensive special provision for them almost seems misplaced. -- Robert Nordier From owner-freebsd-hackers Wed Jul 31 17:13:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA15715 for hackers-outgoing; Wed, 31 Jul 1996 17:13:17 -0700 (PDT) Received: from scooter.quickweb.com (scooter.quickweb.com [199.212.134.8]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA15705 for ; Wed, 31 Jul 1996 17:13:08 -0700 (PDT) Received: from localhost (mark@localhost) by scooter.quickweb.com (8.6.12/8.6.12) with SMTP id UAA02982 for ; Wed, 31 Jul 1996 20:18:29 -0400 Date: Wed, 31 Jul 1996 20:18:28 -0400 (EDT) From: Mark Mayo To: freebsd-hackers@freebsd.org Subject: Routing Problems (link#2 ??) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a problem... I'm on a network with a netmask of 255.255.255.240, and my machine is 199.212.134.8 - so it's in the 'base' logical network. Any machine on the same logical net as me (.8-.15) can get to me fine (arp takes care of it..), the weird thing is that the portmaster dial-in servers can't get to me (they're on a different subnet, but the same physical net). The thing that puzzles me are the result from netstat -nr: default 199.212.134.5 UGc 12 46314 ep0 127 127.0.0.1 URc 0 0 lo0 127.0.0.1 127.0.0.1 UH 6 1025 lo0 199.212.134 link#2 UC 0 0 199.212.134 link#2 UC 0 0 199.212.134.1 0:0:c0:eb:9b:8e UHLW 3 7912 ep0 284 199.212.134.3 0:0:a2:6:90:e8 UHLS 0 18 ep0 199.212.134.4 0:0:c0:0:2e:87 UHLW 3 25728 ep0 678 199.212.134.5 0:0:93:b8:34:98 UHLW 11 232 ep0 1178 199.212.134.6 0:c0:5:1:4a:4b UHLW 0 0 ep0 1112 199.212.134.8 0:20:af:15:38:df UHLW 3 133118 lo0 199.212.134.10 0:c0:5:1:3a:46 UHLW 0 4 ep0 686 199.212.134.11 0:c0:5:1:19:ed UHLW 0 3 ep0 887 199.212.134.12 0:c0:5:1:1d:44 UHLW 0 2 ep0 1157 199.212.134.13 0:c0:5:1:28:3c UHLW 0 2 ep0 1159 199.212.134.14 0:40:ff:0:2a:8 UHLW 0 2 ep0 1194 199.212.134.15 link#2 UHLW 1 11842 199.212.134.80 199.212.134.4 UGc 1 71278 ep0 206.248.60 link#2 UC 0 0 206.248.60.11 0:0:c0:eb:9b:8e UHLW 0 0 ep0 594 206.248.60.80 0:20:af:15:38:df UHLW 0 12 lo0 206.248.60.81 0:20:af:15:38:df UHLW 0 14 lo0 224 link#2 UCS 0 0 What the hell are the link#2's????????????? Why are the 'network' addresses (the .15's) going to link#2, as well as 199.212.134 (the entire class C) going through there.. I can't seem to get rid of them... I can kill gated, route flush, and when gated fires up again, they appear... Rather annoying. In case it's useful, here are the results of netstat -an and netstat -in: mark:{58}/home/mark % netstat -in Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll lp0* 1500 0 0 0 0 0 ep0 1500 00.20.af.15.38.df 7651375 37 2570921 81 0 ep0 1500 199.212.134 199.212.134.8 7651375 37 2570921 81 0 ep0 1500 199.212.134 199.212.134.81 7651375 37 2570921 81 0 ep0 1500 199.212.134 199.212.134.87 7651375 37 2570921 81 0 ep0 1500 199.212.134 199.212.134.88 7651375 37 2570921 81 0 ep0 1500 199.212.134 199.212.134.90 7651375 37 2570921 81 0 ep0 1500 199.212.134 199.212.134.91 7651375 37 2570921 81 0 ep0 1500 199.212.134 199.212.134.84 7651375 37 2570921 81 0 ep0 1500 206.248.60 206.248.60.81 7651375 37 2570921 81 0 ep0 1500 206.248.60 206.248.60.82 7651375 37 2570921 81 0 ep0 1500 206.248.60 206.248.60.83 7651375 37 2570921 81 0 ep0 1500 206.248.60 206.248.60.84 7651375 37 2570921 81 0 ep0 1500 206.248.60 206.248.60.85 7651375 37 2570921 81 0 ep0 1500 206.248.60 206.248.60.86 7651375 37 2570921 81 0 ep0 1500 206.248.60 206.248.60.87 7651375 37 2570921 81 0 ep0 1500 206.248.60 206.248.60.88 7651375 37 2570921 81 0 ep0 1500 206.248.60 206.248.60.89 7651375 37 2570921 81 0 lo0 16384 138300 0 138300 0 0 lo0 16384 127 127.0.0.1 138300 0 138300 0 0 forget the netstat -a.... too much crap.. Here's a ripquery though: scooter# ripquery -r scooter 44 bytes from scooter.quickweb.com(199.212.134.8) to 199.212.134.8 version 2: 199.212.134.80/255.255.255.240 router 199.212.134.4 metric 1 tag 0000 0.0.0.0/0.0.0.0 router 199.212.134.5 metric 1 tag 0000 So I'm not broadcasting anything that would cause hell to break loose.. The other odd thing is that traffic coming in from the internet through 199.212.134.5 (a proteon router on a T1) has no problems getting to the box - it's just things that are (here goes) on the same physical network but on a different logical net..... I'm mostly curious about the link#2 thing, if I could get rid of that, I think I can boss around the routing tables enough to convince it where the class C should be routed through :-) TIA, -mark ------------------------------------------- | Mark Mayo mark@quickweb.com | | C-Soft www.quickweb.com | ------------------------------------------- "To iterate is human, to recurse divine." - L. Peter Deutsch From owner-freebsd-hackers Wed Jul 31 17:35:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA16878 for hackers-outgoing; Wed, 31 Jul 1996 17:35:04 -0700 (PDT) Received: from bessel.nando.net (praj@bessel.nando.net [152.52.2.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA16871 for ; Wed, 31 Jul 1996 17:35:02 -0700 (PDT) Received: (from praj@localhost) by bessel.nando.net (8.7.1/8.6.9) id UAA23054 for freebsd-hackers@freebsd.org; Wed, 31 Jul 1996 20:34:39 -0400 (EDT) From: praj Message-Id: <199608010034.UAA23054@bessel.nando.net> Subject: Upgrade from 2.1.0. to 2.1.5? To: freebsd-hackers@freebsd.org Date: Wed, 31 Jul 1996 20:34:39 +2000 (EDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey, If i build the 2.1.5 kernel from the 2.1.5 sources and use it to boot my 2.1.0 system, am i upgraded to 2.1.5 or is there some other things that i shoudl do? Or is 2.1.5 so radically different from 2.1.0 that i am better off installing the whole thing ? -Raj (praj@nando.net) From owner-freebsd-hackers Wed Jul 31 17:45:47 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA17178 for hackers-outgoing; Wed, 31 Jul 1996 17:45:47 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA17173 for ; Wed, 31 Jul 1996 17:45:43 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA03051; Wed, 31 Jul 1996 17:44:09 -0700 From: Terry Lambert Message-Id: <199608010044.RAA03051@phaeton.artisoft.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: rnordier@iafrica.com (Robert Nordier) Date: Wed, 31 Jul 1996 17:44:08 +1700 (MST) Cc: terry@lambert.org, hackers@freebsd.org In-Reply-To: <199607312325.BAA00549@eac.iafrica.com> from "Robert Nordier" at Aug 1, 96 01:25:57 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > For completeness, any thoughts on how to handle the following? > > Directory containing 3 single-character DOS filenames 0xc3..0xc5: > > SFN LFN > c3 251c > c4 2500 > c5 253c > > AFAIK, DOS filenames containing characters >= 0x80 have never been > much used, or had much practical value. So extensive special > provision for them almost seems misplaced. IBM Code page 819(?) is ISO 8859-1. I think you are allowed to have high bit characters in long file names (I will check this at next opportunity). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jul 31 17:53:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA17404 for hackers-outgoing; Wed, 31 Jul 1996 17:53:39 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA17399 for ; Wed, 31 Jul 1996 17:53:37 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA03097; Wed, 31 Jul 1996 17:51:58 -0700 From: Terry Lambert Message-Id: <199608010051.RAA03097@phaeton.artisoft.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: terry@phaeton.artisoft.com (Terry Lambert) Date: Wed, 31 Jul 1996 17:51:58 +1700 (MST) Cc: rnordier@iafrica.com, terry@lambert.org, hackers@freebsd.org In-Reply-To: <199608010044.RAA03051@phaeton.artisoft.com> from "Terry Lambert" at Jul 31, 96 05:44:08 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > For completeness, any thoughts on how to handle the following? > > > > Directory containing 3 single-character DOS filenames 0xc3..0xc5: > > > > SFN LFN > > c3 251c > > c4 2500 > > c5 253c > > > > AFAIK, DOS filenames containing characters >= 0x80 have never been > > much used, or had much practical value. So extensive special > > provision for them almost seems misplaced. > > IBM Code page 819(?) is ISO 8859-1. > > I think you are allowed to have high bit characters in long file names > (I will check this at next opportunity). Bad news: SFN LFN ASOLUTE asolute On Win95 ( is Greek Beta). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Wed Jul 31 20:06:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA22839 for hackers-outgoing; Wed, 31 Jul 1996 20:06:39 -0700 (PDT) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA22834 for ; Wed, 31 Jul 1996 20:06:35 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.7.5/8.7.3) with SMTP id XAA05782; Wed, 31 Jul 1996 23:06:17 -0400 (EDT) Message-Id: <199608010306.XAA05782@whizzo.transsys.com> X-Authentication-Warning: whizzo.transsys.com: Host localhost.transsys.com [127.0.0.1] didn't use HELO protocol To: dennis@etinc.com (Dennis) cc: hackers@freebsd.org From: "Louis A. Mamakos" Subject: Re: Question about Cisco 2503i price References: <199607311618.MAA06897@etinc.com> In-reply-to: Your message of "Wed, 31 Jul 1996 12:18:03 EDT." <199607311618.MAA06897@etinc.com> Date: Wed, 31 Jul 1996 23:06:16 -0400 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >The 2503i is a mission critical version, it directly includes the software, > >which disables the serial port. You can later buy the full version ($1200 > >list price) to upgrade and use the serial ports. > > Does that include the (required) memory upgrade? > > So your talking $3000. for a box with 2 serial ports, an ISDN connection > and a '386-speed processor? Eeek! Two T1 ports, ISDN, support for T1 PPP, Cisco HDLC, Frame Relay and SMDS. Packet filtering. OSPF, RIP, RIP-2, EIGRP, BGP routing protocols (if you need them). Look at the 2524 which has provisions for integral 56K DDS or T1 CSU/DSUs to further reduce the system cost. Plus, you can plug it in and it works. No interrupt vectors, dma channels to fool with. Small package. Only a fan for moving parts, and no fsck. Not everyone is willing to spend a lot of time integrating a box when you can essentially buy an appliance off the shelf which does a better job. Are we going to start this whole discussion again? louie From owner-freebsd-hackers Wed Jul 31 20:48:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA24705 for hackers-outgoing; Wed, 31 Jul 1996 20:48:05 -0700 (PDT) Received: from trapdoor.dstc.edu.au (root@trapdoor.dstc.edu.au [130.102.176.12]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA24675 for ; Wed, 31 Jul 1996 20:47:53 -0700 (PDT) Received: from foxtail.dstc.edu.au (foxtail.dstc.edu.au [130.102.176.14]) by trapdoor.dstc.edu.au (8.6.9/8.6.12) with ESMTP id NAA27587; Thu, 1 Aug 1996 13:47:35 +1000 Received: (from leonard@localhost) by foxtail.dstc.edu.au (8.6.10/8.6.10) id NAA13864; Thu, 1 Aug 1996 13:47:35 +1000 From: David Leonard Message-Id: <199608010347.NAA13864@foxtail.dstc.edu.au> Subject: Re: kernel assertions (Rev. 1) To: michaelh@cet.co.jp Date: Thu, 1 Aug 1996 13:47:35 +1000 (EST) Cc: hackers@freebsd.org Reply-To: leonard@dstc.edu.au X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > void > bremfree(struct buf * bp) > { > int s = splbio(); > REQUIRE2(bp, "Expected bp to point to something") > REQUIRE1(bp->b_qindex != QUEUE_NONE, "Expected a buffer on a > queue"); > TAILQ_REMOVE(&bufqueues[bp->b_qindex], bp, b_freelist); > bp->b_qindex = QUEUE_NONE; > ENSURE2(bp->b_qindex == QUEUE_NONE, "Buffer should no longer be on > a queue"); > splx(s); > } This might be a little arcane, but as you haven't yet talked about what actual message is emitted, how about going the extra step in readable macros? something a little like this, maybe: REQUIRE("that bp points to something", bp != NULL); mod/file.c:123: require that bp points to something and ENSURE( "that the buffer is no longer queued", bp->b_qindex == QUEUE_NONE ); mod/file.c.124: Failed to ensure that the buffer is no longer queued I really like the idea of names such as REQUIRE/ENSURE over ASSERT, but i hesitate at the numbers. But... one could get used to it I suppose. (sounds like a microsoft attitude) Looking at it again, I think it would raise the readability (and hence learnability/searchability(?)) of the FreeBSD source tree no end! In some ways, having to express the predicate that you are trying to ENSURE() essentially documents your code better! Unless, of course you ENSURE( "bp!=NULL", bp!=NULL ); which I would like to see avoided :) Other problems I can think of are: - side effects of the conditionals - conditions that take longer than constant time to be evaluated So, sure you can whip up some simple-looking examples of ENSURE/REQUIRE, but what about when you end up with something like this: ENSURE( "nothing in the queue has an invalid buffer", ({ thing* x; for(x=queue->head;x;x=x->next) if ( !valid_buffer(x->buffer) ) return 0; return 1; }) ); first, valid_buffer() may have side effects which will alter operation if these (expensive) checks are compiled out ,and second, being a linear time check, an interrupt or something may happen in the middle which might affect the data structures being examined. the long-time problem can be handled with ENSURE2, ENSURE3 and so on, but does anyone have a nice way of handling the side-effect problem? d -- David Leonard Project Officer, DSTC The University of Queensland david.leonard@dstc.edu.au http://www.dstc.edu.au/~leonard/ From owner-freebsd-hackers Wed Jul 31 21:29:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA26350 for hackers-outgoing; Wed, 31 Jul 1996 21:29:48 -0700 (PDT) Received: from scooter.quickweb.com (scooter.quickweb.com [199.212.134.8]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA26345 for ; Wed, 31 Jul 1996 21:29:41 -0700 (PDT) Received: from localhost (mark@localhost) by scooter.quickweb.com (8.6.12/8.6.12) with SMTP id AAA03310 for ; Thu, 1 Aug 1996 00:35:11 -0400 Date: Thu, 1 Aug 1996 00:35:11 -0400 (EDT) From: Mark Mayo To: freebsd-hackers@freebsd.org Subject: Migrating BSDI 1.1 Passwords Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, I have a BSDI 1.1 server with about 3000 users... I REALLY want to move it to FreeBSD (2.1.5), but I'm concerned about the password files. I know FreeBSD ships with MD5, and I'm in Canada so that means I can safely use DES crypt routines - but does that mean I can use password files that are DES encrypted?? (i.e. BSDI 1.1) Has anyone moved BSDI password files to a FreeBSD system? If so, I'd love to hear about your success (hopefully not failure). TIA for any help, -Mark ------------------------------------------- | Mark Mayo mark@quickweb.com | | C-Soft www.quickweb.com | ------------------------------------------- "To iterate is human, to recurse divine." - L. Peter Deutsch From owner-freebsd-hackers Wed Jul 31 21:45:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA27191 for hackers-outgoing; Wed, 31 Jul 1996 21:45:38 -0700 (PDT) Received: from bunyip.cc.uq.oz.au (daemon@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA27174 for ; Wed, 31 Jul 1996 21:45:09 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.oz.au (8.7.5/8.7.3) id OAA02706 for freebsd-hackers@freefall.cdrom.com; Thu, 1 Aug 1996 14:44:56 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id OAA26659 for ; Thu, 1 Aug 1996 14:28:39 +1000 Received: by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id EAA19644; Thu, 1 Aug 1996 04:29:58 GMT Date: Thu, 1 Aug 1996 04:29:58 GMT Message-Id: <199608010429.EAA19644@netfl15a.devetir.qld.gov.au> MIME-Version: 1.0 X-Newsreader: knews 0.9.7 References: In-Reply-To: From: sysseh@devetir.qld.gov.au (Stephen Hocking) Subject: Re: Real Audio Player X-Original-Newsgroups: local.freebsd.hackers To: freebsd-hackers@freefall.FreeBSD.org Content-Type: text/plain; charset=us-ascii Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk And where does one get the RealAudio -player from? Stephen -- The views expressed above are not those of the Worker's Compensation Board of Queensland, Australia. From owner-freebsd-hackers Wed Jul 31 21:59:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA27775 for hackers-outgoing; Wed, 31 Jul 1996 21:59:40 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA27768 for ; Wed, 31 Jul 1996 21:59:37 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id EAA20168; Thu, 1 Aug 1996 04:59:05 GMT Date: Thu, 1 Aug 1996 13:59:05 +0900 (JST) From: Michael Hancock To: David Leonard cc: hackers@freebsd.org Subject: Re: kernel assertions (Rev. 1) In-Reply-To: <199608010347.NAA13864@foxtail.dstc.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, David Leonard wrote: > This might be a little arcane, but as you haven't yet talked about what > actual message is emitted, how about going the extra step in > readable macros? something a little like this, maybe: > > REQUIRE("that bp points to something", bp != NULL); > > mod/file.c:123: require that bp points to something > > and > ENSURE( "that the buffer is no longer queued", > bp->b_qindex == QUEUE_NONE ); > > mod/file.c.124: Failed to ensure that the buffer is no longer queued This is nice. > I really like the idea of names such as REQUIRE/ENSURE over ASSERT, but > i hesitate at the numbers. > But... one could get used to it I suppose. (sounds like a microsoft attitude) I don't like the numbers either, but performance matters to a lot of people. Especially, the kernel. I think for practical purposes 3 levels: No assertions Important assertions Important assertions + Specification assertions are minimally required. We want important assertions in production binary, however having complete specifications in the production binary is too much. I'm sure many have experienced the pitfalls. > Looking at it again, I think it would raise the readability (and hence > learnability/searchability(?)) of the FreeBSD source tree no end! In some ways, > having to express the predicate that you are trying to ENSURE() essentially > documents your code better! Unless, of course you > > ENSURE( "bp!=NULL", bp!=NULL ); > > which I would like to see avoided :) > > The problems below just have to be special cased as they are now. #ifdef DIAGNOSTICS Do a bunch of stuff including writing helper functions or whatever is necessary. #endif You just have to draw a line somewhere. The assertions should just be used for the obvious. The obvious is what our minds often filter out when looking over the same code for a long period of time. Regards, Mike Hancock > Other problems I can think of are: > > - side effects of the conditionals > - conditions that take longer than constant time to be evaluated > > So, sure you can whip up some simple-looking examples of ENSURE/REQUIRE, but > what about when you end up with something like this: > > ENSURE( "nothing in the queue has an invalid buffer", > ({ > thing* x; > for(x=queue->head;x;x=x->next) > if ( !valid_buffer(x->buffer) ) return 0; > return 1; > }) ); > > first, valid_buffer() may have side effects which will alter operation > if these (expensive) checks are compiled out ,and second, being a linear > time check, an interrupt or something may happen in the middle which might > affect the data structures being examined. > > the long-time problem can be handled with ENSURE2, ENSURE3 and so on, but > does anyone have a nice way of handling the side-effect problem? > > d > -- > David Leonard Project Officer, DSTC > The University of Queensland david.leonard@dstc.edu.au > http://www.dstc.edu.au/~leonard/ > From owner-freebsd-hackers Wed Jul 31 22:37:21 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA29145 for hackers-outgoing; Wed, 31 Jul 1996 22:37:21 -0700 (PDT) Received: from iidpwr.com ([204.33.177.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA29139 for ; Wed, 31 Jul 1996 22:37:19 -0700 (PDT) Received: by mail.iidpwr.com id <15360>; Wed, 31 Jul 1996 22:39:14 -0700 Date: Wed, 31 Jul 1996 22:41:53 -0700 From: Tony Tam Organization: Imperial Irrigation District X-Mailer: Mozilla 3.0b5aGold (X11; I; FreeBSD 2.1.5-RELEASE i386) MIME-Version: 1.0 To: Stephen Hocking CC: freebsd-hackers@freefall.freebsd.org Subject: Re: Real Audio Player References: <199608010429.EAA19644@netfl15a.devetir.qld.gov.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <96Jul31.223914pdt.15360@mail.iidpwr.com> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Stephen Hocking wrote: > > And where does one get the RealAudio -player from? > You can get it from http://www.realaudio.com. -- Yours truly, Tony Tam Imperial Irrigation District P.O. BOX 937 Imperial, CA 92251 USA Tel: 619-339-9454 FAX: 619-339-9189 E-Mail: ttam@iidpwr.com From owner-freebsd-hackers Wed Jul 31 22:58:57 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA29975 for hackers-outgoing; Wed, 31 Jul 1996 22:58:57 -0700 (PDT) Received: from zeus.xtalwind.net (slipper3b.xtalwind.net [205.160.242.56]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA29967 for ; Wed, 31 Jul 1996 22:58:52 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by zeus.xtalwind.net (8.7.5/8.7.3) with SMTP id BAA02717; Thu, 1 Aug 1996 01:59:42 -0400 (EDT) Date: Thu, 1 Aug 1996 01:59:42 -0400 (EDT) From: jack X-Sender: jack@localhost To: Mark Mayo cc: freebsd-hackers@freebsd.org Subject: Re: Migrating BSDI 1.1 Passwords In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, Mark Mayo wrote: > Hi all, I have a BSDI 1.1 server with about 3000 users... I REALLY want to > move it to FreeBSD (2.1.5), but I'm concerned about the password files. > > I know FreeBSD ships with MD5, and I'm in Canada so that means I can > safely use DES crypt routines - but does that mean I can use password > files that are DES encrypted?? (i.e. BSDI 1.1) > > Has anyone moved BSDI password files to a FreeBSD system? If so, I'd love > to hear about your success (hopefully not failure). Considering a possible similar move in the future, I copied a ~700 user BSDI 2.0 set to FreeBSD 2.15 and all 8 of the accounts (including root :-}) that I tried worked. Only minor problems was a complaint about some missing paths. -------------------------------------------------------------------------- Jack O'Neill Finger jacko@onyx.xtalwind.net or jack@xtalwind.net http://www.xtalwind.net/~jacko/pubpgp.html #include for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD -------------------------------------------------------------------------- From owner-freebsd-hackers Wed Jul 31 23:07:07 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA00382 for hackers-outgoing; Wed, 31 Jul 1996 23:07:07 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA00377 for ; Wed, 31 Jul 1996 23:07:04 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id GAA20593; Thu, 1 Aug 1996 06:06:39 GMT Date: Thu, 1 Aug 1996 15:06:39 +0900 (JST) From: Michael Hancock To: David Leonard cc: hackers@freebsd.org Subject: Re: kernel assertions (Rev. 1) In-Reply-To: <199608010347.NAA13864@foxtail.dstc.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, David Leonard wrote: > Looking at it again, I think it would raise the readability (and hence > learnability/searchability(?)) of the FreeBSD source tree no end! In some ways, You can write a utility that searches all the files in the source tree and prints out a specification for you like the following ... void bremfree(struct buf * bp) REQUIRE("that bp points to something", bp != NULL); ENSURE( "that the buffer is no longer queued", bp->b_qindex == QUEUE_NONE ); ... How's that for documentation? Regards, Mike Hancock From owner-freebsd-hackers Thu Aug 1 00:19:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA02190 for hackers-outgoing; Thu, 1 Aug 1996 00:19:56 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA02185 for ; Thu, 1 Aug 1996 00:19:52 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id KAA14636; Thu, 1 Aug 1996 10:22:46 +0300 Date: Thu, 1 Aug 1996 10:22:45 +0300 (EET DST) From: Narvi To: Terry Lambert cc: Robert Nordier , terry@lambert.org, hackers@freebsd.org Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? In-Reply-To: <199608010044.RAA03051@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 31 Jul 1996, Terry Lambert wrote: > > For completeness, any thoughts on how to handle the following? > > > > Directory containing 3 single-character DOS filenames 0xc3..0xc5: > > > > SFN LFN > > c3 251c > > c4 2500 > > c5 253c > > > > AFAIK, DOS filenames containing characters >= 0x80 have never been > > much used, or had much practical value. So extensive special > > provision for them almost seems misplaced. Actually they have at least around here. People just like to have filenames with all those a", o", u" and even o~ (although that is one which indeed does make troubles). Nothing ever happened except that nczip refuses to pack them up. > > IBM Code page 819(?) is ISO 8859-1. > > I think you are allowed to have high bit characters in long file names > (I will check this at next opportunity). > You can at least have them there. Sander > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > From owner-freebsd-hackers Thu Aug 1 02:20:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA05926 for hackers-outgoing; Thu, 1 Aug 1996 02:20:04 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA05884 for ; Thu, 1 Aug 1996 02:19:56 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id KAA08745; Thu, 1 Aug 1996 10:22:13 +0100 (BST) Date: Thu, 1 Aug 1996 10:22:13 +0100 (BST) From: Developer To: Mark Mayo cc: freebsd-hackers@FreeBSD.org Subject: Re: Migrating BSDI 1.1 Passwords In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, Mark Mayo wrote: > Hi all, I have a BSDI 1.1 server with about 3000 users... I REALLY want to > move it to FreeBSD (2.1.5), but I'm concerned about the password files. > > I know FreeBSD ships with MD5, and I'm in Canada so that means I can > safely use DES crypt routines - but does that mean I can use password > files that are DES encrypted?? (i.e. BSDI 1.1) Well, correct me if I`m wrong but don`t you just have to copy libdescrypt* to libcrypt* and then freebsd uses des as the standard encryption method? As for exporting cryptography I think the whole thing is very silly - If I want des I`ll download it from the states (To the UK) :P~~~ Regards, Trefor S. From owner-freebsd-hackers Thu Aug 1 03:25:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA08868 for hackers-outgoing; Thu, 1 Aug 1996 03:25:19 -0700 (PDT) Received: from cyclone.degnet.baynet.de (cyclone.degnet.baynet.de [194.95.214.129]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA08863 for ; Thu, 1 Aug 1996 03:25:06 -0700 (PDT) Received: from neuron.bsd.uni-passau.de (ppp2 [194.95.214.132]) by cyclone.degnet.baynet.de (8.6.12/8.6.9) with SMTP id MAA04804; Thu, 1 Aug 1996 12:24:01 +0200 Message-ID: <3200A071.173E@degnet.baynet.de> Date: Thu, 01 Aug 1996 12:17:53 +0000 From: Darius Moos Reply-To: moos@degnet.baynet.de X-Mailer: Mozilla 3.0b5aGold (Win95; I) MIME-Version: 1.0 To: Mark Mayo CC: freebsd-hackers Subject: Re: Routing Problems (link#2 ??) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Hi Mark, a few weeks ago i had a similar problem and solved it by using another net for the dialin-lines. In your special case this means: Try using a 10.1.1.0 net for the dialin-ports asigning the incalling peers an IP of this pool on ppp-startup (or slip; don't know what you are using). Worked for me. Hope this helps. Bye, Darius. Mark Mayo wrote: > > I have a problem... I'm on a network with a netmask of 255.255.255.240, > and my machine is 199.212.134.8 - so it's in the 'base' logical network. > Any machine on the same logical net as me (.8-.15) can get to me fine > (arp takes care of it..), the weird thing is that the portmaster dial-in > servers can't get to me (they're on a different subnet, but the same > physical net). > > The thing that puzzles me are the result from netstat -nr: > > default 199.212.134.5 UGc 12 46314 ep0 > 127 127.0.0.1 URc 0 0 lo0 > 127.0.0.1 127.0.0.1 UH 6 1025 lo0 > 199.212.134 link#2 UC 0 0 > 199.212.134 link#2 UC 0 0 From owner-freebsd-hackers Thu Aug 1 04:23:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA10579 for hackers-outgoing; Thu, 1 Aug 1996 04:23:49 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA10573 for ; Thu, 1 Aug 1996 04:23:44 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id OAA15955; Thu, 1 Aug 1996 14:27:44 +0300 Date: Thu, 1 Aug 1996 14:27:44 +0300 (EET DST) From: Narvi To: Developer cc: Mark Mayo , freebsd-hackers@FreeBSD.org Subject: Re: Migrating BSDI 1.1 Passwords In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, Developer wrote: > > > On Thu, 1 Aug 1996, Mark Mayo wrote: > > > Hi all, I have a BSDI 1.1 server with about 3000 users... I REALLY want to > > move it to FreeBSD (2.1.5), but I'm concerned about the password files. > > > > I know FreeBSD ships with MD5, and I'm in Canada so that means I can > > safely use DES crypt routines - but does that mean I can use password > > files that are DES encrypted?? (i.e. BSDI 1.1) > > Well, correct me if I`m wrong but don`t you just have to copy libdescrypt* > to libcrypt* and then freebsd uses des as the standard encryption method? > > As for exporting cryptography I think the whole thing is very silly - If I > want des I`ll download it from the states (To the UK) :P~~~ Why not just download it from the UK and let the paranoid US customs and crypto people be comforted. Sander > > Regards, > > Trefor S. > > > From owner-freebsd-hackers Thu Aug 1 05:33:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA13152 for hackers-outgoing; Thu, 1 Aug 1996 05:33:11 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA13146 for ; Thu, 1 Aug 1996 05:33:08 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id NAA10900; Thu, 1 Aug 1996 13:34:05 +0100 (BST) Date: Thu, 1 Aug 1996 13:34:04 +0100 (BST) From: Developer To: Narvi cc: Mark Mayo , freebsd-hackers@FreeBSD.org Subject: Re: Migrating BSDI 1.1 Passwords In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, Narvi wrote: > > As for exporting cryptography I think the whole thing is very silly - If I > > want des I`ll download it from the states (To the UK) :P~~~ > > Why not just download it from the UK and let the paranoid US customs and > crypto people be comforted. Well, I would do, but I do a sup from sup.Freebsd.org :) Regards, Trefor S. From owner-freebsd-hackers Thu Aug 1 06:01:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA14229 for hackers-outgoing; Thu, 1 Aug 1996 06:01:58 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA14224 for ; Thu, 1 Aug 1996 06:01:56 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id GAA10155; Thu, 1 Aug 1996 06:00:30 -0700 (PDT) To: Developer cc: Narvi , Mark Mayo , freebsd-hackers@FreeBSD.org Subject: Re: Migrating BSDI 1.1 Passwords In-reply-to: Your message of "Thu, 01 Aug 1996 13:34:04 BST." Date: Thu, 01 Aug 1996 06:00:30 -0700 Message-ID: <10153.838904430@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Well, I would do, but I do a sup from sup.Freebsd.org :) Not the secure bits, obviously? Jordan From owner-freebsd-hackers Thu Aug 1 08:01:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA18933 for hackers-outgoing; Thu, 1 Aug 1996 08:01:14 -0700 (PDT) Received: from aries.isf.rl.af.mil (ARIES.ISF.RL.AF.MIL [128.132.64.38]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA18893; Thu, 1 Aug 1996 08:00:57 -0700 (PDT) Received: (from green@localhost) by aries.isf.rl.af.mil (8.7.5/8.7.3) id LAA03816; Thu, 1 Aug 1996 11:00:21 -0400 (EDT) Date: Thu, 1 Aug 1996 11:00:21 -0400 (EDT) From: Charles Kenneth Green - PRC Message-Id: <199608011500.LAA03816@aries.isf.rl.af.mil> X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: hackers@freebsd.org, questions@freebsd.org Subject: FreeBSD and Mach 64 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has there been a fix for the sio.c bug that fouls up Mach 64 cards. I have a FreeBSD 2.1 system that I had to replace the video card in. The card I ended up getting uses a Mach 64 chip and I'd prefer not to have to send it back. From owner-freebsd-hackers Thu Aug 1 08:22:52 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA20097 for hackers-outgoing; Thu, 1 Aug 1996 08:22:52 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA20080 for ; Thu, 1 Aug 1996 08:22:47 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id KAA25748; Thu, 1 Aug 1996 10:16:31 -0500 From: Joe Greco Message-Id: <199608011516.KAA25748@brasil.moneng.mei.com> Subject: Re: Question about Cisco 2503i price To: louie@TransSys.COM (Louis A. Mamakos) Date: Thu, 1 Aug 1996 10:16:31 -0500 (CDT) Cc: dennis@etinc.com, hackers@FreeBSD.ORG In-Reply-To: <199608010306.XAA05782@whizzo.transsys.com> from "Louis A. Mamakos" at Jul 31, 96 11:06:16 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > >The 2503i is a mission critical version, it directly includes the software, > > >which disables the serial port. You can later buy the full version ($1200 > > >list price) to upgrade and use the serial ports. > > > > Does that include the (required) memory upgrade? > > > > So your talking $3000. for a box with 2 serial ports, an ISDN connection > > and a '386-speed processor? Eeek! > > Two T1 ports, ISDN, support for T1 PPP, Cisco HDLC, Frame Relay and > SMDS. Packet filtering. OSPF, RIP, RIP-2, EIGRP, BGP routing > protocols (if you need them). Look at the 2524 which has provisions > for integral 56K DDS or T1 CSU/DSUs to further reduce the system cost. > > Plus, you can plug it in and it works. No interrupt vectors, dma > channels to fool with. Small package. Only a fan for moving parts, > and no fsck. > > Not everyone is willing to spend a lot of time integrating a box when > you can essentially buy an appliance off the shelf which does a better > job. Are we going to start this whole discussion again? Yes, I agree, the FreeBSD box does a better job. Guys, take it to -chat or -isp, where people either don't give a rip or don't give a rip, respectively. Point for point, you can match Ciscos and FreeBSD boxes, it's simply a matter of which colored glasses you put on. Louis will never admit that a small amount of effort would yield a FreeBSD router that could outperform a Cisco in terms of performance and reliability, and still have no moving parts, because Louis is an "out of the box" bigot. Dennis will take the opposing viewpoint.. So, puh-leeze, let's not get into this again... both sides are right, from a certain point of view. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968 From owner-freebsd-hackers Thu Aug 1 08:59:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA22195 for hackers-outgoing; Thu, 1 Aug 1996 08:59:44 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA22182 for ; Thu, 1 Aug 1996 08:59:41 -0700 (PDT) Received: by sovcom.kiae.su id AA18558 (5.65.kiae-1 ); Thu, 1 Aug 1996 18:51:44 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Thu, 1 Aug 96 18:51:43 +0300 Received: (from ache@localhost) by nagual.ru (8.7.5/8.7.3) id TAA00709; Thu, 1 Aug 1996 19:48:29 +0400 (MSD) Message-Id: <199608011548.TAA00709@nagual.ru> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: rnordier@iafrica.com (Robert Nordier) Date: Thu, 1 Aug 1996 19:48:28 +0400 (MSD) Cc: terry@lambert.org, hackers@freebsd.org In-Reply-To: <199607312325.BAA00549@eac.iafrica.com> from "Robert Nordier" at "Aug 1, 96 01:25:57 am" From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL22 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > AFAIK, DOS filenames containing characters >= 0x80 have never been > much used, or had much practical value. So extensive special > provision for them almost seems misplaced. It isn't true, nationalized Win95 versions actively use it. F.e. Win95 Russian Edition use Russian (CP866) names for many folders/files. There is yet one interesting thing: DOS national charset used, not Windows one. For Russian Windows charset (CP1251) is different with DOS one (CP866). So Win95 does special efforts to convert between charsets. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-hackers Thu Aug 1 09:07:09 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA22525 for hackers-outgoing; Thu, 1 Aug 1996 09:07:09 -0700 (PDT) Received: from axp5.physik.fu-berlin.de (axp5.fddi5B.fu-berlin.de [160.45.5.75]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA22513 for ; Thu, 1 Aug 1996 09:07:03 -0700 (PDT) Received: from mordillo (graichen.dialup.fu-berlin.de [160.45.217.183]) by axp5.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id SAA16381 for ; Thu, 1 Aug 1996 18:06:58 +0200 (MET DST) Received: (from graichen@localhost) by mordillo (8.6.12/8.6.12) id SAA01016 for hackers@FreeBSD.org; Thu, 1 Aug 1996 18:01:34 +0200 From: Thomas Graichen Message-Id: <199608011601.SAA01016@mordillo> Subject: vm questions To: hackers@FreeBSD.org Date: Thu, 1 Aug 1996 18:01:33 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk i'm currently reading "the design & implementation ..." as some kind of relaxation to all the learning for my physics examinations and have some questions about the vm stuff - can someone - john or david - or maybe someone else please look at them ? * on page 145 is written: "a limitation of the implementation is that it cannot collaps two objects if either of them has allocated a pager. this limitation is serious, since pagers are allocated when the system begins running short of memory -- precisely the time when reclaiming of memory from collapsed objects is most necesarry." - is this the swap leaking bug in the original 4.4 BSD vm system ? - how is this problem avoided by the FreeBSD vm system ? (it was from the chapter "collapsing of shadow chains") * on page 158 is written: "a more consistent interface can be obtained by using a common cache for both the virtual-memory system and the filesystem. three approaches to merging the two caches are being undertaken. one approach is to have the filesystem use objects in the virtual-memory system as its cache; a second approach is to have the virtual-memory objects that map files use the existing filesystem cache; the third approach is to create a new cache that is a merger of the two existing caches, and to convert both the virtual memory and the filesystems to use this new cache. each of these approaches has its merits and drawbacks; it is not yet clear which approach will work best." (this is from the chapter "vnode pager") - my questions here are: which of the three ways is implemented in FreeBSD ? - which are implemented in other operating systems (linux, sunos, digital unix, etc.) ? * can anyone please write some lines about the basic changes to the vm-system in FreeBSD (so that i can understand it :-) - i don't know much about the kernel stuff other than reading the mailinglists and commit-messages - but i think i understand whats written in the above book - i hope at least partially :-) - it would also be interesting to get some feeling for the fork/exec/pipe changes ? would be nice if someone could scribble something down about it - so that my couriosity after reading the book is satsified :-) - a lot of thanks in advance t p.s.: and one last question - what is the state of 4.4 BSD ? - in the book it is said that lite 2 was really the last one - but from some mailinglists it sounds that kirk and maybe others are heavily working on filesystems etc. - will there be something like lite 3 ? p.s.2.: by the way - the book is very good - at least for people like who can learn a lot by reading it - i highly recommend it -> "the design and implementation of the 4.4 BSD operating system" -- thomas graichen graichen@mail.physik.fu-berlin.de graichen@FreeBSD.org perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away antoine de saint-exupery From owner-freebsd-hackers Thu Aug 1 09:17:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA22935 for hackers-outgoing; Thu, 1 Aug 1996 09:17:00 -0700 (PDT) Received: from axp5.physik.fu-berlin.de (axp5.fddi5B.fu-berlin.de [160.45.5.75]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA22917 for ; Thu, 1 Aug 1996 09:16:23 -0700 (PDT) Received: from mordillo (graichen.dialup.fu-berlin.de [160.45.217.183]) by axp5.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id SAA16521; Thu, 1 Aug 1996 18:15:34 +0200 (MET DST) Received: (from graichen@localhost) by mordillo (8.6.12/8.6.12) id SAA01210; Thu, 1 Aug 1996 18:15:21 +0200 From: Thomas Graichen Message-Id: <199608011615.SAA01210@mordillo> Subject: Re: tcp/ip over lp0 To: nate@mt.sri.com (Nate Williams) Date: Thu, 1 Aug 1996 18:15:20 +0200 (MET DST) Cc: hackers@FreeBSD.org In-Reply-To: <199607312120.PAA03869@rocky.mt.sri.com> from "Nate Williams" at Jul 31, 96 03:20:38 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk hasn't Nate Williams said ? ... > > > 4308 packets transmitted, 617 packets received, 85% packet loss > > That anything gets through implies that at least the software is setup > correctly, so the remaining factor is hardware. > > > time ago - but now some parts of them have changed - and the cable was > > different) ? - or can it be that the cable is too long (it's really long - > > about 5 meters or so) ? > > That's a *really* long cable. Also, *MAKE SURE* that neither machine > has another device using it's interrupt, and that there is a driver for > all hardware that generate interrupts. > > If you happen to use the commonly-used IRQ 7 for the parallel port and > something other than the parallel port either generates interrupts on 7 > or one another unregistered port you'll have lots of problems. > > Make sure both machines have don't have IRQ conflicts and shorten the > cable. > i tried another shorter cable and it's the same - so it must be the controller - can some bios settings or things like AUTO_EOI* or DUMMY_NOOPS have any influence ? - as far as i'm aware of all interrupts are correct set (ok i think nearly all are used - serial: 3,4,9(2), parallel: 7, ethernet: 5, sound: 11, ide controllers: 14,15 - should'nt i get something like stray interrups if something is wrong ? will this help you ? graichen@mordillo:~> vmstat -i interrupt total rate clk0 irq0 212749 99 rtc0 irq8 272238 127 fdc0 irq6 1 0 wdc0 irq14 20300 9 mcd0 irq10 1 0 vt0 irq1 9619 4 sio0 irq4 6251 2 sio3 irq9 53109 24 ed0 irq5 1 0 Total 574269 269 there's no irq 7 to see - but i haven't used it until the vmstat - does the lptcontrol -p/-i affect the lp0 device too or is it always using the interrupt version ? do you have any idea ? - i'll try to experiment further. thanks in advance - t -- thomas graichen graichen@mail.physik.fu-berlin.de graichen@FreeBSD.org perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away antoine de saint-exupery From owner-freebsd-hackers Thu Aug 1 09:20:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA23102 for hackers-outgoing; Thu, 1 Aug 1996 09:20:55 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA23095 for ; Thu, 1 Aug 1996 09:20:52 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id JAA08842; Thu, 1 Aug 1996 09:20:18 -0700 (PDT) Message-Id: <199608011620.JAA08842@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Thomas Graichen cc: hackers@FreeBSD.org Subject: Re: vm questions In-reply-to: Your message of "Thu, 01 Aug 1996 18:01:33 +0200." <199608011601.SAA01016@mordillo> From: David Greenman Reply-To: dg@root.com Date: Thu, 01 Aug 1996 09:20:18 -0700 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >i'm currently reading "the design & implementation ..." as some kind of >relaxation to all the learning for my physics examinations and have some >questions about the vm stuff - can someone - john or david - or maybe someone >else please look at them ? > >* on page 145 is written: "a limitation of the implementation is that it >cannot collaps two objects if either of them has allocated a pager. this >limitation is serious, since pagers are allocated when the system begins >running short of memory -- precisely the time when reclaiming of memory from >collapsed objects is most necesarry." - is this the swap leaking bug in the >original 4.4 BSD vm system ? - how is this problem avoided by the FreeBSD vm >system ? (it was from the chapter "collapsing of shadow chains") It was in the original system. It's fixed in FreeBSD by changing the code to allow objects with pagers to be collapsed. >* on page 158 is written: "a more consistent interface can be obtained by >using a common cache for both the virtual-memory system and the >filesystem. three approaches to merging the two caches are being >undertaken. one approach is to have the filesystem use objects in the >virtual-memory system as its cache; a second approach is to have the >virtual-memory objects that map files use the existing filesystem cache; the >third approach is to create a new cache that is a merger of the two existing >caches, and to convert both the virtual memory and the filesystems to use this >new cache. each of these approaches has its merits and drawbacks; it is not >yet clear which approach will work best." (this is from the chapter "vnode >pager") - my questions here are: which of the three ways is implemented in >FreeBSD ? - which are implemented in other operating systems (linux, sunos, >digital unix, etc.) ? We use the first approach. I can't speak about what other systems do. >* can anyone please write some lines about the basic changes to the vm-system >in FreeBSD (so that i can understand it :-) - i don't know much about the >kernel stuff other than reading the mailinglists and commit-messages - but i >think i understand whats written in the above book - i hope at least partially >:-) - it would also be interesting to get some feeling for the fork/exec/pipe >changes ? > >would be nice if someone could scribble something down about it - so that my >couriosity after reading the book is satsified :-) - a lot of thanks in >advance Yeah, we could write a book about this...and perhaps someday we will. A description of the changes is far beyond what can be written in email. >p.s.: and one last question - what is the state of 4.4 BSD ? - in the book it >is said that lite 2 was really the last one - but from some mailinglists it >sounds that kirk and maybe others are heavily working on filesystems etc. - >will there be something like lite 3 ? There are no plans for a lite-3 that I know of right now. Kirk is doing consulting work for BSDI and is working on some FFS related performance issues. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Thu Aug 1 09:21:59 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA23160 for hackers-outgoing; Thu, 1 Aug 1996 09:21:59 -0700 (PDT) Received: from axp5.physik.fu-berlin.de (axp5.fddi5B.fu-berlin.de [160.45.5.75]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA23153 for ; Thu, 1 Aug 1996 09:21:37 -0700 (PDT) Received: from mordillo (graichen.dialup.fu-berlin.de [160.45.217.183]) by axp5.physik.fu-berlin.de (8.7.1/8.7.1) with ESMTP id SAA16496 for ; Thu, 1 Aug 1996 18:20:58 +0200 (MET DST) Received: (from news@localhost) by mordillo (8.6.12/8.6.12) id SAA01236; Thu, 1 Aug 1996 18:20:56 +0200 To: hackers@FreeBSD.org Path: graichen From: graichen@axp5.physik.fu-berlin.de (Thomas Graichen) Newsgroups: local.freebsd-hackers Subject: Re: lp booting: first cut Date: 1 Aug 1996 16:20:50 GMT Organization: his FreeBSD box :-) Lines: 18 Distribution: local Message-ID: <4tqlh2$161@mordillo.physik.fu-berlin.de> References: <199607230850.EAA03102@dog.farm.org> NNTP-Posting-Host: localhost.physik.fu-berlin.de X-Newsreader: TIN [version 1.2 PL2] Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Dmitry Kohmanyuk (dk@dog.farm.org) wrote: : hi folks, : I have finally managed to ping(1) my little DTR-1 notebook : booted diskless over printer cable. how much work it would be to get booting over a serial null modem working too ? t -- thomas graichen graichen@mail.physik.fu-berlin.de graichen@FreeBSD.org perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away antoine de saint-exupery From owner-freebsd-hackers Thu Aug 1 10:09:06 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA25397 for hackers-outgoing; Thu, 1 Aug 1996 10:09:06 -0700 (PDT) Received: from eac.iafrica.com (196-7-101-138.iafrica.com [196.7.101.138]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA25391 for ; Thu, 1 Aug 1996 10:09:00 -0700 (PDT) Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id TAA00498; Thu, 1 Aug 1996 19:06:48 +0200 From: Robert Nordier Message-Id: <199608011706.TAA00498@eac.iafrica.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: hackers@freebsd.org Date: Thu, 1 Aug 1996 19:06:47 +0200 (SAT) Cc: terry@lambert.org, narvi@haldjas.folklore.ee, ache@nagual.ru X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > AFAIK, DOS filenames containing characters >= 0x80 have never been > > much used, or had much practical value. So extensive special > > provision for them almost seems misplaced. Sander wrote: > Actually they have at least around here. People just like to have > filenames with all those a", o", u" and even o~ (although that is one > which indeed does make troubles). Nothing ever happened except that nczip > refuses to pack them up. and Andrey A. Chernov wrote: > It isn't true, nationalized Win95 versions actively use it. > F.e. Win95 Russian Edition use Russian (CP866) names > for many folders/files. > There is yet one interesting thing: DOS national charset > used, not Windows one. For Russian Windows charset (CP1251) > is different with DOS one (CP866). So Win95 does special efforts > to convert between charsets. Thanks for this feedback. I was evidently completely wrong on this issue. -- Robert Nordier From owner-freebsd-hackers Thu Aug 1 10:10:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA25481 for hackers-outgoing; Thu, 1 Aug 1996 10:10:19 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA25473 for ; Thu, 1 Aug 1996 10:10:13 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id UAA18000; Thu, 1 Aug 1996 20:13:40 +0300 Date: Thu, 1 Aug 1996 20:13:39 +0300 (EET DST) From: Narvi To: "Jordan K. Hubbard" cc: Developer , Mark Mayo , freebsd-hackers@FreeBSD.ORG Subject: Re: Migrating BSDI 1.1 Passwords In-Reply-To: <10153.838904430@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, Jordan K. Hubbard wrote: > > Well, I would do, but I do a sup from sup.Freebsd.org :) > > Not the secure bits, obviously? > He said he would grab them if he needed. I think he has not (as a person respectful to what US laws have considered to be munition and prohibited the export of) taken them. :-) But there should perhaps be tcp-wrapper work-a-like to recall to the less respectful ones that every decent person gets his crypto sources from outside of the US and does always let those who want to know (especially the powers that are) of it... Sander > Jordan > From owner-freebsd-hackers Thu Aug 1 10:25:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA26336 for hackers-outgoing; Thu, 1 Aug 1996 10:25:02 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA26306 for ; Thu, 1 Aug 1996 10:24:49 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA07242; Thu, 1 Aug 1996 11:23:43 -0600 (MDT) Date: Thu, 1 Aug 1996 11:23:43 -0600 (MDT) Message-Id: <199608011723.LAA07242@rocky.mt.sri.com> From: Nate Williams To: Thomas Graichen Cc: nate@mt.sri.com (Nate Williams), hackers@freebsd.org Subject: Re: tcp/ip over lp0 In-Reply-To: <199608011615.SAA01210@mordillo> References: <199607312120.PAA03869@rocky.mt.sri.com> <199608011615.SAA01210@mordillo> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > That's a *really* long cable. Also, *MAKE SURE* that neither machine > > has another device using it's interrupt, and that there is a driver for > > all hardware that generate interrupts. > > > > If you happen to use the commonly-used IRQ 7 for the parallel port and > > something other than the parallel port either generates interrupts on 7 > > or one another unregistered port you'll have lots of problems. > > > > Make sure both machines have don't have IRQ conflicts and shorten the > > cable. > > > i tried another shorter cable and it's the same - so it must be the > controller - can some bios settings or things like AUTO_EOI* or > DUMMY_NOOPS have any influence ? The BIOS settings could affect it, but I doubt the kernel setting would. > - as far as i'm aware of all interrupts are correct set (ok i > think nearly all are used - serial: 3,4,9(2), parallel: 7, ethernet: 5, > sound: 11, ide controllers: 14,15 - should'nt i get something like stray > interrups if something is wrong ? will this help you ? The parallel controller would 'swallow' them, so you wouldn't see them, except that lpt0 wouldn't work very well. :( > graichen@mordillo:~> vmstat -i > interrupt total rate > clk0 irq0 212749 99 > rtc0 irq8 272238 127 > fdc0 irq6 1 0 > wdc0 irq14 20300 9 > mcd0 irq10 1 0 > vt0 irq1 9619 4 > sio0 irq4 6251 2 > sio3 irq9 53109 24 > ed0 irq5 1 0 > Total 574269 269 > > there's no irq 7 to see - but i haven't used it until the vmstat - does the > lptcontrol -p/-i affect the lp0 device too or is it always using the interrupt > version ? > > do you have any idea ? - i'll try to experiment further. > > thanks in advance - t > > -- > thomas graichen graichen@mail.physik.fu-berlin.de graichen@FreeBSD.org > > perfection is reached, not when there is no longer anything to add, but when > there is no longer anything to take away antoine de saint-exupery From owner-freebsd-hackers Thu Aug 1 10:28:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA26573 for hackers-outgoing; Thu, 1 Aug 1996 10:28:56 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA26567 for ; Thu, 1 Aug 1996 10:28:45 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id LAA07275; Thu, 1 Aug 1996 11:28:23 -0600 (MDT) Date: Thu, 1 Aug 1996 11:28:23 -0600 (MDT) Message-Id: <199608011728.LAA07275@rocky.mt.sri.com> From: Nate Williams To: Nate Williams Cc: Thomas Graichen , hackers@freebsd.org Subject: Re: tcp/ip over lp0 In-Reply-To: <199608011723.LAA07242@rocky.mt.sri.com> References: <199607312120.PAA03869@rocky.mt.sri.com> <199608011615.SAA01210@mordillo> <199608011723.LAA07242@rocky.mt.sri.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate Williams writes: [ Argh, I hit send before I meant to. Sorry ] > > That's a *really* long cable. Also, *MAKE SURE* that neither machine > > has another device using it's interrupt, and that there is a driver for > > all hardware that generate interrupts. > > > > If you happen to use the commonly-used IRQ 7 for the parallel port and > > something other than the parallel port either generates interrupts on 7 > > or one another unregistered port you'll have lots of problems. > > > > Make sure both machines have don't have IRQ conflicts and shorten the > > cable. > > > > i tried another shorter cable and it's the same - so it must be the > controller - can some bios settings or things like AUTO_EOI* or > DUMMY_NOOPS have any influence ? The BIOS settings could affect it, but I doubt the kernel setting would. > - as far as i'm aware of all interrupts are correct set (ok i > think nearly all are used - serial: 3,4,9(2), parallel: 7, ethernet: 5, > sound: 11, ide controllers: 14,15 - should'nt i get something like stray > interrups if something is wrong ? will this help you ? The parallel controller would 'swallow' them, so you wouldn't see them, except that lpt0 wouldn't work very well. :( > graichen@mordillo:~> vmstat -i > interrupt total rate > clk0 irq0 212749 99 > rtc0 irq8 272238 127 > fdc0 irq6 1 0 > wdc0 irq14 20300 9 > mcd0 irq10 1 0 > vt0 irq1 9619 4 > sio0 irq4 6251 2 > sio3 irq9 53109 24 > ed0 irq5 1 0 > Total 574269 269 > > there's no irq 7 to see - but i haven't used it until the vmstat - > does the lptcontrol -p/-i affect the lp0 device too or is it always > using the interrupt version ? It affects it. Also, I'm not sure the lpt0 device actually registers the interrupts. :( > do you have any idea ? - i'll try to experiment further. I still think it's a misconfigured IRQ and/or a parallel port that's not setup correctly. (In the BIOS see if you can set it to 'extended' or some other setting). Nate From owner-freebsd-hackers Thu Aug 1 10:29:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA26618 for hackers-outgoing; Thu, 1 Aug 1996 10:29:26 -0700 (PDT) Received: from mail.think.com (Mail1.Think.COM [131.239.33.245]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA26613 for ; Thu, 1 Aug 1996 10:29:24 -0700 (PDT) Received: from Early-Bird.Think.COM (Early-Bird-1.Think.COM [131.239.146.105]) by mail.think.com (8.7.5/m3) with ESMTP id NAA22677; Thu, 1 Aug 1996 13:28:52 -0400 (EDT) Received: from compound.Think.COM ([206.147.16.34]) by Early-Bird.Think.COM (8.7.5/e1) with ESMTP id NAA26122; Thu, 1 Aug 1996 13:28:49 -0400 (EDT) Received: (from alk@localhost) by compound.Think.COM (8.7.5/8.7.3) id MAA10744; Thu, 1 Aug 1996 12:29:00 -0500 (CDT) Date: Thu, 1 Aug 1996 12:29:00 -0500 (CDT) From: Tony Kimball Message-Id: <199608011729.MAA10744@compound.Think.COM> To: dev@fgate.flevel.co.uk Cc: hackers@freebsd.org Subject: Re: Migrating BSDI 1.1 Passwords Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Quoth dev@fgate.flevel.co.uk on Thu, 1 August: : > Why not just download it from the UK and let the paranoid US customs and : > crypto people be comforted. : : Well, I would do, but I do a sup from sup.Freebsd.org :) Now you've done it. They have to cut off your sup feed. And probably have to hack supfilesrv to special-case export-restricted directories in the long run (wasted manpower) or worse yet cut off all non-US domains from sup.freebsd.org -- otherwise they are not excercising due diligence and are subject to seizure/lien/forfeiture/criminal action. And this happens, here in Amerika, quite often. It would not be at all unheard of for FBI troopers with semiauto shotguns to ram in Jordan's front door with a skiploader, and perhaps kill a few of his children by mistake -- although that sort of thing is usually reserved for drug busts at the wrong address or people with unpopular religious views, such as alienated ex-scientologists or seventh-day adventist splinter groups. From owner-freebsd-hackers Thu Aug 1 10:37:45 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA27071 for hackers-outgoing; Thu, 1 Aug 1996 10:37:45 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA27066 for ; Thu, 1 Aug 1996 10:37:42 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id NAA04173; Thu, 1 Aug 1996 13:36:57 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: Tony Kimball cc: dev@fgate.flevel.co.uk, hackers@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Migrating BSDI 1.1 Passwords In-reply-to: Your message of "Thu, 01 Aug 1996 12:29:00 CDT." <199608011729.MAA10744@compound.Think.COM> Date: Thu, 01 Aug 1996 13:36:56 -0400 Message-ID: <4169.838921016@orion.webspan.net> Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tony Kimball wrote in message ID <199608011729.MAA10744@compound.Think.COM>: > : Well, I would do, but I do a sup from sup.Freebsd.org :) > Now you've done it. They have to cut off your sup feed. And probably > have to hack supfilesrv to special-case export-restricted directories > in the long run (wasted manpower) or worse yet cut off all non-US > domains from sup.freebsd.org -- otherwise they are not excercising due > diligence and are subject to seizure/lien/forfeiture/criminal action. It's ok banning `*.uk', for example, but what happens (for example) if the person wanting the code works for `demon.net' or `xara.net', both of whom are in the UK, and both of whom have US style addresses? We can't win :-( Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-hackers Thu Aug 1 10:39:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA27249 for hackers-outgoing; Thu, 1 Aug 1996 10:39:58 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA27212 for ; Thu, 1 Aug 1996 10:39:42 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id UAA18138; Thu, 1 Aug 1996 20:42:09 +0300 Date: Thu, 1 Aug 1996 20:42:08 +0300 (EET DST) From: Narvi To: Robert Nordier cc: hackers@freebsd.org, terry@lambert.org, ache@nagual.ru Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? In-Reply-To: <199608011706.TAA00498@eac.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, Robert Nordier wrote: > > > AFAIK, DOS filenames containing characters >= 0x80 have never been > > > much used, or had much practical value. So extensive special > > > provision for them almost seems misplaced. > > Sander wrote: > > > Actually they have at least around here. People just like to have > > filenames with all those a", o", u" and even o~ (although that is one > > which indeed does make troubles). Nothing ever happened except that nczip > > refuses to pack them up. > > and Andrey A. Chernov wrote: > > > It isn't true, nationalized Win95 versions actively use it. > > F.e. Win95 Russian Edition use Russian (CP866) names > > for many folders/files. > > There is yet one interesting thing: DOS national charset > > used, not Windows one. For Russian Windows charset (CP1251) > > is different with DOS one (CP866). So Win95 does special efforts > > to convert between charsets. > > Thanks for this feedback. I was evidently completely wrong on this > issue. You were right within a context. That's what the lists are for. Sander > > -- > Robert Nordier > From owner-freebsd-hackers Thu Aug 1 10:51:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA27914 for hackers-outgoing; Thu, 1 Aug 1996 10:51:26 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA27891 for ; Thu, 1 Aug 1996 10:51:16 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA06814 for ; Thu, 1 Aug 1996 19:51:05 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA04057 for freebsd-hackers@freebsd.org; Thu, 1 Aug 1996 19:51:05 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id TAA19103 for freebsd-hackers@freebsd.org; Thu, 1 Aug 1996 19:32:10 +0200 (MET DST) From: J Wunsch Message-Id: <199608011732.TAA19103@uriah.heep.sax.de> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 1 Aug 1996 19:32:09 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199608011548.TAA00709@nagual.ru> from "[?KOI8-R?]" at "Aug 1, 96 07:48:28 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As [?KOI8-R?] wrote: > There is yet one interesting thing: DOS national charset > used, not Windows one. For Russian Windows charset (CP1251) > is different with DOS one (CP866). So Win95 does special efforts > to convert between charsets. Btw., that's same for German. DOS uses cp437, but Winlose uses what they call `ANSI' that is close to ISO-8859-1. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Aug 1 10:51:38 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA27954 for hackers-outgoing; Thu, 1 Aug 1996 10:51:38 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA27949; Thu, 1 Aug 1996 10:51:35 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA06846; Thu, 1 Aug 1996 19:51:27 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA04068; Thu, 1 Aug 1996 19:51:26 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id TAA19313; Thu, 1 Aug 1996 19:41:09 +0200 (MET DST) From: J Wunsch Message-Id: <199608011741.TAA19313@uriah.heep.sax.de> Subject: Re: FreeBSD and Mach 64 To: green@aries.isf.rl.af.mil (Charles Kenneth Green - PRC) Date: Thu, 1 Aug 1996 19:41:08 +0200 (MET DST) Cc: hackers@freebsd.org, questions@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199608011500.LAA03816@aries.isf.rl.af.mil> from Charles Kenneth Green - PRC at "Aug 1, 96 11:00:21 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Charles Kenneth Green - PRC wrote: > Has there been a fix for the sio.c bug that fouls up Mach 64 > cards. I have a FreeBSD 2.1 system that I had to replace the video > card in. The card I ended up getting uses a Mach 64 chip and I'd > prefer not to have to send it back. RTFAQ please. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Aug 1 11:03:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA28651 for hackers-outgoing; Thu, 1 Aug 1996 11:03:40 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA28646 for ; Thu, 1 Aug 1996 11:03:34 -0700 (PDT) Received: (from narvi@localhost) by haldjas.folklore.ee (8.6.12/8.6.12) id VAA18270; Thu, 1 Aug 1996 21:07:50 +0300 Date: Thu, 1 Aug 1996 21:07:50 +0300 (EET DST) From: Narvi To: Joerg Wunsch cc: FreeBSD hackers Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? In-Reply-To: <199608011732.TAA19103@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, J Wunsch wrote: > As [?KOI8-R?] wrote: > > > There is yet one interesting thing: DOS national charset > > used, not Windows one. For Russian Windows charset (CP1251) > > is different with DOS one (CP866). So Win95 does special efforts > > to convert between charsets. > > Btw., that's same for German. DOS uses cp437, but Winlose uses what > they call `ANSI' that is close to ISO-8859-1. It does so in every and other place where there is a separate code page for DOS but windows uses just the same one they call ansi. I hope not everybody from every such country (all western European + I think also others) will not want to say here too! Sander > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) > From owner-freebsd-hackers Thu Aug 1 11:22:26 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA29615 for hackers-outgoing; Thu, 1 Aug 1996 11:22:26 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA29603 for ; Thu, 1 Aug 1996 11:22:20 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA07594; Thu, 1 Aug 1996 20:21:00 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id UAA04394; Thu, 1 Aug 1996 20:21:00 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id UAA19764; Thu, 1 Aug 1996 20:01:49 +0200 (MET DST) From: J Wunsch Message-Id: <199608011801.UAA19764@uriah.heep.sax.de> Subject: Re: Upgrade from 2.1.0. to 2.1.5? To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 1 Aug 1996 20:01:49 +0200 (MET DST) Cc: praj@nando.net (praj) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199608010034.UAA23054@bessel.nando.net> from praj at "Jul 31, 96 08:34:39 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As praj wrote: > If i build the 2.1.5 kernel from the 2.1.5 sources and use it to boot my > 2.1.0 system, am i upgraded to 2.1.5 or is there some other things that i > shoudl do? The kernel is only the first step, you need to rebuild the userland as well. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Thu Aug 1 11:36:30 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA00394 for hackers-outgoing; Thu, 1 Aug 1996 11:36:30 -0700 (PDT) Received: from po2.glue.umd.edu (po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA00389 for ; Thu, 1 Aug 1996 11:36:28 -0700 (PDT) Received: from fiber.eng.umd.edu (fiber.eng.umd.edu [129.2.98.185]) by po2.glue.umd.edu (8.7.5/8.7.3) with ESMTP id OAA09488; Thu, 1 Aug 1996 14:36:25 -0400 (EDT) Received: from localhost (chuckr@localhost) by fiber.eng.umd.edu (8.7.5/8.7.3) with SMTP id OAA21986; Thu, 1 Aug 1996 14:36:24 -0400 (EDT) X-Authentication-Warning: fiber.eng.umd.edu: chuckr owned process doing -bs Date: Thu, 1 Aug 1996 14:36:24 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@fiber.eng.umd.edu To: Tony Kimball cc: dev@fgate.flevel.co.uk, hackers@FreeBSD.ORG Subject: Re: Migrating BSDI 1.1 Passwords In-Reply-To: <199608011729.MAA10744@compound.Think.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, Tony Kimball wrote: > Quoth dev@fgate.flevel.co.uk on Thu, 1 August: > > : > Why not just download it from the UK and let the paranoid US customs and > : > crypto people be comforted. > : > : Well, I would do, but I do a sup from sup.Freebsd.org :) > > Now you've done it. They have to cut off your sup feed. And probably > have to hack supfilesrv to special-case export-restricted directories > in the long run (wasted manpower) or worse yet cut off all non-US > domains from sup.freebsd.org -- otherwise they are not excercising due > diligence and are subject to seizure/lien/forfeiture/criminal action. > And this happens, here in Amerika, quite often. It would not be at > all unheard of for FBI troopers with semiauto shotguns to ram in > Jordan's front door with a skiploader, and perhaps kill a few of his > children by mistake -- although that sort of thing is usually reserved > for drug busts at the wrong address or people with unpopular religious > views, such as alienated ex-scientologists or seventh-day adventist > splinter groups. 1) That's a huge exaggeration. It's true in exceptions, but calling it common is a lie, and just as bad as the original incidents. 2) This list is hardly a reasonable place to post such, regardless of their truth. Go hit some usenet advocacy list. 3) We all probably disagree to some extent with the US crypto laws, but calling mistakes to general attention sure isn't doing any good for the person asking for help, is it? Be constructive. I probably agree with your basic notions, but they're too hidden underneath the general rant. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Thu Aug 1 11:47:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA00984 for hackers-outgoing; Thu, 1 Aug 1996 11:47:55 -0700 (PDT) Received: from filitov.isf.rl.af.mil (FILITOV.ISF.RL.AF.MIL [128.132.64.25]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA00963; Thu, 1 Aug 1996 11:47:48 -0700 (PDT) Received: (from green@localhost) by filitov.isf.rl.af.mil (8.7.3/8.7.3) id OAA24550; Thu, 1 Aug 1996 14:07:14 -0400 (EDT) Message-Id: <199608011807.OAA24550@filitov.isf.rl.af.mil> From: green@filitov.isf.rl.af.mil (Charles Green) Date: Thu, 1 Aug 1996 14:07:13 +1000 In-Reply-To: J Wunsch "Re: FreeBSD and Mach 64" (Aug 1, 19:41) X-Mailer: Mail User's Shell (7.2.4 2/2/92) To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: FreeBSD and Mach 64 Cc: hackers@freebsd.org, questions@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk You know, I did check the FAQ. I read 7.12 and saw that it was a recognized problem. What I didn't do was notice that 7.13 showed a fix. Oops :) I think 7.12 and 7.13 should be made into one entry, all the other questions have the solution included with the explaination of the problem. J Wunsch stands accused of saying: } Date: Aug 1, 19:41 } Subject: Re: FreeBSD and Mach 64 } As Charles Kenneth Green - PRC wrote: } } > Has there been a fix for the sio.c bug that fouls up Mach 64 } > cards. I have a FreeBSD 2.1 system that I had to replace the video } > card in. The card I ended up getting uses a Mach 64 chip and I'd } > prefer not to have to send it back. } } RTFAQ please. } } -- } cheers, J"org } } joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE } Never trust an operating system you don't have sources for. ;-) }-- End of excerpt from J Wunsch -- Charles Green, PRC, Inc. Rome Laboratory, NY From owner-freebsd-hackers Thu Aug 1 12:03:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01693 for hackers-outgoing; Thu, 1 Aug 1996 12:03:08 -0700 (PDT) Received: from nrlmry.navy.mil (HELIUM.NRLMRY.NAVY.MIL [199.9.2.40]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA01688 for ; Thu, 1 Aug 1996 12:03:05 -0700 (PDT) From: norton@nrlmry.navy.mil Received: from norton.nrlmry.navy.mil by nrlmry.navy.mil (4.1/SMI-4.1) id AA15760; Thu, 1 Aug 96 12:03:58 PDT Received: by norton.nrlmry.navy.mil (SMI-8.6/SMI-SVR4) id MAA05218; Thu, 1 Aug 1996 12:02:58 -0700 Date: Thu, 1 Aug 1996 12:02:58 -0700 Message-Id: <199608011902.MAA05218@norton.nrlmry.navy.mil> To: hackers@FreeBSD.ORG Subject: PPP vs. PLIP Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I just picked up a microcom modem for connecting to my ISP (they hook into a T1). They are running microcom modems also. This is a 28.8 modem. The modem info says that you can hook it up to either a serial port or a parallel port - and claims that the parallel port arrangement will give you about 3x the throughput. I was wondering if anyone had any feedback as to if you would really see higher bandwidth running through the parallel port (using PLIP, I guess) vs. running PPP via the serial port. Also - I've been using the user PPP and it seems to be pretty solid. How does the user version compare the to kernel version to the PLIP implementation in terms of both speed and reliability? From what I can tell, I get about 18kbits/sec on things like ftp's currently. Thanks for any responses you care to send. -dave From owner-freebsd-hackers Thu Aug 1 12:31:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02732 for hackers-outgoing; Thu, 1 Aug 1996 12:31:25 -0700 (PDT) Received: from eac.iafrica.com (196-7-101-132.iafrica.com [196.7.101.132]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA02707 for ; Thu, 1 Aug 1996 12:31:16 -0700 (PDT) Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id VAA00586; Thu, 1 Aug 1996 21:28:08 +0200 From: Robert Nordier Message-Id: <199608011928.VAA00586@eac.iafrica.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: terry@lambert.org (Terry Lambert) Date: Thu, 1 Aug 1996 21:28:07 +0200 (SAT) Cc: hackers@freebsd.org In-Reply-To: <199607311829.LAA02458@phaeton.artisoft.com> from "Terry Lambert" at Jul 31, 96 11:29:44 am X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > > > The FAT fs primitives are done and tested and I'm currently working > > on VFAT support. > > Before you get too far on that, I have the algorithm it uses to avoid > short name name space collisions. It's not pretty, but it works, and > I think that was all Microsoft really cared about. > I'm also not sure about the long name space storage which is in > ISO-10646/16 (16 bit Unicode), since it is not possible to pass > Unicode across the lookup interface (this will be a problem for > any NTFS as well -- Linux is unfortunately way ahead of BSD here). > I can't help with the Unicode stuff given the current state of the BSD > VFS; my suggestion is to punt, and treat the high byte as zero in all > cases, converting it to ISO-8859-1 (Latin 1). This will damage utility > for anyone outside the Latin 1 scope, but that can't be helped without > the underlying VFS changes (appologies to non-Latin 1 using countries > up front). > > If you get to where you need to work on name collision, let me know, > and I can describe the algorithm in a couple of pages. I was doing some work on this just recently. When you have the time, I'd appreciate your description. There may be a few points that my derived algorithm misses. Following your suggestion of dropping the Unicode high byte, a primary concern is that this will itself lead to name space collisions. I'm a bit vague on the complete range of encodings, but I assume that LFNs could coexist in a directory where the only difference is in bits 8-15, which are then masked off. Alternatively, masking off the high byte may result in a value of (binary) zero embedded in the LFN, or something equally undesirable. Won't this entail a further algorithm to produce distinct BSD LFN representations, or do you forsee another way around this? -- Robert Nordier From owner-freebsd-hackers Thu Aug 1 13:50:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA27968 for hackers-outgoing; Thu, 1 Aug 1996 13:50:51 -0700 (PDT) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA27963 for ; Thu, 1 Aug 1996 13:50:49 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.7.5/8.6.12) with SMTP id NAA12608; Thu, 1 Aug 1996 13:45:18 -0700 (PDT) Message-Id: <199608012045.NAA12608@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: Host localhost [127.0.0.1] didn't use HELO protocol To: "Eric L. Hernes" Cc: freebsd-hackers@freebsd.org Subject: Re: cvs commit: ports/devel/gcc11 - Imported sources Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 01 Aug 1996 13:45:18 -0700 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996 12:54:21 -0700 (PDT) "Eric L. Hernes" wrote: > Log Message: > new port for gcc 2.6.3 cross compiler for MC68HC11 You mean the 6811 back-end isn't in the gcc master sources yet? What a drag! -- save the ancient forests - http://www.bayarea.net/~thorpej/forest/ -- Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-hackers Thu Aug 1 14:02:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA28641 for hackers-outgoing; Thu, 1 Aug 1996 14:02:23 -0700 (PDT) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA28636 for ; Thu, 1 Aug 1996 14:02:14 -0700 (PDT) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id QAA04821; Thu, 1 Aug 1996 16:01:51 -0500 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma004800; Thu Aug 1 16:01:35 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id QAA19130; Thu, 1 Aug 1996 16:01:35 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.5/8.6.12) with SMTP id QAA21994; Thu, 1 Aug 1996 16:01:39 -0500 (CDT) Message-Id: <199608012101.QAA21994@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: Jason Thorpe cc: "Eric L. Hernes" , freebsd-hackers@freebsd.org Subject: Re: cvs commit: ports/devel/gcc11 - Imported sources In-reply-to: Your message of "Thu, 01 Aug 1996 13:45:18 PDT." <199608012045.NAA12608@lestat.nas.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Aug 1996 16:01:39 -0500 From: "Eric L. Hernes" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jason Thorpe writes: > >You mean the 6811 back-end isn't in the gcc master sources yet? What a >drag! to be honest, I don't know. I found this stuff at a 6811 archive and didn't think to look at the current gcc. It works with 2.6.3, same as FBSD, which may be of some merrit, probably not though. > > -- save the ancient forests - http://www.bayarea.net/~thorpej/forest/ -- >Jason R. Thorpe thorpej@nas.nasa.gov >NASA Ames Research Center Home: 408.866.1912 >NAS: M/S 258-6 Work: 415.604.0935 >Moffett Field, CA 94035 Pager: 415.428.6939 eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Thu Aug 1 14:29:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA00306 for hackers-outgoing; Thu, 1 Aug 1996 14:29:42 -0700 (PDT) Received: from fuzzy.poly.edu (fuzzy.poly.edu [128.238.32.160]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA00301 for ; Thu, 1 Aug 1996 14:29:36 -0700 (PDT) Received: (from slava@localhost) by fuzzy.poly.edu (8.6.12/8.6.12) id RAA00837; Thu, 1 Aug 1996 17:23:18 -0400 Date: Thu, 1 Aug 1996 17:23:17 -0400 (EDT) From: Slava Rozman To: hackers@freebsd.org Subject: parallel port tape backup Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi! Just 2 questions. 1. Is it possible to use parallel port tape backup on freebsd 2.1.0-RELEASE? 2. Is Creative Labs 6x CD-ROM supported on the same system? Thank you for you help! From owner-freebsd-hackers Thu Aug 1 14:31:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA00419 for hackers-outgoing; Thu, 1 Aug 1996 14:31:25 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA00410; Thu, 1 Aug 1996 14:31:17 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id WAA20042; Thu, 1 Aug 1996 22:14:50 +0200 (MET DST) To: dg@Root.COM cc: Thomas Graichen , hackers@FreeBSD.org Subject: Re: vm questions In-reply-to: Your message of "Thu, 01 Aug 1996 09:20:18 PDT." <199608011620.JAA08842@root.com> Date: Thu, 01 Aug 1996 22:14:48 +0200 Message-ID: <20040.838930488@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > There are no plans for a lite-3 that I know of right now. Kirk is doing >consulting work for BSDI and is working on some FFS related performance >issues. I asked him directly, and his answer was a very convincing no. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-hackers Thu Aug 1 14:51:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA01684 for hackers-outgoing; Thu, 1 Aug 1996 14:51:16 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA01679; Thu, 1 Aug 1996 14:51:12 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by misery.sdf.com (8.7.5/UNS-1.0) with SMTP id PAA22345; Thu, 1 Aug 1996 15:07:01 -0700 (PDT) Date: Thu, 1 Aug 1996 15:07:00 -0700 (PDT) From: Tom Samplonius To: Gary Palmer cc: Tony Kimball , dev@fgate.flevel.co.uk, hackers@FreeBSD.org Subject: Re: Migrating BSDI 1.1 Passwords In-Reply-To: <4169.838921016@orion.webspan.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, Gary Palmer wrote: > Tony Kimball wrote in message ID > <199608011729.MAA10744@compound.Think.COM>: > > : Well, I would do, but I do a sup from sup.Freebsd.org :) > > > Now you've done it. They have to cut off your sup feed. And probably > > have to hack supfilesrv to special-case export-restricted directories > > in the long run (wasted manpower) or worse yet cut off all non-US > > domains from sup.freebsd.org -- otherwise they are not excercising due > > diligence and are subject to seizure/lien/forfeiture/criminal action. > > It's ok banning `*.uk', for example, but what happens (for example) if > the person wanting the code works for `demon.net' or `xara.net', both > of whom are in the UK, and both of whom have US style addresses? We > can't win :-( Yes, you can. There are only a limited number of netblocks allocated to the UK, and all of those could be banned. Apparently, gatekeeper.dec.com has been using access control via a database of netblocks for a few years now for this exact purpose (or maybe this has changed recently). Tom From owner-freebsd-hackers Thu Aug 1 15:46:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA04274 for hackers-outgoing; Thu, 1 Aug 1996 15:46:55 -0700 (PDT) Received: from bacall.lodgenet.com (bacall.lodgenet.com [205.138.147.242]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA04259 for ; Thu, 1 Aug 1996 15:46:45 -0700 (PDT) Received: (from mail@localhost) by bacall.lodgenet.com (8.6.12/8.6.12) id RAA08974; Thu, 1 Aug 1996 17:46:25 -0500 Received: from garbo.lodgenet.com(204.124.123.250) by bacall via smap (V1.3) id sma008968; Thu Aug 1 17:45:59 1996 Received: from jake.lodgenet.com (jake.lodgenet.com [204.124.120.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id RAA21803; Thu, 1 Aug 1996 17:45:58 -0500 Received: from localhost (localhost [127.0.0.1]) by jake.lodgenet.com (8.7.5/8.6.12) with SMTP id RAA02592; Thu, 1 Aug 1996 17:46:03 -0500 (CDT) Message-Id: <199608012246.RAA02592@jake.lodgenet.com> X-Authentication-Warning: jake.lodgenet.com: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.2 7/18/95 To: Jason Thorpe cc: "Eric L. Hernes" , freebsd-hackers@freebsd.org Subject: Re: cvs commit: ports/devel/gcc11 - Imported sources In-reply-to: Your message of "Thu, 01 Aug 1996 13:45:18 PDT." <199608012045.NAA12608@lestat.nas.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Aug 1996 17:46:03 -0500 From: "Eric L. Hernes" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jason Thorpe writes: > >You mean the 6811 back-end isn't in the gcc master sources yet? What a >drag! > just checked gcc-2.7.2 off prep, nope. :( > -- save the ancient forests - http://www.bayarea.net/~thorpej/forest/ -- >Jason R. Thorpe thorpej@nas.nasa.gov >NASA Ames Research Center Home: 408.866.1912 >NAS: M/S 258-6 Work: 415.604.0935 >Moffett Field, CA 94035 Pager: 415.428.6939 > eric. -- erich@lodgenet.com http://rrnet.com/~erich erich@rrnet.com From owner-freebsd-hackers Thu Aug 1 16:06:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA05092 for hackers-outgoing; Thu, 1 Aug 1996 16:06:17 -0700 (PDT) Received: from mail.think.com (Mail1.Think.COM [131.239.33.245]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA05087 for ; Thu, 1 Aug 1996 16:06:14 -0700 (PDT) Received: from Early-Bird.Think.COM (Early-Bird-1.Think.COM [131.239.146.105]) by mail.think.com (8.7.5/m3) with ESMTP id TAA05433; Thu, 1 Aug 1996 19:06:04 -0400 (EDT) Received: from compound.Think.COM ([206.147.16.34]) by Early-Bird.Think.COM (8.7.5/e1) with ESMTP id TAA01584; Thu, 1 Aug 1996 19:05:55 -0400 (EDT) Received: (from alk@localhost) by compound.Think.COM (8.7.5/8.7.3) id SAA12090; Thu, 1 Aug 1996 18:05:34 -0500 (CDT) Date: Thu, 1 Aug 1996 18:05:34 -0500 (CDT) From: Tony Kimball Message-Id: <199608012305.SAA12090@compound.Think.COM> To: chuckr@glue.umd.edu Subject: rants [Meta-mail] Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [This is meta-mail and may be immediately deleted without review by anyone with exclusively project-oriented interests.] 1) That's a huge exaggeration. It's true in exceptions, but calling it common is a lie, and just as bad as the original incidents. ^^^ It is with some trepidation that I post. I would have kept this message private, except that I feel this single word leaves me publically defamed, and so I feel obligated to respond in the same forum in the interests of preserving the utility (such as it is) of my public reputation. With this post, I feel that I have adequately defended my public reputation at this time, and I undertake to refrain from any further posts to the list on this subject, barring more substantive cause. (Advisory warning: The detail of this post may be excruciating for some readers.) alk contra chuckr ----------------- 1) That's a huge exaggeration. It's true in exceptions, but calling it common is a lie, and just as bad as the original incidents. A lie? I don't read the newspapers as a rule, and I never watch TV. Yet in the past 5 years I could cite *dozens* of similar instances. If my media-deprived ignorant condition can produce so many examples, reason tells me that there must be a large number of similar cases. A large number makes such common, to my mind. If you are being hit in a nerve by my statements, okay, express yourself, but I'd thank you kindly not to paint me a liar. Because I am not. "Deluded" or "ignorant" or "mistaken", I can deal with. "Liar" cuts off the possibility of dialog, at the personal level, and in a public forum defames my character. I urge that it only be used in instances where there is probable cause to believe that an intentional and manifest untruth has uttered without cause or quotation. Also, I would opine that lying to someone is *not* "just as bad" as killing them. 2) This list is hardly a reasonable place to post such, regardless of their truth. Go hit some usenet advocacy list. It was topically appropriate because the individual in question (and probably many other readers) did not appreciate the seriousness of the matter. A graphic description of the possible extreme consequences was entirely suitable to the education of non-US residents in the matter, which is a shared interest of the FreeBSD community in general and the hackers in particular, who are most effected by impact on sup servers and the like. 3) We all probably disagree to some extent with the US crypto laws, but calling mistakes to general attention sure isn't doing any good for the person asking for help, is it? That wasn't my point. While I do believe that the existing ITAR regulations remain (marginally) offensive to good sense, we agree that "hackers" is not in any wise an appropriate venue for rhetoric on this subject. The point was to explain the seriousness of the matter, because failure to understand it can materially hurt people. A small probability of great damage provides a mathematical expectation of loss equal to that of a proportionately larger probability of a proportionately smaller loss. That the scope of damage to which I alluded is at least improbable, I can agree. That it is entirely consistent with recent experience with the US Federal government is to me manifest, regardless of our shared distaste for this admittedly distasteful state of affairs. I estimated the expectation of loss to be greater in the marginal, extreme case, so I used that example to convey my point. Methinks I set the wrong tone with my intentional misspelling of America, and you might have recieved my post more hospitably in its absence. If so, I can clearly understand the effect, and sincerely apologize for the petty rhetorical ploy -- I was in fact wearing my heart on my sleeve, as it were. I shall certainly endeavour to be more circumspect in avoiding politically sensitive allusion in any future posts to "hackers". I have no more enjoyment of the noise of metamail than any other reader. Finally, lest the last paragraph should imply the "damn" of "faint praise", I am aware that other aspects of my text were similarly ranging into rhetorical territories all too likely to provoke primarily emotional responses. I need to think about that somewhat. (I have a hyperbolic style, and may need to temper it, although I would prefer not to do so if it is not strictly necessary. I thank you for providing an occasion for possible useful introspection.) //alk From owner-freebsd-hackers Thu Aug 1 16:44:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA06282 for hackers-outgoing; Thu, 1 Aug 1996 16:44:33 -0700 (PDT) Received: from veda.is (root@ubiq.veda.is [193.4.230.60]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA06277 for ; Thu, 1 Aug 1996 16:44:27 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.7.5/8.7.3) id XAA22251; Thu, 1 Aug 1996 23:43:12 GMT From: Adam David Message-Id: <199608012343.XAA22251@veda.is> Subject: Re: missed SIGALRM To: fcurrent@jraynard.demon.co.uk (James Raynard) Date: Thu, 1 Aug 1996 23:43:10 +0000 (GMT) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199607211230.MAA00718@jraynard.demon.co.uk> from James Raynard at "Jul 21, 96 12:30:11 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I wrote: > > I have noticed that a SIGALRM can sometimes be missed altogether under certain > > conditions, perhaps as a side-effect of heavy machine load. Thanks to people who responded. :) Since it is clearly not relevant to -current, this is redirected from there. Closer analysis showed that it was not a case of missing alarms, but the return value of time(3) is not guaranteed monotonic so this had to be worked around. Is there any long-range timer which is monotonic across reboots, and is not prone to negative increments under the influence of NTP ? -- Adam David From owner-freebsd-hackers Thu Aug 1 17:47:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA08436 for hackers-outgoing; Thu, 1 Aug 1996 17:47:22 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA08431 for ; Thu, 1 Aug 1996 17:47:19 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA04852; Thu, 1 Aug 1996 17:43:14 -0700 From: Terry Lambert Message-Id: <199608020043.RAA04852@phaeton.artisoft.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: rnordier@iafrica.com (Robert Nordier) Date: Thu, 1 Aug 1996 17:43:14 -0700 (MST) Cc: terry@lambert.org, hackers@freebsd.org In-Reply-To: <199608011928.VAA00586@eac.iafrica.com> from "Robert Nordier" at Aug 1, 96 09:28:07 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > If you get to where you need to work on name collision, let me know, > > and I can describe the algorithm in a couple of pages. > > I was doing some work on this just recently. When you have the > time, I'd appreciate your description. There may be a few points > that my derived algorithm misses. The name collision is handled differently based on "intend lookup" vs. "intend create". The "EXCLUSIVE" flag I added for lookups which are expected to return an EEXISTS in the "intend create" case (create target, rename target, etc.) will help. When a name is passed in, it is either capable of being a valid 8.3 name or it isn't. If it is, then the name is looked up in the 8.3 name space. For an 8.3 name, the LFN will always be the same as the 8.3 name. Note that the 8.3 name is a case insensitive name; a name "Foo" and "foo" are identical for case insensitive lookup/case sensitive storage; they are the valid short name "FOO". The short name lookup will match or fail to match. In no case is it possible for a valid short name to have a long name form that collides with another long name form. Short names are looked up in the short name space and in the long name space. The long name space lookup is done because of the direction collisions are handled. In the LFN case, the lookup is done in the long name space. This is because any LFN that comes into lookup will have an LFN form if it has been previously stored. In the LFN case, the short name is not examined. The long file name that does not match in the create case will be cannonized to a tentative short name by searching for a '.' seperated suffix from the right side of the LFN moving left. The long name up to the first period, or 6 characters, will be copied moving right. The last two characters preceeding the suffix are replaced with a provisional "tail" value: "~1". Thus: ThisIsALong.Named.Document -> THISIS~1.DOC VeryLongName.TXT -> VERYLO~1.TXT Short.doc -> SHORT.DOC (8.3 name on input) The tail is permitted to increment based on collision, "eating" the characters leftward. Windows95 and WindowsNT have support routines for VFAT that do all of this for you. For instance, "VeryLongName.TXT" has a tentative short name with a provisional numeric "tail" of "VERYLO~1.TXT". Now if there already exists a "VERYLO~9.TXT", the next allowable post-collision value is "VERYL~10.TXT". This requires that your pattern match match the suffix (".TXT"), then go through matching "VERLO" for all possible tail vales that already exist. This requires a full traversal of the short name space for the directory. Windows95 wimps out and uses a "max" value on the tail, so if you had "VERYLO~8.TXT" but no "VERYLO~1.TXT", it would still end up with the post-collision name "VERYLO~9.TXT". Mac fanatics might note that since HFS has case sensitive storage and case insensitive lookup as well, a retraversal of the directory is probably going to be a common occurance for Mac NS support, or for a NetWare Volume mounting FS, which supports DOS, Mac, Unicode, OS/2, and UNIX name spaces. Eventually, the VOP_READDIR wants to be used to implement the VOP_LOOKUP (adding create flags and removing VOP_LOOKUP), and the VOP_READDIR wants to be split out into getdirblock and getdirblockelementfromdirblock parts, per the discussion of how to get rid of the "cookie" interface that causes so many problems in the NFS server implementation. > Following your suggestion of dropping the Unicode high byte, a > primary concern is that this will itself lead to name space > collisions. No, it won't. This is because you assume that lookup (open/stat/et al.) comes in as an ISO 8859-1 character set path. If you were masking on the way in, *then* you could get collisions. For short names, masking on the way in, you *can* get collisions. These you resolve with the normal collision resoloution algorithms. > I'm a bit vague on the complete range of encodings, but I assume > that LFNs could coexist in a directory where the only difference > is in bits 8-15, which are then masked off. No. A path comes into Win95's IFS (which the VFS interface is replacing in the BSD implementation) with an attribute of "terminal component is LFN" or "terminal component is 8.3" and an attribute of "path not including terminal components does/doesn't contain LFN components". For the sake of matching the Win95 collision algorithm in a VFS implementation, you will need to process each component and determine if it is a valid 8.3 name. If it isn't, it's an LFN. The short name equivalent of an LFN component passed in *always* goes to the collision name space... it could not have been a valid short name if it is a long name. > Alternatively, masking off the high byte may result in a value of > (binary) zero embedded in the LFN, or something equally undesirable. The LFN is *always* stored as a Unicode value. Therefore it is always stored as a 16 bit value, not two 8 bit values, so an embedded 8 bit zero is allowable (even expected). The predominance of Microsoft's ISO-10646/16 (Unicode) implementation is precisely why I wanted a 16 bit instead of a 32 bit wchar_t, and why I introduced the ISUNICODE flag in the path processing constants, and why I've been arguing for a shortword character (not char) length prefix for path processing. POSIX compatability in a Unicode environment is probably best done in the library, eventually. > Won't this entail a further algorithm to produce distinct BSD LFN > representations, or do you forsee another way around this? There will be a short term interoperability issue for upgrade to a internationalized file name space, when and if it is supported at the system call layer. Other than that, it should be as 8 bit clean for typical use, and we can adulterate non-ISO-8859-1 names into the 8 bit space available. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Thu Aug 1 17:57:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA08791 for hackers-outgoing; Thu, 1 Aug 1996 17:57:44 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA08782 for ; Thu, 1 Aug 1996 17:57:40 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.7.5/CET-v2.1) with SMTP id AAA27000; Fri, 2 Aug 1996 00:57:34 GMT Date: Fri, 2 Aug 1996 09:57:34 +0900 (JST) From: Michael Hancock Reply-To: Michael Hancock To: Poul-Henning Kamp cc: FreeBSD Hackers Subject: Re: vm questions In-Reply-To: <20040.838930488@critter.tfs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 Aug 1996, Poul-Henning Kamp wrote: > > There are no plans for a lite-3 that I know of right now. Kirk is doing > >consulting work for BSDI and is working on some FFS related performance > >issues. > > I asked him directly, and his answer was a very convincing no. Is the traditional BSD release engineering going to be carried on? Remember, 4.4 was a new feature release that is assumed to need fixing. Lite-2 was a "let's do what we can with the remaining budget" and it doesn't come close to a 4.5. 2.2 looks like it'll be more of a new feature release, so I guess we could get back to the fix release in the 2.3 time frame. Arggh! Never mind. Mike Hancock From owner-freebsd-hackers Thu Aug 1 17:59:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA08858 for hackers-outgoing; Thu, 1 Aug 1996 17:59:02 -0700 (PDT) Received: from central.picker.com (central.picker.com [144.54.31.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA08851 for ; Thu, 1 Aug 1996 17:59:00 -0700 (PDT) Received: from ct.picker.com by central.picker.com with smtp (Smail3.1.28.1 #3) id m0um8NZ-0004rrC; Thu, 1 Aug 96 20:46 EDT Received: from elmer.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA01179; Thu, 1 Aug 96 20:45:05 EDT Received: by elmer.picker.com (SMI-8.6/SMI-SVR4) id UAA09666; Thu, 1 Aug 1996 20:40:14 -0400 From: rhh@ct.picker.com (Randall Hopper) Message-Id: <199608020040.UAA09666@elmer.picker.com> Subject: Re: PPP vs. PLIP To: norton@nrlmry.navy.mil Date: Thu, 1 Aug 1996 20:40:14 -0400 (EDT) Cc: hackers@freebsd.org In-Reply-To: <199608011902.MAA05218@norton.nrlmry.navy.mil> from "norton@nrlmry.navy.mil" at Aug 1, 96 12:02:58 pm Reply-To: rhh@ct.picker.com Organization: Picker International, CT Division X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk norton@nrlmry.navy.mil: >I just picked up a microcom modem for connecting to my ISP (they hook >into a T1). They are running microcom modems also. This is a 28.8 >modem. > >The modem info says that you can hook it up to either a serial port or >a parallel port - and claims that the parallel port arrangement will >give you about 3x the throughput. > >I was wondering if anyone had any feedback as to if you would really >see higher bandwidth running through the parallel port (using PLIP, I ... >terms of both speed and reliability? From what I can tell, I get >about 18kbits/sec on things like ftp's currently. If you've got a fast serial port (16550 -- 16 byte FIFO), that's plenty fast enough to handle 28.8K dial-up connection even with full data compression on (56K-60K or so for highly compressible content). Also to my knowledge, FreeBSD supports FIFOs on fast serial ports, but doesn't support the advanced features of ECP/EPP parallel ports. So I think you'd have less system overhead with SLIP or PPP over a fast serial port (though at dial-up speeds I really don't know whether it'd make a noticable difference). Randall Hopper rhh@ct.picker.com From owner-freebsd-hackers Thu Aug 1 20:13:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA14815 for hackers-outgoing; Thu, 1 Aug 1996 20:13:35 -0700 (PDT) Received: from seagull.rtd.com (root@seagull.rtd.com [198.102.68.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA14795; Thu, 1 Aug 1996 20:13:23 -0700 (PDT) Received: (from dgy@localhost) by seagull.rtd.com (8.7.5/8.7.3) id UAA13351; Thu, 1 Aug 1996 20:13:18 -0700 (MST) From: Don Yuniskis Message-Id: <199608020313.UAA13351@seagull.rtd.com> Subject: syscons fonts To: freebsd-hackers@freefall.FreeBSD.org (FreeBSD hackers), freebsd-ports@freefall.FreeBSD.org (FreeBSD ports) Date: Thu, 1 Aug 1996 20:13:18 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greetings! Below is a listing of my /usr/share/syscons/fonts/MISC directory. I have no idea as to the quality of any of these fonts. Nor can I even vouch that they are appropriately named. I dragged them over from my 1.1.5.1 box a while ago. I *know* some of the oddball sizes are waste of clusters (i.e. EGA_alternate-8x11.fnt) byt they come in handy for me when I need to burn a character generator ROM or somesuch... --don total 2228 -r--r--r-- 1 bin bin 3584 Aug 28 1993 ASCII_standard-8x14.fnt -r--r--r-- 1 bin bin 2560 May 10 1995 EGA_alternate-8x10.fnt -r--r--r-- 1 bin bin 2816 May 10 1995 EGA_alternate-8x11.fnt -r--r--r-- 1 bin bin 3072 May 10 1995 EGA_alternate-8x12.fnt -r--r--r-- 1 bin bin 3328 May 10 1995 EGA_alternate-8x13.fnt -r--r--r-- 1 bin bin 2048 May 10 1995 EGA_alternate-8x8.fnt -r--r--r-- 1 bin bin 2304 May 10 1995 EGA_alternate-8x9.fnt -r--r--r-- 1 bin bin 2048 Aug 28 1993 MacIntosh-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 Macintosh-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 Macintosh-8x16.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 TeX_math-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 TeX_math-8x16.fnt -r--r--r-- 1 bin bin 3584 May 10 1995 VGA_ROM-8x14.fnt -r--r--r-- 1 bin bin 4096 May 10 1995 VGA_ROM-8x16.fnt -r--r--r-- 1 bin bin 2048 May 10 1995 VGA_ROM-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 antique-8x14.fnt -r--r--r-- 1 bin bin 4096 Jul 14 1994 antique-8x16.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 arabic_draft-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 arabic_kufi-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 arabic_naftih-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 arabic_naskh-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 armenian-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 armenian-8x16.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 armenian-8x8.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 artistic-8x16.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 backward-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 binary_editor-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 block_dec_ctrls-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 block_hex-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 block_hex_alts-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 block_hex_codes-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 block_hex_ctrls-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 block_thin-8x14.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 bongartz_arabic-8x14.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 bongartz_broadway-8x14.fnt -r--r--r-- 1 bin bin 4096 Aug 28 1993 bongartz_broadway-8x16.fnt -r--r--r-- 1 bin bin 2048 Aug 28 1993 bongartz_cp437-8x8.fnt -r--r--r-- 1 bin bin 2048 Aug 28 1993 bongartz_cp437_fine-8x8.fnt -r--r--r-- 1 bin bin 2048 Aug 28 1993 bongartz_cyrillic-8x8.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 bongartz_fractur-8x14.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 bongartz_gaelic-8x14.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 bongartz_georgian-8x14.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 bongartz_italic-8x14.fnt -r--r--r-- 1 bin bin 4096 Aug 28 1993 bongartz_italic-8x16.fnt -r--r--r-- 1 bin bin 4096 Aug 28 1993 bongartz_large-8x16.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 bongartz_misc-8x14.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 bongartz_ocr-8x14.fnt -r--r--r-- 1 bin bin 4096 Aug 28 1993 bongartz_ocr-8x16.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 bongartz_oldenglish-8x14.fnt -r--r--r-- 1 bin bin 6144 Aug 28 1993 bongartz_pc-8x24.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 bongartz_pc_6-8x14.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 bongartz_pc_7-8x14.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 bongartz_polish-8x14.fnt -r--r--r-- 1 bin bin 2048 Aug 28 1993 bongartz_roman-8x8.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 bongartz_roundbox-8x14.fnt -r--r--r-- 1 bin bin 4096 Aug 28 1993 bongartz_roundbox-8x16.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 bongartz_script-8x14.fnt -r--r--r-- 1 bin bin 2560 Aug 28 1993 bongartz_sideways-8x10.fnt -r--r--r-- 1 bin bin 2048 Aug 28 1993 bongartz_special-8x8.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 bongartz_thin_sanserif-8x14.fnt -r--r--r-- 1 bin bin 4096 Aug 28 1993 bongartz_thin_sanserif-8x16.fnt -r--r--r-- 1 bin bin 2048 Aug 28 1993 bongartz_thin_sanserif-8x8.fnt -r--r--r-- 1 bin bin 4096 Jul 14 1994 broadway-8x16.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 broadway_A-8x14.fnt -r--r--r-- 1 bin bin 2560 Aug 28 1993 cafe-8x10.fnt -r--r--r-- 1 bin bin 3072 Aug 28 1993 cafe-8x12.fnt -r--r--r-- 1 bin bin 4096 Jul 14 1994 courier-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp111-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp111-8x16.fnt -r--r--r-- 1 bin bin 4864 Jun 3 1993 cp111-8x19.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp111-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp112-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp112-8x16.fnt -r--r--r-- 1 bin bin 4864 Jun 3 1993 cp112-8x19.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp112-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp113-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp113-8x16.fnt -r--r--r-- 1 bin bin 4864 Jun 3 1993 cp113-8x19.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp113-8x8.fnt -r--r--r-- 1 bin bin 3584 Jan 18 1996 cp437-8x14.fnt -r--r--r-- 1 bin bin 4096 Jan 18 1996 cp437-8x16.fnt -r--r--r-- 1 bin bin 4864 Jan 18 1996 cp437-8x19.fnt -r--r--r-- 1 bin bin 2048 Jan 18 1996 cp437-8x8.fnt -r--r--r-- 1 bin bin 3584 Jan 18 1996 cp850-8x14.fnt -r--r--r-- 1 bin bin 4096 Jan 18 1996 cp850-8x16.fnt -r--r--r-- 1 bin bin 4864 Jan 18 1996 cp850-8x19.fnt -r--r--r-- 1 bin bin 2048 Jan 18 1996 cp850-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp851-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp851-8x16.fnt -r--r--r-- 1 bin bin 4864 Jun 3 1993 cp851-8x19.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp851-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp852-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp852-8x16.fnt -r--r--r-- 1 bin bin 4864 Jun 3 1993 cp852-8x19.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp852-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp853-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp853-8x16.fnt -r--r--r-- 1 bin bin 4864 Jun 3 1993 cp853-8x19.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp853-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp860-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp860-8x16.fnt -r--r--r-- 1 bin bin 4864 Jun 3 1993 cp860-8x19.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp860-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp861-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp861-8x16.fnt -r--r--r-- 1 bin bin 4864 Jun 3 1993 cp861-8x19.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp861-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp862-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp862-8x16.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp862-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp863-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp863-8x16.fnt -r--r--r-- 1 bin bin 4864 Jun 3 1993 cp863-8x19.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp863-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp864-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp864-8x16.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp864-8x8.fnt -r--r--r-- 1 bin bin 3584 Jan 18 1996 cp865-8x14.fnt -r--r--r-- 1 bin bin 4096 Jan 18 1996 cp865-8x16.fnt -r--r--r-- 1 bin bin 4864 Jan 18 1996 cp865-8x19.fnt -r--r--r-- 1 bin bin 2048 Jan 18 1996 cp865-8x8.fnt -r--r--r-- 1 bin bin 3584 Jan 18 1996 cp866-8x14.fnt -r--r--r-- 1 bin bin 4096 Jan 18 1996 cp866-8x16.fnt -r--r--r-- 1 bin bin 2048 Jan 18 1996 cp866-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp880-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp880-8x16.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp880-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp881-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp881-8x16.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp881-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp882-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp882-8x16.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp882-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp883-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp883-8x16.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp883-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp884-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp884-8x16.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp884-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cp885-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cp885-8x16.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cp885-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cyrillic-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cyrillic_A-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cyrillic_A-8x16.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cyrillic_A-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cyrillic_B-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cyrillic_B-8x16.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cyrillic_B-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 cyrillic_C-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 cyrillic_C-8x16.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 cyrillic_C-8x8.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 decorative-8x16.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 english_arabic_persian_urdu-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 english_arabic_persian_urdu-8x16.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 english_arabic_persian_urdu-8x8.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 esperanto-8x16.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 esperanto_skewed-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 esperanto_skewed-8x16.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 finnish-8x14.fnt -r--r--r-- 1 bin bin 4096 Jul 14 1994 fresno-8x16.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 greek-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 greek-8x16.fnt -r--r--r-- 1 bin bin 1536 Jun 3 1993 greek-8x6.fnt -r--r--r-- 1 bin bin 1792 Jun 3 1993 greek-8x7.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 greek-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 greek_sanserif-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 greek_sanserif-8x16.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 greek_sanserif-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 handwritten-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 handwritten-8x16.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 handwritten_ugly-8x16.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 hebrew_KtavYad_thick-8x16.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 hebrew_KtavYad_thin-8x16.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 hebrew_Yossi-8x16.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 hebrew_big-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 hebrew_block_bold-8x16.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 hebrew_bold_lcd-8x16.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hebrew_calligraphic-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 hebrew_calligraphic-8x16.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 hebrew_handwritten-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hebrew_large_bold-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 hebrew_large_bold-8x16.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 hebrew_medium-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 hebrew_no_lowercase-8x16.fnt -r--r--r-- 1 bin bin 3584 Jan 17 1996 hebrew_old_new-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 hebrew_old_new-8x16.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 hebrew_sanserif-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 hebrew_ugly-8x16.fnt -r--r--r-- 1 bin bin 2560 Jun 3 1993 hercules-8x10.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules-8x14.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 hercules-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules_big_sanserif-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules_big_serif-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 hercules_big_serif-8x16.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules_block-8x14.fnt -r--r--r-- 1 bin bin 2560 Jun 3 1993 hercules_block_sanserif-8x10.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules_bold-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules_broadway-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules_computer-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules_courier-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules_futuristic-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules_greek-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules_hollow-8x14.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 hercules_italic-8x8.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules_lcd-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules_medieval-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules_sanserif-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 hercules_sanserif-8x16.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules_script-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules_slant-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hercules_standard-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 hercules_standard-8x16.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 hylas-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 icons-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 intex_arabic-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 intex_europe-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 intex_farsi-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 intex_gaelic-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 intex_greek-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 intex_hebrew-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 intex_polish-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 intex_russian-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 intex_turkish-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 intex_urdu-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 intex_yugoslavian-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 inverted-8x14.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 iso8859-2-8x14.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 iso8859-3-8x14.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 iso8859-4-8x14.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 iso8859-8x14.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 iso8859_cyrillic-8x14.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 iso8859_greek-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 italics-8x14.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 katakana-8x14.fnt -r--r--r-- 1 bin bin 4096 Aug 28 1993 katakana-8x16.fnt -r--r--r-- 1 bin bin 2560 Aug 28 1993 madrid-8x10.fnt -r--r--r-- 1 bin bin 4096 Jul 14 1994 medieval-8x16.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 modern-8x16.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 nethack-8x16.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 norway-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 norway_A-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 oldenglish-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 oldenglish-8x16.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 oldenglish_fancy-8x16.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 persian-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 persian-8x16.fnt -r--r--r-- 1 bin bin 4096 Aug 28 1993 police-8x16.fnt -r--r--r-- 1 bin bin 2560 Jun 3 1993 readable-8x10.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 readable-8x8.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 readable_7-8x16.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 readable_8-8x16.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 reverse-8x14.fnt -r--r--r-- 1 bin bin 2560 Jun 3 1993 rimrock-8x10.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 rimrock_bold-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 rimrock_thin-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 roman-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 roman-8x16.fnt -r--r--r-- 1 bin bin 4096 Aug 28 1993 roman_A-8x16.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 ruling_ESC0-8x14.fnt -r--r--r-- 1 bin bin 3584 Jan 17 1996 runic-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 runic-8x16.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 russian-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 russian-8x16.fnt -r--r--r-- 1 bin bin 2048 Jun 3 1993 russian-8x8.fnt -r--r--r-- 1 bin bin 4096 Aug 28 1993 sanserif_A-8x16.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 scrawl-8x16.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 scrawl_wiggly-8x16.fnt -r--r--r-- 1 bin bin 4096 Jul 14 1994 script-8x16.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 securites-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 smallcaps-8x14.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 smallcaps_A-8x14.fnt -r--r--r-- 1 bin bin 3072 Jun 3 1993 square-8x12.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 stretched_wide-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 subscript_superscript-8x16.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 superscript-8x16.fnt -r--r--r-- 1 bin bin 3584 Aug 28 1993 supplementary_ESC3-8x14.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 swiss-8x16.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 swiss_AV-8x16.fnt -r--r--r-- 1 bin bin 4096 Aug 28 1993 swiss_AV_A-8x16.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 swiss_block-8x16.fnt -r--r--r-- 1 bin bin 4096 Aug 28 1993 swiss_block_A-8x16.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 thai-8x14.fnt -r--r--r-- 1 bin bin 4096 Jul 14 1994 thai-8x16.fnt -r--r--r-- 1 bin bin 2560 Jun 3 1993 thin-8x10.fnt -r--r--r-- 1 bin bin 2560 Jan 18 1996 thin-8x8.fnt -r--r--r-- 1 bin bin 1792 Jun 3 1993 thin_ASCII-8x7.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 thin_script-8x14.fnt -r--r--r-- 1 bin bin 3584 Jun 3 1993 thin_smallcaps-8x14.fnt -r--r--r-- 1 bin bin 4096 Aug 28 1993 voynich-8x16.fnt -r--r--r-- 1 bin bin 4096 Jun 3 1993 wiggly-8x16.fnt From owner-freebsd-hackers Thu Aug 1 20:56:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA16599 for hackers-outgoing; Thu, 1 Aug 1996 20:56:10 -0700 (PDT) Received: from ginger.cmf.nrl.navy.mil (root@ginger.cmf.nrl.navy.mil [134.207.10.161]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA16594 for ; Thu, 1 Aug 1996 20:56:08 -0700 (PDT) Received: from excalibur.cmf.nrl.navy.mil (excalibur.cmf.nrl.navy.mil [134.207.6.17]) by ginger.cmf.nrl.navy.mil (8.7.5/8.7.3) with ESMTP id XAA05775; Thu, 1 Aug 1996 23:55:28 -0400 (EDT) Message-Id: <199608020355.XAA05775@ginger.cmf.nrl.navy.mil> To: "Eric L. Hernes" cc: Jason Thorpe , freebsd-hackers@FreeBSD.org Subject: Re: cvs commit: ports/devel/gcc11 - Imported sources In-reply-to: Your message of "Thu, 01 Aug 1996 16:01:39 CDT." <199608012101.QAA21994@jake.lodgenet.com> X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4 WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d gD\SW #]iN_U0 KUmOR.P<|um5yPkEpSD@*e` Date: Thu, 01 Aug 1996 23:55:50 -0400 From: Ken Hornstein Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Jason Thorpe writes: >> >>You mean the 6811 back-end isn't in the gcc master sources yet? What a >>drag! > >to be honest, I don't know. I found this stuff at a 6811 archive >and didn't think to look at the current gcc. It works with 2.6.3, >same as FBSD, which may be of some merrit, probably not though. Supposedly they contributed it to the FSF, but I haven't seen it appear in there yet. Judging from the response I got when I asked the original authors about the improvements I made to the assembler for that port, I think development on it has stopped. That's a shame, because the current pseudo-register scheme the 6811 backend uses ends up being rather inefficient. Good thing the optimizer is pretty good :-) --Ken From owner-freebsd-hackers Thu Aug 1 21:01:41 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA16914 for hackers-outgoing; Thu, 1 Aug 1996 21:01:41 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA16905 for ; Thu, 1 Aug 1996 21:01:33 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id NAA28419 for hackers@freebsd.org; Fri, 2 Aug 1996 13:39:56 +0930 From: Michael Smith Message-Id: <199608020409.NAA28419@genesis.atrad.adelaide.edu.au> Subject: minor patch to ppp's route.c To: hackers@freebsd.org Date: Fri, 2 Aug 1996 13:39:55 +0930 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just for the sake of ISP's using the user-mode ppp for large numbers of clients, it would be good to patch route.c : int GetIfIndex(name) char *name; { struct ifreq *ifrp; int s, len, elen, index; struct ifconf ifconfs; struct ifreq reqbuf[32]; and change 32 to something higher (at ~2 per interface, this runs out of steam at about 15 interfaces). -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Thu Aug 1 22:12:16 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA19966 for hackers-outgoing; Thu, 1 Aug 1996 22:12:16 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA19960 for ; Thu, 1 Aug 1996 22:12:13 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.7.5/8.7.3) id BAA02032 for freebsd-hackers@freebsd.org; Fri, 2 Aug 1996 01:12:11 -0400 (EDT) From: Charles Henrich Message-Id: <199608020512.BAA02032@crh.cl.msu.edu> Subject: Linux Willows on -current? To: freebsd-hackers@freebsd.org Date: Fri, 2 Aug 1996 01:12:10 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Okay I think I've found all the elf libraries I need from the slackware distributions, now when I run the xwin (willows windows emulator) I get: FatalAppExit: DPMI failure FatalAppExit: DPMI failure >From dmesg: Linux-emul(2026): open(/home/henrich/.twinrc, 0x0, 0x1b6) Linux-emul(2026): open returns error 0 Linux-emul(2026): newfstat(4, *) Linux-emul(2026): brk(0819c000) Linux-emul(2026): lseek(4, -26, 1) Linux-emul(2026): brk(0819c000) Linux-emul(2026): brk(0819e000) Linux-emul(2026): brk(0819f000) Linux-emul(2026): modify_ldt() not supported Linux-emul(2026): newselect(4, efbfcd8c, 0, 0, 0) Linux-emul(2026): real select returns 0 Linux-emul(2026): newselect_out -> 0 Is it choking on the modify_ldt? -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Thu Aug 1 23:51:46 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA23351 for hackers-outgoing; Thu, 1 Aug 1996 23:51:46 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA23199 for ; Thu, 1 Aug 1996 23:45:36 -0700 (PDT) Received: (from rbezuide@localhost) by zibbi.mikom.csir.co.za (8.7.5/8.7.3) id IAA01827 for freebsd-hackers@freebsd.org; Fri, 2 Aug 1996 08:44:57 +0200 (SAT) From: R Bezuidenhout Message-Id: <199608020644.IAA01827@zibbi.mikom.csir.co.za> Subject: h2ph and machine/* To: freebsd-hackers@freebsd.org Date: Fri, 2 Aug 1996 08:44:56 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL16 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all I am using a perl script that is trying to use syslog for its logging. It includes /usr/share/perl/syslog.ph which in turn tries to include /usr/share/perl/machine/ansi.ph In /usr/share/perl/syslog.ph if (defined &KERNEL) { } else { require 'machine/ansi.ph'; require 'sys/cdefs.ph'; } But there is no machine directory in /usr/share/perl .. only a sys. I had a look and in the Makefile in /usr/src/gnu/usr.bin/perl/x2p and there h2ph is called: h2ph * sys/* ??? Why isn't machine/* added to this list ? Is there a reason for this ... if there isn't :) can someone please add it :) I see this in 2.1.5 and CURRENT Thanx Reinier -- ######################################################################## # # # Reinier Bezuidenhout Company: Mikomtek CSIR, ZA # # # # Network Engineer - NetSec development team # # # # Current Projects: NetSec - Secure Platform firewall system # # http://www.mikom.csir.co.za # # # # E-mail: rbezuide@mikom.csir.co.za # # # ######################################################################## From owner-freebsd-hackers Fri Aug 2 00:35:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA24710 for hackers-outgoing; Fri, 2 Aug 1996 00:35:19 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA24705 for ; Fri, 2 Aug 1996 00:35:17 -0700 (PDT) Received: from korin.warman.org.pl ([148.81.168.248]) by mail.crl.com with SMTP id AA00605 (5.65c/IDA-1.5 for ); Fri, 2 Aug 1996 00:34:16 -0700 Received: (from abial@localhost) by korin.warman.org.pl (8.7.5/8.7.3) id IAA06051; Fri, 2 Aug 1996 08:47:24 +0200 (MET DST) Date: Fri, 2 Aug 1996 08:47:24 +0200 (MET DST) From: Andrzej Bialecki To: freebsd-hackers@FreeBSD.ORG Subject: 2.1.5R sysinstall Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi! Yesterday as I was installing 2.1.5R I noticed the same bug (feature?) of sysinstall as in 2.0.5R. When using label editor I choose an (A) option (automatic selection of filesystems sizes), and then I looked at the numbers and wanted to slightly change them to suit my specific needs. So I went on and deleted some (not all) entries to free up space. Then I started to assign them anew, and at the last chunk I've simply chosen ``the rest'' of space by simply pressing Enter, when asked about size of the filesystem. And then this fella tells me something like: "total numbers of blocks exceeded" or "size too big" - I don't remember exactly. Anyway, it miscalculated ``the rest'' of free space. It didn't help also when I deleted all already assigned space and started again - it was still complaining. Finally, I quit the label editor and entered it again. This time I manually assigned sizes, and encountered no problems. So, that's it. Andy From owner-freebsd-hackers Fri Aug 2 01:39:03 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA27284 for hackers-outgoing; Fri, 2 Aug 1996 01:39:03 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA27261; Fri, 2 Aug 1996 01:38:49 -0700 (PDT) Received: from localhost (dev@localhost) by fgate.flevel.co.uk (8.7.5/8.6.9) with SMTP id JAA19320; Fri, 2 Aug 1996 09:33:42 +0100 (BST) Date: Fri, 2 Aug 1996 09:33:41 +0100 (BST) From: Developer To: Tom Samplonius cc: Gary Palmer , Tony Kimball , hackers@FreeBSD.org Subject: Re: Migrating BSDI 1.1 Passwords In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > Now you've done it. They have to cut off your sup feed. And probably > > > have to hack supfilesrv to special-case export-restricted directories > > > in the long run (wasted manpower) or worse yet cut off all non-US > > > domains from sup.freebsd.org -- otherwise they are not excercising due > > > diligence and are subject to seizure/lien/forfeiture/criminal action. > > > > It's ok banning `*.uk', for example, but what happens (for example) if > > the person wanting the code works for `demon.net' or `xara.net', both > > of whom are in the UK, and both of whom have US style addresses? We > > can't win :-( > > Yes, you can. There are only a limited number of netblocks allocated to > the UK, and all of those could be banned. > > Apparently, gatekeeper.dec.com has been using access control via a > database of netblocks for a few years now for this exact purpose (or maybe > this has changed recently). Okay, so you ban all UK sites from suping the crypto source, but it becomes pretty pointless - you would have to remove it from the ftp sites as well or hack the ftp daemon. The all UK users have to do is get someone in the us to email it to them, or use a US account and then transfer it from there to the UK. Still, you are not gaining anything - the crypto sources will appear on non us sites, which means they have been exported somehow. Is there not a decent sup site for freebsd in the UK? Regards, Trefor S. From owner-freebsd-hackers Fri Aug 2 04:20:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA03190 for hackers-outgoing; Fri, 2 Aug 1996 04:20:34 -0700 (PDT) Received: from DATAPLEX.NET (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA03181 for ; Fri, 2 Aug 1996 04:20:27 -0700 (PDT) Received: from 199.183.109.242 by DATAPLEX.NET with SMTP (MailShare 1.0fc5); Fri, 2 Aug 1996 06:19:13 -0600 Message-ID: Date: 2 Aug 1996 06:18:51 -0500 From: "Richard Wackerbarth" Subject: Re: 2.1.5R sysinstall To: "Andrzej Bialecki" Cc: "freebsd-hackers@FreeBSD.ORG" X-Mailer: Mail*Link PT/Internet 1.6.0 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Yesterday as I was installing 2.1.5R I noticed the same bug (feature?) of > sysinstall as in 2.0.5R. > > When using label editor I choose an (A) option (automatic selection of > filesystems sizes), and then I looked at the numbers and wanted to > slightly change them to suit my specific needs. > > So I went on and deleted some (not all) entries to free up space. Then I > started to assign them anew, and at the last chunk I've simply chosen > ``the rest'' of space by simply pressing Enter, when asked about size of > the filesystem. > > And then this fella tells me something like: "total numbers of blocks > exceeded" or "size too big" - I don't remember exactly. Anyway, it > miscalculated ``the rest'' of free space. > > It didn't help also when I deleted all already assigned space and started > again - it was still complaining. Finally, I quit the label editor and > entered it again. This time I manually assigned sizes, and encountered no > problems. > > So, that's it. Yep. I "found" that one also. I also tried allocating something less than all and still hit the problem. I'm guessing that the allocation doesn't properly "erase" things. -- Richard Wackerbarth rkw@dataplex.net From owner-freebsd-hackers Fri Aug 2 04:34:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA03531 for hackers-outgoing; Fri, 2 Aug 1996 04:34:34 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA03525 for ; Fri, 2 Aug 1996 04:34:21 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id NAA02655 for ; Fri, 2 Aug 1996 13:30:04 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id NAA13206 for freebsd-hackers@freefall.cdrom.com; Fri, 2 Aug 1996 13:17:24 +0200 Date: Fri, 2 Aug 1996 13:17:24 +0200 From: "Christoph P. Kukulies" Message-Id: <199608021117.NAA13206@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: sendmail (8bit char problem?) Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk It is happening more and more these days that we get mail originating from non-unix systems causing cumber to unix mail-readers like elm,elm+mime, netscape, etc. Just happened to me in this list the other day that someone sent a ms-tnef appendix which neither netscape nor elm+mime could parse. (probably due to the lack of an appropriate filter) In the following case for which I'm begging this list for support I'm receiving mail on gil (running 2.1.0) which cannot be processed by elm+mime [ELM 2.4ME+ PL16 (25)]. Could some sendmail expert have a look at it please. From the headers I understand that the sending host is directly contacting my sendmail on gil: (the contents of the following digest contains some discussion on the topic as well) --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de |From samba@arvidsjaur.anu.edu.au Fri Aug 2 13:00:03 1996 |Received: from arvidsjaur (arvidsjaur.anu.edu.au [150.203.160.29]) by |gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) with ESMTP id MAA12962 |for ; Fri, 2 Aug 1996 12:59:44 +0200 |X-Warning: Original message contained 8-bit characters, however during | the SMTP transport session the receiving system was unable to | announce capability of receiving 8-bit SMTP (RFC 1425-1428), | and as this message does not have MIME headers (RFC 1341) to | enable encoding change, we had very little choices. |X-Warning: We ASSUME it is less harmfull to add the MIME headers, and | convert the text to Quoted-Printable, than not to do so, | and to strip the message to 7-bits.. (RFC 1428 Appendix A) |MIME-Version: 1.0 |Content-Type: TEXT/PLAIN; charset=UNKNOWN-8BIT |Content-Transfer-Encoding: QUOTED-PRINTABLE |Received: by arvidsjaur.anu.edu.au via suspension id <66010-186>; Fri, |2 Aug 1996 20:34:49 +1000 |Received: from arvidsjaur ([127.0.0.1]) by arvidsjaur.anu.edu.au with |SMTP id <65147-186>; Fri, 2 Aug 1996 17:23:18 +1000 |Errors-To: listproc-errors@arvidsjaur.anu.edu.au |Reply-To: samba@arvidsjaur.anu.edu.au |Originator: samba@samba.anu.edu.au |Sender: samba@arvidsjaur.anu.edu.au |Precedence: bulk |From: samba@arvidsjaur.anu.edu.au |To: Multiple recipients of list |Subject: SAMBA digest 1013 |X-Listprocessor-Version: 6.0 -- ListProcessor by Anastasios Kotsikonas |X-Comment: Discussion of Samba software package |Message-Id: <96Aug2.172318+1000est.65147-186+1752@arvidsjaur.anu.edu.au> |Date: Fri, 2 Aug 1996 16:14:07 +1000 |Status: RO | | SAMBA Digest 1013 | |For information on unsubscribing and on what is appropriate to post to |this list see ftp://samba.anu.edu.au/pub/lists/samba.txt | |Topics covered in this issue include: | | 1) Re: Quoted-Printable | by jem@mystery.milleredp.com (John Edward Miller) | 2) Re: Problem with Digest 1010 - is it just me? | by "Christoph P. Kukulies" | 3) Re: Problem with Digest 1010 - is it just me? | by Jochen Friedrich | 4) SAMBA ON SCO | by CBADET@aol.com | 5) Re: Birddroppings | by Rask Ingemann Lambertsen | 6) Re: SAMBA ON SCO | by bill@celestial.com (Bill Campbell) | 7) SAMBA ON SCO UNIX 3.4V4.2 | by CBADET@aol.com | 8) Re: Birddroppings | by DAVID GAUDINE | 9) Samba on linux AND be able to check mail | by Chris Boller | 10) Max. Number of Clients Per Samba Host | by Hong Trac | |---------------------------------------------------------------------- | |Date: Wed, 31 Jul 1996 23:34:59 -0700 (PDT) |From: jem@mystery.milleredp.com (John Edward Miller) |To: samba@arvidsjaur.anu.edu.au |Subject: Re: Quoted-Printable |Message-ID: <199608010633.XAA06018@mystery.milleredp.com> | |> . this is standard Qouted-Printable Encoding in MIME-Mails.. |> You should look into the setup of your Mailer (MUA) if you can enable |> automatic MIME-Decoding or switch to a Mailer which is MIME-capable. |=20 |For individual messages that's true but for digests the digest software= | would |have to deal with it since methinks the resulting digest is not sent as |content-type quoted-printable. | |Then we would try to get list software to discard MS-TNEF bodyparts sen= |t out by |ragged MS mail products, etc... | |John. | | | |------------------------------ | |Date: Thu, 1 Aug 1996 10:17:23 +0200 |From: "Christoph P. Kukulies" |To: chris@suite.sw.oz.au |Cc: samba@anu.edu.au |Subject: Re: Problem with Digest 1010 - is it just me? |Message-ID: <199608010817.KAA06804@gilberto.physik.rwth-aachen.de> | | |Of the last 10 or so digests about the half was unreadable due to |some 8 bit stuff of some such which my 'elm' mail reader |discovered as Mime encapsulated but trying to 'v'iew it |didn't show anything. I was blaming it to my elm setup |but now that you are saying it I doubt that it's on my side. | |--Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de | | |------------------------------ | |Date: Thu, 1 Aug 1996 10:37:48 +0200 (MESZ) |From: Jochen Friedrich |To: "Christoph P. Kukulies" |Cc: Multiple recipients of list |Subject: Re: Problem with Digest 1010 - is it just me? |Message-ID: | |Hi Christoph, | |> Of the last 10 or so digests about the half was unreadable due to |> some 8 bit stuff of some such which my 'elm' mail reader |> discovered as Mime encapsulated but trying to 'v'iew it |> didn't show anything. I was blaming it to my elm setup |> but now that you are saying it I doubt that it's on my side. | |Apparently, one "sendmail" in the path to you is either a very old one = |or |configured to only accept 7bit mails. The problam starts as soon as a |message contains 8bit characters (like i.e. german umlauts). In this ca= |se |modern sendmails (8.7 or better) try to compensate this by adding a MIM= |E |header and flagging it as "UNKNOWN-8BIT" (sendmail really has to chance= | to |know what character set the author originally used). You may check the |complete mail headers where in the path this conversion was done (the M= |IME |header gets inserted below the Received header of the machine which onl= |y |accepts 7 bit). | |Cheers, |Jochen |-- |Jochen Friedrich, eurjof@eur.sas.com |"Few things are as much fun as 'accidentally' rm -Rf'ing /usr..." | -- Matt McLeod | | | |------------------------------ | |Date: Thu, 1 Aug 1996 08:54:01 -0400 |From: CBADET@aol.com |To: samba@arvidsjaur.anu.edu.au |Subject: SAMBA ON SCO |Message-ID: <960801085401_169329470@emout19.mail.aol.com> | |Hello ! | |I try to install samba on sco unix 3.2v4.2, but i have some problems to |compile samba : | |i don't have the request file netdb.h. | |Can somebody help me ? |thanks. | | |------------------------------ | |Date: 01 Aug 96 14:47:02 +0100 ||From: Rask Ingemann Lambertsen |To: samba@arvidsjaur.anu.edu.au |Subject: Re: Birddroppings |Message-ID: | |On 31 Jul 1996 16:12 +1000 (+0900), degraaf@vnet.net wrote to me: | |> Date: Tue, 30 Jul 1996 14:12:23 -0400 (EDT) |> From: degraaf@vnet.net |> To: samba@arvidsjaur.anu.edu.au |> Subject: Birddroppings |> Message-ID: <199607301812.OAA21631@katie.vnet.net> | |> This isn't purely samba related, but is probably list-server related. | |> Does anyone else find the extra characters that show up in posts |> annoying? I'm referring to the "=3D20" at ends of lines and "3D" |> following =3D's. They really make it hard (for me) to read. |> Here's an egregious example from a recent post of=20 |> someone's smb.conf fragment: | |> [homes]=3D20 |> comment =3D3D This is your UNIX directory |> writable =3D3D yes=3D20 |> create mode =3D3D 750=3D20 |> ;=3D20 |> ; A publicly accessible directory,=3D20 | |> I don't know how this shows up for you; on my screen I see "=3D20" |> at the end of each line except the second, and "3D" after the "=3D" o= |n |> lines 2, 3 and 4. Clearly, these were not intended. | |I don't get any of these :-) | |> I had thought these were due to use of an inept MS editor, and smugly |> thought that since I use elm and vi I could never be guilty of such | ^^^ |> ugly stuff. | |Closing in on the problem, I think. | |> Imagine my surprise when my recent post appeared, decorated with a fe= |w |> of these birddroppings. | |> How can this happen??? Is the listserver doing it? |> Can it be fixed? Do I need to change something? | |It looks like either your mail system doesn't support ESMTP and/or |your mailer doesn't know about MIME. AFAIK, elm doesn't support MIME, |so that is most likely your problem. In any case, maybe it is time for |an upgrade? | |All this happens because the inventors of SMTP didn't think it was |necessary to support 8-bit characters. Sigh. | |Regards, | |/=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= |=AF=AF=AF=AF=AF=AF=AF=AFT=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF= |=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF\ || Rask Ingemann Lambertsen | E-mail: rask@kampsax.dtu.dk = | | || Amiga GNU CC README maintainer | WWW: http://www.gbar.dtu.dk/~c948374= |/ | || Try my finger-WWW gateway at http://www.bbar.dtu.dk/~c948374/f.cgi = | | || Keyboard error: and are stuck - press to continue = | | | | |------------------------------ | |Date: Thu, 1 Aug 1996 08:52:17 -0700 (PDT) |From: bill@celestial.com (Bill Campbell) |To: CBADET@aol.com |Cc: samba@arvidsjaur.anu.edu.au |Subject: Re: SAMBA ON SCO |Message-ID: | |> |>Hello ! |> |>I try to install samba on sco unix 3.2v4.2, but i have some problems t= |o |>compile samba : |> |>i don't have the request file netdb.h. |> |It sounds like you have an SCO release prior to Release 5 and you |don't have either the ODT development system or the TCP/IP development |system so you don't have the sockets libraries and headers. | |We have compiled SAMBA available on ftp.celestial.com : | /pub/sco-ports/unix/samba-1.9.15p8.tar.gz | /pub/sco-ports/unix_3_2v5/samba-1.9.15p8.tar.gz | |The first is for 3.2v4.? and the second for Release 5. | |Bill |-- |INTERNET: bill@Celestial.COM Bill Campbell; Celestial Systems, Inc. |UUCP: camco!bill PO Box 820; 2835 82nd Avenue S.E. S-100 |FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236= |-1676 |URL: http://www.celestial.com/ | |The very powerful and the very stupid have one thing in common. |Instead of altering their views to fit the facts, they alter the facts |to fit their views ... which can be very uncomfortable if you happen to |be one of the facts that needs altering. | -- Doctor Who, "Face of Evil" | | |------------------------------ | |Date: Thu, 1 Aug 1996 13:02:33 -0400 |From: CBADET@aol.com |To: samba@arvidsjaur.anu.edu.au |Subject: SAMBA ON SCO UNIX 3.4V4.2 |Message-ID: <960801130233_250568495@emout17.mail.aol.com> | |In a message dated 96-08-01 08:51:29 EDT, you write: | |<< Subj: SAMBA ON SCO | Date: 96-08-01 08:51:29 EDT | From: CBADET |samba@arvidsjaur.anu.edu.au |=20 | Hello ! |=20 | I try to install samba on sco unix 3.2v4.2, but i have some problems t= |o |compile samba : |=20 | i don't have the request file netdb.h. |=20 | Can somebody help me ? | thanks. >> | | | |------------------------------ | |Date: Thu, 1 Aug 1996 13:36:12 -0400 (EDT) |From: DAVID GAUDINE |To: rask@kampsax.dtu.dk |Subject: Re: Birddroppings |Message-ID: <199608011736.NAA02188@alcor.concordia.ca> | | |I'm not one of the ones who brought this up before, but just to show yo= |u |exactly what your .signature looks like to me, I've attached it below. |I doubt that this has anything to do with the inventors of SMTP, more l= |ikely |we're not using the same character set. | |----- | |All this happens because the inventors of SMTP didn't think it was |necessary to support 8-bit characters. Sigh. | |Regards, | |/\257\257\257\257\257\257\257\257\257\257\257\257\257\257\257\257\257\2= |57\257\257\257\257\257\257\257\257\257\257\257\257\257\257\257\257\257\= |257\257\257\257\257\257\257\257\257\257\257\257\257\257\257\257\257\257= |\257\257\257\257\257\257\257\257\257\257\257\257\257\257\257\257\257\25= |7 || Rask Ingemann Lambertsen | E-mail: rask@kampsax.dtu.dk = | | || Amiga GNU CC README maintainer | WWW: http://www.gbar.dtu.dk/~c948374= |/ | || Try my finger-WWW gateway at http://www.bbar.dtu.dk/~c948374/f.cgi = | | || Keyboard error: and are stuck - press to continue = | | | | |------------------------------ | |Date: Thu, 1 Aug 1996 21:09:50 +0100 (GMT+0100) |From: Chris Boller |To: samba@anu.edu.au |Subject: Samba on linux AND be able to check mail |Message-ID: | |Hi! | |I've got a WfWg network connected to a linux box which also checks mail= |. |This setup works if in /etc/hosts the name corresponds to the 192.168.x= |.x |address for the local network, but if it's set to 158.152.x.x (for the |dialup mail) the other clients cannot "find" the server. I've scoured |the FAQs but no mention of how to do this - maybe it's common sense :^) |(Mail works when set to the dialin but not for the LAN and vice-versa.) | |All help will be appreciated | |Thanks | |Chris | | | | |------------------------------ | |Date: Thu, 1 Aug 1996 17:04:39 -0600 (MDT) |From: Hong Trac |To: samba@arvidsjaur.anu.edu.au |Subject: Max. Number of Clients Per Samba Host |Message-ID: | |Hi Samba users, | |I have been using Samba for 8 months and it works great in our environm= |ent. |As our number of clients grows up to 90, many users start experiencing=20 |network connection problems to the samba server. For example, Win95 us= |ers |would get messages like: | | "Connecting H: to \\sambahost\userfiles" | | "The following error occurred while connecting to | \\sambahost\userfiles. | Permanent connection not available. | Do you want to restore this connection the next time you log on?" | |If users select "Yes" and go to "My Computer" to access those "off-line= |" |network drives a few times then they might be re-connected. WinNT user= |s |also get similar symtomps. If all fail then rebooting samba host helps |until the next time. | |I do not recall seeing his problem when we had less than ~ 70 PCs. | |I just wonder if you have seen this in a similar environment. Is 90 |PC clients too many for a samba host (configuration at the end)? | |Thanks in advance for your inputs, | |H Trac | |*** Configuration: | | - One samba host: UltraSparc 1 with Solaris 2.5, 192 MB RAM. | - Samba Version 1.9.15p6, runs as daemon (approx. 90 smbd run | at a given time, server load usually at 0.5 to 1.5) | - Clients: ~ 90 PCs (Win95, WinNT) with Pentium or 486DX33+. | Max. simultaneous clients: 90. | |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D |Hong Trac Valmet Automation (Canada) Ltd. |Network Administrator Calgary, Alberta, Canada. |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D | | | |------------------------------ | |End of SAMBA Digest 1013 |************************ | From owner-freebsd-hackers Fri Aug 2 04:56:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA04232 for hackers-outgoing; Fri, 2 Aug 1996 04:56:15 -0700 (PDT) Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.109.160]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA04227 for ; Fri, 2 Aug 1996 04:56:13 -0700 (PDT) Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id GAA27157; Fri, 2 Aug 1996 06:53:13 -0500 From: Joe Greco Message-Id: <199608021153.GAA27157@brasil.moneng.mei.com> Subject: Re: minor patch to ppp's route.c To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Fri, 2 Aug 1996 06:53:12 -0500 (CDT) Cc: hackers@freebsd.org In-Reply-To: <199608020409.NAA28419@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Aug 2, 96 01:39:55 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Just for the sake of ISP's using the user-mode ppp for large numbers of > clients, it would be good to patch route.c : > > int > GetIfIndex(name) > char *name; > { > struct ifreq *ifrp; > int s, len, elen, index; > struct ifconf ifconfs; > struct ifreq reqbuf[32]; > > and change 32 to something higher (at ~2 per interface, this runs out of > steam at about 15 interfaces). I believe I posted a suggestion once to raise this to something like 1024 :-) which I had done on several boxes. ... JG From owner-freebsd-hackers Fri Aug 2 06:35:41 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA07457 for hackers-outgoing; Fri, 2 Aug 1996 06:35:41 -0700 (PDT) Received: from walkabout.asstdc.com.au (root@walkabout.asstdc.com.au [202.12.127.73]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA07450 for ; Fri, 2 Aug 1996 06:35:32 -0700 (PDT) Received: (from imb@localhost) by walkabout.asstdc.com.au (8.7.5/BSD4.4) id XAA09607 Fri, 2 Aug 1996 23:34:49 +1000 (EST) From: michael butler Message-Id: <199608021334.XAA09607@walkabout.asstdc.com.au> Subject: Re: Migrating BSDI 1.1 Passwords To: dev@fgate.flevel.co.uk (Developer) Date: Fri, 2 Aug 1996 23:34:49 +1000 (EST) Cc: hackers@freebsd.org In-Reply-To: from Developer at "Aug 2, 96 09:33:41 am" X-Comment: Phone 0419-240-180, International +61-419-240-180 X-Comment: finger imb@asstdc.com.au for PGP public key X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Okay, so you ban all UK sites from suping the crypto source, but it > becomes pretty pointless - you would have to remove it from the ftp sites > as well or hack the ftp daemon. It most certainly is *not* pointless - _responsible_ people abide by the law as far as they are able. > The all UK users have to do is get someone in the us to email it to them, > or use a US account and then transfer it from there to the UK. And in so doing, you may be _responsible_ (there's that word again) for the removal of someone's liberty. Export of cryptographic software from the US is a punishable offence. I don't wish to argue the politics of this since I think we all agree that the legislation it falls under is _way_ out of date, however, it _is_ the law and _is_ enforceable. Until that changes (and we all hope that it's sooner rather than later), please protect other peoples' freedom by respecting the laws under which they must live. > Still, you are not gaining anything - the crypto sources will appear on > non us sites, which means they have been exported somehow. If you cared to read the copyrights and headers in the non-US versions, they were written _outside_ the US .. some of it in Australia, other parts in Europe and South Africa. > Is there not a decent sup site for freebsd in the UK? If there isn't one in the UK, hit one in Europe or clone your own from .za but do *not* sup the "secure" packages from any site in the US or Canada. Oh .. as a side note .. mere _possession_ of strong cryptographic software in France without government approval is presently a punishable offense .. good for a gaol term, I'm told. It matters and you should care .. michael From owner-freebsd-hackers Fri Aug 2 06:54:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA08025 for hackers-outgoing; Fri, 2 Aug 1996 06:54:33 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA07999 for ; Fri, 2 Aug 1996 06:54:29 -0700 (PDT) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id GAA00394 for ; Fri, 2 Aug 1996 06:54:28 -0700 (PDT) Message-Id: <199608021354.GAA00394@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: hackers@freebsd.org Subject: m_copym crash Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 02 Aug 1996 06:54:27 -0700 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a tcl script crashing my system here at the close of a tcp connection. Basically, when the file gets close and it calls a series of tcp close related functions, the system crashes at "m_copym 3" Has anyone seen this before on -current? Tnks, Amancio ---- struct mbuf * m_copym(m, off0, len, wait) register struct mbuf *m; int off0, wait; register int len; { register struct mbuf *n, **np; register int off = off0; struct mbuf *top; int copyhdr = 0; if (off < 0 || len < 0) panic("m_copym 1"); if (off == 0 && m->m_flags & M_PKTHDR) copyhdr = 1; while (off > 0) { if (m == 0) panic("m_copym 2"); if (off < m->m_len) break; off -= m->m_len; m = m->m_next; } np = ⊤ top = 0; while (len > 0) { if (m == 0) { if (len != M_COPYALL) panic("m_copym 3"); **** crash site ***** break; } From owner-freebsd-hackers Fri Aug 2 07:38:19 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA10516 for hackers-outgoing; Fri, 2 Aug 1996 07:38:19 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA10511 for ; Fri, 2 Aug 1996 07:38:16 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id JAA08551; Fri, 2 Aug 1996 09:38:13 -0500 (EST) X-Authentication-Warning: fallout.campusview.indiana.edu: jfieber owned process doing -bs Date: Fri, 2 Aug 1996 09:38:12 -0500 (EST) From: John Fieber X-Sender: jfieber@fallout.campusview.indiana.edu To: Charles Henrich cc: freebsd-hackers@freebsd.org Subject: Re: Linux Willows on -current? In-Reply-To: <199608020512.BAA02032@crh.cl.msu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 2 Aug 1996, Charles Henrich wrote: > Is it choking on the modify_ldt? do you have USER_LDT in your kernel config? -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-hackers Fri Aug 2 08:35:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA13369 for hackers-outgoing; Fri, 2 Aug 1996 08:35:04 -0700 (PDT) Received: from eac.iafrica.com (196-7-101-145.iafrica.com [196.7.101.145]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA13351 for ; Fri, 2 Aug 1996 08:34:33 -0700 (PDT) Received: (from rnordier@localhost) by eac.iafrica.com (8.6.12/8.6.12) id RAA00207; Fri, 2 Aug 1996 17:31:09 +0200 From: Robert Nordier Message-Id: <199608021531.RAA00207@eac.iafrica.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: terry@lambert.org (Terry Lambert) Date: Fri, 2 Aug 1996 17:31:07 +0200 (SAT) Cc: hackers@freebsd.org In-Reply-To: <199608020043.RAA04852@phaeton.artisoft.com> from "Terry Lambert" at Aug 1, 96 05:43:14 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert wrote: > When a name is passed in, it is either capable of being a valid > 8.3 name or it isn't. If it is, then the name is looked up in > the 8.3 name space. For an 8.3 name, the LFN will always be > the same as the 8.3 name. There is the complication of legacy directory entries (or those created when running Win95 in "MS-DOS 7" mode -- without "Windows" loaded.) For example, "FILE ONE.TXT" is "capable of being a valid 8.3 name" (in the sense that it can legally occur in the short name space, and -- having no LFN -- must be looked up there.) However, when created in a DOS window, it becomes "FILEON~1.TXT". By this criterion of what constitutes an 8.3 name, the LFN won't necessarily "always be the same as the 8.3 name". Incidentally, this anomaly in the handling of legal 8.3 names allows a situation to develop where the same name exists in the short name space and in the long name space, but refers to different files: RUNME~1 COM 3,380 06-17-94 1:03a RUN ME.COM RUN ME COM 15,118 10-18-91 1:01a RUN ME.COM > Note that the 8.3 name is a case > insensitive name; a name "Foo" and "foo" are identical for case > insensitive lookup/case sensitive storage; they are the valid > short name "FOO". > > The short name lookup will match or fail to match. In no case is > it possible for a valid short name to have a long name form that > collides with another long name form. Short names are looked up > in the short name space and in the long name space. The long name > space lookup is done because of the direction collisions are > handled. I gather, though, that the long name space lookup is done first. (And, because of this -- in the above example -- Win95 and DOS will find and run different files.) > In the LFN case, the lookup is done in the long name space. This > is because any LFN that comes into lookup will have an LFN form > if it has been previously stored. In the LFN case, the short name > is not examined. OK. Which can actually break legacy DOS applications that use > 8.3 names to refer to existing files. Previously "Description.ASCII" would find "DESCRIPT.ASC" in the short (ie. only) name space, but this no longer works without converting the directory entry to create an associated LFN. > > The long file name that does not match in the create case will be > cannonized to a tentative short name by searching for a '.' seperated > suffix from the right side of the LFN moving left. > > The long name up to the first period, or 6 characters, will be copied > moving right. However, the order in which this is done is important. For example, ".profile" results in "PROFIL~1" not "~1.PRO". There is also other name mangling: for instance, the stripping of space characters, and replacement of illegal 8.3 name characters: eg. "c++.exe" -> "C__~1.EXE". > > The last two characters preceeding the suffix are replaced with a > provisional "tail" value: "~1". > > Thus: > > ThisIsALong.Named.Document -> THISIS~1.DOC > VeryLongName.TXT -> VERYLO~1.TXT > Short.doc -> SHORT.DOC (8.3 name on input) > > > The tail is permitted to increment based on collision, "eating" the > characters leftward. But only if "eating" is necessary. Thus, following "FILE~9.TXT" would be "FILE~10.TXT", not "FIL~10.TXT". > Windows95 and WindowsNT have support routines > for VFAT that do all of this for you. > > For instance, "VeryLongName.TXT" has a tentative short name with > a provisional numeric "tail" of "VERYLO~1.TXT". Now if there already > exists a "VERYLO~9.TXT", the next allowable post-collision value is > "VERYL~10.TXT". > > This requires that your pattern match match the suffix (".TXT"), then > go through matching "VERLO" for all possible tail vales that already > exist. This requires a full traversal of the short name space for the > directory. Windows95 wimps out and uses a "max" value on the tail, > so if you had "VERYLO~8.TXT" but no "VERYLO~1.TXT", it would still > end up with the post-collision name "VERYLO~9.TXT". Apparently this isn't (at least any longer) the case: VERYLO~8.TXT VeryLongName8.TXT copy VeryLongName8.TXT VeryLongNameToo.TXT VERYLO~1.TXT VeryLongNameToo.TXT VERYLO~8.TXT VeryLongName8.TXT (To use attempt to wimp out and rely on a "max" value would only invite problems, since a "~9999999.TXT" could be present.) Thanks for all this, Terry. Incidentally, I have a note somewhere relating to VFAT on Linux and a "-posix" mount option. (Apparently it is intended to enable full case sensitivity for LFNs, allowing eg. "longfilename" and "LongFileName" to coexist. And isn't currently fully implemented.) Any comments on the desirability of this? -- Robert Nordier From owner-freebsd-hackers Fri Aug 2 09:06:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA14482 for hackers-outgoing; Fri, 2 Aug 1996 09:06:25 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA14477 for ; Fri, 2 Aug 1996 09:06:19 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.7.5/8.7.3) id MAA00657; Fri, 2 Aug 1996 12:06:13 -0400 (EDT) From: Charles Henrich Message-Id: <199608021606.MAA00657@crh.cl.msu.edu> Subject: Re: Linux Willows on -current? To: jfieber@indiana.edu (John Fieber) Date: Fri, 2 Aug 1996 12:06:13 -0400 (EDT) Cc: freebsd-hackers@freebsd.org In-Reply-To: from John Fieber at "Aug 2, 96 09:38:12 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > On Fri, 2 Aug 1996, Charles Henrich wrote: > > > Is it choking on the modify_ldt? > > do you have USER_LDT in your kernel config? Yep, but the linux emulator doesnt support the modify_ldt routine.. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-hackers Fri Aug 2 10:10:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA17017 for hackers-outgoing; Fri, 2 Aug 1996 10:10:28 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA17010 for ; Fri, 2 Aug 1996 10:10:26 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA05897; Fri, 2 Aug 1996 10:07:51 -0700 From: Terry Lambert Message-Id: <199608021707.KAA05897@phaeton.artisoft.com> Subject: Re: anyone working on upgrading the msdosfs to NetBSD levels? To: rnordier@iafrica.com (Robert Nordier) Date: Fri, 2 Aug 1996 10:07:51 -0700 (MST) Cc: terry@lambert.org, hackers@freebsd.org In-Reply-To: <199608021531.RAA00207@eac.iafrica.com> from "Robert Nordier" at Aug 2, 96 05:31:07 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Terry Lambert wrote: > > > When a name is passed in, it is either capable of being a valid > > 8.3 name or it isn't. If it is, then the name is looked up in > > the 8.3 name space. For an 8.3 name, the LFN will always be > > the same as the 8.3 name. > > There is the complication of legacy directory entries (or those > created when running Win95 in "MS-DOS 7" mode -- without "Windows" > loaded.) [ ... ] I just noticed this was going to the list. I will spare the rest of you the details and respond to Robert privately... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Fri Aug 2 10:43:10 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA18863 for hackers-outgoing; Fri, 2 Aug 1996 10:43:10 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA18855 for ; Fri, 2 Aug 1996 10:43:07 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id TAA25213; Fri, 2 Aug 1996 19:43:03 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id TAA32639; Fri, 2 Aug 1996 19:42:13 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.5/keltia-uucp-2.8) id TAA10919; Fri, 2 Aug 1996 19:14:50 +0200 (MET DST) Message-Id: <199608021714.TAA10919@keltia.freenix.fr> Date: Fri, 2 Aug 1996 19:14:50 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: kuku@gilberto.physik.rwth-aachen.de (Christoph P. Kukulies) Cc: freebsd-hackers@freefall.freebsd.org Subject: Re: sendmail (8bit char problem?) In-Reply-To: <199608021117.NAA13206@gilberto.physik.rwth-aachen.de>; from Christoph P. Kukulies on Aug 2, 1996 13:17:24 +0200 References: <199608021117.NAA13206@gilberto.physik.rwth-aachen.de> X-Mailer: Mutt 0.38 Mime-Version: 1.0 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Christoph P. Kukulies: > |From samba@arvidsjaur.anu.edu.au Fri Aug 2 13:00:03 1996 > |Received: from arvidsjaur (arvidsjaur.anu.edu.au [150.203.160.29]) by > |gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) with ESMTP id MAA12962 > |for ; Fri, 2 Aug 1996 12:59:44 +0200 The problem is here, on the preceding line. The Received: line is malformed because without whitespace to "continue" the line, it looks like multiple lines. To be correct, it should be Received: from arvidsjaur (arvidsjaur.anu.edu.au [150.203.160.29]) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) with ESMTP id MAA12962 for ; Fri, 2 Aug 1996 12:59:44 +0200 ^^^^ either spaces or TAB. One of the transport agent in the path of the message is broken WRT RFC-822. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #16: Sun Jul 21 13:26:53 MET DST 1996 From owner-freebsd-hackers Fri Aug 2 10:43:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA18922 for hackers-outgoing; Fri, 2 Aug 1996 10:43:36 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA18917 for ; Fri, 2 Aug 1996 10:43:33 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id TAA25215; Fri, 2 Aug 1996 19:43:04 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id TAA32641; Fri, 2 Aug 1996 19:42:13 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.5/keltia-uucp-2.8) id TAA10933; Fri, 2 Aug 1996 19:17:09 +0200 (MET DST) Message-Id: <199608021717.TAA10933@keltia.freenix.fr> Date: Fri, 2 Aug 1996 19:17:08 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: imb@asstdc.com.au (michael butler) Cc: dev@fgate.flevel.co.uk (Developer), hackers@freebsd.org Subject: Re: Migrating BSDI 1.1 Passwords In-Reply-To: <199608021334.XAA09607@walkabout.asstdc.com.au>; from michael butler on Aug 2, 1996 23:34:49 +1000 References: <199608021334.XAA09607@walkabout.asstdc.com.au> X-Mailer: Mutt 0.38 Mime-Version: 1.0 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to michael butler: > Oh .. as a side note .. mere _possession_ of strong cryptographic software > in France without government approval is presently a punishable offense .. > good for a gaol term, I'm told. The law is not clear on "Possession". Use of authentication and encryption devices is subject to respectively declaration and authorization. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #16: Sun Jul 21 13:26:53 MET DST 1996 From owner-freebsd-hackers Fri Aug 2 14:16:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA01677 for hackers-outgoing; Fri, 2 Aug 1996 14:16:15 -0700 (PDT) Received: from rush.u-netsys.com.br (RUSH.U-NETSYS.COM.BR [200.246.214.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA01661 for ; Fri, 2 Aug 1996 14:16:05 -0700 (PDT) Received: from rush ([200.246.214.10]) by rush.u-netsys.com.br (post.office MTA v1.9.1 ID# 0-11148) with SMTP id AAA138 for ; Fri, 2 Aug 1996 18:12:15 -0300 Message-ID: <3202611F.2C66@u-netsys.com.br> Date: Fri, 02 Aug 1996 18:12:15 -0200 From: paul@u-netsys.com.br (Paulo C. Marques F.) Reply-To: paul@u-netsys.com.br X-Mailer: Mozilla 3.0b4 (WinNT; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: DOS Emulation. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Unfortunately, I have to run some dos binaries (a Clipper 5.2 .EXE) under FreeBSD 2.1.5. What is the better way to do it? May I "emulate the Linux dos emulator"? Thanks in advance, Paulo Marques paul@u-netsys.com.br From owner-freebsd-hackers Fri Aug 2 14:20:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA02059 for hackers-outgoing; Fri, 2 Aug 1996 14:20:56 -0700 (PDT) Received: from iago.ienet.com (iago.ienet.com [207.78.32.53]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA02051 for ; Fri, 2 Aug 1996 14:20:50 -0700 (PDT) Received: from ienet.com (localhost.ienet.com [127.0.0.1]) by iago.ienet.com (8.7.5/8.7.3) with ESMTP id OAA28784; Fri, 2 Aug 1996 14:20:10 -0700 (PDT) Message-Id: <199608022120.OAA28784@iago.ienet.com> To: freebsd-hackers@FreeBSD.ORG From: pius@ienet.com Subject: su question Date: Fri, 02 Aug 1996 14:20:09 -0700 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just out of curiosity, when someone does an su to root, why does su check that the username is explicitly listed as a member of group 0 in /etc/group instead of just making sure that the user is part of that group with getgroups(2)? In other words, why should a user with a group ID of 0 in /etc/passwd also have to be listed as a member of wheel in /etc/group in order to su to root? Thanks, Pius From owner-freebsd-hackers Fri Aug 2 15:06:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA05280 for hackers-outgoing; Fri, 2 Aug 1996 15:06:49 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA05268 for ; Fri, 2 Aug 1996 15:06:45 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by misery.sdf.com (8.7.5/UNS-1.0) with SMTP id PAA23991; Fri, 2 Aug 1996 15:22:55 -0700 (PDT) Date: Fri, 2 Aug 1996 15:22:54 -0700 (PDT) From: Tom Samplonius To: pius@ienet.com cc: freebsd-hackers@FreeBSD.ORG Subject: Re: su question In-Reply-To: <199608022120.OAA28784@iago.ienet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 2 Aug 1996 pius@ienet.com wrote: > Just out of curiosity, > > when someone does an su to root, why does su check that the > username is explicitly listed as a member of group 0 in /etc/group > instead of just making sure that the user is part of that group > with getgroups(2)? In other words, why should a user with a group > ID of 0 in /etc/passwd also have to be listed as a member of wheel > in /etc/group in order to su to root? > > Thanks, > Pius For security reasons. Tom From owner-freebsd-hackers Fri Aug 2 21:49:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA26197 for hackers-outgoing; Fri, 2 Aug 1996 21:49:34 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA26190 for ; Fri, 2 Aug 1996 21:49:31 -0700 (PDT) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id VAA00378 for ; Fri, 2 Aug 1996 21:49:30 -0700 (PDT) Message-Id: <199608030449.VAA00378@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 to: hackers@freebsd.org Subject: Help! (Re: m_copym crash ) In-reply-to: Your message of "Fri, 02 Aug 1996 06:54:27 PDT." <199608021354.GAA00394@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Fri, 02 Aug 1996 21:49:29 -0700 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here is stack trace dump {root} gdb -k GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details= =2E GDB 4.13 (i386-unknown-freebsd), Copyright 1994 Free Software Foundation,= Inc. (kgdb) pwd Working directory /usr/src/sys/compile/STAR-GATE. (kgdb) ls Undefined command: "ls". Try "help". (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file /var/crash/kernel.0 /var/crash/kernel.0: No such file or directory. (kgdb) exec-file /usr/crash/kernel.0 (kgdb) core-file /var/crash/vmcore.0 /var/crash/vmcore.0: No such file or directory. (kgdb) core-file /usr/crash/vmcore.0 IdlePTD ab9000 current pcb at 223184 panic: m_copym 3 #0 boot (howto=3D260) at ../../i386/i386/machdep.c:750 750 dumppcb.pcb_cr3 =3D rcr3(); (kgdb) bt #0 boot (howto=3D260) at ../../i386/i386/machdep.c:750 #1 0xf0119a67 in panic (fmt=3D0x0) at ../../kern/subr_prf.c:127 #2 0xf01014fa in db_fncall (dummy1=3D-267280555, dummy2=3D0, dummy3=3D-2= 72630584, = dummy4=3D0xefbffc88 "") at ../../ddb/db_command.c:493 #3 0xf010122e in db_command (last_cmdp=3D0xf020bb34, cmd_table=3D0xf020b= 994) at ../../ddb/db_command.c:288 #4 0xf01013ad in db_command_loop () at ../../ddb/db_command.c:417 #5 0xf0103758 in db_trap (type=3D3, code=3D0) at ../../ddb/db_trap.c:73 #6 0xf01c4baa in kdb_trap (type=3D3, code=3D0, regs=3D0xefbffd78) at ../../i386/i386/db_interface.c:136 #7 0xf01cd49c in trap (frame=3D{tf_es =3D 16, tf_ds =3D 16, tf_edi =3D -= 272630280, = tf_esi =3D -267228959, tf_ebp =3D -272630340, tf_isp =3D -272630368= , = tf_ebx =3D 256, tf_edx =3D -266580571, tf_ecx =3D 2000, tf_eax =3D = 18, = tf_trapno =3D 3, tf_err =3D 0, tf_eip =3D -266580525, tf_cs =3D 8, = tf_eflags =3D 582, tf_esp =3D -266580587, tf_ss =3D -267281922}) at ../../i386/i386/trap.c:402 #8 0xf01c5421 in calltrap () #9 0xf0119a5e in panic (fmt=3D0xf01268e1 "m_copym 3") at ../../kern/subr_prf.c:125 #10 0xf012698f in m_copym (m=3D0xf1499400, off0=3D608, len=3D301, wait=3D= 1) at ../../kern/uipc_mbuf.c:363 #11 0xf0156518 in tcp_output (tp=3D0xf17e2d00) at ../../netinet/tcp_outpu= t.c:496 #12 0xf01584b4 in tcp_disconnect (tp=3D0xf17e2d00) ---Type to continue, or q to quit--- = at ../../netinet/tcp_usrreq.c:1092 #13 0xf0157a44 in tcp_usr_disconnect (so=3D0xf17e2e00) at ../../netinet/tcp_usrreq.c:590 #14 0xf0127dd8 in sodisconnect (so=3D0xf17e2e00) at ../../kern/uipc_socke= t.c:302 #15 0xf0127b86 in soclose (so=3D0xf17e2e00) at ../../kern/uipc_socket.c:1= 89 #16 0xf011c687 in soo_close (fp=3D0xf178b900, p=3D0xf17d7000) at ../../kern/sys_socket.c:206 #17 0xf010d5c4 in closef (fp=3D0xf178b900, p=3D0xf17d7000) at ../../kern/kern_descrip.c:889 #18 0xf010ccdf in close (p=3D0xf17d7000, uap=3D0xefbfff94, retval=3D0xefb= fff84) at ../../kern/kern_descrip.c:390 #19 0xf01cdef7 in syscall (frame=3D{tf_es =3D 39, tf_ds =3D 39, tf_edi =3D= 5, = tf_esi =3D 0, tf_ebp =3D -272644908, tf_isp =3D -272629788, tf_ebx = =3D 220000, = tf_edx =3D 217124, tf_ecx =3D 22, tf_eax =3D 6, tf_trapno =3D 12, t= f_err =3D 7, = tf_eip =3D 134917857, tf_cs =3D 31, tf_eflags =3D 518, tf_esp =3D -= 272644948, = tf_ss =3D 39}) at ../../i386/i386/trap.c:890 #20 0xf01c5475 in Xsyscall () #21 0x1f35a in ?? () #22 0x1f24e in ?? () #23 0x1f4cb in ?? () #24 0x1ed0d in ?? () #25 0x227f9 in ?? () #26 0xa2d4 in ?? () ---Type to continue, or q to quit--- #27 0x294cc in ?? () #28 0xa2d4 in ?? () #29 0xb251 in ?? () #30 0xa2d4 in ?? () #31 0x1f6c in ?? () #32 0x22ea in ?? () #33 0xa022 in ?? () #34 0x294cc in ?? () #35 0xa2d4 in ?? () #36 0x1f6c in ?? () #37 0x22ea in ?? () #38 0xa022 in ?? () Cannot access memory at address 0xefbfd068. a few gdb's up later... (kgdb) up #9 0xf0119a5e in panic (fmt=3D0xf01268e1 "m_copym 3") at ../../kern/subr_prf.c:125 125 Debugger ("panic"); (kgdb) up #10 0xf012698f in m_copym (m=3D0xf1499400, off0=3D608, len=3D301, wait=3D= 1) at ../../kern/uipc_mbuf.c:363 363 panic("m_copym 3"); (kgdb) print *m $1 =3D {m_hdr =3D {mh_next =3D 0x7205c766, mh_nextpkt =3D 0x34000004, = mh_data =3D 0xe5895512
, = mh_len =3D -1935867286, mh_type =3D -28968, mh_flags =3D -28960}, M_d= at =3D {MH =3D { MH_pkthdr =3D {rcvif =3D 0xc2e8e8, len =3D 12320768}, MH_dat =3D {M= H_ext =3D { ext_buf =3D 0xe80020b0
, = ext_free =3D 0x14b, ext_size =3D 588791993}, = MH_databuf =3D "=B0 \000=E8K\001\000\000=B9@\030#\000=BF\214=B4!\= 000)=F91=C0=FC=F3=AA=E8I\002\0 00\000=A1|=B0 \000\017\"=D8\017 =C0\r\001\000\000\200\017\"=C0hS\000\020=F0= =C3=BC\000\000=C0=EF1=C0\2 11=C5=A1\204=B0 =F0\2135|=B0 =F0\211p\034\2135p=B0 =F0V=E82\201\f\000^j\0= 00=FF5\f=F1\"=F0j"}}, = M_databuf =3D "=E8=E8=C2\000\000\000=BC\000=B0 \000=E8K\001\000\000=B9= @\030#\000=BF\214=B4!\000 )=F91=C0=FC=F3=AA=E8I\002\000\000=A1|=B0 \000\017\"=D8\017 =C0\r\001\000\= 000\200\017\"=C0hS\000\020=F0=C3 =BC\000\000=C0=EF1=C0\211=C5=A1\204=B0 =F0\2135|=B0 =F0\211p\034\2135p=B0= = =F0V=E82\201\f\000^j\000=FF5\f=F1\"=F0j"}} > = > Has anyone seen this before on -current? > = > Tnks, > Amancio > = > ---- > = > struct mbuf * > m_copym(m, off0, len, wait) > register struct mbuf *m; > int off0, wait; > register int len; > { > register struct mbuf *n, **np; > register int off =3D off0; > struct mbuf *top; > int copyhdr =3D 0; > = > if (off < 0 || len < 0) > panic("m_copym 1"); > if (off =3D=3D 0 && m->m_flags & M_PKTHDR) > copyhdr =3D 1; > while (off > 0) { > if (m =3D=3D 0) > panic("m_copym 2"); > if (off < m->m_len) > break; > off -=3D m->m_len; > m =3D m->m_next; > } > np =3D ⊤ > top =3D 0; > while (len > 0) { > if (m =3D=3D 0) { > if (len !=3D M_COPYALL) > panic("m_copym 3"); > **** crash site ***** > break; > } > = > = > = > = From owner-freebsd-hackers Sat Aug 3 01:43:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA12297 for hackers-outgoing; Sat, 3 Aug 1996 01:43:35 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA12281 for ; Sat, 3 Aug 1996 01:43:30 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id KAA14074; Sat, 3 Aug 1996 10:39:12 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id KAA29144; Sat, 3 Aug 1996 10:52:31 +0200 From: "Christoph P. Kukulies" Message-Id: <199608030852.KAA29144@gilberto.physik.rwth-aachen.de> Subject: Re: sendmail (8bit char problem?) To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Sat, 3 Aug 1996 10:52:30 +0200 (MET DST) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-hackers@freefall.freebsd.org In-Reply-To: <199608021714.TAA10919@keltia.freenix.fr> from Ollivier Robert at "Aug 2, 96 07:14:50 pm" Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL16 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > According to Christoph P. Kukulies: > > |From samba@arvidsjaur.anu.edu.au Fri Aug 2 13:00:03 1996 > > |Received: from arvidsjaur (arvidsjaur.anu.edu.au [150.203.160.29]) by > > |gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) with ESMTP id MAA12962 > > |for ; Fri, 2 Aug 1996 12:59:44 +0200 > > The problem is here, on the preceding line. The Received: line is malformed > because without whitespace to "continue" the line, it looks like multiple > lines. Sorry, I hand edited that line (some lines in the header) to avoid posting overly long lines. So I don't believe that's the problem. > > To be correct, it should be > > Received: from arvidsjaur (arvidsjaur.anu.edu.au [150.203.160.29]) by > gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) with ESMTP id MAA12962 > for ; Fri, 2 Aug 1996 12:59:44 +0200 > ^^^^ > either spaces or TAB. > > One of the transport agent in the path of the message is broken WRT > RFC-822. How can I tell which one? Isn't it obvious from the headers that there are arvidsjaur.anu.edu.au and gil.physik.rwth-aachen.de envolved in the mail transfer? > > -- > Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 2.2-CURRENT #16: Sun Jul 21 13:26:53 MET DST 1996 > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-hackers Sat Aug 3 01:53:24 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA13400 for hackers-outgoing; Sat, 3 Aug 1996 01:53:24 -0700 (PDT) Received: from jraynard.demon.co.uk (jraynard.demon.co.uk [158.152.42.77]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id BAA13389 for ; Sat, 3 Aug 1996 01:53:11 -0700 (PDT) Received: (from fhackers@localhost) by jraynard.demon.co.uk (8.6.12/8.6.12) id AAA06468; Sat, 3 Aug 1996 00:17:25 GMT From: James Raynard Message-Id: <199608030017.AAA06468@jraynard.demon.co.uk> Subject: Re: FreeBSD and Mach 64 To: green@filitov.isf.rl.af.mil (Charles Green) Date: Sat, 3 Aug 1996 00:17:24 +0000 () Cc: hackers@freebsd.org In-Reply-To: <199608011807.OAA24550@filitov.isf.rl.af.mil> from "Charles Green" at Aug 1, 96 02:07:13 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > You know, I did check the FAQ. I read 7.12 and saw that it was a > recognized problem. What I didn't do was notice that 7.13 showed a > fix. Oops :) > > I think 7.12 and 7.13 should be made into one entry, all the > other questions have the solution included with the explaination of > the problem. Not to mention the two following questions... Anyway, I'll be checking in a patch to combine these four answers into one shortly. From owner-freebsd-hackers Sat Aug 3 05:11:36 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA01428 for hackers-outgoing; Sat, 3 Aug 1996 05:11:36 -0700 (PDT) Received: from pdx1 (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id FAA01417 for ; Sat, 3 Aug 1996 05:11:32 -0700 (PDT) Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1 (8.6.9/8.6.9) with ESMTP id FAA29228 for ; Sat, 3 Aug 1996 05:13:28 -0700 Received: (proff@localhost) by suburbia.net (8.7.4/Proff-950810) id WAA16275 for freebsd-hackers@freebsd.org; Sat, 3 Aug 1996 22:11:24 +1000 Date: Sat, 3 Aug 1996 22:11:24 +1000 From: Julian Assange Message-Id: <199608031211.WAA16275@suburbia.net> To: freebsd-hackers@freebsd.org Subject: per-line profiling Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anyone know where I can get one? From owner-freebsd-hackers Sat Aug 3 05:23:51 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA02618 for hackers-outgoing; Sat, 3 Aug 1996 05:23:51 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA02612 for ; Sat, 3 Aug 1996 05:23:49 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id FAA01128 for ; Sat, 3 Aug 1996 05:23:13 -0700 (PDT) To: hackers@freebsd.org Subject: Anyone know how anoncvs actually works? Date: Sat, 03 Aug 1996 05:23:13 -0700 Message-ID: <1124.839074993@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It might be something we should set up, just to give complete coverage (then we could say we offered the repository via CTM, WWW, sup, cvsup, FTP and anoncvs - how many more options could one want? ;-). Anyway, I'd like to find out what's involved first since the security implications of what little I've been able to puzzle out seem fuzzy. Jordan From owner-freebsd-hackers Sat Aug 3 05:26:01 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA02910 for hackers-outgoing; Sat, 3 Aug 1996 05:26:01 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA02905 for ; Sat, 3 Aug 1996 05:25:57 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id OAA25770; Sat, 3 Aug 1996 14:25:38 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id OAA09180; Sat, 3 Aug 1996 14:25:15 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Alpha.7/keltia-uucp-2.9) id OAA02812; Sat, 3 Aug 1996 14:10:26 +0200 (MET DST) Message-Id: <199608031210.OAA02812@keltia.freenix.fr> Date: Sat, 3 Aug 1996 14:10:26 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: kuku@gilberto.physik.rwth-aachen.de (Christoph Kukulies) Cc: freebsd-hackers@freefall.freebsd.org Subject: Re: sendmail (8bit char problem?) In-Reply-To: <199608030852.KAA29144@gilberto.physik.rwth-aachen.de>; from Christoph P. Kukulies on Aug 3, 1996 10:52:30 +0200 References: <199608030852.KAA29144@gilberto.physik.rwth-aachen.de> X-Mailer: Mutt 0.38 Mime-Version: 1.0 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Christoph P. Kukulies: > Sorry, I hand edited that line (some lines in the header) to avoid posting > overly long lines. So I don't believe that's the problem. OK. > How can I tell which one? Isn't it obvious from the headers that there are > arvidsjaur.anu.edu.au and gil.physik.rwth-aachen.de envolved in the > mail transfer? There are two problems: - It is "gil.physik.rwth-aachen.de", running sendmail 8.6.11 (you MUST upgrade BTW, it has some security problems, use only 8.7.5). 8.6.* doesn't advertise the ESMTP extention called 8BITMIME so the mailer on arvidsjaur.anu.edu.au has rewritten the message in Quoted-Unreadable. As it is not able to correctly label the message, it uses Unknown-8bit as the charset. Using 8.7.5 would solve the problem on this side. - ELM-ME+ is not able to display "Unknown-8bit"-labelled text, even if you put it in compatcharset. This is a misfeature IMO and Mutt, the MUA I use now, display it correctly with the following warning (as Elm): ------------------------------------------------------------ [Warning! UNKNOWN-8BIT charset is not compatible with your display.] SAMBA Digest 1013 For information on unsubscribing and on what is appropriate to post to this list see ftp://samba.anu.edu.au/pub/lists/samba.txt ------------------------------------------------------------ The solution I offer is to switch to Mutt from Elm. The author is Michael Elkins, known for the original ME patches to Elm and the PGP/MIME RFC draft. See (it is a SmartList list) The PGP-aware version, export-restricted has appeared on a german site, look in the mail archive to find it. The look and feel is based on Elm (even if the display has chaned now). It is highly configurable (key bindings, display formats...). You'll need the following patch to build 0.38 on FreeBSD: Index: curs_lib.c =================================================================== RCS file: /build/master/mail/mutt/curs_lib.c,v retrieving revision 1.1.1.2 retrieving revision 1.2 diff -u -2 -r1.1.1.2 -r1.2 --- curs_lib.c 1996/07/28 16:21:23 1.1.1.2 +++ curs_lib.c 1996/07/29 04:47:11 1.2 @@ -16,4 +16,6 @@ */ +#include /* needed for HAVE_SYS_PARAM_H */ + #ifdef HAVE_SYS_PARAM_H #include /* needed for definition of BSD on BSD-ish systems. */ Even as alpha code, I'm convinced that Mutt is a very good MUA and I've switched permanently now... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #16: Sun Jul 21 13:26:53 MET DST 1996 From owner-freebsd-hackers Sat Aug 3 07:06:05 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA10172 for hackers-outgoing; Sat, 3 Aug 1996 07:06:05 -0700 (PDT) Received: from po1.glue.umd.edu (po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA10166 for ; Sat, 3 Aug 1996 07:06:02 -0700 (PDT) Received: from fiber.eng.umd.edu (fiber.eng.umd.edu [129.2.98.185]) by po1.glue.umd.edu (8.7.5/8.7.3) with ESMTP id KAA12577; Sat, 3 Aug 1996 10:06:00 -0400 (EDT) Received: from localhost (chuckr@localhost) by fiber.eng.umd.edu (8.7.5/8.7.3) with SMTP id KAA23675; Sat, 3 Aug 1996 10:05:59 -0400 (EDT) X-Authentication-Warning: fiber.eng.umd.edu: chuckr owned process doing -bs Date: Sat, 3 Aug 1996 10:05:59 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@fiber.eng.umd.edu To: "Jordan K. Hubbard" cc: hackers@FreeBSD.ORG Subject: Re: Anyone know how anoncvs actually works? In-Reply-To: <1124.839074993@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 3 Aug 1996, Jordan K. Hubbard wrote: > It might be something we should set up, just to give complete coverage > (then we could say we offered the repository via CTM, WWW, sup, cvsup, > FTP and anoncvs - how many more options could one want? ;-). > > Anyway, I'd like to find out what's involved first since the security > implications of what little I've been able to puzzle out seem fuzzy. Is someone workong on testing rsync? > > Jordan > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hackers Sat Aug 3 07:14:56 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA10682 for hackers-outgoing; Sat, 3 Aug 1996 07:14:56 -0700 (PDT) Received: from robin.camelot.de (root@robin.camelot.de [194.97.87.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA10677 for ; Sat, 3 Aug 1996 07:14:52 -0700 (PDT) Received: from lancelot.camelot.de(really [194.97.87.4]) by robin.camelot.de via sendmail with smtp id for ; Sat, 3 Aug 1996 16:14:47 +0200 (MET DST) (Smail-3.2 1996-Jul-4 #1 built DST-Jul-28) Received: by lancelot.camelot.de via sendmail with stdio id for freebsd-hackers@freebsd.org; Sat, 3 Aug 1996 16:14:46 +0200 (MET DST) (Smail-3.2 1996-Jul-4 #1 built DST-Jul-28) To: freebsd-hackers@freebsd.org Path: not-for-mail From: knarf@camelot.de (Frank Bartels) Newsgroups: muc.lists.freebsd.hackers Subject: ppp dumps core Date: 3 Aug 1996 14:14:44 GMT Organization: Camelot Online Services Lines: 26 Message-ID: <4tvmsl$b7v@lancelot.camelot.de> NNTP-Posting-Host: lancelot.camelot.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [UNIX 1.3 950726BETA PL0] Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I use the user mode ppp to connect to a linux box running pppd 2.2.0f. After a while ppp on the FreeBSD machine says: 08-02 14:53:06 [2055] Unknown protocol 0x000d 08-02 14:53:06 [2055] LCP: SendProtoRej 08-02 14:53:06 [2055] Unknown protocol 0xc261 08-02 14:53:06 [2055] LCP: SendProtoRej and dumps core! :/ I have disabled and denied lqr and pred1 on the FreeBSD machine. The FreeBSD version is one of the last SNAPs before 2.1.0-RELEASE (sorry, not sure). I tried to use the 2.1.5-R binary of ppp, but it also dumps core. I added "-vj -bsdcomp -pred1comp" to the pppd call on the linux machine and now it seems to work fine. Bye, Knarf -- Frank Bartels |UUCP/ZModem/Fax: +49 89 5469593| "Captain, why not just knarf@camelot.de | http://www.camelot.de/~knarf/ | give the Borg Windows?" From owner-freebsd-hackers Sat Aug 3 08:07:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA14813 for hackers-outgoing; Sat, 3 Aug 1996 08:07:17 -0700 (PDT) Received: from robin.camelot.de (root@robin.camelot.de [194.97.87.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA14806 for ; Sat, 3 Aug 1996 08:07:12 -0700 (PDT) Received: from lancelot.camelot.de(really [194.97.87.4]) by robin.camelot.de via sendmail with smtp id for ; Sat, 3 Aug 1996 17:07:09 +0200 (MET DST) (Smail-3.2 1996-Jul-4 #1 built DST-Jul-28) Received: by lancelot.camelot.de via sendmail with stdio id for freebsd-hackers@freebsd.org; Sat, 3 Aug 1996 17:07:08 +0200 (MET DST) (Smail-3.2 1996-Jul-4 #1 built DST-Jul-28) To: freebsd-hackers@freebsd.org Path: not-for-mail From: knarf@camelot.de (Frank Bartels) Newsgroups: muc.lists.freebsd.hackers Subject: de0 problems Date: 3 Aug 1996 15:07:08 GMT Organization: Camelot Online Services Lines: 39 Message-ID: <4tvpus$b7v@lancelot.camelot.de> NNTP-Posting-Host: lancelot.camelot.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [UNIX 1.3 950726BETA PL0] Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'm running FreeBSD 2.1.5-RELEASE on a ASUS SP3G with a de0 card (TP). After some days the card stops working. The whole machine runs fine, but everything through the card does not. After a reboot everything is okay again. The last time the problem occured, I tried to ifconfig down, delete and up again and it worked again! I have two other ASUS pentium boards (P/I-P55TP4N and P/I-P55T2P4) with the same ethernet card (D-Link DE-530CT+) and there are no such problems. On all three machines I sometimes get the following errors in syslog: Aug 1 10:16:35 robin /kernel: de0: abnormal interrupt: 0xfc689084 [0x09000] Aug 1 10:16:41 lancelot /kernel: de0: abnormal interrupt: 0xfc669004 [0x09000] Aug 1 10:16:37 galahad /kernel: de0: abnormal interrupt: 0xfc669004 [0x09000] Hmm, at this time I installed a new TP-Hub if I remember correctly. So this messages seems to say "de0: No Carrier."? robin: de0 rev 36 int a irq 15 on pci0:5 de0: DC21040 [10Mb/s] pass 2.4 Ethernet address 00:80:c8:0d:2e:63 de0: enabling 10baseT/UTP port lancelot: de0 rev 36 int a irq 12 on pci0:10 de0: DC21040 [10Mb/s] pass 2.4 Ethernet address 00:80:c8:0d:2d:40 de0: enabling 10baseT/UTP port galahad: de0 rev 36 int a irq 11 on pci0:10 de0: DC21040 [10Mb/s] pass 2.4 Ethernet address 00:80:c8:0d:21:39 de0: enabling 10baseT/UTP port Bye, Knarf -- Frank Bartels |UUCP/ZModem/Fax: +49 89 5469593| "Captain, why not just knarf@camelot.de | http://www.camelot.de/~knarf/ | give the Borg Windows?" From owner-freebsd-hackers Sat Aug 3 11:29:24 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA28275 for hackers-outgoing; Sat, 3 Aug 1996 11:29:24 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA28267 for ; Sat, 3 Aug 1996 11:29:20 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA16287; Sat, 3 Aug 1996 12:29:11 -0600 (MDT) Date: Sat, 3 Aug 1996 12:29:11 -0600 (MDT) Message-Id: <199608031829.MAA16287@rocky.mt.sri.com> From: Nate Williams To: "Jordan K. Hubbard" Cc: hackers@freebsd.org Subject: Re: Anyone know how anoncvs actually works? In-Reply-To: <1124.839074993@time.cdrom.com> References: <1124.839074993@time.cdrom.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > It might be something we should set up, just to give complete coverage > (then we could say we offered the repository via CTM, WWW, sup, cvsup, > FTP and anoncvs - how many more options could one want? ;-). > > Anyway, I'd like to find out what's involved first since the security > implications of what little I've been able to puzzle out seem fuzzy. I *think* they have a special 'anoncvs' account that uses a version of cvs which disables all operations that would change the repository. Nate From owner-freebsd-hackers Sat Aug 3 11:43:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA29496 for hackers-outgoing; Sat, 3 Aug 1996 11:43:55 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA29490 for ; Sat, 3 Aug 1996 11:43:52 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA16352; Sat, 3 Aug 1996 12:43:47 -0600 (MDT) Date: Sat, 3 Aug 1996 12:43:47 -0600 (MDT) Message-Id: <199608031843.MAA16352@rocky.mt.sri.com> From: Nate Williams To: Nate Williams Cc: "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: Anyone know how anoncvs actually works? In-Reply-To: <199608031829.MAA16287@rocky.mt.sri.com> References: <1124.839074993@time.cdrom.com> <199608031829.MAA16287@rocky.mt.sri.com> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > It might be something we should set up, just to give complete coverage > > (then we could say we offered the repository via CTM, WWW, sup, cvsup, > > FTP and anoncvs - how many more options could one want? ;-). > > > > Anyway, I'd like to find out what's involved first since the security > > implications of what little I've been able to puzzle out seem fuzzy. > > I *think* they have a special 'anoncvs' account that uses a version of > cvs which disables all operations that would change the repository. Yep, look at freefall:/f/OpenBSD/src/gnu/usr.bin/cvs/src In particular, the cvswrite and readonly_fs changes. If need be, you could pull them out and/or drop the original CVS 1.8.1 distribution on top of the sources and do a diff to see what has changed. Nate From owner-freebsd-hackers Sat Aug 3 12:05:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01055 for hackers-outgoing; Sat, 3 Aug 1996 12:05:08 -0700 (PDT) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA01047 for ; Sat, 3 Aug 1996 12:05:02 -0700 (PDT) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id VAA28895 for hackers@freebsd.org; Sat, 3 Aug 1996 21:13:52 +0200 From: Luigi Rizzo Message-Id: <199608031913.VAA28895@labinfo.iet.unipi.it> Subject: TCP SACK anyone ? To: hackers@freebsd.org Date: Sat, 3 Aug 1996 21:13:52 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I remember somebody talking about porting of the SACK implementation from Berkeley (Hari Balakrishnan) to FreeBSD. I cannot find the message, though, and don't remember if it was on this or some other list. Is someone already working on this, or I can go ahead and do it myself (I have already done most of the work, but there are some parts of the original code which do frequent malloc/free of very small amount of memory and I would like to rewrite them more efficiently). Luigi ==================================================================== Luigi Rizzo Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it Universita' di Pisa tel: +39-50-568533 via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 http://www.iet.unipi.it/~luigi/ ==================================================================== From owner-freebsd-hackers Sat Aug 3 12:24:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02780 for hackers-outgoing; Sat, 3 Aug 1996 12:24:14 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA02774 for ; Sat, 3 Aug 1996 12:24:11 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id NAA09243; Sat, 3 Aug 1996 13:23:00 -0600 (MDT) Message-Id: <199608031923.NAA09243@rover.village.org> To: Nate Williams Subject: CVS 1.8.1 Cc: "Jordan K. Hubbard" , hackers@freebsd.org In-reply-to: Your message of Sat, 03 Aug 1996 12:43:47 MDT Date: Sat, 03 Aug 1996 13:23:00 -0600 From: Warner Losh Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : could pull them out and/or drop the original CVS 1.8.1 distribution on Any reason to not go with CVS 1.8.1? It built out of the box for me, but I haven't merged in the FreeBSD changes. If people would like a set of diffs with those changes merged in, say the word and I'll generate it. Last time this came up I recall there was some reason people didn't want to do this, but I could be misremembering. Warner From owner-freebsd-hackers Sat Aug 3 12:25:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA02886 for hackers-outgoing; Sat, 3 Aug 1996 12:25:48 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA02879 for ; Sat, 3 Aug 1996 12:25:45 -0700 (PDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id NAA16533; Sat, 3 Aug 1996 13:25:33 -0600 (MDT) Date: Sat, 3 Aug 1996 13:25:33 -0600 (MDT) Message-Id: <199608031925.NAA16533@rocky.mt.sri.com> From: Nate Williams To: Warner Losh Cc: Nate Williams , "Jordan K. Hubbard" , hackers@freebsd.org Subject: Re: CVS 1.8.1 In-Reply-To: <199608031923.NAA09243@rover.village.org> References: <199608031923.NAA09243@rover.village.org> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > : could pull them out and/or drop the original CVS 1.8.1 distribution on > > Any reason to not go with CVS 1.8.1? It built out of the box for me, > but I haven't merged in the FreeBSD changes. If people would like a > set of diffs with those changes merged in, say the word and I'll > generate it. > > Last time this came up I recall there was some reason people didn't > want to do this, but I could be misremembering. Peter had a version all ready to go a while back, but I expressed some reservation given the focus of the changes made then. One of the recent releases of CVS reserved *ALL* uppercase tags for CVS, which was backed out later after a number of folks complained. Nate From owner-freebsd-hackers Sat Aug 3 14:04:39 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA14993 for hackers-outgoing; Sat, 3 Aug 1996 14:04:39 -0700 (PDT) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA14844; Sat, 3 Aug 1996 14:02:50 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id PAA14656; Sat, 3 Aug 1996 15:02:40 -0600 Message-Id: <199608032102.PAA14656@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: smp@freebsd.org cc: hackers@freebsd.org Subject: halt & sysctl Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Aug 1996 15:02:40 -0600 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I have observed that when halting SMP kernels the 'sync' never finishes unless I manually disable the 2nd CPU via: sysctl -w kern.smp_active=0 before issuing the halt command. I have been looking for a way to do the equivalent in machdep.c:boot(): boot(howto) int howto; { #ifdef SMP /** * FIXME: all but the first CPU needs to be disabled here!!! * we want to do equiv. of "sysctl -w kern.smp_active=0" */ int status; int sctl[2]; sctl[0] = CTL_KERN; >>> sctl[1] = ???; status = kernel_sysctl(&proc0, sctl, 2, 0, 0, 0, sizeof( int ), 0); printf( "\nsysctl status: %d\n", status ); #endif /* SMP */ if (!cold && (howto & RB_NOSYNC) == 0 && waittime < 0) { ... } Am I barking up the right tree? Anyone know the proper value for sctl[1]? -- Steve Passe | powered by smp@csn.net | FreeBSD From owner-freebsd-hackers Sat Aug 3 14:31:49 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA16226 for hackers-outgoing; Sat, 3 Aug 1996 14:31:49 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA16221 for ; Sat, 3 Aug 1996 14:31:42 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id PAA09609; Sat, 3 Aug 1996 15:30:23 -0600 (MDT) Message-Id: <199608032130.PAA09609@rover.village.org> To: Nate Williams Subject: Re: CVS 1.8.1 Cc: "Jordan K. Hubbard" , hackers@freebsd.org In-reply-to: Your message of Sat, 03 Aug 1996 13:25:33 MDT Date: Sat, 03 Aug 1996 15:30:22 -0600 From: Warner Losh Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk : Peter had a version all ready to go a while back, but I expressed some : reservation given the focus of the changes made then. One of the recent : releases of CVS reserved *ALL* uppercase tags for CVS, which was backed : out later after a number of folks complained. So does that mean it can go in now, or that you still have some reservations about it? Warner From owner-freebsd-hackers Sat Aug 3 16:10:08 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA24624 for hackers-outgoing; Sat, 3 Aug 1996 16:10:08 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA24614; Sat, 3 Aug 1996 16:10:03 -0700 (PDT) Received: from rah.star-gate.com (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id QAA06408; Sat, 3 Aug 1996 16:08:17 -0700 (PDT) Message-Id: <199608032308.QAA06408@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: shanee@rabbit.augusta.de (Andreas Kohout) cc: multimedia@freebsd.org, hackers@freebsd.org Subject: Re: http://www.uni-paderborn.de/~SciTeXt/ In-reply-to: Your message of "Sat, 03 Aug 1996 22:36:00 +0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Aug 1996 16:08:16 -0700 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of Andreas Kohout : > It looks like Windows-Write/Word but is pre-alpha -> missing lots of > features. Well, I managed to port scitext over here and it was not that hard to port. I added this to the Makefile: # common rules for all Makefiles - do not edit .c.i: $(RM) $@ $(CC) -E $(CFLAGS) $(_NOOP_) $*.c > $@ ------- .C.o: $(RM) $@ $(CXX) -c -o $@ $(CFLAGS) $(CXXEXTRA_INCLUDES) $*.C ------- The rule to build ".C.o" files was missing ... As for scitext , I like the presentation so far and yes it looks like is missing a lot of features which means that is an opportunity for cool hackers to step in and lend a hand 8) I really would like to see a nice word processor which we can at least distribute the sources . Now with Open One from netscape or ILU this word processor can get very interesting 8) Info on ILU: ftp://parcftp.parc.xerox.com/pub/ilu/ilu.html Info on Open One: http://developer.netscape.com/library/one/index.html Enjoy, Amancio From owner-freebsd-hackers Sat Aug 3 17:09:02 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA28055 for hackers-outgoing; Sat, 3 Aug 1996 17:09:02 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA28034 for ; Sat, 3 Aug 1996 17:08:56 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id RAA29102; Sat, 3 Aug 1996 17:07:47 -0700 (PDT) To: Warner Losh cc: Nate Williams , hackers@freebsd.org Subject: Re: CVS 1.8.1 In-reply-to: Your message of "Sat, 03 Aug 1996 15:30:22 MDT." <199608032130.PAA09609@rover.village.org> Date: Sat, 03 Aug 1996 17:07:47 -0700 Message-ID: <29100.839117267@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > So does that mean it can go in now, or that you still have some > reservations about it? I think we need to find out what Peter thinks, given that he's the CVS repository meister around here. Peter? Jordan From owner-freebsd-hackers Sat Aug 3 19:00:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA03432 for hackers-outgoing; Sat, 3 Aug 1996 19:00:32 -0700 (PDT) Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA03421 for ; Sat, 3 Aug 1996 19:00:27 -0700 (PDT) Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from mail.hanse.de (193.174.9.9) with smtp id ; Sun, 4 Aug 96 04:00 MEST Received: from wavehh.UUCP by mail.hanse.de with UUCP for freebsd-hackers@freebsd.org id ; Sun, 4 Aug 96 04:00 MET DST Received: by wavehh.hanse.de (4.1/SMI-4.1) id AA23678; Sun, 4 Aug 96 00:10:34 +0200 Date: Sun, 4 Aug 96 00:10:34 +0200 From: cracauer@wavehh.hanse.de (Martin Cracauer) Message-Id: <9608032210.AA23678@wavehh.hanse.de> To: jkh@time.cdrom.COM Cc: freebsd-hackers@freebsd.org Subject: Re: Anyone know how anoncvs actually works? Newsgroups: hanse-ml.freebsd.hackers References: <1124.839074993@time.cdrom.com> Reply-To: cracauer@wavehh.hanse.de Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan wrote: > Subject: Re: Anyone know how anoncvs actually works? http://www.openbsd.org/anoncvs.shar I don't know how good the information provided here it, though. I don't run such a server by myself. >It might be something we should set up, just to give complete coverage >(then we could say we offered the repository via CTM, WWW, sup, cvsup, >FTP and anoncvs - how many more options could one want? ;-). Well, since sup is a bit unreliable, it won't last long until someone rewrites it using a HTTP server :-) Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.bik-gmbh.de/~cracauer Where do you want to go today? Hard to tell running your calendar on a junk OS, eh? From owner-freebsd-hackers Sat Aug 3 19:38:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA05909 for hackers-outgoing; Sat, 3 Aug 1996 19:38:22 -0700 (PDT) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA05904 for ; Sat, 3 Aug 1996 19:38:19 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id TAA11223; Sat, 3 Aug 1996 19:37:43 -0700 (PDT) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma011221; Sat Aug 3 19:37:17 1996 Received: (from archie@localhost) by bubba.whistle.com (8.6.12/8.6.12) id TAA05031; Sat, 3 Aug 1996 19:37:16 -0700 From: Archie Cobbs Message-Id: <199608040237.TAA05031@bubba.whistle.com> Subject: flock() broken on certain files To: freebsd-hackers@freebsd.org Date: Sat, 3 Aug 1996 19:37:16 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk How hard would it be to get flock() to work on a fifo? Right now it seems that it doesn't... could someone else verify this? It seems that fifo's are exactly the kind of thing you would want to be able to set a lock on, e.g., when multiple processes are writing to it. Here's a sample program: /* foo.c */ #include #include #include #include #include int main() { int fd; FILE *fp; fd = open("fifo", O_WRONLY, O_EXLOCK | O_NONBLOCK); if (fd < 0) { warn("pid %lu: open", getpid()); exit(1); } if ((fp = fdopen(fd, "a")) == NULL) { warn("pid %lu: fdopen", getpid()); exit(1); } warnx("pid %lu opened fifo", getpid()); sleep(5); fprintf(fp, "pid %lu reporting 1\n", getpid()); fflush(fp); sleep(5); fprintf(fp, "pid %lu reporting 2\n", getpid()); fflush(fp); sleep(5); fprintf(fp, "pid %lu reporting 3\n", getpid()); fflush(fp); warnx("pid %lu exiting", getpid()); return(0); } The open()'s are not being blocked, even though O_EXLOCK is specified: $$ mkfifo fifo csh: cat fifo > /dev/null & [3] 5017 $$ ./foo & [4] 5018 foo: pid 5018 opened fifo $$ ./foo & [5] 5019 foo: pid 5019 opened fifo $$ wait foo: pid 5018 exiting [4] Done ./foo foo: pid 5019 exiting [5] Done ./foo [3] Done cat fifo > /dev/null $$ -Archie ___________________________________________________________________________ Archie L. Cobbs, archie@whistle.com * Whistle Communications Corporation From owner-freebsd-hackers Sat Aug 3 20:36:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA08289 for hackers-outgoing; Sat, 3 Aug 1996 20:36:25 -0700 (PDT) Received: from goodguy.goodnet.com (iconia@goodnet.com [207.98.129.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA08283 for ; Sat, 3 Aug 1996 20:36:19 -0700 (PDT) Received: from localhost (iconia@localhost) by goodguy.goodnet.com (8.7.5/8.7.1) with SMTP id UAA03440 for ; Sat, 3 Aug 1996 20:35:48 -0700 (MST) Date: Sat, 3 Aug 1996 20:35:48 -0700 (MST) From: Kaehno X-Sender: iconia@goodguy To: hackers@FreeBSD.ORG In-Reply-To: <1124.839074993@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I know this sounds silly and is subject to flame, but bear in mind, I have wondered this..: I subscribed to one list (the oper list) and have been added inadvertantly to this one. Would someone email me the solution on how to get unsubscribe to this list?