Re: uvscan & __stderrp

2002-11-16 Thread Jim Weeks

On Fri, 15 Nov 2002, Larry Rosenman wrote:

> Set COMPAT3X=yes in /etc/make.conf, re-cvsup, including the compat stuff,
> and re-make world.

On a related note, I had problems with FrontPage extensions after the
upgrade.  The following worked for me.

cd /usr/ports/misc/compat3x
make && make install && make clean

Regards,
--
Jim



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



Re: 4.6 > poppassd fails

2002-07-29 Thread Jim Weeks

Thanks Calvin,

That was easy enough ;-)  Another strange thing for you, this seems to
have been corrected in the qpopper port.

/usr/ports/mail/qpopper/files/extra-patch-password::poppassd.c

 static char *P4[] =
{
+ "passwd: updating the database...\npasswd: done ", /* FreeBSD */
+ "nis password has been changed * ", /* FreeBSD NIS */
  "password changed. ", /* shadow */
  "password changed ",  /* smb */
  ""

Good day,

--
Jim

On Mon, 29 Jul 2002, Calvin NG wrote:

> Greetings,
>
>   the response from the operating system with regards to
>   change password has changed,
>
>   the response used to be
>  "rebuilding the database..."
>
>   now, it is
>  "updating the database..."
>
>   this causes the poppassd to think that the changing of password
>   has failed, because the response does not match any "success"
>   response it is looking for.
>
>   edit the .c code, modify "static char *P4[] =" (around line 178)
>   accordingly, and you are back in business.
>
> Regards,
> /calvin
>
> lines with :> are quotes from Jim Weeks's email
> :> Good morning,
> :>
> :> This is definitely a new problem, I have verified that up through 4.5 it
> :> didn't exist, at least for me. I have checked the archives and can't seem
> :> to find anything.  What is really strange is that the password is actually
> :> changed, but the error indicates that it is not.  A point in the right
> :> direction would be appreciated.
> :>
> :> $ telnet 127.0.0.1 106
> :> Trying 127.0.0.1...
> :> Connected to localhost.
> :> Escape character is '^]'.
> :> 200 poppassd v1.2 hello, who are you?
> :> user jim
> :> 200 your password please.
> :> pass mypass
> :> 200 your new password please.
> :> newpass newpass
> :> 500 Unable to change password.
> :> Connection closed by foreign host.
> :>
> :> BTW, the "user not in wheel" bug that had been reported earlier doesn't
> :> seem to exist on these machines. All of these have the problem:
> :>
> :> 4.6-STABLE #1: Fri Jul 12
> :> 4.6-STABLE #1: Mon Jul 15
> :> 4.6-STABLE #0: Mon Jul 8
> :>
> :> --
> :> Jim Weeks
> :>
> :>
>


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



Re: tracing a crash

2001-05-02 Thread Jim Weeks

Jano,

If you aren't seeing anything extraordinary in the logs, this is an
indication that the crash was caused by a w/r error.  You may have a
problem with your disk drive, controller card, cable, etc.  Unfortunately,
when your machine quits writing to the disk, there will be no log
entries.  You will only see the errors from the console.

--
Jim Weeks


On Wed, 2 May 2001, Jano Lukac wrote:

> Hi,
> 
> My freebsd 4.3-release (cvsupped to stable a few days ago) box stopped
> responding to everything except ping yesterday.  I was too lazy to attach a
> monitor, so I simply gave it the three-fingered salute, figuring all would go
> well and I could see anything strange happened in the logs later.  Well.. it
> didn't and I had to attach a monitor.  Seems fsck had a lot of problems on my
> /usr slice/partition, particularily with the src and obj directories.  I'm
> looking now through the logs and haven't found anything out of the ordinary.
> 
> Other than re-reading the logs and waiting for this to happen again (hopefully
> it won't), what else can I do to see what might have happened?
> 
> jano
> 
> ps i'm on the list, no need to cc me in reply.
> 
> __
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great prices
> http://auctions.yahoo.com/
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
> 


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



Re: top failing with nlist error

2001-04-17 Thread Jim Weeks

Ok,

I have been following the list for a long time and the only time I have
seen this happen it has been a sync problem.  Maybe once top itself was
broken.

Did you cvsup your sources, or are you using the ones pulled down during
the binary install?

If you cvsuped /usr/src and did makeworld, mergemaster, and  buildkernel
all with the same src tree, I don't know what it could be :-(

--
Jim Weeks


On Tue, 17 Apr 2001, Simon Edwards wrote:

> On Tue, Apr 17, 2001 at 10:33:41AM -0400, Jim Weeks wrote:
> > I didn't ask, but you did reboot your new kernel?
> > 
> 
> Yeah, that was the first thing i doubled checked :)
> 
> -- 
> Simon Edwards
> "Don't threaten me. There are worse things than death,
>   and uh, I can do all of them."
> 


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



Re: top failing with nlist error

2001-04-17 Thread Jim Weeks

Did you run mergemaster?

--
Jim Weeks


On Tue, 17 Apr 2001, Simon Edwards wrote:

> Hiya,
> 
> I just installed 4.3 RC3 from cdrom (and via FTP, when the cd didn`t work) :)
> 
> and I am getting the error :
> 
> # top
> top: nlist failed
> 
> I had a look at the handbook, and it says that either kernel and userland are
> not synced, even though it was a fresh install, i buildworld and build kernel'd
> 
> This made no difference.
> 
> The hand book also said that it may be that I wasn`t using /boot/loader
> Checked that and I am.
> 
> I haven`t installed any software at all, has anyone got any ideas or 
> suggestions ? 
> 
> Cheers
> 
> -- 
> Simon Edwards
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
> 


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



Re: strange 3Com 3C509 probe behaviour

2001-03-26 Thread Jim Weeks

I believe placing the following line in your Kernel config rather than the
default (device  ep) should work.

device  ep0 at isa? port 0x220 irq 10

--
Jim Weeks


On Mon, 26 Mar 2001, Hellmuth Michaelis wrote:

> Hi,
> 
> i have one 3Com 3C509 in a 4.x-stable machine. At boot time, it produces
> the following messages:
> 
> isa0: if_ep: <3Com 3C509-TP EtherLink III> at port 0x220-0x230 irq 11
> ...
> ep0: <3Com 3C509-TP EtherLink III> at port 0x220-0x22f irq 11 on isa0
> ep0: No irq?!
> ep0: ep_alloc() failed! (6)
> device_probe_and_attach: ep0 attach returned 6
> ...
> ep1: <3Com 3C509B-TP EtherLink III (PnP)> at port 0x210-0x21f irq 10 on isa0
> ep1: Ethernet address 00:20:af:4a:26:1f
> bpf: ep1 attached
> 
> This card is detected as a PnP card by the (Award PnP-) BIOS.
> 
> I'd like to get this working under ep0 instead of ep1, has someone an
> idea what goes wrong here ?
> 
> hellmuth
> -- 
> Hellmuth MichaelisTel   +49 40 55 97 47-70
> HCS Hanseatischer Computerservice GmbHFax   +49 40 55 97 47-77
> Oldesloer Strasse 97-99   Mail  hm [at] hcs.de
> D-22457 Hamburg   WWW   http://www.hcs.de
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
> 


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



Re: PNP > /boot/kernel.conf

2000-10-14 Thread Jim Weeks


On Sat, 14 Oct 2000, Erik Trulsson wrote:
 
> Unless I am badly mistaken you can use exactly the same syntax in
> /boot/kernel.conf and boot -c so you can put the lines above (minus
> prompts) in /boot/kernel.conf and it should work fine.

Well, I thought I had tried this when the box was running 3.2 and had been
plagued with errors :/

However, the proof is in the pudding ;-)

config> pnp 1 0 enable os irq0 3 drq0 0 port0 0x2f8
config> pnp 2 0 enable os irq0 5 drq0 0 port0 0x3e8
config> q
avail memory = 17395712 (16988K bytes)
Preloaded elf kernel "kernel" at 0xc0328000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc032809c.
Probing for PnP devices:
CSN 1 Vendor ID: BRI9411 [0x1194490a] Serial 0xb562d73a Comp ID: @@@
[0x]
sio1: type 16550A
sio1 (siopnp  sn 0xb562d73a) at 0x2f8-0x2ff irq 3 on isa
CSN 2 Vendor ID: BRI9410 [0x1094490a] Serial 0xdd877d7e Comp ID: @@@
[0x]
sio2: type 16550A
sio2 (siopnp  sn 0xdd877d7e) at 0x3e8-0x3ef irq 5 on isa

Thanks,

Jim



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



Re: No UPDATING for RELENG_3?

2000-10-01 Thread Jim Weeks

I know for a fact this works.  I have done binary upgrades straight from
2.2.6 to 4.0-STABLE snapshots.

One note, the next time you SVSUP and build you should rebuild
/usr/src/release/sysinstall since it doesnt automatically build during
makeworld.

--
Jim Weeks


On Sat, 30 Sep 2000, Crist J . Clark wrote:

> On Sat, Sep 30, 2000 at 07:59:43PM -0700, Ken Bolingbroke wrote:
> > 
> > 
> > On Sat, 30 Sep 2000, Crist J . Clark wrote:
> > 
> > > On Sat, Sep 30, 2000 at 03:13:23PM -0700, Ken Bolingbroke wrote:
> > > > 
> > > > I'm in the middle of updating a machine from 2.2.5 to 4.1.1, hopefully.  
> > > > I've got it to 2.2.8-S, successfully, then when the initial attempt to go
> > > > from 2.2.8 to 3.5-S failed, I dropped down to 3.2-R which was successful.
> > > 
> > > You did a binary upgrade to 3.2-R? Why not just do the binary upgrade
> > > to 4.1.1?
> > 
> > I didn't do a binary upgrade, I cvsup'd RELENG_3_2_0.  The machine in
> > question doesn't have either a CD or floppy drive, and it also only has
> > 8 meg of RAM, all of which make binary upgrading a bit difficult.  
> > Otherwise, I'd have wiped the machine and installed 4.1.1 fresh.
> 
> Holy, @#$%! And you do buildworlds on this machine!? Sounds like a
> source upgrade would be even tougher. How long does it take to do one?
> 
> Can you not do sysinstall on 8 MB anymore? If you can, I'd recommend
> doing the minimal install of 4.1.1 over FTP. I can't imagine that that
> would take longer than two or three buildworlds unless you are running
> over a 1200 baud connection.
> 
> If sysinstall does not work on 8 MB anymore, do you have another
> machine that you can use to help? That opens up a lot more options.
> -- 
> Crist J. Clark   [EMAIL PROTECTED]
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
> 



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



Re: 4.1-STABLE, make world problems, funny case

2000-09-23 Thread Jim Weeks


On Sat, 23 Sep 2000, Brad Knowles wrote:
 
>   Note that ECC RAM usually helps in this case, but it is possible 
> for there to be so many errors that even ECC can't save you.

An interesting observation.  

I have a couple of machines running ECC chips that produce this
error on occasion.

(httpd), uid 65534: exited on signal 11

No other process has ever exited on signal 11.  I realize that signal 11
is usually memory related but make build/installworlds never fail, at
least for this reason.

--
Jim 



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



Re: 4.0-RELEASE to 4.0-STABLE upgrade

2000-05-28 Thread Jim Weeks


On Mon, 29 May 2000, Szilveszter Adam wrote:
> 
> OK, I was caught at this:-) The Handbook is still not updated to reflect
> this (although I remembered otherwise) so you should see man page for
> mergemaster(8)... it is in the base system for 3.4 for sure (and of course
> above) but normally you do not need much documentation for using it:

This has been discussed on docs lately.  There is a PR in for changes to
the Make World page.  Mergemaster will be included.

 
> cd to /usr/src/etc and say 'mergemaster'. It will build a temproot
> environment under /var/tmp/temproot just as the Handbook does tell you but
> you do not have to do it by hand and also it automatically diffs the files
> in /etc and the temproot and if it spots any differences, you are given the
> choice of installing the new file as is, to keep the old file (eg you should
> do this with master.passwd) or to merge the two. It can also leave the file
> untouched and then you can finish it up later by hand. After it is finished,
> it asks if you want to delete the old temproot. (which you normally want to
> do, unless there are files you want to deal with by hand.)
> 
Another note,

As was mentioned look over man mergemaster.  If you have done a typical
install you probably only have 20mb for /var so I suggest you use /usr for
the temporary files.  As in the following command.

mergemaster -t /usr/tmp/root -d

which will also add a date to the directory in case you need to save it
for some reason.

You know better than anyone else which files you have made changes to that
should not be changed during upgrade.  Just pay attention to the file
names and the diffs on the screen before installing new files. 

Good luck,

Jim Weeks
 A mind is a terrible thing to lose!  How I miss mine..




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



Re: ad0 drivers revisited

2000-05-25 Thread Jim Weeks


> In message <[EMAIL PROTECTED]>, Kent Stewart writes:
> 
> The sysctl code in rc IMO needs to be executed earlier.  If one is 
> having problems reading from an ATA boot disk, e.g. cannot load init or 
> rc, these modes need to be set earlier.  Why not a boot flag that sets 
> atamodes to be as conservative as possible, that could be set in 
> loader.conf.  I see in the loader(8) man page that some sysctl 
> variables can be set in loader.conf.  Can atamodes be set in 
> loader.conf?  If not, maybe it should.

Yes, this is it in a nutshell.  All of the suggestions so far are good,
but they come to late in the boot sequence to fix this problem.   

Jim Weeks
- A mind is a terrible thing to lose!  How I miss mine...




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



Re: unable to delete a file

2000-04-07 Thread Jim Weeks

Jason,

Watch your back side.  I had an individual open an account with someone
else's domain name and email address.  It didn't feel right so I watched
for a day to see what he was doing.  He didn't upload a web page, but
uploaded a script named .x which turned out to be a transfer of services
script.

Jim

On Thu, 6 Apr 2000, JMS Internet wrote:

> Someone has logged into my system via anonymous FTP and uploaded a 
> directory or file of a large size which I can not seem to delete either via 
> FTP or telnet.  The complete name as listed by 'du' is:
> /users/ftp/incoming/   .x  /for JUSTiSO/by KradLrobR/   (file of some type 
> here)
> When I try to cd to this directory I get:
> cd: Too many arguments.
> 
> Anyone's help would greatly be appreciated.
> Thank You,
> Jason Scott 
 



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



Re: make world failed

2000-04-03 Thread Jim Weeks



Which much venom, Brennan W Stehling wrote:
 
> I am not a moron that does not read any documentation.  So let me lash
> back a bit here, maybe you should read someones full email and the rest of
> the thread before flaming them.
> 
> You only come off as a prick and discourage people from using FreeBSD.  I
> love it and have been using it for over 2 years but the flames I got
> recently when asking for a few suggestions have been discouraging.

First, I apologize if that is the way it seemed.  I only meant to point
out what has bitten me in the back side so often, and I had read the rest
of the thread.  I know how hard it can be to keep up with the mailing
list, but this exact procedure has been worn out on the mailing list ever
since the release. 

> It's like I should just stick to reading the README's and online
> documentation and avoid all contact with any mailing list or chat room.

Not at all.  In fact you will find this on the Make World page.

If you try and track -STABLE or -CURRENT and do not read the
<[EMAIL PROTECTED]> or <[EMAIL PROTECTED]> mailing lists then you are
asking for trouble. 

Which brings us back to the fact that the correct procedure has
been discussed at length on this list for the past two or three weeks.

No flame intended,

Jim



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



Re: Small spaces

2000-03-18 Thread Jim Weeks

I have seen a few messages in the mail archives about putting pico.bsd on
small hardrives to implement a gateway.  Also if you have another small hd
lying around maybe even a 40mb you could then use the 200 just for /usr

You don't have to worry about the bios limit as long as you keep the
root low.  I have used a number of 386 and 486 boards with large
hard drives.

I believe you could optionally install 2.2.8.  It takes less space.

Jim

A little knowledge is a DANGEROUS thing 
   James W. Weeks <[EMAIL PROTECTED]> 

On Sat, 18 Mar 2000, Laurence Berland wrote:

> I'm trying to install FreeBSD 3.4 on an old 486 I've got lying around to
> use as a NATing firewall for my home network, but I've only got a 200
> Meg HD around.  I'm gonna go get another HD later, but right now I'd
> like to get running with just that.  So far I've been trying with 16 to
> swap and various other combinations, but it always seems to run out of
> /usr space.  I figure / should be at least 32MB, and the rest (~152MB)
> goes to /usr.  I'm trying to install the binaries, the docs, and the
> kernel source (but not the rest of the source).  Any idea if it's even
> possible?  Should I shrink down the root partition more?  I've done
> loads of installs at this point, but all on HDs with at least a gig for
> FreeBSD.  Any ideas where I can get a bigger HD that's still under the
> limit for old BIOSen?  Thanks in advance for any help.



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



Re: Desperate help upgrading from 3.2-R > 3.4-S

2000-03-17 Thread Jim Weeks

This may be your problem.  You either need to specify all, or each one
individually.  I have had trouble using the all option

> src-all
> src-crypto
> src-eBones
> src-secure

You shouldn't need to use this in 3.x-stable

> USA_RESIDENT=   YES

It is not necessary to upgrade from 3.2 if you are just trying to install
a
package.  You can install the upgrade package, 
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-3-stable/Latest/32upgrade.tgz
You should then be able to install ports.

If you still want to upgrade to 3.4 try cleaning /etc/obj and /usr/src and
use this cvsupfile

*default  host=cvsup5.FreeBSD.org
*default  base=/usr
*default  prefix=/usr
*default  release=cvs
*default  tag=RELENG_3
*default  delete use-rel-suffix

src-base
src-bin
src-contrib
src-crypto
src-etc
src-games
src-gnu
src-include
src-kerberosIV
src-lib
src-libexec
src-release
src-sbin
src-secure
src-share
src-sys
src-tools
src-usrbin
src-usrsbin
*default tag=.
ports-all
doc-all


Hope this helps,

Jim



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



Re: strange named behavior in 3.4-STABLE

1999-12-25 Thread Jim Weeks

Your problem is most likely sendmail.  It will always issue a request
when
booting and if you have the standard "sendmail -bd -q30m"
set in /etc/rc.conf it will cause dial up every 30 minutes.  You could
change
the command to "sendmail -bd" to stop the 30 minute dialing, but it will

still dial during boot.

Good luck,
Jim Weeks


Lev Serebryakov wrote:

>Whet it was 3.3-STABLE (really -- 3.3-RELEASE with stable kernel)
>everything works perfectly. PPP doesn't call my ISP until I (or
>somebody in local network) need connection.
>But with new system (3.4-RELEASE) ``named'' initiate dial-up just
>after start! Why new named want to connect when there is no any
>outgoing packets? How could I disable such behavior?



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



Re: 3.4-19991218-STABLE kernel build fails

1999-12-19 Thread Jim Weeks

Hi again,

I didn't get any response to this post and have since tried numerous things
to correct this error.  I have now installed  3.4-19991219-STABLE from
snapshots and receive a different error when I try building a new kernel.
Everything seemed to install ok and make depend went well, but when doing
make I get this error.

sentinel# make
cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes  -Wpointer-arith
-Winline -Wuninitialized -Wformat -Wunused  -fformat-extensions -ansi
-nostdinc -I- -I. -I../.. -I/usr/include  -DKERNEL -DVM_STACK -include
opt_global.h -elf  ../../cam/scsi/scsi_cd.c
In file included from ../../cam/scsi/scsi_cd.c:60:
../../sys/cdio.h:91: warning: useless keyword or type name in empty
declaration
../../sys/cdio.h:91: warning: empty declaration
../../sys/cdio.h:91: parse error before `_'
../../sys/cdio.h:91: warning: no semicolon at end of struct or union
../../sys/cdio.h:92: warning: data definition has no type or storage class
../../sys/cdio.h:92: parse error before `}'
../../sys/cdio.h:96: syntax error before `{'
../../sys/cdio.h:98: warning: data definition has no type or storage class
../../sys/cdio.h:98: parse error before `osiricn'
../../sys/cdio.h:100: warning: data definition has no type or storage class

../../sys/cdio.h:100: parse error before `rscr_cn'
../../sys/cdio.h:100: warning: data definition has no type or storage class

../../sys/cdio.h:100: parse error before `t'
../../sys/cdio.h:101: warning: data definition has no type or storage class

../../sys/cdio.h:102: parse error before `/'
../../sys/cdio.h:103: warning: data definition has no type or storage class

../../sys/cdio.h:104: parse error before `}'
../../cam/scsi/scsi_cd.c: In function `cdioctl':
../../cam/scsi/scsi_cd.c:1966: sizeof applied to an incomplete type
../../cam/scsi/scsi_cd.c:1969: sizeof applied to an incomplete type
../../cam/scsi/scsi_cd.c:1991: dereferencing pointer to incomplete type
../../cam/scsi/scsi_cd.c:1992: dereferencing pointer to incomplete type
../../cam/scsi/scsi_cd.c:1993: dereferencing pointer to incomplete type
../../cam/scsi/scsi_cd.c:1994: dereferencing pointer to incomplete type
../../sys/libkern.h:57: warning: inlining failed in call to `min'
../../cam/scsi/scsi_cd.c:1995: warning: called from here
*** Error code 1

Any suggestions would be appreciated.

Jim Weeks wrote:

> I installed fresh on an old machine yesterday and when I try to make the
> new kernel I get this message,
>
> In file included from ../../msdosfs/msdosfs_denode.c:66:
> ../../msdosfs/denode.h:282: macro '__P' used with too many (2) args
> *** Error code 1
>
> The only thing I have added to the system at this point is
> /usr/src/sys/i386/isa/sio.c with two additional pnp entries.
>



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