RE: @Home Connect.
On Mon, 4 Oct 1999, Milliken, Scott wrote: One extremely important note about @Home service...make sure that you disable all of your services in inetd before ever calling them up to report outages or for any other tech support issue. The first time that I placed a Sounds like you should build an ipfw firewall which disallows connections from the @home network. That way unless they portscan from an external host, they'll never know.. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: @Home Connect.
On Mon, 4 Oct 1999, Kris Kennaway wrote: On Mon, 4 Oct 1999, Milliken, Scott wrote: One extremely important note about @Home service...make sure that you disable all of your services in inetd before ever calling them up to report outages or for any other tech support issue. The first time that I placed a Sounds like you should build an ipfw firewall which disallows connections from the @home network. That way unless they portscan from an external host, they'll never know.. Kris Or, if you've got connected friends, an encrypted tunnel to their network could be a handy thing.. chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
make world errors
Hi still I get: /usr/src/secure/lib/libcrypt/../../../lib/libcrypt/crypt.c: In function `crypt': /usr/src/secure/lib/libcrypt/../../../lib/libcrypt/crypt.c:62: warning: unused variable `j' /usr/src/secure/lib/libcrypt/../../../lib/libcrypt/crypt.c: At top level: /usr/src/secure/lib/libcrypt/../../../lib/libcrypt/crypt.c:14: warning: `rcsid' defined but not used make: don't know how to make crypt-md5.c. Stop *** Error code 2 Stop. *** Error code 1 where lies the problem ? TIA _ Lauri Laupmaa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: -DNOCLEAN failure
On 4 Oct 1999, Michael Sperber [Mr. Preprocessor] wrote: This is possibly a stupid newbie question; I'm doing my first serious stable build, cvsupped yesterday. I'm doing the build in AFS using arla, which is not absolutely stable yet. The build gets far, but arla will usually quit before the build finishes completely. Hence, I'm using to -DNOCLEAN to restart the build. This fails in one place: The buildworld tries to overwrite readonly files via vanilla cp -p to /usr/obj/usr/src/tmp/usr/bin which fails. I need to do Why are these files readonly? make world is _supposed_ to write to the files under /usr/obj. I'm not sure what you mean by readonly, either - if this is something arla (I don't know what that is either, but I guess it's related to AFS :) is doing then it sounds like a problem with arla.. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: how can i ...? what with ipfw?
On Mon, 4 Oct 1999, Martin McFlySr wrote: Hello [EMAIL PROTECTED], 1. How can i see what namely was changed in files after CVSup is done? I can seen at log CVSup, but can see only what files was changed: Subscribe to the cvs-all mailing list for a description of the changes are they take place (you could set up procmail to filter out non-stable commits - see the archives for how to do this). Alternatively, use the cvsweb interface to the CVS archives on www.freebsd.org. 2. What happying with ipfw? after change rc.firewall, sh rc.firewall, on console i see: dn_rule_delete, r 0xc09e6e30, default 0xc09e6eb0, 0 matches dn_rule_delete, r 0xc09e6e20, default 0xc09e6eb0, 0 matches dn_rule_delete, r 0xc09e6e10, default 0xc09e6eb0, 0 matches dn_rule_delete, r 0xc09e6e00, default 0xc09e6eb0, 0 matches This sounds like broken binary compatability - are your kernel and ipfw binary in sync (i.e. have you built a new kernel and done a make world with sources of the same date)? ISTR that binary compatability was broken (and documented as such) between 3.2 and 3.3 or so, you should check the release notes and UPDATING file each time you update to catch these. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Multiple crashes.
The crashes alternate between the previous message's backtrace and
this one.
panic: rlist_free: free start overlaps already freed area
(kgdb) bt
#0 boot (howto=256) at ../../kern/kern_shutdown.c:285
#1 0xc014c469 in panic (
fmt=0xc01f0a34 "rlist_free: free start overlaps already freed area")
at ../../kern/kern_shutdown.c:446
#2 0xc0155f36 in rlist_free (rlh=0xc0243338, start=0, end=7)
at ../../kern/subr_rlist.c:159
#3 0xc01aecc7 in swap_pager_freeswapspace (object=0xca0e9b24, from=0, to=7)
at ../../vm/swap_pager.c:422
#4 0xc01aeda8 in swap_pager_freespace (object=0xca0e9b24, start=48,
size=20500) at ../../vm/swap_pager.c:445
#5 0xc01b4209 in vm_map_delete (map=0xca2edd80, start=134868992,
end=218836992) at ../../vm/vm_map.c:1833
#6 0xc01b42ac in vm_map_remove (map=0xca2edd80, start=134868992,
end=218836992) at ../../vm/vm_map.c:1874
#7 0xc01bc14b in obreak (p=0xca2a89a0, uap=0xca400f94)
at ../../vm/vm_unix.c:107
#8 0xc01d6f1b in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 134868992,
tf_esi = 134549792, tf_ebp = -1077946648, tf_isp = -901771292,
tf_ebx = 671987304, tf_edx = 671987284, tf_ecx = 671987280, tf_eax = 17,
tf_trapno = 0, tf_err = 2, tf_eip = 671951256, tf_cs = 31,
tf_eflags = 647, tf_esp = -1077946684, tf_ss = 39})
at ../../i386/i386/trap.c:1100
#9 0xc01cc49c in Xint0x80_syscall ()
#10 0x280d2402 in ?? ()
#11 0x804c1a8 in ?? ()
#12 0x804b087 in ?? ()
#13 0x804a6c1 in ?? ()
#14 0x80490f5 in ?? ()
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: kernel panic
On Fri, 1 Oct 1999, Mr. K. wrote: FreeBSD my.computer.com 3.2-RELEASE FreeBSD 3.2-RELEASE #0: Tue May 18 04:05:08 GMT 1999 jkh@cathair:/usr/src/sys/compile/GENERIC i386 I just got a kernel panic while telnetted into my machine. I didn't have the console plugged in, and i missed the panic message. Is there anywhere I can get the message? (I tried dmesg, but that didn't have it). Unless you have your machine configured to dump state on panic, no. See the handbook for how to set it up - it's a useful (almost essential) diagnostic aid. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: @Home Connect.
On Sun, 3 Oct 1999, David Kott wrote: That seems odd to me. My roommate and I share the same cable modem. We are not proxied as each of us have a distinct, and static IP. @Home allows us to purchase additional IPs (up to 3 per household) to add additional computers. The modem is a Mot. Cybersurfer Wave. Both times I set up cable modems on unix, they had a single IP. The power cycle rule applied for the single-IP config on the old (big) motorola, and the new (small) motorola on Comcast cable system in Baltimore County, MD, and to the system in Norfolk VA. In both cases, we set up a BSD machine with two ethernet cards. One connected to teh cable modem directly, the other connected to the LAN (LAN side is 100mbit too). The unix machine took on the real IP, and the 100mbit network was configured with NATD (illegally for @home, but who cares). John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ...
:Speaking of mmap, was this DoS every fixed/ commited to stable ? : :With :slag3% limit -h :cputime unlimited :filesize32768 kbytes No. There is no limit on how much memory can be allocated via mmap(). There will soon be a resource limit to help determine which process(es) to kill when a machine runs out of swap, and someone was working on a per-user (rather then per-process) overall memory use resource-limit, but neither yet exists . -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ...
At 12:34 PM 10/4/99 -0700, Matthew Dillon wrote: :Speaking of mmap, was this DoS every fixed/ commited to stable ? : :With :slag3% limit -h :cputime unlimited :filesize32768 kbytes No. There is no limit on how much memory can be allocated via mmap(). There will soon be a resource limit to help determine which process(es) to kill when a machine runs out of swap, and someone was working on a per-user (rather then per-process) overall memory use resource-limit, but neither yet exists . Thanks for the response. Do you imagine that this would be integrated into stable, or would this be a 4.x branch change only. ---Mike Mike Tancsa, tel 01.519.651.3400 Network Administrator,[EMAIL PROTECTED] Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
More on the crashes already mentioned.
In reference to the two crash dumps I've posted, the most interesting thing about them is that a non-debug kernel seems to be stable on the box. I can't really explain why, but we tried all kinds of things --- changing hardware... even exchanging whole guts of machines and those two examples of crashes persisted. Then in a fit of despairation, I recompiled the kernel w/o debug symbols and so far (touch wood) the machine has been stable. Now... the machine has 256M of memory ... so I wouldn't expect that kernel size *should* be an issue, but something is not right here. Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
