Re: Network/ARP problem? Maybe pn driver?
Stefan Esser writes: You could have blocked reception of ARP requests / ARP replies in your IPFW rules on one of the systems involved. Just try again with a completely open FYI- There's no way to block ARP packets with ipfw... it only deals with IP packets. er... if you use bridging and enable ipfw on bridged packets (net.link.ether.bridge_ipfw=1) then you can block non-ip packets if you don't use an open firewall. I don't think the original poster is in this situation that's why i did not spoke before. cheers luigi ---+- Luigi RIZZO . EMAIL: lu...@iet.unipi.it. Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) ---+- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Maximize your website's traffic!
Maximize your website's traffic. INCREASE YOUR SEARCH ENGINE RANK! If your Web site isn't getting the traffic it should, it's likely that it's not ranked well on the major Internet search engines. According to recent Internet E-commerce studies, over 90% of consumers find the Web sites they visit by using eight major search engines, which are Yahoo!, Excite, AltaVista, Infoseek, Lycos, Web Crawler, HotBot, and Northern Light. If your website isn't located in the top-30 listings of these engines, chances are your site will never be seen. The single most important thing you can do to increase your Web site's traffic is to increase your search engine ranking. - PUT YOUR NAME IN LIGHTS -- List your business with search engines to make sure potential customers can find it. -- BIZ Excite, PC Computing magazine, November 1998 - THE BASICS: HOW SEARCH ENGINES RANK YOUR SITE When you submit your website to a search engine to be indexed in its database, it sends a robot to scan your page. Using complex algorithms to rank your page for keyword relevance, the robot determines whether you'll be ranked number 1 or 1,000,000 when potential visitors conduct a search looking for sites like yours. Because the search engines are constantly changing their algorithms to provide users with the best possible search results, there's only one true solution to high search engine placement--us. In short, submission alone isn't enough. *Good search engine ranking* is critical to your site's success. - HERE'S WHAT WE DO -- A UNIQUE, SUCCESSFUL APPROACH In order to counter the ever-changing search engine algorithms, we create an entire series of entry pages that are optimized for the search engines--one for every keyword (or keyword phrase) that you provide. Each entry page is optimized for a different set of algorithm variables. In other words, instead of having only *one* page struggling to rank well on all engines, we create separate, search engine-specific entry pages for each keyword. As a result, your pages rank well because they contain information relevant to search queries that are related to your industry. - HOW ENTRY PAGES AFFECT YOUR WEB SITE'S CURRENT STRUCTURE Put simply, they don't. When creating entry pages we *do not* make any changes to the existing structure, content, or functionality of your current site. The entry pages act as a welcome screen for your Web site when people enter from your highly ranked link on the search engine. The pages will say a few introductory words about your site, which are keyword and/or keyword phrase rich, and then provide a link that asks the visitor to Click Here To Enter, which moves them directly to your current homepage. HERE'S WHAT WE DON'T *EVER* DO TO HELP YOUR SEARCH ENGINE RANK We *will not* build pages for irrelevant--yet popular--keywords. Also, we will *never* spamdex pages. Spamdexing is stuffing a Web page full of words for the search engine's robots. You may have seen spamdexing, which is placing many words in the same text color as a background onto a Web page. Spamdexing will actually get your pages kicked from search engine indexes. What we *will* do is simply present very relevant keywords for your site to the search engines in the way that they like to see it. - It's simple: If they can't find you on the search engines, they can't buy from you. -- J. LeRoss, Internet Sales Consultant HOW WELL DOES THE SERVICE WORK? We'll send you a detailed report of your current search engine ranking on The Big Six engines before we begin. Then, once your new entry pages have been indexed, we'll send you a second report showing how they've ranked. Here's a sampling of some results we've acheived for previous clients. (These examples are for competitive keywords--not just obscure words on which no one is conducting searches.) 6 top-10 rankings on Infoseek for different relevant keywords 18 top-10 rankings across the major search engines 3 top-10 rankings on Alta Vista for one keyword 16 total *number one* rankings 40 top-30 rankings, spread across the different engines. 1 to 2 hits per week increased to 500 per day 45,000 hits per month grew to 108,000. HOW MUCH DOES YOUR SERVICE COST? Our basic services start at only $385. The basic package includes: Construction of optimized entry pages for up to 20 keywords -- This gives you good coverage in your industry Submission of the keyword-dense entry pages to the Big Six search engines When you contact us, ask about other services we provide that may be able to help your Internet initiatives succeed. We have special services that can be tailored for your specific Internet marketing needs. HOW DO I GET STARTED? Call us--we'll answer any questions you may
Re: vn and 4.0
:Is vn safe right now on -current? And does current's msdos fs :support fat-32? : :-- :Daniel C. Sobral (8-DCS) :d...@newsguy.com With that most recent patch ( which I am just committing now ) ... maybe. In -4.x, the alternate B_PAGING path in vn.c's vnstrategy() code is used for VM faults as well as swap I/O. In -3.x that path was only used for swap I/O. It is possible that there are more bugs in this section of vn.c. I would say it is 'probably' ok, but it will take more people testing the vn device under -4.x to be able to say that it is safe. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: btokup().. patch to STYLE(9) (fwd)
In nlc.lists.freebsd-current you wrote: At 12:09 PM 2/1/99 +1100, Gregory Bond wrote: You are not supposed to understand this. You are not expected to understand this. It was (IIRC) the process switching magic at the heart of fork() in V7 (and earlier, I assume). If I remember right, it referred to the non-local goto juju where if the forked processed was swapped out, the label jumped was changed to yet another place. Unfortunately, my annotated V6 listing is not accessible right now... It's inside the swtch() function call. Just having a quick look now. Inside expand(), where core is allocated for a process, if no core is available the process is swapped out with a call to xswap(), then switched out with a call to swtch(). When core becomes available and the process image is read in from swap, the process will be selected by swtch() to become runnable. However with the current context, swtch() would return and the tail end of the expand() function would execute. So inside expand() a call is made to save the stack state so that when swtch() restores this state, the return skips over the expand() function entirely. Cheers. --++ . | John Saunders - mailto:j...@nlc.net.au(EMail) | ,--_|\|- http://www.nlc.net.au/ (WWW) | / Oz \ |- 02-9489-4932 or 041-822-3814 (Phone) | \_,--\_/ | NHJ NORTHLINK COMMUNICATIONS - Supplying a professional, | v| and above all friendly, internet connection service. | ++ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: btokup().. patch to STYLE(9) (fwd)
-Original Message- From: John Saunders [SMTP:john.saund...@nlc.net.au] Sent: Monday, February 01, 1999 10:53 AM To: freebsd-current@FreeBSD.ORG Cc: Dan Swartzendruber Subject: Re: btokup().. patch to STYLE(9) (fwd) In nlc.lists.freebsd-current you wrote: At 12:09 PM 2/1/99 +1100, Gregory Bond wrote: You are not supposed to understand this. You are not expected to understand this. It's inside the swtch() function call. Just having a quick look now. Inside expand(), where core is allocated for a process, if no core is available the process is swapped out with a call to xswap(), then switched out with a call to swtch(). When core becomes available and the process image is read in from swap, the process will be selected by swtch() to become runnable. However with the current context, swtch() would return and the tail end of the expand() function would execute. So inside expand() a call is made to save the stack state so that when swtch() restores this state, the return skips over the expand() function entirely. [ML] I don't understand that. But, then again, I am not supposed to :) P.S I did understand it, but it was too good an opportunitiy to miss. /Marino To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Can't boot from 1st disk on 2nd IDE controller
Santiago Perez-Cacho Jr. wrote: changing root device to wd1s1a ^^ changing root device to wd1a error 6: panic : cannot mount root (2) It doesn't matter what I set as num_ide_disks and rootdev, the system always tries to mount partitions on wd1. Is this a known issue or am I doing something wrong? Someone here had the same problem, and modified the source code to deal with it. The easiest solution is simply to use wd1. Instead of configuring your second IDE as wd2, configure it as wd1. -- Daniel C. Sobral(8-DCS) d...@newsguy.com She just looked at him over the rotating pencil like, how slow can a mammal be and still have respiratory functions? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: LINUX clone? sched_yield?
Hi, On Sat, 30 Jan 1999, Richard Seaman, Jr. wrote: You need to: 1) Upgrade your source tree to Jan 28 or later for 3.X or Jan 26 or later for 4.0 current, and make world and config and remake and install a new kernel, That's ok now :-). Thanks, Paulo. -- ... Overall we've found FreeBSD to excel in performace, stability, technical support, and of course price. Two years after discovering FreeBSD, we have yet to find a reason why we switch to anything else -David Filo, Yahoo! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: SIOCADDMULTI doesn't work, proposed fix
On Mon, 1 Feb 1999 02:02:48 -0500 (EST), Bill Paul wp...@skynet.ctr.columbia.edu said: to compare 0 bytes worth of data and returns success). In my opinion, this is a bug: either the equal() macro should return false, or the zero length field should be detected by a sanity check and the function should return EINVAL. OK, I'll agree that this is a bug. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same woll...@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: nuts'n'bolts in vfs_bio
:Hello Matthew, : :thank you for reviewing vfs_bio.c. Your patch seems to :solve the problem with NFS writes remaining uncommitted. :At the time I can't see any NFS related data corruption. : :But when shutting down the server it still panics complaining :about dirty bufs. (happens in 9 out of 10 times). : : Bjoern I haven't been able to reproduce this one yet. I can see how there might be dirty buffers on the client, but there shouldn't be dirty buffers on the server. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: nuts'n'bolts in vfs_bio
I've seen this for a non-NFS case. On Mon, 1 Feb 1999, Matthew Dillon wrote: :Hello Matthew, : :thank you for reviewing vfs_bio.c. Your patch seems to :solve the problem with NFS writes remaining uncommitted. :At the time I can't see any NFS related data corruption. : :But when shutting down the server it still panics complaining :about dirty bufs. (happens in 9 out of 10 times). : : Bjoern I haven't been able to reproduce this one yet. I can see how there might be dirty buffers on the client, but there shouldn't be dirty buffers on the server. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: Kernel wont compile
On 31-Jan-99 Tim Preece wrote: In file included from ../../sys/types.h:48, from ../../sys/param.h:56, from ../../i386/i386/genassym.c:45: ../../sys/inttypes.h:11: parse error before `int8_t' ../../sys/inttypes.h:11: warning: data definition has no type or storage class Parse error? Mmmm, I believe I once had such a problem which I fixed by first rebuilding lex and yacc. Try it and let us know =) --- Jeroen Ruigrok van der Werven It's a Dance of Energy, asmodai(at)wxs.nl when the Mind goes Binary... Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Powered by Knowledge Know-how http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
how to run a cvs server ?
Sorry if this is not 100% freebsd related... i wonder what should i use to run a local cvs server (to understand, something i can access setting CVSROOT=:pserver:u...@host:/pathname) i haven't found anything obvious with man -k cvs or man -k pserver... thanks luigi ---+- Luigi RIZZO . EMAIL: lu...@iet.unipi.it. Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) ---+- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: how to run a cvs server ?
check out http://www.cyclic.com/ (makers of CVS) or my favorite cvs manual at: http://www.loria.fr/~molli/cvs/doc/cvs_toc.html The section of the online manual that talks about how to set up a pserver is at: http://www.loria.fr/~molli/cvs/doc/cvs_2.html#SEC30 -john -Original Message- From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-curr...@freebsd.org]on Behalf Of Luigi Rizzo Sent: Monday, February 01, 1999 12:31 PM To: curr...@freebsd.org Subject: how to run a cvs server ? Sorry if this is not 100% freebsd related... i wonder what should i use to run a local cvs server (to understand, something i can access setting CVSROOT=:pserver:u...@host:/pathname) i haven't found anything obvious with man -k cvs or man -k pserver... thanks luigi ---+- Luigi RIZZO . EMAIL: lu...@iet.unipi.it. Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) ---+- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: btokup().. patch to STYLE(9) (fwd)
Someone wrote: You are not supposed to understand this. I'd suggest that there's a vast difference in the intended audience of the code containing the above comment and FreeBSD. Not to mention a 20+ year gap in time. Whilst the official codebase may be under the control of a select group of committers, the code should be capable of being understood by anyone who is reasonably proficient with C. If understanding the kernel requires that you be a guru-level expert in C, then people won't bother. FreeBSD will wind up being a small collection of people trying to outdo each other in obtuseness. Whenever someone suggests adding something new, there's usually a chorus of `where are the patches'. People can't write patches if they can't understand the code they want to modify. BTW, anyone looking further afield from the above comment might notice code like: register *foo; foo = u.u_area; foo-p_xyzzy =+ n; There aren't may C compilers left that can handle this sort of code... Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Can't boot from 1st disk on 2nd IDE controller
Daniel C. Sobral d...@newsguy.com wrote:
Santiago Perez-Cacho Jr. wrote:
changing root device to wd1s1a
^^
changing root device to wd1a
error 6: panic : cannot mount root (2)
It doesn't matter what I set as num_ide_disks and rootdev, the system
always tries to mount partitions on wd1. Is this a known issue or am I
doing something wrong?
It is a known problem and was discussed here last month. The issue is
basically that BIOS uses a different algorithm to the kernel to count
disks. For various reasons, it's not practical for the kernel to use
the same algorithm as the BIOS. Someone (I think it's Mike Smith) is
looking at a reasonably general kludge to resolve the problem.
Someone here had the same problem, and modified the source code to
deal with it.
I wrote the following kludge. This treats an IDE disk number supplied
by the BIOS as the Nth IDE disk found by the kernel probe. You'll
have to read the original thread for reasons why this solution may not
work in all cases.
Index: i386/i386/autoconf.c
===
RCS file: /home/CVSROOT/./src/sys/i386/i386/autoconf.c,v
retrieving revision 1.110
diff -b -u -r1.110 autoconf.c
--- autoconf.c 1998/10/26 07:05:34 1.110
+++ autoconf.c 1999/01/21 23:18:18
@@ -433,6 +433,10 @@
#define FDMAJOR 2
#define FDUNITSHIFT 6
+/* KLUDGE for bios handling of multiple devices */
+#defineWDMAJOR 0
+intwd_mask = 0;/* mask of WD devices found during probe */
+
/*
* Attempt to find the device from which we were booted.
* If we can do so, and not instructed not to do so,
@@ -467,6 +471,18 @@
slice = COMPATIBILITY_SLICE;
part = RAW_PART;
mindev = unit FDUNITSHIFT;
+ } else if (majdev == WDMAJOR) {
+ /*
+* XXX kludge to handle holes in numbering
+*/
+ for (part = 0, mindev = unit; part 32 mindev = 0; part++)
+ if (wd_mask (1 part))
+ mindev--;
+ if (mindev == -1)
+ unit = part - 1;
+
+ part = B_PARTITION(bootdev);
+ mindev = dkmakeminor(unit, slice, part);
} else {
part = B_PARTITION(bootdev);
mindev = dkmakeminor(unit, slice, part);
Index: i386/isa/wd.c
===
RCS file: /home/CVSROOT/./src/sys/i386/isa/wd.c,v
retrieving revision 1.186
diff -b -u -r1.186 wd.c
--- wd.c1999/01/17 05:46:24 1.186
+++ wd.c1999/01/21 23:18:18
@@ -223,6 +223,8 @@
static struct buf rwdbuf[NWD]; /* buffers for raw IO */
#endif
+extern int wd_mask;/* This is a KLUDGE */
+
static int wdprobe(struct isa_device *dvp);
static int wdattach(struct isa_device *dvp);
static void wdustart(struct disk *du);
@@ -551,6 +553,8 @@
DEVSTAT_NO_ORDERED_TAGS,
DEVSTAT_TYPE_DIRECT |
DEVSTAT_TYPE_IF_IDE);
+ /* KLUDGE: mark drive as present */
+ wd_mask |= 1 lunit;
} else {
free(du, M_TEMP);
wddrives[lunit] = NULL;
Peter
--
Peter Jeremy (VK2PJ)peter.jer...@alcatel.com.au
Alcatel Australia Limited
41 Mandible St Phone: +61 2 9690 5019
ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: btokup().. patch to STYLE(9) (fwd)
=Whilst the official codebase may be under the control of a select =group of committers, the code should be capable of being understood by =anyone who is reasonably proficient with C. Depends on your definition of reasonably, Mr. Special Counselor... That's what is being tirelessly debated for the last several days. -mi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
NAT
Hi! Is there any limit for open NAT connections? If it is where it can be set/change? Thanks, -pal To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Problems with SLIP under 4.0-current...
Hello! % uname -a ..4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sun Jan 31 22:42:09 MSK 1999 % ifconfig sl0 sl0: flags=c013UP,BROADCAST,POINTOPOINT,LINK2,MULTICAST mtu 296 inet 195.2.84.116 -- 195.2.84.115 netmask 0xfff0 broadcast 195.2.84.115 i can't connect to my 195.2.84.115 FreeBSD box... Whats wrong? Rgdz, Осокин Сергей aka oZZ, o...@etrust.ru To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Can't boot from 1st disk on 2nd IDE controller
On Sun, 31 Jan 1999, Mike Smith wrote: set root_disk_unit=2 That did it!!! FreeBSD 4.0-CURRENT is now happily running on the master disk of the second IDE controller. Hello!! I'm running 4.0-CURRENT cvsupped last Friday. I've tried to move my installation from a partition on the first disk of the first IDE controller to a new disk that I've placed as master of the second IDE controller. Everything looks fine until the system tries to mount the root partition and can't find it, so it panics. I've tried breaking the boot process and setting num_ide_disks and rootdev to no avail. Here is the dmesg and error messages: [snip] -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com Thanks to all that answered! - Santiago Perez-Cacho san...@pcfa.es.eu.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Even more interesting NFS problems..
Date: Mon, 1 Feb 1999 14:25:03 +1300
From: Joe Abley jab...@clear.co.nz
Never had a problem with it. Just to confirm that amd is not hideously
broken beyond the point where _some_ people can use it just fine.
Likewise, though nearly all of our NFS activity is among FreeBSD boxen.
And we use NIS for the amd maps:
pau-amma[1] grep amd /etc/rc.conf
amd_enable=YES# Run amd service with $amd_flags (or NO).
amd_flags=-nr -k i386 -l syslog -x all
amd_map_program=ypcat -k amd.master
Such as
pau-amma[2] ypcat -k amd.n
*
host!=${key};os==freebsd3;type:=host;fs:=${autodir}/${rhost}/root;opts:=vers=2,proto=udp,nosuid,grpid,soft,intr
host!=${key};os!=freebsd3;type:=host;fs:=${autodir}/${rhost}/root;opts:=nfsv2,noconn,nosuid,grpid,soft,intr
host==${key};type:=link;fs:=/
/defaults rhost:=${key}
Urrgh... That's a little ugly. Reformatted:
* host!=${key};os==freebsd3;type:=host;fs:=${autodir}/${rhost}/root;\
opts:=vers=2,proto=udp,nosuid,grpid,soft,intr
host!=${key};os!=freebsd3;type:=host;fs:=${autodir}/${rhost}/root;\
opts:=nfsv2,noconn,nosuid,grpid,soft,intr
host==${key};type:=link;fs:=/
/defaults rhost:=${key}
Basically: if this is the host in question, don't even use NFS; let amd
simulate a symlink. Otherwise, use the release-specific incantation to
force the use of NFS V2/UDP.
And amd.n is the map we use for the equivalent of the Sun automounter
/hosts map.
Putting the release-specific incantation stuff in there managed to
shut am-util's whining about nfsv2 up.
And using the rel. 1.2 of contrib/amd/libamu/mount_fs.c made it quit
spitting out silly messages about noconn. (Yes, I also sent a copy of
that patch to the am-utils maintainer.)
david
--
David Wolfskill UNIX System Administrator
d...@whistle.comvoice: (650) 577-7158 pager: (650) 371-4621
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
3c589 doesn't work?
Hi, Is there any reason why the 3c589 in my laptop stopped working after I upgraded it to -current? During boot it now only tells me: Initializing PC-card drivers: ed Instead of 3.0-RELEASE, which says: Initializing PC-card drivers: ed ep Any ideas? Alex -- Gezeur. Ik heb gewoon al lekker met mijn zoon achter de pjoeter gezeten en hem M$ Publisher uitgelegd. Hij vond het heel interessant. Marcel en Erin To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Obutuse code (was: btokup().. patch to STYLE(9) (fwd))
On Tuesday, 2 February 1999 at 7:11:06 +1100, Peter Jeremy wrote:
BTW, anyone looking further afield from the above comment might notice
code like:
register *foo;
foo = u.u_area;
foo-p_xyzzy =+ n;
There aren't may C compilers left that can handle this sort of code...
Ah, but there's better:
#define PS 016
struct {
int integ;
};
sleep(chan, pri)
{
int s;
register *rp;
s = PS-integ;
Greg
--
See complete headers for address, home page and phone numbers
finger g...@lemis.com for PGP public key
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: style 9 pet annoyance
Hi All, You should run vi with set tabstop=3 and shiftwidth=3 and see what you think of the 4 spaces that are IMHO now making the code look really bad. I think that the spaces stuff should be eliminated in favor of only tabs. Yes, i just deal with it. eric haug Saint Louis Univ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Fix problems with SLIP under 4.0-current...
Hello! Here is a patch for SLIP under 4.0-current... After make it, i recompile kernel SLIP work. --- if_sl.c Tue Feb 2 01:42:35 1999 +++ if_sl.c.origTue Feb 2 01:56:41 1999 @@ -222,8 +222,7 @@ #ifdef SLIP_IFF_OPTS SLIP_IFF_OPTS; #else -/* IFF_BROADCAST | IFF_POINTOPOINT | SC_AUTOCOMP | IFF_MULTICAST; */ - IFF_POINTOPOINT | SC_AUTOCOMP | IFF_MULTICAST; + IFF_BROADCAST | IFF_POINTOPOINT | SC_AUTOCOMP | IFF_MULTICAST; #endif sc-sc_if.if_type = IFT_SLIP; sc-sc_if.if_ioctl = slioctl; Plz fix it. Rgdz, Sergey A. Osokin o...@etrust.ru To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: style 9 pet annoyance
On Monday, 1 February 1999 at 17:03:55 -0600, Eric Haug wrote: Hi All, You should run vi with set tabstop=3 and shiftwidth=3 and see what you think of the 4 spaces that are IMHO now making the code look really bad. If that's the case, maybe we shouldn't. I think that the spaces stuff should be eliminated in favor of only tabs. I don't think that will meet with general agreement. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
how to record audio from the casstte thru pci128 audio in
Hello, I would like to know if there exist some software which can allow the user to record the audio from the cassette through the pci128 audio in. If so, would you please show me yours steps. Thanks. Clarence To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Fix problems with SLIP under 4.0-current...
:Hello! :Here is a patch for SLIP under 4.0-current... :After make it, i recompile kernel SLIP work. : :--- if_sl.cTue Feb 2 01:42:35 1999 :+++ if_sl.c.orig Tue Feb 2 01:56:41 1999 :@@ -222,8 +222,7 @@ : #ifdef SLIP_IFF_OPTS : SLIP_IFF_OPTS; : #else :-/*IFF_BROADCAST | IFF_POINTOPOINT | SC_AUTOCOMP | IFF_MULTICAST; */ :- IFF_POINTOPOINT | SC_AUTOCOMP | IFF_MULTICAST; :+ IFF_BROADCAST | IFF_POINTOPOINT | SC_AUTOCOMP | IFF_MULTICAST; : #endif : :Plz fix it. : :Rgdz, :Sergey A. Osokin :o...@etrust.ru Ach. I forgot to restore the original IFF_ options when I added SLIP_IFF_OPTS. I am presuming that you actually mean 'remove IFF_BROADCAST from the default options'. I'll commit a fix. -Matt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
KLD confusion..
Take the following scenario: compiled in: module A kldstat -v shows module 'A' kldload A damned thing succeeds. e.g. [phaser.whistle.com] 516 kldstat -v Id Refs AddressSize Name 12 0xf010 1c8198 kernel.try Contains modules: Id Name 1 rootbus 2 netgraph [...] 21 0xf07f 4000 netgraph.ko Contains modules: Id Name 31 netgraph this is handleable by just not loading 'A' but what about the following: kldload 'B' where B is defined to have a dependency on 'A' and 'A' is already loaded.. A get's loaded again.. leading to REALLY strange behaviour if the kernel is talking to one copy of A and B is talking to the other. I saw a suggestion from Peter to do something to change this, but I didn't understand it at the time. Now I think I saw what he was talking about. can whatever he was suggesting be done? as it is I can't win.. If I don't declare a dependency between A and B then I need to have A compiled in for B to load, but if A is loaded instead of compiled, B can't find it. If I DO declare a dependency, then if I load B it will ALWAYS load A even if it's already compiled in. as a result, the only way I can make it work is if either both A and B are compiled in or A and B are both loaded. Unfortunatly, I have some node that need to be compiled in as the infrastructure is not quite ready for them to be loaded yet, (e.g. interrupt hooking etc.) so ALL ofthe nodes need to be compiled in. Effectively, this is the same as not having KLDs. If I can't use them, what good are they? I've had a look at the code, but I think this would be a 20 minute thing for the right person, rather than a 2 day thing for me... julian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
swap_page_getswapspace failed (don't do stupid things with /dev/mem)
So, never do stupid things as root; that's always my moto. Well, so I did
something stupid as root, but it wasn't inherrently *that* stupid, at
least not stupid enough to require a hard boot :). Below is the source
code for the beginnings of an audit daemon--all it does is disable
auditing on its own process, then read from /dev/audit. My goal was
simply to make sure that data was going back and forth via the device
correctly.
Except I decided to test that feature that overrides the device filename
(normally /dev/audit). Instead, I chose /dev/mem. Don't do that (ouch).
The machine began to churn -- ok, so the buffer expands as necessary
without limit, which is something that will go away once I actually write
the daemon. But it kept churning, and gradually I lost control of
things--my keyboard, eventually my mouse, and eventually the system just
hung. Retrying it after a hard boot (and let me tell you that the off
switch did not work on my IBM 560E notebook for a few tries :), I tried
again on the console. The system is reduced to an endlessly printed:
swap_pager_getswapspace: failed
from the kernel. And needless to say, it loops fairly tightly and we
don't get much in the way of key-pressing. Clearly, this is not something
you should do with /dev/mem, but how was I to know :). Perhaps someone
could determine if there is a race condition/etc that allows this
condition to be entered, and instead default to killing the process or
something. My kernel code is a few days old on the 4.0-CURRENT branch.
Source: auditd.c (just disable auditing stuff to make it compile). Invoke
as auditd /dev/mem.
/*-
* Copyright (c) 1999 Robert Watson
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
*notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
*notice, this list of conditions and the following disclaimer in the
*documentation and/or other materials provided with the distribution.
*
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*
* $Id: $
*/
/*
* User-land audit daemon
* Listens on /dev/audit reading out records, and dropping them into
* /var/log/audit.
* Disables its own auditing to prevent nasties.
*/
#include sys/types.h
#include sys/audit.h
#include sys/fcntl.h
#include sys/uio.h
#include stdio.h
#include stdlib.h
#include unistd.h
#include auditd.h
void usage(void)
{
fprintf(stderr, auditd [-d] [-f auditdevice]\n);
exit(-1);
}
void main(int argc, char *argv[])
{
int i, fd, size, bufsize, not_daemon;
charch, *buf, *devfile=AUDIT_DEVICE;
not_daemon = 0;
while ((ch = getopt(argc, argv, df:)) != -1) {
switch(ch) {
case 'd':
not_daemon = 1;
break;
case 'f':
devfile = optarg;
break;
default:
/* warnx(unknown flag -%c ignored, optopt); */
usage();
}
}
buf = (char *) malloc(AUDIT_DEF_BUF_SIZE * sizeof(char));
if (!buf) {
fprintf(stderr, auditd: unable to malloc buffer\n);
exit(-1);
}
bufsize = AUDIT_DEF_BUF_SIZE;
i = aud_switch(AUD_STATE_OFF);
if (i == -1) {
perror(auditd: aud_switch);
exit(-1);
}
fd = open(devfile, O_RDONLY);
if (fd == -1) {
perror(auditd: open: audit device);
exit(-1);
}
if (!not_daemon) {
i = daemon(1, 1);
if (i == -1) {
perror(auditd: daemon);
exit(-1);
}
}
while (1) {
/* read the size of the next block */
i = read(fd, size, sizeof(size));
if (i == sizeof(size)) {
if (size bufsize) {
Re: style 9 pet annoyance
On Tue, 2 Feb 1999, Greg Lehey wrote: On Monday, 1 February 1999 at 17:03:55 -0600, Eric Haug wrote: Hi All, You should run vi with set tabstop=3 and shiftwidth=3 and see what you think of the 4 spaces that are IMHO now making the code look really bad. If that's the case, maybe we shouldn't. Having 4 (not 3) spaces would be a better idea. Many people do this. I think that the spaces stuff should be eliminated in favor of only tabs. I don't think that will meet with general agreement. I don't see why it shouldn't, except people like to be stuck in their ways. If everyone could just echo set ts=4 sw=4 .exrc, we wouldn't have these tab/space arguments. That's probably way too much to ask, of course. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Make world failure in lpr.c
Hi, 4.0-current sources current as of 9pm EST. Is anyone else seeing this problem? Version 1.28 (wollman) seems to have broken this... The relevant pieces being: +static char*Uflag; /* user name specified with -U flag */ + uflag = optarg; uflag = optarg;looks like it should be Uflag. Thanks, John === usr.sbin/lpr/lpr cc -nostdinc -O -pipe -I/usr/src/usr.sbin/lpr/lpr/../common_source -Wall -Wnested-externs -Wmissing-prototypes -Wno-unused -Wredundant-decls -Wstrict-prototypes -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/lpr/lpr/lpr.c /usr/src/usr.sbin/lpr/lpr/lpr.c: In function `main': /usr/src/usr.sbin/lpr/lpr/lpr.c:192: `uflag' undeclared (first use this function) /usr/src/usr.sbin/lpr/lpr/lpr.c:192: (Each undeclared identifier is reported only once /usr/src/usr.sbin/lpr/lpr/lpr.c:192: for each function it appears in.) *** Error code 1 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
lpr.c problem (never mind)
Hi, I see 1.29 (the fix) as of 10:30 EST... Thanks, John To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
3.0-current(12/98) - RELENG_3 problems
I had a hoard of problems upgrading a 3.0-current a.out system circa ~12/7/98 to RELENG_3. After CVSuping, running make aout-to-elf-build would complain about OBJFORMAT previously being set in /etc/make.conf (which I don't think it was) and suggested I override it. Setting OBJFORMAT to elf, the aout-to-elf would fail unable to find make. Setting OBJFORMAT to aout, cause a nasty warning about a.out not being supported. I tried a few combinations and could not get aout-to-elf to build. However, I was around this by: setenv OBJFORMAT aout setenv REALLY_WANT_DEPRECIATED_AOUT 1 make buildworld mergemaster make installworld reboot make upgrade Kurt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: swap_page_getswapspace failed (don't do stupid things with /dev/mem)
:So, never do stupid things as root; that's always my moto. Well, so I did :something stupid as root, but it wasn't inherrently *that* stupid, at :least not stupid enough to require a hard boot :). Below is the source :... :Except I decided to test that feature that overrides the device filename :(normally /dev/audit). Instead, I chose /dev/mem. Don't do that (ouch). :The machine began to churn -- ok, so the buffer expands as necessary :without limit, which is something that will go away once I actually write :... :swap_pager_getswapspace: failed : :from the kernel. And needless to say, it loops fairly tightly and we :... Uh. Mm.. Hmm :-) i = read(fd, size, sizeof(size)); ... malloc(bufsize * sizeof(char)) i = read(fd, buf, bufsize); When you are reading /dev/mem, 'size' can turn out to be anything. You are then allocating 'size' bytes ( which could be some insane value ). Finally, you try to read() from /dev/mem into the buffer the same insane value. The system is almost certainly trying to kill this process, but it can't because the process is stuck in an uninterruptable system read() of an insane amount of data. I don't think there is anything to 'fix' here. The system is making the best of a bad situation. Perhaps, though, we could test for signal 9 within the insanely huge read() loops and pop out. -Matt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: swap_page_getswapspace failed (don't do stupid things with /dev/mem)
On Mon, 1 Feb 1999, Matthew Dillon wrote: Uh. Mm.. Hmm :-) i = read(fd, size, sizeof(size)); ... malloc(bufsize * sizeof(char)) i = read(fd, buf, bufsize); When you are reading /dev/mem, 'size' can turn out to be anything. You are then allocating 'size' bytes ( which could be some insane value ). Finally, you try to read() from /dev/mem into the buffer the same insane value. The system is almost certainly trying to kill this process, but it can't because the process is stuck in an uninterruptable system read() of an insane amount of data. I don't think there is anything to 'fix' here. The system is making the best of a bad situation. Perhaps, though, we could test for signal 9 within the insanely huge read() loops and pop out. So this probably works for non-root users on files like /dev/zero that can produce as much data as you might be interested in, suggesting a fun denial of service attack for the bored and/or insane. Robert N Watson rob...@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: 03 01 DD 8E 15 67 48 73 25 6D 10 FC EC 68 C1 1C Carnegie Mellon Universityhttp://www.cmu.edu/ TIS Labs at Network Associates, Inc. http://www.tis.com/ SafePort Network Services http://www.safeport.com/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: swap_page_getswapspace failed (don't do stupid things with /dev/mem)
: :So this probably works for non-root users on files like /dev/zero that can :produce as much data as you might be interested in, suggesting a fun :denial of service attack for the bored and/or insane. : : Robert N Watson : :Carnegie Mellon Universityhttp://www.cmu.edu/ :TIS Labs at Network Associates, Inc. http://www.tis.com/ :SafePort Network Services http://www.safeport.com/ Presumably the datasize limit can be used restrict the size of the process. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: swap_page_getswapspace failed (don't do stupid things with /dev/mem)
On Mon, 1 Feb 1999, Robert Watson wrote:
On Mon, 1 Feb 1999, Matthew Dillon wrote:
Uh. Mm.. Hmm :-)
i = read(fd, size, sizeof(size));
... malloc(bufsize * sizeof(char))
i = read(fd, buf, bufsize);
When you are reading /dev/mem, 'size' can turn out to be anything.
You are then allocating 'size' bytes ( which could be some insane
value ). Finally, you try to read() from /dev/mem into the buffer
the same insane value.
The system is almost certainly trying to kill this process, but it
can't because the process is stuck in an uninterruptable system read()
of an insane amount of data.
I don't think there is anything to 'fix' here. The system is making
the best of a bad situation. Perhaps, though, we could test for signal
9 within the insanely huge read() loops and pop out.
So this probably works for non-root users on files like /dev/zero that can
produce as much data as you might be interested in, suggesting a fun
denial of service attack for the bored and/or insane.
/dev/zero isn't too bad DoS-wise. /dev/urandom is much worse - this was
raised a month or so ago (it's probably been one of those repeating problems
people periodically notice but which hadn't ever been fixed).
bde posted this to -security last week:
From b...@zeta.org.au Tue Feb 2 16:16:18 1999
Date: Wed, 27 Jan 1999 23:35:01 +1100
From: Bruce Evans b...@zeta.org.au
To: secur...@freebsd.org
Subject: Re: signal handling in urandom can cause lockup
I finally finished my fix for this.
The problem has very little to do with signal handling, at least under
FreeBSD. It is a general problem with slow devices that can transfer
large amounts of data without blocking. E.g.,
dd if=/dev/urandom of=/dev/null bs=10m count=1
runs at about 1MB per 3.8 seconds on a P5/133, so the read() syscall
for 10MB spends about 38 seconds in the kernel without blocking.
My fix blocks most i/o hog processes in uiomove() and associated
functions if they would be rescheduled if they were running in user
mode. Unfortunately, signals can't be handled at this level since
it would be surprising if disk i/o could be aborted by a signal.
My fix only checks for signals for /dev/urandom. I don't know of
any other devices that need it.
Bruce
diff -c2 src/sys/alpha/include/cpu.h~ src/sys/alpha/include/cpu.h
*** src/sys/alpha/include/cpu.h~Wed Oct 7 21:32:44 1998
--- src/sys/alpha/include/cpu.h Tue Jan 26 00:14:30 1999
***
*** 76,80
* or after the current trap/syscall if in system mode.
*/
! #define need_resched() { want_resched = 1; aston(); }
/*
--- 76,82
* or after the current trap/syscall if in system mode.
*/
! #define need_resched() do { want_resched = 1; aston(); } while
(0)
!
! #define resched_wanted()want_resched
/*
diff -c2 src/sys/i386/include/cpu.h~ src/sys/i386/include/cpu.h
*** src/sys/i386/include/cpu.h~ Tue Sep 1 15:54:52 1998
--- src/sys/i386/include/cpu.h Tue Jan 26 00:13:47 1999
***
*** 84,88
* or after the current trap/syscall if in system mode.
*/
! #define need_resched() { want_resched = 1; aston(); }
/*
--- 84,90
* or after the current trap/syscall if in system mode.
*/
! #define need_resched() do { want_resched = 1; aston(); } while
(0)
!
! #define resched_wanted()want_resched
/*
diff -c2 src/sys/kern/kern_subr.c~ src/sys/kern/kern_subr.c
*** src/sys/kern/kern_subr.c~ Mon Jan 11 03:15:05 1999
--- src/sys/kern/kern_subr.cTue Jan 26 00:41:50 1999
***
*** 45,48
--- 45,49
#include sys/malloc.h
#include sys/lock.h
+ #include sys/resourcevar.h
#include sys/vnode.h
***
*** 52,55
--- 53,60
#include vm/vm_map.h
+ #include machine/cpu.h
+
+ static intuio_yield __P((void));
+
int
uiomove(cp, n, uio)
***
*** 82,85
--- 87,92
case UIO_USERSPACE:
case UIO_USERISPACE:
+ if (resched_wanted())
+ uio_yield();
if (uio-uio_rw == UIO_READ)
error = copyout(cp, iov-iov_base, cnt);
***
*** 140,143
--- 147,152
case UIO_USERSPACE:
case UIO_USERISPACE:
+ if (resched_wanted())
+ uio_yield();
if (uio-uio_rw == UIO_READ) {
if (vfs_ioopt ((cnt PAGE_MASK) == 0)
***
*** 215,218
--- 224,229
cnt = ~PAGE_MASK;
+ if (resched_wanted())
+ uio_yield();
error = vm_uiomove(curproc-p_vmspace-vm_map, obj,
uio-uio_offset, cnt,
Dual console don't work
I use -h -D in /boot.config Today I wanted to boot with monitor and keyboard. All I got was the first stage of the news boot loader on vga and seriel. The prompt itself goes only on seriel so there wasn't a chance to switch the console back to vga without a terminal. -- B.Walter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: how to run a cvs server ?
On Mon, 01 Feb 1999 18:30:40 +0100, Luigi Rizzo wrote: i wonder what should i use to run a local cvs server (to understand, something i can access setting CVSROOT=:pserver:u...@host:/pathname) i haven't found anything obvious with man -k cvs or man -k pserver... Hi Luigi, There is a lot of documnetation available in the FreeBSD info distribution. The FreeBSD Handbook does make reference to the info files. Try ``info cvs'' at the shell prompt. For help on navigating the info system, try ``info info''. If you find info(1) difficult to use, try installing tkinfo from the ports tree or packages. Suggestions should obviously be typed without the quotes. :-) Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
