Re: Error building current

[David O'Brien]

On Thu, Jan 20, 2000 at 11:01:10AM -0800, Tim Moore wrote:
> CVS'uped today:
... 
> gcc/version.c is "dead" in my CVS repository.  Has my repository been
> corrupted somehow?

Please try again.  Did you change release tags or something?  Possibly
checked out RELENG_3 on top of the HEAD or something?
 
-- 
-- David([EMAIL PROTECTED])


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

Re: sysinstall's fdisk/disklabel broken?

[james]

At 19:44 20/01/00 +0100, Anton Berezin wrote:
>On Fri, Jan 21, 2000 at 04:11:24AM +1100, james wrote:
>
> > I was going to use sysinstall's disklabel to repartition/relabel one
> > of my drives, but when i went into it in the post-installation menu it
> > said:
>
> > No disks found!
>
> > BTW i'm using 4.0-CURRENT (obviously), and i cvsupp'd and make world'd
> > about 2 days ago.
>
>I just bumped into this, half an hour ago. :-)
>
>How old is your /stand/sysinstall (it does not get updated as a make
>world process)?
>
># cd /usr/src/release/sysinstall && make all install

I tried that and it still didn't work. :(

Somebody pointed out that it could be that i've accidently included non-PCI 
ata devices from LINT:

device ata0at isa? port IO_WD1 irq 14
device ata1at isa? port IO_WD2 irq 15

I'll get rid of them and recompile and reboot sometime soon and see how it 
goes. Don't know how much difference it'll make because:

ata-isa0: already registered as ata0
ata-isa1: already registered as ata1

is in my dmesg. I presume that means that those non-PCI ata device things 
weren't used anyway.

Cheers




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

buildworld broken on alpha?

[Wilko Bulte]

metoaddr.po.tmp etherent.po.tmp savefile.po.tmp bpf_filter.po.tmp
bpf_image.po.tmp scanner.po.tmp version.po.tmp libpcap_p.a
rm -f grammar.So pcap-bpf.So pcap.So inet.So gencode.So optimize.So
nametoaddr.So etherent.So savefile.So bpf_filter.So bpf_image.So scanner.So
version.So grammar.so pcap-bpf.so pcap.so inet.so gencode.so optimize.so
nametoaddr.so etherent.so savefile.so bpf_filter.so bpf_image.so scanner.so
version.so grammar.So.tmp pcap-bpf.So.tmp pcap.So.tmp inet.So.tmp
gencode.So.tmp optimize.So.tmp nametoaddr.So.tmp etherent.So.tmp
savefile.So.tmp bpf_filter.So.tmp bpf_image.So.tmp scanner.So.tmp
version.So.tmp  libpcap.so.2 libpcap.so  libpcap.so.* libpcap.so
libpcap_pic.a
rm -f .depend /usr/src/lib/libpcap/GPATH /usr/src/lib/libpcap/GRTAGS
/usr/src/lib/libpcap/GSYMS /usr/src/lib/libpcap/GTAGS
===> lib/libposix1e
cd: can't cd to /usr/src/lib/libposix1e
*** Error code 2

Stop in /usr/src/lib.
*** Error code 1

Stop in /usr/src.
*** Error code 1

This is a fresh -current on alpha. On intel buildworld seems to continue.

-- 
Wilko Bulte Arnhem, The Netherlands   - The FreeBSD Project 
WWW : http://www.tcja.nl  http://www.freebsd.org


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

Re: Still getting 'R/W mount of / denied ...' after valid fsck

[Poul-Henning Kamp]

In message <[EMAIL PROTECTED]>, Matthew Dillon writes:

>I am still getting 'R/W mount of / denied' failures when rebooting a
>crashed -current machine.  It thinks / is dirty but the fsck on it ran
>just fine.  If I immediately /sbin/reboot again the machine comes up
>normally.

fsck fails to remount and fails to tell that, so despite the fact
that the fs on the disk is clean the kernel doesn't get told.

I belive Paul Saab is working on some improvements to fsck which
will help this...

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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

Re: Error building current

[Warner Losh]

In message <[EMAIL PROTECTED]> "David O'Brien" writes:
: On Thu, Jan 20, 2000 at 11:01:10AM -0800, Tim Moore wrote:
: > CVS'uped today:
: ... 
: > gcc/version.c is "dead" in my CVS repository.  Has my repository been
: > corrupted somehow?
: 
: Please try again.  Did you change release tags or something?  Possibly
: checked out RELENG_3 on top of the HEAD or something?

I hit this problem as well.  Put 'delete' in your cvsup file.
Otherwise you'll get screwed.  This is a misfeature of cvsup, imho,
but if you don't have 'delete' in your cvsup file, versions that go
away aren't removed and branch changes don't seem to happen...

Warner


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

RE: error wich devices ad*

[joanra]

I have done all what you have told me to do, but it still doesn't work. Now
i have another problem, i have removed the DEVICES WD* (as you told me) and
i can't mount partitions. It mounts WD on / but just as READ-ONLY and i
can't do anything, How could i mount it whith writing permisions to continue
trying things??

PS: the error message at init is the same that appeared me the first time
when i make: mount /dev/as2s1f /usr (for example), the error is:
mount: device block required

please help
-Mensaje original-
De: Nick Hibma <[EMAIL PROTECTED]>
Para: joanra <[EMAIL PROTECTED]>
Fecha: jueves, 20 de enero de 2000 23:32
Asunto: Re: error wich devices ad*


>
>Boot with kernel.old and remake all your devices:
>
> cp /usr/src/etc/MAKEDEV /dev/MAKEDEV
> cd /dev
> sh MAKEDEV all
>
>and make sure you update /etc/fstab as well. wd -> ad, wcd -> acd. Then
>do a to clean up your device tree:
>
> cd /dev
> rm -f wcd* wd* rwcd* rwd*
>
>Nick
>
>On Thu, 20 Jan 2000, joanra wrote:
>
>> Hi when i run freebsd, display:
>>
>> Mounting root from ufs: /dev/ad2s1a
>> no such device ad
>> setrootbyname failed
>> ffs_mountroot: can't find rootvp
>> root mount failed: 6
>> mounting root from ufs: wd2s1a
>> swapon: /dev/ad2s1b: device not configure
>> Automatic reboot in ptogress
>> can't open /dev/ad2s1a: device not configured
>>
>> my fstab:
>>
>> # DeviceMountpoint
>> /dev/ad2s1b none
>> /dev/ad2s1a /
>> /dev/ad2s1f /usr
>> /dev/ad2s1e /var
>> /dev/cd0c   /cdrom  cd9660
>> proc/proc
>>
>> anyone help me please?
>>
>> P.S: i recompiled a new kernel, and i create the new devices ad*, and my
hd
>> is seconday
>>
>> thanks
>>
>>
>>
>> To Unsubscribe: send mail to [EMAIL PROTECTED]
>> with "unsubscribe freebsd-current" in the body of the message
>>
>
>--
>[EMAIL PROTECTED]
>[EMAIL PROTECTED]  USB project
>http://www.etla.net/~n_hibma/
>
>



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

Re: Problems with PCMCIA Cards

[Wes Peters]

