Re: How do I subscribe to the mailing list?
Roy, You can check up the following site for infomation on subscribing. http://www.freebsd.org/handbook/eresources.html#ERESOURCES-MAIL HTH.. -Rajiv. Roy Shimmyo wrote: > > did I just do it? > -- > If little else, the brain is an educational toy. -- Tom Robbins > > 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
Dump problem
Hello all, Dump seems seriously broken in 4.3-RC, any dump of level higher than 0 seems missing a lot of files. With dump of 4.3-RC: (/dev/da0s1f is /var) 1025 [9:47] root@fire:/var/log> /sbin/dump 1sf 1048576 /dev/null /dev/da0s1f DUMP: Date of this level 1 dump: Wed Apr 18 09:47:10 2001 DUMP: Date of last level 0 dump: Thu Apr 12 02:19:09 2001 DUMP: Dumping /dev/da0s1f (/var) to /dev/null DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 578 tape blocks on 0.00 tape(s). DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 200 tape blocks on 1 volume DUMP: finished in less than a second DUMP: Closing /dev/null DUMP: DUMP IS DONE I'm pretty sure that 200 tapes block is not enough, /var/log contains a lot of files changed since dump 0, including gigabytes of log and a huge ldap database. With an old dump copied from 4.2-STABLE before 3 March (time of change in traverse.c): 1027 [9:48] root@fire:/var/log> ~at/dump 1sf 1048576 /dev/null /dev/da0s1f DUMP: Date of this level 1 dump: Wed Apr 18 09:48:15 2001 DUMP: Date of last level 0 dump: Thu Apr 12 02:19:09 2001 DUMP: Dumping /dev/da0s1f (/var) to /dev/null DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 886865 tape blocks on 0.05 tape(s). DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 58.93% done, finished in 0:03 DUMP: DUMP: 886654 tape blocks on 1 volume DUMP: finished in 472 seconds, throughput 1878 KBytes/sec DUMP: Closing /dev/null DUMP: DUMP IS DONE -- Alain Thivillon -+- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
pam issues with (cclient|imap)-uw-0104101757
After upgrading to the above version I get the following messages in the maillog (I have the relevant parts in pam.conf): (This is on a FreeBSD-4.2 STABLE box) Apr 18 09:49:52 mxhst12 popd[89724]: unable to resolve symbol: \ pam_sm_open_session Apr 18 09:49:52 mxhst12 popd[89724]: unable to resolve symbol: \ pam_sm_close_session Any ideas? Regards +-- Dan Larsson | Tel: +46 8 550 120 21 Tyfon Svenska AB | Fax: +46 8 550 120 02 GPG and PGP keys | finger [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Dump problem
Alain Thivillon <[EMAIL PROTECTED]> writes:
> Dump seems seriously broken in 4.3-RC, any dump of level higher than 0
> seems missing a lot of files.
This is sort of a known problem. ``Sort of'' meaning that not all
machines display it, although I think they should. Could you please
try the patch in PR bin/26507 and let me know if it helps? I've also
attached it for your convenience.
Thanks,
Dima Dorfman
[EMAIL PROTECTED]
Index: traverse.c
===
RCS file: /st/src/FreeBSD/src/sbin/dump/traverse.c,v
retrieving revision 1.12
diff -u -r1.12 traverse.c
--- traverse.c 2001/03/03 11:35:50 1.12
+++ traverse.c 2001/04/07 22:50:35
@@ -155,13 +155,15 @@
if ((mode = (dp->di_mode & IFMT)) == 0)
continue;
/*
-* All dirs go in dumpdirmap; only inodes that are to
-* be dumped go in usedinomap and dumpinomap, however.
+* Everything must go in usedinomap so that a check
+* for "in dumpdirmap but not in usedinomap" to detect
+* dirs with nodump set has a chance of succeeding
+* (this is used in mapdirs()).
*/
+ SETINO(ino, usedinomap);
if (mode == IFDIR)
SETINO(ino, dumpdirmap);
if (WANTTODUMP(dp)) {
- SETINO(ino, usedinomap);
SETINO(ino, dumpinomap);
if (mode != IFREG && mode != IFDIR && mode != IFLNK)
*tapesize += 1;
@@ -169,8 +171,11 @@
*tapesize += blockest(dp);
continue;
}
- if (mode == IFDIR)
+ if (mode == IFDIR) {
+ if (!nonodump && (dp->di_flags & UF_NODUMP))
+ CLRINO(ino, usedinomap);
anydirskipped = 1;
+ }
}
/*
* Restore gets very upset if the root is not dumped,
@@ -218,7 +223,7 @@
* it isn't in usedinomap, we have to go through it to
* propagate the nodump flag.
*/
- nodump = (TSTINO(ino, usedinomap) == 0);
+ nodump = !nonodump && (TSTINO(ino, usedinomap) == 0);
if ((isdir & 1) == 0 || (TSTINO(ino, dumpinomap) && !nodump))
continue;
dp = getino(ino);
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Dump problem
Dima Dorfman <[EMAIL PROTECTED]> écrivait (wrote) : > This is sort of a known problem. ``Sort of'' meaning that not all > machines display it, although I think they should. Could you please > try the patch in PR bin/26507 and let me know if it helps? I've also Yep, works now ! Thanks. I hope this patch will be incorporated in 4.3-RELEASE, we definitly need a working dump :) |Index: traverse.c |=== |RCS file: /st/src/FreeBSD/src/sbin/dump/traverse.c,v |retrieving revision 1.12 |diff -u -r1.12 traverse.c |--- traverse.c 2001/03/03 11:35:50 1.12 |+++ traverse.c 2001/04/07 22:50:35 -- Patching file traverse.c using Plan A... Hunk #1 succeeded at 155. Hunk #2 succeeded at 171. Hunk #3 succeeded at 223. done 1033 [10:15] root@fire:/usr/src/sbin/dump> make cc -O -pipe -DRDUMP -I/usr/src/sbin/dump/../../libexec/rlogind -c /usr/src/sbin/dump/traverse.c cc -O -pipe -DRDUMP -I/usr/src/sbin/dump/../../libexec/rlogind-static -o dump itime.o main.o optr.o dumprmt.o tape.o traverse.o unctime.o 1034 [10:15] root@fire:/usr/src/sbin/dump> make install install -c -s -o root -g tty -m 2555 dump /sbin /sbin/rdump -> /sbin/dump install -c -o root -g wheel -m 444 dump.8.gz /usr/share/man/man8 /usr/share/man/man8/rdump.8.gz -> /usr/share/man/man8/dump.8.gz 1035 [10:15] root@fire:/usr/src/sbin/dump> cd 1036 [10:15] root@fire:~> /sbin/dump 1sf 1048576 /dev/null /dev/da0s1f DUMP: Date of this level 1 dump: Wed Apr 18 10:15:31 2001 DUMP: Date of last level 0 dump: Thu Apr 12 02:19:09 2001 DUMP: Dumping /dev/da0s1f (/var) to /dev/null DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 892446 tape blocks on 0.05 tape(s). DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 58.37% done, finished in 0:03 DUMP: DUMP: 892237 tape blocks on 1 volume DUMP: finished in 457 seconds, throughput 1952 KBytes/sec DUMP: Closing /dev/null DUMP: DUMP IS DONE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: subscribe
At 06:34 PM 4/17/01 -0500, David W. Chapman Jr. wrote: >We're not going to let you. Resistance is futile. > >- Original Message - >From: "Ian Perrett" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Tuesday, April 17, 2001 6:29 PM >Subject: subscribe > > > > > > subscribe > > And why perchance does this require you to keep the CC to the list? My reason is to point out such behaviour isn't all the friendly and the fact there is no reason to CC the list when helping, or heckling, a lost soul. Not what I would call a good example. Everyone else - pardon my adding to noise level here. Jeff Mountin - [EMAIL PROTECTED] Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Programmers Documentation Project
-On [20010417 20:56], Daryl Chance ([EMAIL PROTECTED]) wrote: >I just posted this on -doc, but I thought I'd ask you all for >thoughts on this since -stable will probably be the main target >for questions while/if this project is going on. Heh, you could've cc:'d me in the emails. :P >I was looking through the list of projects to see if one existed >for documenting the FBSD code. The closest I came to it was this: >http://home.wxs.nl/~asmodai/pdp.html > >Does anyone know if there has been any recent work done on this? >the top of this page: >http://home.wxs.nl/~asmodai/source-overview.txt We moved a lot of that to the Developer's Handbook. Nik Clayton just fixed it to the daily doc build and provided soem links towards it on the webpages. >Has a date of 1999/04/01, a little over 2 years. Mea culpa. Real life sucks. :P >I say this is the closest, because I was looking for something else, >something a little more "thourough", like (I realize this would be >a HUGE undertaking) commenting all the functions in the FBSD source >and running something like ScanDoc against it or some other auto- >matic code documentation programs. That was what I was working on. Until I got dragged into a commit bit. I still need to expand on, and include it in the handbook, my newbus doc at people.freebsd.org/~asmodai/newbus-draft.txt >Anyone have any suggestions? Offer any help? I thought about this >which watching the recent discussion on "VM Balance" on -stable. >This would be a great project to start so that someone interested >in browsing the FBSD source can see more then just the code, they >can see the functions, structs, etc etc and read the comments >against those. It may help the people doing work on FBSD to learn >more about the source. Neil Blakey and me have been looking at the GDK project's way of documenting. Looks interesting. >Thoughts? I'd be willing to help out, or even lead this project. >I do think this would take a lot of patience from the -stable people >answering our questions about things that they would consider >trivial :). I'm only on a Cable connection w/ a K6 333 as my most >powerful server, but I can offer up this to see this project get off >the ground and to show that theres some interest. I'd also have >to learn scandoc or whatever documentation tool we plan on using if >theres any interest. All documentation eventually returns to SGML/DocBook. -- Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Of all that is to come, the Dream has just begun... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ftpd security patch fails to compile
I had this problem and I solved it by: going to /usr/src/include and 'make install' You could probably just manually copy over the new glob.h in /usr/src/include/ to /usr/include. Dan Langille wrote: > > I'm following the instructions for the latest security advisory. I'm getting > the following compile error under 4.2-STABLE dated 2 15:36:52 NZDT > 2001. Any clues? > > [root@lists:/usr/src/lib/libc] # make all install > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include - > D__DBINTERFACE > _PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale - > DBROKEN_DES > -DYP -c /usr/src/lib/libc/../libc/gen/glob.c -o glob.o > /usr/src/lib/libc/../libc/gen/glob.c: In function `glob': > /usr/src/lib/libc/../libc/gen/glob.c:171: `GLOB_MAXPATH' undeclared > (first use i > n this function) > /usr/src/lib/libc/../libc/gen/glob.c:171: (Each undeclared identifier is > reporte > d only once > /usr/src/lib/libc/../libc/gen/glob.c:171: for each function it appears in.) > /usr/src/lib/libc/../libc/gen/glob.c: In function `globextend': > /usr/src/lib/libc/../libc/gen/glob.c:689: `GLOB_LIMIT' undeclared (first > use in > this function) > *** Error code 1 > > Stop in /usr/src/lib/libc. > > -- > Dan Langille > pgpkey - finger [EMAIL PROTECTED] | http://unixathome.org/finger.php > > 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: Weird ipnat(?) behaviour
On Tue, Apr 17, 2001 at 01:47:18PM +0200, Morten A . Middelthon wrote: > > I've got a 4.1.1-STABLE box running ipf/ipnat for my local networks. > > /etc/ipnat.conf: > map fxp0 10.0.0.0/16 -> xxx.xxx.xxx.xxx/32 > > When two or more boxes behind my ipnat-box try pinging the same host on the outside > only one of them can ping it at a time. Pinging different boxes on the outside > works fine. > > I start pinging an outside-box on two local boxes simultaneously and only one > of them gets responses. As soon as I stop pinging on the box which receives > responses the other one continues, but then with a packet loss, ofcourse. > > Any good explanation for this? Just tried this on a box with natd/ipfw, and it worked wonderfully there. Is it just me or my setup which is borked? :} -- Morten A. Middelthon Freenix Norge http://www.freenix.no/ -- Always borrow money from a pessimist; he doesn't expect to be paid back. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ports not working
At 15:31 18-04-01 +0400, you wrote: >SH> hi >SH> when i try to build ports on my system i get > >SH> test# cd /usr/ports/ >SH> test# cd security/sudo/ >SH> test# make patch >SH> ===> sudo-1.6.3.7 : Your system is too old to use this >SH> bsd.port.mk. You need a fresh make world or an upgrade kit. Please go >SH> to http://www.FreeBSD.org/ports/ or a mirror site and follow the >SH> instructions. >SH> test# uname -a >SH> FreeBSD test.mailsurf.com 4.3-RC FreeBSD 4.3-RC #2: Wed Apr 18 >SH> 10:08:47 GMT 2001 >SH> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MAILSURF i386 >SH> test# > >SH> what am i missing? >SH> make world has finished 10min before with a repository i got yesterday. >SH> ports is also fresh. > >SH> fyi: i am running a diskless machine, so /var is created on boot via mfs > >File /var/db/port.mkversion usually holds date when pkg_*** utilites >were rebuild. It is checked by port's Makefile. If it is missing or >has very old date you will see message > > Your system is too old to use this > >It should contain string like 20010201 (it is from one of my boxes). > > >-- > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >| Ilya Martynov (http://martynov.org/)| >| GnuPG 1024D/323BDEE6 D7F7 561E 4C1D 8A15 8E80 E4AE BE1A 53EB 323B DEE6 | >| AGAVA Software Company (http://www.agava.com/) | > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Well, how do you avoid this? I usually cvsup ports-all before trying to install a port, and cvsup ports-all every couple of weeks. When I get this message the only thing I've been able to figure out to do is delete the directory and cvsup again. If I haven't deleted a particular port before cvsup'ing it sometimes seems not to update the port. -- Roger You're only young once, but you can be immature forever! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
help needed to setup pppd dial-in service
Hi all! Our company has a test server which has been set-up already using 4.3-RC, with ipfilter/ipnat. We want to test if it is possible to add a pppd dial-in service in this box. Hardware: Asus AP-100 server with a PIII-500, 256MB 18.2GB SCSI-HDD, 3 NICS & USR 56K Modem. Assumptions: Server already set-up as a firewall/gateway with ipfilter/ipnat What we did: 1. Installed mgetty+sendfax via ports. Used the standard /usr/local/etc/mgetty+sendfax/mgetty.config. Only modified the "init-chat" option to ""ATZ OK AT&F1M0E1Q0S0= OK 2. Modified the /etc/ttys : ttyd0 "/usr/local/sbin/mgetty -s 115200" dialup on secure 3. Edited /usr/local/etc/mgetty+sendfax/login.config : /AutoPPP/ - - /etc/ppp/ppp-login 4. Created /etc/ppp/ppp-login. Chmod +x ppp-login #!/bin/sh /usr/bin/mesg n stty -tostop exec /usr/sbin/pppd /dev/ttyd0 115200 5. Create /etc/ppp/options detach require-pap auth crtscts defaultroute lock passive 192.168.0.1:192.168.0.15 domain my.domain idle 300 login modem ms-dns dns.ip.addr netmask 255.255.255.0 proxyarp asyncmap 0 6. Edit kernel config file; added more ppp pseudo-devices (kernel file already configured as gateway) Results... the dial-in answers, but PPP doesn't want to authenticate. Can anyone give us suggestions? TIA Ramon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
