Re: SSH Must Die

Mike Silbersack wrote: > On Sun, 13 May 2001, Peter Wemm wrote: > > Mike Silbersack wrote: > > > 1. Is ssh working yet? > > > > Yes, it is working perfectly. The only problem is that it now works > > slightly differently to what people have expected. ie: it treats > > sshv1 rsa keys as totally

Re: SSH Must Die

Kris Kennaway wrote: > On Sat, May 12, 2001 at 04:24:48PM -0700, Terry Lambert wrote: > > Jordan Hubbard wrote: > > > ssh works just fine for me in 4.3. You must be doing something > > > wrong. > > > > I used that "sysinstall" thing Jordan wrote to upgrade > > from a 4.2 to a 4.3 system. > > > >

Re: wint_t

Valentin Nechayev wrote: > Modern Unicode allows character codes more than 65534. > wchar_t(65536) is Egyptian glyph;) Maximum allowed AFAIR is > 2**31-1. So at least 32 bits integer type required if you > don't want adapt system to former millennium requires. This argument came up on comp.lang.

Memory organization in case of large amount of data (jumbo grams)

Hi, My doubt is whether freebsd uses the normal mbuf & clusters in case of large amount of data (like jumbogram in ipv6 or the maximum ipv4 datagram size of 65536 bytes)? My understanding is that for such a large amount of data, clusters which can hold only 2048 byes are not economical. Hen

Mbuf organization in case of large amount of data.

Hi, My doubt is how data will be organized in buffers in case we want to transmit large amount of data. My doubt is regarding the organization of mbufs in case we want to transmit the maximum ip datagram size. In the normal case data is stored in clusters for data size greater than 208

Re: Memory organization in case of large amount of data (jumbo grams)

On Tue, May 15, 2001 at 08:15:56AM -0400, [EMAIL PROTECTED] wrote: > My doubt is whether freebsd uses the normal mbuf & clusters in case > of large amount of data (like jumbogram in ipv6 or the maximum ipv4 > datagram size of 65536 bytes)? FreeBSD provides two standard types of storage (mbufs and

ipv6 only?

Hello there, I wonder if anybody here has any experience with compiling pure IPv6 system without IPv4 support in the kernel at all? Are there any projects like that? Alexis To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message

Bootable ISO's

First let me apologize for butting in like this - I get hackers via the digest, so its tough to reply to the right people. I think its useful to note the principle of a bootable CD. You don't really boot the CD. (No really) What you are doing is loading an image of a floppy into RAM, the BIOS th

Re: xargs(1) "replstr" patch

At 11:52 PM -0700 5/14/01, Dima Dorfman ably wrote: >This is a simplistic example that can be done in many other ways >(including using -J), but it shows what -I is supposed to be able to >do. -J doesn't work with the above since it only looks for the >replstr once, and will not find it unless it

Re: SSH Must Die: problem resolved

] > Let me rephrase: ] > ] > 1. Terry, is ssh working for you yet? ] ] The /etc/pam.conf additions have fixed some of the systems, ] but not all of them. ] ] The difference between the systems that work with the ] changes, and the onces which do not, is the precise ] upgrade process. ] ] The

ypserv, the continuing battle...

I saw this the other day: http://www.sleepycat.com/historic.html Down at the bottom: > Finally, you should not upgrade your GNU gcc or Solaris compiler. > Optimizations in versions of gcc 2 that were in alpha test in the > summer of 1997, and a version of the standard Solaris WorkShop Compiler

Kqueue and FreeBSD versions

Hi -hackers, Just a quick question. What value of __FreeBSD_version should I require for kqueue? (I mean ) - was it introduced in 4.1 or 4.2 (memory fails me)? TIA, -- farooq <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of th

Re: Kqueue and FreeBSD versions

On Tue, May 15, 2001 at 03:16:23PM -0700, Farooq Mela wrote: > Hi -hackers, > > Just a quick question. > What value of __FreeBSD_version should I require for kqueue? (I mean > ) - was it introduced in 4.1 or 4.2 (memory fails me)? was introduced a loong time ago, and it was subsequently obsolet

Re: Kqueue and FreeBSD versions

In article [EMAIL PROTECTED]> you write: >Hi -hackers, > >Just a quick question. >What value of __FreeBSD_version should I require for kqueue? (I mean >) - was it introduced in 4.1 or 4.2 (memory fails me)? It was introduced with 4.1; I believe the correct __FreeBSD_version to use is 41000. -- Jo

Re: Kqueue and FreeBSD versions

Will Andrews wrote: > was introduced a loong time ago, and it was subsequently > obsoleted two years ago in favor of . > > The CVS logs will indicate which __FreeBSD_version you need for > kqueue(). I imagine the number is around 45. Thanks. Maybe the documentation for FreeBSD_version in /

Re: Kqueue and FreeBSD versions

Jonathan Lemon wrote: > It was introduced with 4.1; I believe the correct __FreeBSD_version > to use is 41000. > -- > Jonathan > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message Great, thanks. I figured you'd be the authority on thi

Re: wint_t

Tue, May 15, 2001 at 03:39:52, tlambert2 (Terry Lambert) wrote about "Re: wint_t": [...skip...] > I maintain that the correct size for wchar_t is 16 bits, > until someone can point to a character set that needs > more than that, and which has been ratified by a standards > body. I'm fully agre

Re: Kqueue and FreeBSD versions

Tue, May 15, 2001 at 16:39:29, fmela0 (Farooq Mela) wrote about "Re: Kqueue and FreeBSD versions": > > It was introduced with 4.1; I believe the correct __FreeBSD_version > > to use is 41000. s/41000/41/ - fix typo at least. > Great, thanks. I figured you'd be the authority on this one ;