Bill Fumerola wrote:
> 
> On Wed, Jan 19, 2000 at 03:50:49PM -0700, Wes Peters wrote:
> 
> > Mmm...  Good point.  This means updating code and compiling a new kernel
> > every time Joe's hardware company sticks their own name on a generic OEM
> > PCI or PCCard, doesn't it?  I love this industry.
> 
> Do the above and try and figure out and track down if the marketing information
> matches what actually shows up on the product, now find out if it works exactly
> the same or if there is some stupid quirk that Joe's Hardware added to the
> chip Welcome to Bill Paul's hell. :->

I know, Bill, I know.  I used to work for a company that made (well, OEM'd)
PCMCIA cards, and made one of a very few PCMCIA-based routers in the world.

;^)

-- 
"Where am I, and what am I doing in this handbasket?"

Wes Peters Softweyr LLC
[EMAIL PROTECTED]   http://softweyr.com/


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

Current not compiling.

[Raul Zighelboim]

Hello there
the last 3 days of current 'make buildworld' have ended with:

speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref'
/usr/local/lib/libcrypto.a(rsa_lib.o): In function `RSA_new_method':
rsa_lib.o(.text+0x91): undefined reference to `RSA_PKCS1_RSAref'
/usr/local/lib/libcrypto.a(err_all.o): In function
`ERR_load_crypto_strings':
err_all.o(.text+0x33): undefined reference to `ERR_load_RSAREF_strings'
*** Error code 1

Stop in /usr/src/secure/usr.bin/openssl.
*** Error code 1

Stop in /usr/src/secure/usr.bin.
*** Error code 1

Stop in /usr/src/secure.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.



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

half-fix for stream.c

[Alfred Perlstein]

you can find it at:

http://www.freebsd.org/~alfred/tcp_fix.diff

-- 
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]


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

Re: half-fix for stream.c

[Don Lewis]

On Jan 20,  5:41pm, Alfred Perlstein wrote:
} Subject: half-fix for stream.c
} you can find it at:
} 
} http://www.freebsd.org/~alfred/tcp_fix.diff

Don't you want to defer the checksum even further (after the bogus
packets have been dropped)?  It doesn't look like the change you
made will save any unnecessary work.

Also, it looks like you can save a few CPU cycles by only searching
for wildcard sockets if the SYN flag is set, so only set the 6th
argument to in_pcblookup_hash() if (thflags & TH_SYN) is true.


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

Re: Error building current

[John Polstra]

In article <[EMAIL PROTECTED]>,
Warner Losh  <[EMAIL PROTECTED]> wrote:
> 
> I hit this problem as well.  Put 'delete' in your cvsup file.
> Otherwise you'll get screwed.  This is a misfeature of cvsup, imho,

I'm sorry you think so.  I did it that way for backward compatibility
with sup.  If I hadn't made it compatible, I never could have
persuaded anybody to try the software.

Also, there are situations (e.g., maintaining local modifications
in your repository) where delete should not be used.  So it really
needs to be an option.  It would be better if the default were to
delete and there was a "nodelete" option.  But that wouldn't have been
compatible.

John
-- 
  John Polstra   [EMAIL PROTECTED]
  John D. Polstra & Co., Inc.Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa



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

Re: half-fix for stream.c

[Alfred Perlstein]

* Jim Bloom <[EMAIL PROTECTED]> [000120 18:02] wrote:
> In you fix below, shouldn't the second block of NTOHx actually be HTONx.  I
> realize that this works because the functions are the same, but it should be
> coded correctly.
> 
> Jim Bloom
> [EMAIL PROTECTED]
> 
> +   NTOHL(th->th_seq);
> +   NTOHL(th->th_ack);
> +   NTOHS(th->th_win);
> +   NTOHS(th->th_urp);
> +   th->th_sum = in_cksum(m, len);
> +   if (th->th_sum) {
> +   tcpstat.tcps_rcvbadsum++;
> +   goto drop;
> +   }
> +   NTOHL(th->th_seq);
> +   NTOHL(th->th_ack);
> +   NTOHS(th->th_win);
> +   NTOHS(th->th_urp);

hmm, that's prolly right, i've been on irc trying to discuss this with
people and bit harried.

I'm sure there's a better way to do this, but the idea is to move
the checksum until after the pcb lookup, but i still have to look
at this more.

-Alfred


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

Re: ...(file transfer crashes system) ethernet driver or IP stack bug?

[arnee]

Matthew Dillon wrote:

