Re: Segfaults and bus errors in 4.6.2?
Robert Withrow wrote: Man, am I read in the face!!! I just got through writing that I had built a kernel with this: :- options DISABLE_PSE but I just went and looked and found out I had edited GENERIC but built the kernel with another config file: [ ... ] Whoops! So it appears as if the act of building the kernel with a config *identical* to GENERIC made my problem go away! Weird. Is the distributed 4.6.2 kernel not identical to one built with the distributed 4.6.2 GENERIC config? Sorry for the bogus report. The problem is such that this is expected to work around the problem in a small number of cases. Your original bug report is probably correct, too. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Any users of matcd(4), mcd(4), or scd(4)?
On Mon, Oct 07, 2002 at 01:26:50PM -0700, Terry Lambert wrote: John Baldwin wrote: I can appreciate matcd being dropped for 5.0 on pragmatic grounds, but it would have been nice to have it ride out the rest of 4.x, given that it actually works right now. (As I understand it, it's the adoption of GEOM that signalled the death knell of these old drivers, but GEOM is a 5.x feature that wouldn't be MFC'd back to 4.x...) Unfortunately there were other issues with the driver unrelated to GEOM that required its removal. What are these? I've read the license, and it doesn't appear to be a license issue... Terry, Please be sure that you are not confusing 'matcd' with 'mcd'. The former has a 10 clause license and is not suitable for use in FreeBSD any more. The latter has a traditional 4 clause BSD license and is not scheduled for removal. In fact, there is at least one person doing active maintenance on it. Folks, I mourned the passing of matcd, too. It supported the first CD-ROM drive I owned. However, it is a closed issue. I encourage anyone who still desired support for this hardware to investigate other code bases which we could leverage off of, as long as the licensing issues involved are well understood and amenible. Please do not let it distract from the progress we are making towards the 5.0 release. Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Any users of matcd(4), mcd(4), or scd(4)?
On 2002-Oct-07 16:48:28 +0100, Mark Murray [EMAIL PROTECTED] wrote: I can appreciate matcd being dropped for 5.0 on pragmatic grounds, but it would have been nice to have it ride out the rest of 4.x, given that it actually works right now. (As I understand it, it's the adoption of GEOM that signalled the death knell of these old drivers, but GEOM is a 5.x feature that wouldn't be MFC'd back to 4.x...) Matcd was dropped because it had an unfriendly license. One that was impossible to comply with legally. Possibly there is a license issue. I agree that it's somewhat more restrictive than I'd like. However, there is no mention of any licensing problems in the commit messages deleting it: It was deleted from -current with the message: :Alas, poor matcd, I knew ye well. : :It doesn't work. :It cannot be made to work. :Goodbye. : :X-MFC after:ASAP And from -stable with the message: :matcd Help! Help, scottl is trying to *BANG* *BANG* *BANG* :CVSHello? Hello? Are you still there? : :Approved by:re (rwatson) Neither of these messages contain any suggestion that there is/was a licensing issue. The only discussion here indicated that matcd(4) and friends needed some work to make them work with -current and support would be dropped unless someone came forward to undertake said work. (And I'm sure I saw at least one offer). There was an explicit statement that these drivers would continue to be supported under 4.x. Then, out of the blue and with no discussion here, scottl deletes the driver. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Traffic shaping
On 2002-Oct-06 16:19:08 +0200, Christoph Moench-Tegeder [EMAIL PROTECTED] wrote: ## Daniel O'Connor ([EMAIL PROTECTED]): Actually, if you limit incoming TCP it will adapt to the correct speed. I do this at home without hassle (except the latency in games goes up from ~40 to ~100 but it is still acceptable) How much do you have to limit TCP for the desired effect? I never tried shaping on asymmetric lines, and the traffic ratio for a single TCP bulk transfer (1500 (or little less in case of PPPoE, PPTP, etc.) bytes incoming vs. 40 bytes outgoing) does not match the up/down-ratio of his line (1:6) by any means. ipfw/dummynet pipes only handle a single flow direction: If you have something like ipfw NUMBER pipe 1 ip from any to any via ifX then both incoming and outgoing traffic share the pipe and you are limiting the combined uplink and downlink traffic - which probably isn't what you want. Instead, you need two pipes with uplink traffic in one and downlink traffic in the other. Since the pipes are independent, you can set the uplink and downlink limits to suit your ADSL link: ipfw pipe 1 config bw UPLINK kbps ipfw NUMBER pipe 1 ip from any to any out xmit ifX ipfw pipe 2 config bw DOWNLINK kbps ipfw NUMBER pipe 2 ip from any to any in recv ifX Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: sshd_config vs. PAM
BTW, is there a way to completely disable PAM on a system? I was looking at it a couple months back. There is the NOPAM compiler flag. Unfortunately, telnet and ssh does not obey it. I have some untested patch at home before I got too busy with other non-FreeBSD things. --- Samuel Chow [EMAIL PROTECTED] This message is displayed using recycled electrons. Segmentation Fault (core dumped) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: sshd_config vs. PAM
On Mon, Oct 07, 2002 at 04:57:39PM -0600, Samuel Chow wrote: BTW, is there a way to completely disable PAM on a system? I was looking at it a couple months back. There is the NOPAM compiler flag. Unfortunately, telnet and ssh does not obey it. I have some untested patch at home before I got too busy with other non-FreeBSD things. PAM is considered to be an integral part of the system thesedays; as such there's no support for compiling without it. Kris msg50230/pgp0.pgp Description: PGP signature
Re: Traffic shaping
## Peter Jeremy ([EMAIL PROTECTED]): ipfw/dummynet pipes only handle a single flow direction: If you have something like ipfw NUMBER pipe 1 ip from any to any via ifX then both incoming and outgoing traffic share the pipe and you are limiting the combined uplink and downlink traffic - which probably isn't what you want. Yes, I see. My last experience with things like this suffered a little from a slightly underfunctional implementation of bandwidth control (and using dummynet/FreeBSD was not an option). I only had control over the outgoing queue on the external interface, so I tried slowing down slow start by limiting the acks from teh destination to the source of the transfer based on calculations with packet sizes and -rates (which seemed to be more than a little unreliable). [Perhaps I could construct a scenario with some more interfaces, where limiting the outgoing rates would be easier, but that would be too far fetched for now]. So my problem in short: How much do I have to limit acks in the direction with the lower bandwidth in order to control the usage of the other direction? This is a little away from the original thread, but I just would like to know (might come in handy some time and perhaps I can ptimize my old solution a little with other people's experience). Regards, cmt -- Spare Space To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re:mozilla compile problems
On Sun, 6 Oct 2002 13:31-0700, Kevin G. Eliuk wrote: =20 =20 I have been unable to build www/mozilla and have recently done a fresh cvsup of the ports collection to weed out any errors. The same error i= s occuring at different location of the build at every build attempt. If no one else has noticed the same errors, then could someone suggest = a possible. =20 If it fails at a different point every time, that sounds like a hardware problem... I was getting internal compiler errors while making buildworld. Turned out not to be the source; I had previously compiled world with the k6 optimizations in make.conf, so I figured maybe it wasn't working with gcc. I installed a new base system via packages, and builtworld fine. good luck -Mike Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: sshd_config vs. PAM
On Mon, Oct 07, 2002 at 04:20:51PM -0700, Kris Kennaway wrote: On Mon, Oct 07, 2002 at 04:57:39PM -0600, Samuel Chow wrote: BTW, is there a way to completely disable PAM on a system? I was looking at it a couple months back. There is the NOPAM compiler flag. Unfortunately, telnet and ssh does not obey it. I have some untested patch at home before I got too busy with other non-FreeBSD things. PAM is considered to be an integral part of the system thesedays; as such there's no support for compiling without it. Too bad. I find it to be rather painful to understand and configure, and overkill for most of uses. Bob Kris -- Bob WillcoxWe seem to have forgotten the simple truth that [EMAIL PROTECTED] reason is never perfect. Only non-sense attains Austin, TX perfection. -- Poul Henningsen [1894-1967] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: sshd_config vs. PAM
On Mon, Oct 07, 2002 at 04:56:24PM -0700, Kris Kennaway wrote: On Mon, Oct 07, 2002 at 06:42:48PM -0500, Bob Willcox wrote: On Mon, Oct 07, 2002 at 04:20:51PM -0700, Kris Kennaway wrote: On Mon, Oct 07, 2002 at 04:57:39PM -0600, Samuel Chow wrote: BTW, is there a way to completely disable PAM on a system? I was looking at it a couple months back. There is the NOPAM compiler flag. Unfortunately, telnet and ssh does not obey it. I have some untested patch at home before I got too busy with other non-FreeBSD things. PAM is considered to be an integral part of the system thesedays; as such there's no support for compiling without it. Too bad. I find it to be rather painful to understand and configure, and overkill for most of uses. Well, the point is that the default configuration is supposed to be exactly equivalent to the old non-PAM behaviour, so you shouldn't have to touch *anything* unless you want to change this behaviour (which would have required code changes in the non-PAM case). I have to admit, that recently (last year or so) this seems to be the case. It wasn't always that way, though. As I recall, rlogin didn't work w/o modifying the PAM configuration file for quite some time. I still contend that, for the PAM challenged, the description of the configuration file is a tough read. Bob Kris -- Bob WillcoxWe seem to have forgotten the simple truth that [EMAIL PROTECTED] reason is never perfect. Only non-sense attains Austin, TX perfection. -- Poul Henningsen [1894-1967] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: sshd_config vs. PAM
On Mon, Oct 07, 2002 at 06:42:48PM -0500, Bob Willcox wrote: On Mon, Oct 07, 2002 at 04:20:51PM -0700, Kris Kennaway wrote: On Mon, Oct 07, 2002 at 04:57:39PM -0600, Samuel Chow wrote: BTW, is there a way to completely disable PAM on a system? I was looking at it a couple months back. There is the NOPAM compiler flag. Unfortunately, telnet and ssh does not obey it. I have some untested patch at home before I got too busy with other non-FreeBSD things. PAM is considered to be an integral part of the system thesedays; as such there's no support for compiling without it. Too bad. I find it to be rather painful to understand and configure, and overkill for most of uses. Well, the point is that the default configuration is supposed to be exactly equivalent to the old non-PAM behaviour, so you shouldn't have to touch *anything* unless you want to change this behaviour (which would have required code changes in the non-PAM case). Kris msg50235/pgp0.pgp Description: PGP signature
Re: sshd_config vs. PAM
- Original Message - From: Kris Kennaway [EMAIL PROTECTED] BTW, is there a way to completely disable PAM on a system? I was looking at it a couple months back. There is the NOPAM compiler flag. Unfortunately, telnet and ssh does not obey it. I have some untested patch at home before I got too busy with other non-FreeBSD things. PAM is considered to be an integral part of the system thesedays; as such there's no support for compiling without it. I was trying to trim FreeBSD to below 16MB and to run it as an embedded system. I find PAM to be quite a baggage to have for simple root ssh login and perhaps ssh tunnelling. --- Samuel Chow [EMAIL PROTECTED] This message is displayed using recycled electrons. Segmentation Fault (core dumped) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Ok, I guess I need some help
I posted a problem with 4.7 RC, when I installed the port for mod_php4, it could not finish configuration. Where should I be posting this? Thanks in advance for any help. A.G. -- ___ A.G. Russell IV KC5KFDThe Knife Company e-mail: [EMAIL PROTECTED] Phone 479-631-0055 FAX 479-631-8734 Old Klingon Saying -- 'oH majQa' yIn je bang, Qo' bang --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: sshd_config vs. PAM
On Mon, Oct 07, 2002 at 06:34:33PM -0600, Samuel Chow wrote: PAM is considered to be an integral part of the system thesedays; as such there's no support for compiling without it. I was trying to trim FreeBSD to below 16MB and to run it as an embedded system. I find PAM to be quite a baggage to have for simple root ssh login and perhaps ssh tunnelling. The ssh-picobsd port exists for this purpose. Kris msg50238/pgp0.pgp Description: PGP signature