> :Fatal trap 12: page fault while in kernel mode
> :fault virtual address  = 0x8bc93139
> :fault code = supervisor read, page not present
> :instruction pointer= 0x8:0xc018aa5f
> :stack pointer  = 0x10:0xc437be0c
> :frame pointer  = 0x10:0xc437be28
> :code segment   = base 0x0, limit 0xf, type 0x1b
> :   = DPL 0, pres 1, def32 1, gran 1
> :processor eflags   = interrupt enabled, resume, IOPL = 0
> :current process= 163 (smbd)
> :interrupt mask =
> :kernel: type 12 trap, code=0
> :Stopped at  ip_input+0xc7:   lock adcb  $0x75,%al
> :db> trace
> :ip_input(c03ca500) at ip_input+0xc7
> :ipintr(c0209880,0,c021e3c2,c0156ac3,0) at ipintr+0x4b
> :swi_net_next(c3fe1b40,c437bed0,c435bedc,0,0) at swi_net_next
> :recvit(c410a400,7,c437bf20,0,c410a400) at recvit+0x101
> :recvfrom((c410a400,c437bf80,281b0ec8,6bbb,) at recvfrom+0x6c
> :syscall(bfbf002f,c437002f,bfbf002f,,6bbb) at syscall+0x176
> :Xint0x80_syscall() at Xint0x80_syscall+0x26
> :
> :By this time I am suspecting that it might be samba. So, I tried another scenario.
>
> This looks to me like a bug in either the ethernet driver or
> the IP stack.
>
> Could you supply the output from 'dmesg'?  With NFS and softupdates not
> being the cause this isn't really in my court any more but maybe
> someone else in -current has some ideas.
>
> -Matt
> Matthew Dillon
> <[EMAIL PROTECTED]>

Thanks for the help matt. Here is the 'dmesg'...

arnee

FreeBSD 4.0-CURRENT-2118-08:18 #4: Tue Jan 18 13:17:49 PST 2000
root@groovinit:/usr/src/sys/compile/GROOVINIT
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 249919443 Hz
CPU: Cyrix 6x86MX (249.92-MHz 686-class CPU)
  Origin = "CyrixInstead"  Id = 0x601  Stepping = 1  DIR=0x1453
  Features=0x80a135
real memory  = 29360128 (28672K bytes)
avail memory = 25792512 (25188K bytes)
Preloaded elf kernel "kernel" at 0xc02c9000.
md0: Malloc disk
npx0:  on motherboard
npx0: INT 16 interface
pcib0:  on motherboard
pci0:  on pcib0
isab0:  at device 1.0 on pci0
isa0:  on isab0
ata-pci0:  port
0x4000-0x400f,0xa8c42268-0xa8c4226b,0x35d8a0c0-0x35d8a0c7,0xc7cc0-0xc7cc3,0x42140728-0x4214072f
irq 0 at device 1.1 on pci0
ata-pci0: Busmastering DMA supported
ata-pci1:  port
0xf080-0xf0bf,0xf7e0-0xf7e3,0xf790-0xf797,0xf7f0-0xf7f3,0xf7a0-0xf7a7 mem
0xffac-0xffad irq 11 at device 13.0 on pci0
ata-pci1: Busmastering DMA supported
ata2 at 0xf7a0 irq 11 on ata-pci1
dc0: <82c169 PNIC 10/100BaseTX> port 0xf200-0xf2ff mem 0xffaaff00-0xffaa irq 9 at
device 15.0 on pci0
dc0: Ethernet address: 00:a0:cc:58:fa:0f
miibus0:  on dc0
ukphy0:  on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
vga-pci0:  port 0xf400-0xf47f mem
0xffaf-0xffaf,0xff40-0xff7f irq 10 at device 20.0 on pci0
fdc0:  at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
atkbdc0:  at port 0x60-0x6f on isa0
atkbd0:  irq 1 on atkbdc0
vga0:  at port 0x3b0-0x3df iomem 0xa-0xb on isa0
sc0:  on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0:  at port 0x378-0x37f irq 7 flags 0x40 on isa0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ad4:  ATA-4 disk at ata2 as master
ad4: 16448MB (33687360 sectors), 33420 cyls, 16 heads, 63 S/T, 512 B/S
ad4: 16 secs/int, 1 depth queue, UDMA66
Mounting root from ufs:/dev/ad4s1a





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

Re: error wich devices ad*

[Darryl Okahata]

"joanra" <[EMAIL PROTECTED]> wrote:

> I have done all what you have told me to do, but it still doesn't work. Now
> i have another problem, i have removed the DEVICES WD* (as you told me) and
> i can't mount partitions. It mounts WD on / but just as READ-ONLY and i
> can't do anything, How could i mount it whith writing permisions to continue
> trying things??

 At this point, you're slightly screwed -- you can probably fix your 
system, but it's going to take some work.  I hope you have backups.

> -Mensaje original-
> De: Nick Hibma <[EMAIL PROTECTED]>
> 
> >
> >Boot with kernel.old and remake all your devices:
> >
> > cp /usr/src/etc/MAKEDEV /dev/MAKEDEV
> > cd /dev
> > sh MAKEDEV all

 This will probably only work if you did an installworld, as MAKEDEV
needs the new version of /sbin/mknod; the old, existing version won't
work.  Also note that "MAKEDEV all" doesn't make the slice devices
(e.g., /dev/ad0s1a); you'll have to explicitly tell MAKEDEV to build
those.

 If you didn't do an installworld, but did rebuild the kernel and
attempted to mess with /dev, the general procedure for fixing this is:

[ DANGER: I HAVE NOT TESTED THE FOLLOWING PROCEDURE.  I AM CREATING THE
  FOLLOWING PROCEDURE FROM MEMORY, AND SO IT MAY BE MISSING KEY PARTS,
  WHICH COULD DESTROY ALL DATA ON YOUR SYSTEM.  MAKE SURE YOU HAVE
  BACKED UP YOUR SYSTEM BEFORE TRYING ANY OF THE FOLLOWING. ]

1. Boot from a fixit floppy/CDROM.  In the past, I've used a FreeBSD
   3.3-RELEASE CDROM for this.

   [ I'm also amazed that the following procedure works, given that I'm
 running -current binaries under 3.3-RELEASE.  ]

2. Mount the hard disk.  I generally mount it as "/mnt".

3. Do (assuming /mnt as the mount point):

cd /mnt
mv dev dev.old
mkdir dev
cd dev
cp /mnt/usr/src/etc/MAKEDEV .

4. If you did a buildworld:

cp /mnt/usr/obj/usr/src/sbin/mknod/mknod /sbin

   If you did not do a buildworld (yes, this is messy, but it should
   work):

cd /mnt/usr/src/sbin/mknod
make
cp mknod /sbin

5. Do:

cp /mnt/usr/src/etc/group /etc  # Needed for group "wheel"
cd /mnt/dev
sh ./MAKEDEV all
sh ./MAKEDEV ad2s1a # since you use the ad2 slices

   NOTE 1: the first time you run MAKEDEV, it may complain about missing
   programs; if so, put/install the missing programs into the correct
   locations, and re-run MAKEDEV (until no errors occur).

   NOTE 2: You don't have to execute "sh MAKEDEV ad2s1b", etc., to make
   the other slice devices; running "sh MAKEDEV ad2s1a" will create all
   of the "ad2s1*" devices.

> >and make sure you update /etc/fstab as well. wd -> ad, wcd -> acd. Then
> >do a to clean up your device tree:
> >
> > cd /dev
> > rm -f wcd* wd* rwcd* rwd*
> >
> >Nick
> >
> >On Thu, 20 Jan 2000, joanra wrote:
> >
> >> Hi when i run freebsd, display:
> >>
> >> Mounting root from ufs: /dev/ad2s1a
> >> no such device ad
> >> setrootbyname failed
> >> ffs_mountroot: can't find rootvp
> >> root mount failed: 6
> >> mounting root from ufs: wd2s1a
> >> swapon: /dev/ad2s1b: device not configure
> >> Automatic reboot in ptogress
> >> can't open /dev/ad2s1a: device not configured
> >>
> >> my fstab:
> >>
> >> # DeviceMountpoint
> >> /dev/ad2s1b none
> >> /dev/ad2s1a /
> >> /dev/ad2s1f /usr
> >> /dev/ad2s1e /var
> >> /dev/cd0c   /cdrom  cd9660
> >> proc/proc
> >>
> >> anyone help me please?
> >>
> >> P.S: i recompiled a new kernel, and i create the new devices ad*, and my
> hd
> >> is seconday
> >>
> >> thanks
> >>
> >>
> >>
> >> To Unsubscribe: send mail to [EMAIL PROTECTED]
> >> with "unsubscribe freebsd-current" in the body of the message
> >>
> >
> >--
> >[EMAIL PROTECTED]
> >[EMAIL PROTECTED]  USB project
> >http://www.etla.net/~n_hibma/
> >
> >
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
> 


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

Re: Current not compiling.

[Sheldon Hearn]

On Thu, 20 Jan 2000 18:53:12 CST, Raul Zighelboim wrote:

> the last 3 days of current 'make buildworld' have ended with:
> 
> speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref'

So you haven't been reading your -current mail for 3 days?  Bad
pussycat. :-)

As stated several times on this mailing list by the guy who knows it's a
problem and is working on it, the openssl build in CURRENT is picking up
libcrypto in /usr/local/lib.  Either pkg_delete or move aside your
openssl installation.

Ciao,
Sheldon.


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

Re: Still getting 'R/W mount of / denied ...' after valid fsck

[Bruce Evans]

On Thu, 20 Jan 2000, Poul-Henning Kamp wrote:

> In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
> 
> >I am still getting 'R/W mount of / denied' failures when rebooting a
> >crashed -current machine.  It thinks / is dirty but the fsck on it ran
> >just fine.  If I immediately /sbin/reboot again the machine comes up
> >normally.
> 
>   fsck fails to remount and fails to tell that, so despite the fact
>   that the fs on the disk is clean the kernel doesn't get told.
> 
>   I belive Paul Saab is working on some improvements to fsck which
>   will help this...

fsck is supposed to be improved already, but the improvements may have
broken the (misconfigured) case where the root device is still a bdev.

Bruce



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

Re: ...(file transfer crashes system) ethernet driver or IP stack bug?

[Matthew Dillon]

:Thanks for the help matt. Here is the 'dmesg'...
:
:arnee

Hmm.  If possible I would try backing away from the ata driver entirely
and going back to the 'wd' driver.  This isn't to say that the ata
driver is the problem, but it *could* be the problem.   A number of people
have had problems with the ata driver.  There isn't anything else in your
config that strikes a chord... the rest of it looks ok to me.

-Matt



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

Re: ...(file transfer crashes system) ethernet driver or IP stack bug?

[Peter Wemm]

Matthew Dillon wrote:
> 
> :Thanks for the help matt. Here is the 'dmesg'...
> :
> :arnee
> 
> Hmm.  If possible I would try backing away from the ata driver entirely
> and going back to the 'wd' driver.  This isn't to say that the ata
> driver is the problem, but it *could* be the problem.   A number of peopl
e
> have had problems with the ata driver.  There isn't anything else in your
> config that strikes a chord... the rest of it looks ok to me.

Not possible. the wd driver doesn't support the Promise ATA-66 controllers
that he is using.

Cheers,
-Peter



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

cvsup 3.4-release to -current

[Matt M.]

Just wondering what potential problems I am facing by going from
3.4-release to -current. I was told on irc that my chances may not be
well.



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

Re: ...(file transfer crashes system) ethernet driver or IP stack bug?

[Matthew Dillon]

:> Hmm.  If possible I would try backing away from the ata driver entirely
:> and going back to the 'wd' driver.  This isn't to say that the ata
:> driver is the problem, but it *could* be the problem.   A number of peopl
:e
:> have had problems with the ata driver.  There isn't anything else in your
:> config that strikes a chord... the rest of it looks ok to me.
:
:Not possible. the wd driver doesn't support the Promise ATA-66 controllers
:that he is using.
:
:Cheers,
:-Peter

Fubar.  The crashes are occuring all over the place -- ip_input, 
ffs_blkfree, ip_output.  Maybe it's a BIOS configuration problem... 
perhaps the ram is configured to be too fast or something like that.  
I don't know.  This has all the earmarks of overclocking or a memory
problem.

-Matt
Matthew Dillon 
<[EMAIL PROTECTED]>


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

Re: cvsup 3.4-release to -current

[f.johan.beisser]

that's very accurate. you'd be better off getting a SNAP image and
upgrading your system from that.

that is, if you really need to do it now.

i'd just wait, untill the final release, since it's coming up Real Soon
Now.

-- jan

On Thu, 20 Jan 2000, Matt M. wrote:

> Just wondering what potential problems I am facing by going from
> 3.4-release to -current. I was told on irc that my chances may not be
> well.
> 

 +-//  f. johan beisser  //--+
  email: jan[at]caustic.org   web: http://www.caustic.org/~jan 
   "knowledge is power. power corrupts. study hard, be evil."



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

Re: ...(file transfer crashes system) ethernet driver or IP stack bug?

[Bill Paul]

Of all the gin joints in all the towns in all the world, arnee had to walk 
into mine and say: 
 
> FreeBSD 4.0-CURRENT-2118-08:18 #4: Tue Jan 18 13:17:49 PST 2000
> root@groovinit:/usr/src/sys/compile/GROOVINIT
> Timecounter "i8254"  frequency 1193182 Hz
> Timecounter "TSC"  frequency 249919443 Hz
> CPU: Cyrix 6x86MX (249.92-MHz 686-class CPU)

Ack...

>   Origin = "CyrixInstead"  Id = 0x601  Stepping = 1  DIR=0x1453
>   Features=0x80a135
> real memory  = 29360128 (28672K bytes)
> avail memory = 25792512 (25188K bytes)
> Preloaded elf kernel "kernel" at 0xc02c9000.
> md0: Malloc disk
> npx0:  on motherboard
> npx0: INT 16 interface
> pcib0:  on motherboard

No, please...

> pci0:  on pcib0
> isab0:  at device 1.0 on pci0
> isa0:  on isab0
> ata-pci0:  port
> 
>0x4000-0x400f,0xa8c42268-0xa8c4226b,0x35d8a0c0-0x35d8a0c7,0xc7cc0-0xc7cc3,0x42140728-0x4214072f
> irq 0 at device 1.1 on pci0
> ata-pci0: Busmastering DMA supported
> ata-pci1:  port
> 0xf080-0xf0bf,0xf7e0-0xf7e3,0xf790-0xf797,0xf7f0-0xf7f3,0xf7a0-0xf7a7 mem
> 0xffac-0xffad irq 11 at device 13.0 on pci0
> ata-pci1: Busmastering DMA supported

Stop, you're killing me...

> ata2 at 0xf7a0 irq 11 on ata-pci1
> dc0: <82c169 PNIC 10/100BaseTX> port 0xf200-0xf2ff mem 0xffaaff00-0xffaa irq 9 at
> device 15.0 on pci0

Aie!

Oh for the love of *god*. Rip this thing out of your machine now. Put it
on the ground. Stomp on it. Repeatedly. Then set it on fire. Bury the
remains in the back yard. Then run - don't walk! - to your local computer
store, put a crowbar in your wallet, and buy a better ethernet card.

Don't whine, don't bitch, don't moan, don't complain that it works with
Windows (actually, I bet it doesn't; not on that hardware, using bus
master DMA for both controllers). Just do it.

You have a Cyrix CPU, and I'm willing to bet you've overclocked it. ("What?
You mean that might have some effect on the situation?") You have a PCI 
chipset which the probe messages don't even identify, and you're using 
not one but *two* bus master devices on it, one of which is a PNIC ethernet
controller that can barely do bus master DMA correctly on a good day. Not 
only that, but you have two ATA controllers in this machine, one of which has 
no devices on it, and you have the damn hard disk on the *second* controller. 
Why do you have two controllers? Why not just use the built-in one!

I'm also missing some information here since I arrived in the middle of
this exchange. You didn't say if you're using 10Mbps or 100Mbps with this
card. And you don't say what it's connected to (hub? switch? vendor?
model?)

Does this have something to do with the PNIC? Oh, probably. But I'm not going
to even attempt to debug this. There's no way in hell I could duplicate this 
hardware configuration locally, and even if I did, I probably couldn't 
duplicate the exact same problem. And even if I could do *that*, I
still wouldn't know how to fix it. I'm sorry, but I've pulled out enough
hair over this damn chip. I'm sure I've wasted at least a couple months
of my life trying to make this thing work reliably. I've added several
software workarounds, I defaulted the stupid transmit threshold setting
to store and forward mode. Well I've had it: no more. I'm through trying
to bitchslap this rotten piece of silicon to its senses. I'm not going to
go nuts every time somebody comes up with yet another oddball hardware
combination. There's a limit to my patience and this chip has reached it.
Now it's somebody else's turn to lose their sanity. I have the datasheet for 
the PNIC at http://www.freebsd.org/~wpaul/PNIC. You have the driver source.
Somebody *else* try and figure it out, and then tell me then answer when
you have it.

That said, if you have overclocked this machine, then un-overclock it *right* 
*now* and never, ever do it again! PCI bus master DMA is goofy enough without
people sticking their fingers in the works.

Man, why does PC hardware have to suck so hard.

-Bill

-- 
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home:  [EMAIL PROTECTED] | Columbia University, New York City
=
 "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=


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

Re: NO_IDEA

[Kris Kennaway]

On Wed, 19 Jan 2000, Terje Elde wrote:

> Because of copyright issues OpenSSL is being built with -DNO_IDEA. IMHO
> it's bad to do this for all systems, as it's only limited in some
> countries.
> 
> What I'm wondering if we could do is to add a COUNTRY=whatever, which
> could be used to look up a value in a file which could provide information
> about patent issues for algorithms like IDEA, as well as be a nice index
> to which ftp server to use by default.

This has already been suggested..it won't be implemented for 4.0, but
might be looked at afterwards. The problem is the extra complexity it
adds..

Kris


"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson



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

boot.flp doesn't reconize dos partition

[Keizo Shimizu]

Hello,

I first made 50MB primary partition (MS-DOS's meaning)
on my 20GB IDE disk and tried to use the rest for FreeBSD current.
But boot.flp/mfsroot.flp made from current snapshots doesn't recognize
dos partition.

Anyone has any idea ?



--
Keizo SHIMIZU ($B@6?eX*;0(B) <[EMAIL PROTECTED]>


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

make release broken

[John Hay]

Hi,

Make release on current is broken. It dies with:

--
>>> Filesystem is 1440 K, -52 left
>>> 4000 bytes/inode, 10 left
touch release.9
0 blocks
Setting up CDROM distribution area
0 blocks
0 blocks
0 blocks
0 blocks
...
0 blocks
0 blocks
0 blocks
cp: /usr/src/release/texts/HARDWARE.TXT: No such file or directory
*** Error code 1

Stop in /usr/src/release.
*** Error code 1

Stop in /usr/src/release.
*** Error code 1

Stop in /usr/src/release.
---

It looks like the handling of HARDWARE.TXT in release/Makefile is broken.

John
-- 
John Hay -- [EMAIL PROTECTED]


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

Re: Problems with an0 and ISA Aironet Card..

[Bill Paul]

Of all the gin joints in all the towns in all the world, Paul Reece had to 
walk into mine and say:
 
> Having a few problems trying to get an ISA Aironet 4800 card working under
> FreeBSD 4.0-CURRENT.  I did try with 3.4-RELEASE first with the
> appropriate drivers, but had even less luck.
 
> What I'm seeing at boot:

Back up. You're leaving out some info.

- When did you buy these cards? (The firmware rev may be an issue.
  knowing when you bought the card helps me figure out if your firmware
  is newer than mine.)
- What sort of machine are you using? (Show us the *whole* dmesg output.
  Timing may also be an issue, in which case I need to know the CPU speed.)
 
> first suspect lines:
> 
> isa0: unexpected tag 14
> isa0: unexpected tag 14

I'm not sure if this is related.
 
> then:
> 
> an0: reset failed
> unknown0:  at port 0x100-0x13f irq 5 on isa0
> an0: reset failed
> unknown1:  at port 0x140-0x17f irq 10 on isa0
> 
> 
> (machine has 2 cards in it).  When trying with NON PNP mode, the cards
> also have the same problem.

Tell us what kernel config line you use when using the card in non-PnP
mode. Note that the switches on the card must all be in the correct
position in order to enable PnP mode: consult your user's manual for
the proper settings. I believe they all need to be in the off position,
however I don't have the manual here at home with me so I could be
mistaken. (I do remember they all have to be set the same way.)

>  PCI cards work fine, just not the ISA
> equivalents..
> 
> Anyone have any clues/hints/tips etc?

Not really. My one and only ISA card works fine, or at least it did when
I did my tests right before I imported the driver. It would help if you
could actually look at the card when the kernel boots to see if the LEDs
flash at all. If the reset is screwing up, then you should see the LEDs
flicker when it tries to access the board. If it's failing to access the
board at all, the LEDs won't change at all.

Try commenting out the code in an_reset() (i.e. make it an empty
function that does nothing) and see if it works then. If it *still*
doesn't work, then there's something else wrong. Try to run the
following program as root:

#include 
#include 
#include 

#include 

#define IOADDR  0x100 /* change to 0x140 for other card */

main()
{
int f;

f = open("/dev/io", O_RDWR);

printf("COMMAND: %x\n", inw(IOADDR));
printf("PARAM0: %x\n", inw(IOADDR + 0x2));
outw(IOADDR + 0x2, 0x1234);
printf("PARAM0: 0x\n", inw(IOADDR + 0x2));

exit(0);
}

This will print out the command and status registers for the card
at iobase 0x100. If the card has been properly activated, you should
see  for the COMMAND and PARAM0 registers initially, then the
program will try to write 0x1234 to the PARAM0 register and read it
back. If it reads back 0x1234, then the card is configured right
and the reset is screwing up. If on the other hand the program prints
 for all of the register contents, then the card is not really
configured properly for address 0x100.

> 
> Cheers.
> 
> 
> Regards,
> Paul.
> 
> (replies to me direct please - not on list)

I'm doing both. Deal with it.

-Bill

-- 
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home:  [EMAIL PROTECTED] | Columbia University, New York City
=
 "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=


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

Re: Problems with an0 and ISA Aironet Card..

[Paul Reece]

On Thu, 20 Jan 2000, Bill Paul wrote:



> Back up. You're leaving out some info.
> 
> - When did you buy these cards? (The firmware rev may be an issue.
>   knowing when you bought the card helps me figure out if your firmware
>   is newer than mine.)

Cards were purchased in the past 6 months.  Revision of the card I'm using
at the moment is 3.13 - I upgraded the firmware to the latest. (Win DGS
under 'status' reports 3.13).

> - What sort of machine are you using? (Show us the *whole* dmesg output.
>   Timing may also be an issue, in which case I need to know the CPU speed.)

CPU: Pentium III/Xeon (451.02-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x673  Stepping = 3
Features=0x383f9ff
real memory  = 201261056 (196544K bytes)
avail memory = 192323584 (187816K bytes)
Preloaded elf kernel "kernel" at 0xc02b4000.
Pentium Pro MTRR support enabled
md0: Malloc disk
npx0:  on motherboard
npx0: INT 16 interface
pcib0:  on motherboard
pci0:  on pcib0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
vga-pci0:  mem
0xe600-0xe6ff,0xe400-0xe4ff irq 11 at device 0.0 on pci1
isab0:  at device 7.0 on pci0
isa0:  on isab0
ata-pci0:  port 0xf000-0xf00f at device 7.1
on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086,
dev=0x7112) at 7.2 irq 10
pci0: unknown card (vendor=0x1319, dev=0x0801) at 8.0 irq 11
pci0: unknown card (vendor=0x1319, dev=0x0802) at 8.1
rl0:  port 0xec00-0xecff mem
0xe700-0xe7ff irq 9 at device 9.0 on pci0
rl0: Ethernet address: 00:c0:df:25:f1:5c
miibus0:  on rl0
rlphy0:  on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
isa0: unexpected tag 14
fdc0:  at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ata-isa0: already registered as ata0
atkbdc0:  at port 0x60-0x6f on isa0
atkbd0:  irq 1 on atkbdc0
psm0:  irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0:  at port 0x3b0-0x3df iomem 0xa-0xb on isa0
sc0:  on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
pcic1: not probed (disabled)
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0:  at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
lpt0:  on ppbus0
lpt0: Interrupt-driven port
plip0:  on ppbus0
ppi0:  on ppbus0
an0: reset failed
unknown0:  at port 0x100-0x13f irq 5 on isa0
ad0:  ATA-4 disk at ata0 as master
ad0: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 1 depth queue, UDMA33
acd0:  CDROM drive at ata0 as slave 
acd0: 128KB buffer, PIO4
acd0: Reads: CD-R, CD-RW, CD-DA stream, packet
acd0: Audio: play, 255 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: no/blank disc inside, unlocked

I've only got one card in the machine now.  Only one 'unexpected tag'
line now..

> Tell us what kernel config line you use when using the card in non-PnP
> mode. Note that the switches on the card must all be in the correct
> position in order to enable PnP mode: consult your user's manual for
> the proper settings. I believe they all need to be in the off position,
> however I don't have the manual here at home with me so I could be
> mistaken. (I do remember they all have to be set the same way.)

for non-PnP mode, they are set as per the manual. Config line for the
above was:

device an0 at isa? port 0x100 irq 5

same result whether I'm using PnP or not. (above output is from PnP).

> Not really. My one and only ISA card works fine, or at least it did when
> I did my tests right before I imported the driver. It would help if you
> could actually look at the card when the kernel boots to see if the LEDs
> flash at all. If the reset is screwing up, then you should see the LEDs
> flicker when it tries to access the board. If it's failing to access the
> board at all, the LEDs won't change at all.

The RED LED statys on during boot, until the kernel tries to init the card
- then the RED LED goes out, and thats it.

> Try commenting out the code in an_reset() (i.e. make it an empty
> function that does nothing) and see if it works then. If it *still*
> doesn't work, then there's something else wrong.

Tried this - doesn't even list the card in the output except for then
unknown line.

> Try to run the
> following program as root:



> This will print out the command and status registers for the card
> at iobase 0x100. If the card has been properly activated, you should
> see  for the COMMAND and PARAM0 registers initially, then the
> program will try to write 0x1234 to the PARAM0 register and read it
> back. If it reads back 0x1234, then the card is configured right
> and the reset is screwing up. If on the other hand the program prints
>  for all of the register contents, then the card is not really
> configured properly for address 0x100.

pcpaul# ./testa 
COM

NO_IDEA

[Terje Elde]

Hi all,

Because of copyright issues OpenSSL is being built with -DNO_IDEA. IMHO
it's bad to do this for all systems, as it's only limited in some
countries.

What I'm wondering if we could do is to add a COUNTRY=whatever, which
could be used to look up a value in a file which could provide information
about patent issues for algorithms like IDEA, as well as be a nice index
to which ftp server to use by default.

Another thing to consider is adding a COMMERCIAL=[yes|no], which could
also help sorting out patent issues.

Just some thoughts...

Terje Elde


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

Re: boot messages for pci devices...

[Jeroen Ruigrok/Asmodai]

-On [2119 08:00], Warner Losh ([EMAIL PROTECTED]) wrote:
>In message <[EMAIL PROTECTED]> Chris Piazza writes:
>: I *thought* I noticed it was different.  I actually find this pretty
>: annoying because it wraps almost all of the lines and makes it difficult
>: to read dmesg.
>
>I don't mind them, but wouldn't object to a generic wrapping
>mechanism.

Ditto,

I like the current verbosity, and the really bootverbose stuff is WAY
much more verbose than this.

For me, at least, this allows easy debugging without going full verbose.

That wrapping issue seems very useful indeed.  At least it would
structure the information a bit more orderly.

-- 
Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org]
Documentation nutter/B-rated Coder BSD: Technical excellence at its best  
The BSD Programmer's Documentation Project 
Peace with honour...


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

Parallel Port Zip Drive works when EPP-Mode is choosen in Bios

[F. Heinrichmeyer]

Subject says all! This evening i will try a patch for the ata driver so
maybe all my 
hardware at home will work again with current when certain patches are
applied.


-- 
Fritz Heinrichmeyer mailto:[EMAIL PROTECTED]
FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany)
tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh


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

swap_pager_getswapspace: failed (4.0-CURRENT) (fwd)

[chrw]

-- Forwarded message --
Date: Wed, 19 Jan 2000 15:35:23 +0100 (CET)
From: chrw <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: swap_pager_getswapspace: failed (4.0-CURRENT)


Helllo,

I am experiencing problems regarding the swap handler.

I am running 4.0-CURRENT FreeBSD 4.0-CURRENT #10

The box is running apache-1.3.9, cucipop v1.32, and sendmail 8.9.3, and
also runs as an NFS client.

Kernel is configured with 512 MAXUSERS, swap device is 400MB with
real memory  = 134201344 (131056K bytes)
avail memory = 126275584 (123316K bytes)

Apache is is configured to run with
MinSpareServers 50 MaxSpareServers 100


The box runs without any problems, and not using very much swap space for
about 24 hours, then suddenly it generates the error message:

Jan 19 13:03:03  hostname /kernel: swap_pager_getswapspace: failed

and about 1 min later, it stops responding to any service requests.

I would be gratefull for any hints or suggestions concerning what might
cause this fatal problem and possible solutions.

CW




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

Re: Majordomo results

[Satyajit Das]

do anyone help me subscribe  freebsd-question.
I have so many question which i like to share with freebsd-question.
please help anyone , how can i subscribe  in freebsd-question mailing list.

please note, i wrote  email address:  [EMAIL PROTECTED]
and in body :  subscribe freebsd-question
may i do wrong ?





[EMAIL PROTECTED] wrote:

> --
>
>  subscribe  freebsd-question
>  subscribe: unknown list 'freebsd-question'.
> 
> 
> 
>  Help for [EMAIL PROTECTED]:
>
> This help message is being sent to you from the Majordomo mailing list
> management system at [EMAIL PROTECTED]
>
> This is version 1.94.4 of Majordomo.
>
> If you're familiar with mail servers, an advanced user's summary of
> Majordomo's commands appears at the end of this message.
>
> Majordomo is an automated system which allows users to subscribe
> and unsubscribe to mailing lists, and to retrieve files from list
> archives.
>
> You can interact with the Majordomo software by sending it commands
> in the body of mail messages addressed to "[EMAIL PROTECTED]".
> Please do not put your commands on the subject line; Majordomo does
> not process commands in the subject line.
>
> You may put multiple Majordomo commands in the same mail message.
> Put each command on a line by itself.
>
> If you use a "signature block" at the end of your mail, Majordomo may
> mistakenly believe each line of your message is a command; you will
> then receive spurious error messages.  To keep this from happening,
> either put a line starting with a hyphen ("-") before your signature,
> or put a line with just the word
>
> end
>
> on it in the same place.  This will stop the Majordomo software from
> processing your signature as bad commands.
>
> Here are some of the things you can do using Majordomo:
>
> I.  FINDING OUT WHICH LISTS ARE ON THIS SYSTEM
>
> To get a list of publicly-available mailing lists on this system, put the
> following line in the body of your mail message to [EMAIL PROTECTED]:
>
> lists
>
> Each line will contain the name of a mailing list and a brief description
> of the list.
>
> To get more information about a particular list, use the "info" command,
> supplying the name of the list.  For example, if the name of the list
> about which you wish information is "demo-list", you would put the line
>
> info demo-list
>
> in the body of the mail message.
>
> II. SUBSCRIBING TO A LIST
>
> Once you've determined that you wish to subscribe to one or more lists on
> this system, you can send commands to Majordomo to have it add you to the
> list, so you can begin receiving mailings.
>
> To receive list mail at the address from which you're sending your mail,
> simply say "subscribe" followed by the list's name:
>
> subscribe demo-list
>
> If for some reason you wish to have the mailings go to a different address
> (a friend's address, a specific other system on which you have an account,
> or an address which is more correct than the one that automatically appears
> in the "From:" header on the mail you send), you would add that address to
> the command.  For instance, if you're sending a request from your work
> account, but wish to receive "demo-list" mail at your personal account
> (for which we will use "[EMAIL PROTECTED]" as an example), you'd put
> the line
>
> subscribe demo-list [EMAIL PROTECTED]
>
> in the mail message body.
>
> Based on configuration decisions made by the list owners, you may be added
> to the mailing list automatically.  You may also receive notification
> that an authorization key is required for subscription.  Another message
> will be sent to the address to be subscribed (which may or may not be the
> same as yours) containing the key, and directing the user to send a
> command found in that message back to [EMAIL PROTECTED]  (This can be
> a bit of extra hassle, but it helps keep you from being swamped in extra
> email by someone who forged requests from your address.)  You may also
> get a message that your subscription is being forwarded to the list owner
> for approval; some lists have waiting lists, or policies about who may
> subscribe.  If your request is forwarded for approval, the list owner
> should contact you soon after your request.
>
> Upon subscribing, you should receive an introductory message, containing
> list policies and features.  Save this message for future reference; it
> will also contain exact directions for unsubscribing.  If you lose the
> intro mail and would like another copy of the policies, send this message
> to [EMAIL PROTECTED]:
>
> intro demo-list
>
> (substituting, of course, the real name of your list for "demo-list").
>
> III.UNSUBSCRIBING FROM MAILING LISTS
>
> Your original intro message contains the exact command which should be
> used to remove your address from the list.  However, in most cases, you
> may simply send the command "unsubscribe" followed by the list name:
>
> unsubscribe demo

sell ceramic title products

[thomas xiao]

Dear sir:
   We are one of the largest Ceramic tiles and Sanitary ware
manufacturer in the China.specializing in producing wall and floor
tiles with large production scale, complete product varieties and
sizes and excellent prestige. our Group has introduced world advanced
technologies and equipment from Germany and Italy in succession, and
owned over 10 wall and floor tiles production lines and five
polishing production lines, of which, the 4200T press and super large
polishing line introduced from 
Italy are both the international top equipment. our Group which leads
the trend in space, beautifies the living space and pursues the more
modernized people and enterprise has integrated the Chinese essence
and spirit, and constantly created the perfect products. our Group
has made the products of numerous varieties, which can satisfy the
different requirements of vast clients. The company has obtained the
recognition of ISO9002 international quality assurance system, and
produced the matched, serial, high-quality,practical and artistic
products. Depending on its solid strength, 
we have already become the well-known brand highly praised by people
in the construction and decoration industry. our Products Merit:
1.Anti-pollution
By improving the formula for raw materials of the product,we have
reduced the pores and the caliber of the pore on its ceramic tiles,
and painted a layer of special coating on the tile surface,
preventing the dirty liquid permeating into its products.
This has solved the problem on "dirt absorbing" of polished ceramic
tiles existing in China for a long time, and filled up the gap of
domestic anti-pollution polished ceramic tile products. Passing the
inspection of the Building Material Test Center of the state, the
anti-pollution performance of the polished tile has reached the
international standard: SO/DIS 10545/14-1994
2.Electronstatics resistant
our ceramic tiles can be directly installed on the floor of the
program controller room, computer room and microelectronic production
and installation workshop to prevent the electrostatic function, 
or made into the electrostatics resistant moving floor by compounding
the wooden shaving board and cement shaving board or other materials,
or used as the floor or wall decoration in all places with
electrostatic requirements such as the intelligent office, bank, post
office and power control room. This product is dust-proof, with
stable system resistance, complete pattern and convenient
installation, and without the problem on 
aging and cracks in winter. 
3.Radiation-free
Inspected by the Building Material Test Center of the state, our
ceramic tiles contain no radiative element. Being safe and reliable,
they are the guarantee for health, and are the ideal selection for
high-quality decoration. Dongpeng ceramic tiles are the ideal
substitute products of natural stone materials. 
Contact us Now:
-Tel. +86-757-6239656,6336141
mov:+86013923115367
Fax. +86-757-6336141 









»¶Ó­µ½http://2888.com ÉêÇëÃâ·Ñ¡¢¶à¹¦ÄÜ¡¢´óÈÝÁ¿¡¢ÖÐÓ¢Îĵĵç×ÓÐÅÏä¡£
»¹ÓÐÈ«¸öÐÔ»¯±¨Ö½¼°Ã¿ÈÕÓʵݡ¢¾«ÃÀºØ¿¨¡¢×Ô¶¯ÃØÊé¡¢ËæÉíÐÅÏä¡¢ËæÉí±Ê¼Ç¡¢
Ãâ·ÑÍøÖ·¡¢¹©Çó¡¢ÕÐƸÇóÖ°¡¢ÍøÉÏÇéÔµÐÅÏ¢µÈµÈºÜʵÓõÄÃâ·Ñ·þÎñ¡£
ÊÀ½çÂÛ̳Íø(http://wforum.com )·Ç³£Óп´Í·£¬ºÜÖµµÃ²Î¼Ó¡£

Get your free, feature-rich, huge e-mailbox at http://2888.com
-



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

Re: Majordomo results

[Steve O'Hara-Smith]

On 20-Jan-00 Satyajit Das wrote:
> please note, i wrote  email address:  [EMAIL PROTECTED]
> and in body :  subscribe freebsd-question

The list is called freebsd-questions not freebsd-question.




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

Re: swap_pager_getswapspace: failed (4.0-CURRENT) (fwd)

[Matthew Dillon]

:Helllo,
:
:I am experiencing problems regarding the swap handler.
:
:I am running 4.0-CURRENT FreeBSD 4.0-CURRENT #10
:
:The box is running apache-1.3.9, cucipop v1.32, and sendmail 8.9.3, and
:also runs as an NFS client.
:
:Kernel is configured with 512 MAXUSERS, swap device is 400MB with
:real memory  = 134201344 (131056K bytes)
:avail memory = 126275584 (123316K bytes)
:
:Apache is is configured to run with
:MinSpareServers 50 MaxSpareServers 100
:
:The box runs without any problems, and not using very much swap space for
:about 24 hours, then suddenly it generates the error message:
:
:Jan 19 13:03:03  hostname /kernel: swap_pager_getswapspace: failed
:
:and about 1 min later, it stops responding to any service requests.
:
:I would be gratefull for any hints or suggestions concerning what might
:cause this fatal problem and possible solutions.
:
:CW

It sounds like some process is running away on you.  I recommend you
open up several windows and run various system monitoring utilities in
each one.  'vmstat 1', 'systat -vm 1', 'top', and so forth.

-Matt
Matthew Dillon 
<[EMAIL PROTECTED]>


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

Re: devfs?

[Brian J. Swetland]

["Brian J. Swetland" <[EMAIL PROTECTED]>]
> 
> I'm interested in mucking about with the devfs stuff a bit -- is there
> currently any active developer/maintainer/docs?  I grabbed the 4.0 
> snapshot from the 17th, installed it, grabbed the kernel sources from
> CVS, got stuff building and figured out how to enable DDB (not that
> much different from the kdebug environment I'm used to from BeOS). I
> figured I'd see if there was any more information than the sources.

I see (after digging through some recent list archives) that I missed
some discussion of this from as recent as a week ago.  Also I notice
that devfs does build, is mountable, is mountable, and shows a goodly
number of the active devices in my system.  

Somebody mentioned the issue of figuring out when things change
in sysctl/devfs/etc (and please excuse me if we've been here before),
but there seem to be two non-polling solutions that are workable
(though the second is much more work).  Either provide /dev/devchanges
or whatnot that interested processes can read (and block on) to receive
change events (similar to the Linux cardmgr socket stuff) or provide
general node monitoring (where processes can register for notifications
for move/modify/remove/directorychanged with some entity that plugs 
into the vfs layer).  The latter has some really neat effects (which
BeOS makes heavy use of) generally involving not needing to poll for
fs changes (input server node monitors /dev/input/... and sees new 
mice, etc as they're plugged in, GUI file browser gets events when
third parties modify stuff in open windows, etc).

Also, if anyone did reply to me over the last day or two, I've been
having entertaining mail problems (now resolved) which probably 
resulted in me missing the reply.

Brian

-- 
Brian Swetland - [EMAIL PROTECTED] | "If I have hacked deeper than them, it
  http://www.frotz.net/swetland/| is because I stand in their trenches."
|-- Graham Nelson


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

sysinstall's fdisk/disklabel broken?

[james]

Hi,

I was going to use sysinstall's disklabel to repartition/relabel one of my 
drives, but when i went into it in the post-installation menu it said:


No disks found!  Please verify that your disk controller is being
properly probed at boot time.  See the Hardware Guide on the
Documentation menu for clues on diagnosing this type of problem.


My disks show up in dmesg as:

ata-pci0:  port 0x3000-0x300f at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0

ata-isa0: already registered as ata0
ata-isa1: already registered as ata1

ad0:  ATA-4 disk at ata0 as master
ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 1 depth queue, WDMA2
ad2:  ATA-0 disk at ata1 as master
ad2: 1036MB (2121840 sectors), 2105 cyls, 16 heads, 63 S/T, 512 B/S
ad2: 16 secs/int, 1 depth queue, WDMA2


My kernel config (relevant bits) is:

device  ata0at isa? port IO_WD1 irq 14
device  ata1at isa? port IO_WD2 irq 15
device  atadisk0
options ATA_STATIC_ID
options ATA_ENABLE_ATAPI_DMA


Can somebody please fix this? Or is there a problem with my config?

BTW i'm using 4.0-CURRENT (obviously), and i cvsupp'd and make world'd 
about 2 days ago.

Cheers




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

Still getting 'R/W mount of / denied ...' after valid fsck

[Matthew Dillon]

I am still getting 'R/W mount of / denied' failures when rebooting a
crashed -current machine.  It thinks / is dirty but the fsck on it ran
just fine.  If I immediately /sbin/reboot again the machine comes up
normally.

The devices are all up to date (and in anycase couldn't be the cause
since block devices no longer exist).  

This problem existed before and was fixed, but apparently someone has
broken it again sometime in the last few weeks.

-Matt


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

Re: sysinstall's fdisk/disklabel broken?

[Anton Berezin]

On Fri, Jan 21, 2000 at 04:11:24AM +1100, james wrote:

> I was going to use sysinstall's disklabel to repartition/relabel one
> of my drives, but when i went into it in the post-installation menu it
> said:

> No disks found!

> BTW i'm using 4.0-CURRENT (obviously), and i cvsupp'd and make world'd
> about 2 days ago.

I just bumped into this, half an hour ago. :-)

How old is your /stand/sysinstall (it does not get updated as a make
world process)?

# cd /usr/src/release/sysinstall && make all install

Cheers,
-- 
Anton Berezin <[EMAIL PROTECTED]>
The Protein Laboratory, University of Copenhagen


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

Error building current

[Tim Moore]

CVS'uped today:

cd /usr/src/gnu/usr.bin/cc/cc_tools; make build-tools
cannot open
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/version.c: no
such file
"/usr/src/gnu/usr.bin/cc/cc_tools/../Makefile.inc", line 28: warning: "sed
-e 's/.*\"\([^ \"]*\)[ \"].*/\1/' <
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/version.c"
returned non-zero status
make: don't know how to make c-parse.gperf. Stop

gcc/version.c is "dead" in my CVS repository.  Has my repository been
corrupted somehow?

Tim




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

error wich devices ad*

[joanra]

Hi when i run freebsd, display:

Mounting root from ufs: /dev/ad2s1a
no such device ad
setrootbyname failed
ffs_mountroot: can't find rootvp
root mount failed: 6
mounting root from ufs: wd2s1a
swapon: /dev/ad2s1b: device not configure
Automatic reboot in ptogress
can't open /dev/ad2s1a: device not configured

my fstab:

# DeviceMountpoint
/dev/ad2s1b none
/dev/ad2s1a /
/dev/ad2s1f /usr
/dev/ad2s1e /var
/dev/cd0c   /cdrom  cd9660
proc/proc

anyone help me please?

P.S: i recompiled a new kernel, and i create the new devices ad*, and my hd
is seconday

thanks



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

rpc.lockd

[David E. Cross]

It is almost done.  A working and very lightly tested version of the code will
be made available on Monday (Jan 24).  It should be considered alpha quality,
I would not recommend running important NFS servers with this code.

--
David Cross   | email: [EMAIL PROTECTED] 
Acting Lab Director   | NYSLP: FREEBSD
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd 
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
Department of Computer Science| Fax: 518.276.4033
I speak only for myself.  | WinNT:Linux::Linux:FreeBSD


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