Re: ftp and mail much slower into fbsd 4.4 vs and old BSDi
On Monday, July 1, 2002, at 12:00 , D J Hawkey Jr wrote: > Could you explain what newreno is, in a nutshell, the upshots of using > it, > and what the ramifications of turning it off are? http://www.google.com/search?q=tcp+new+reno To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: how do I see the current number of PTYs in use ?
On Saturday, March 2, 2002, at 12:23 , Paul Halliday wrote: > [00:12am]-root@dissent~# pstat -t | grep 'tty[pqrsPQRS]' | grep OCc | > wc -l Oh, and pstat -t | egrep -ic 'tty[pqrs].* OCc ' saves two forks. Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: how do I see the current number of PTYs in use ?
On Saturday, March 2, 2002, at 12:23 , Paul Halliday wrote: > Your not very bright are you? Hey, at least I can spell. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: how do I see the current number of PTYs in use ?
On Fri, Mar 01, 2002 at 09:51:22PM -0600, Paul Halliday wrote:
> On Fri, 1 Mar 2002, Joe Abley wrote:
>
> >
> > On Friday, March 1, 2002, at 05:49 , Dan Nelson wrote:
> >
> > > In the last episode (Mar 02), Daniel O'Connor said:
> > >> On Fri, 2002-03-01 at 21:19, Danny Braniss wrote:
> > >>> fstat | awk '{print $8}' | egrep 'tty[pqrsPQRS]' | sort -u | wc -l
> > >>>
> > >>> is IMHO correct, ;-)
> > >>
> > >> Ach, of course :)
> > >> I hope the original poster is satisfied 8-)
> > >
> > > Easier might be "pstat -t | grep 'tty[pqrsPQRS]' | wc -l"
> >
> > pstat -t | grep -ic 'tty[pqrs]'
> >
> > saves a fork. Since we're being silly.
>
> err.. we are not being silly..
Oh yes we are.
> not accurate (read last post)
> your modification still produces erroneous results.
My modification saves a fork from your modification, as specified.
If there is a god, this thread will now die.
Joe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: how do I see the current number of PTYs in use ?
On Friday, March 1, 2002, at 05:49 , Dan Nelson wrote:
> In the last episode (Mar 02), Daniel O'Connor said:
>> On Fri, 2002-03-01 at 21:19, Danny Braniss wrote:
>>> fstat | awk '{print $8}' | egrep 'tty[pqrsPQRS]' | sort -u | wc -l
>>>
>>> is IMHO correct, ;-)
>>
>> Ach, of course :)
>> I hope the original poster is satisfied 8-)
>
> Easier might be "pstat -t | grep 'tty[pqrsPQRS]' | wc -l"
pstat -t | grep -ic 'tty[pqrs]'
saves a fork. Since we're being silly.
Joe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: AWK/perl hacker needed to assist the Sparc64 port
On Tue, Feb 12, 2002 at 08:49:18AM -0800, David O'Brien wrote: > In rev 1.20 of sys/kern/vnode_if.pl Eivind converted this from a > Bourne+AWK script into a Perl script. Well that just makes porting to > new architectures VERY difficult as the boot strapping of Perl 5 is quite > difficult. > > A shell hacker could really help out the FreeBSD/sparc64 porting effort > by updating vnode_if.pl rev 1.19 to have all the functionality the perl > version has today. I spend more time than is healthy hacking awk, most days. I am behind on my mail and haven't followed this thread through to its conclusion, but if an awk hacker is still required, I am here, able and willing :) Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: serial ports
On Fri, Oct 05, 2001 at 10:25:47AM -0400, Benjamin Gross wrote: > what device file represents port 1 on a pc ? Assuming you mean "the lowest-numbered port on a PC" (the one commonly found at IRQ4 on the ISA bus): /dev/ttyd0 for callin ports /dev/ttyid0 corresponding callin initial-state device /dev/ttyld0 corresponding callin lock-state device /dev/cuaa0 for callout ports /dev/cuaaia0 corresponding callout initial-state device /dev/cuaala0 corresponding callout lock-state device See sio(4). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: No tools on 4.4-RELEASE ISO?
On Fri, Sep 21, 2001 at 03:44:56PM +, Olafur Osvaldsson wrote: > > On Fri, 21 Sep 2001, Alfred Perlstein wrote: > > > Wouldn't it be trivial to just mount the ISO, tar copy it, add the > > files then rerun mkisofs? > > > > This would result in all mirrors re-downloading the image wich is not such a > big deal except now there are a minimum of 5 users downloading the image at > any given time wich locks the file so it won't get updated unless the admin > disconnects the users and then the user can't resume the download and can't > start again untill the mirror site has finished downloading the image from the > master wich in some cases takes hours. Surely most mirror scripts pull down new content to a temporary file with no general read privs, then atomically mv that temporary file to the name of the updated file? Similarly on the master ftp server. I see no locking issues, or need to disconnect anybody. The only issue is that some people will have versions of the ISO without tools. Producing a new "with-tools" ISO sounds like a needless waste of mirror operators' disk :) Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: whois(1) patch for review
On Thu, Jun 21, 2001 at 10:23:43PM +0400, Andrey A. Chernov wrote: > On Thu, Jun 21, 2001 at 10:39:05 -0400, Joe Abley wrote: > > > > > > whois -c ru freebsd.org.ru (use -- whois.ripn.net) > > > > whois -Q freebsd.org.ru > > > > > whois -c ua freebsd.org.ua (use -- whois.net.ua) > > > > whois -Q freebsd.org.ua > > > > > Resume: with this patch included to add new country's whois server > > > we'll need to add only one string to text file, not to modify > > > whois(1) code as it has been done by Andrey for '-R' and as > > > some pending PR's proposed to do. > > > > This list is already maintained in the whois-servers.net zone. > > For domain names it works without '-Q' too. The main problem not with > domain names wich have "." found via whois-servers.net, but for > identificators or subnets without suffix, like: > > whois -c ru XXX-RIPN > whois -c ru 123.123.123.123 That seems entirely reasonable. I just wanted to point out that it wasn't necessary to maintain a big local list of whois servers for individual tlds in the case that you're looking up domains. Your patch certainly looks usable for other resources retrievable using whois. Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: whois(1) patch for review
On Thu, Jun 21, 2001 at 04:08:21PM +0300, Alexey Zelkin wrote: > It adds new command line modifier "-c" to declare server code. > Originally it was supposed to point to country's whois > server, but with no modifications can be used for other areas. > > For example you can have following string in your whoisservers > configuration file (system wide -- /usr/share/misc/whoiservers > or personal ~/.whoisservers): > > local whois.mydomain.com I wrote a patch for the openbsd whois client a year or so ago which used lookups under the whois-servers.net zone to locate appropriate whois servers for domain names. Looks like someone ported that to FreeBSD's client (the -Q option). Just thought I'd mention it, since your examples include: > It also supposed to be used for country's whois servers. For example > with whoisservers. > > ... > ruwhois.ripn.net > uawhois.net.ua > ... > > whois -c ru freebsd.org.ru (use -- whois.ripn.net) whois -Q freebsd.org.ru > whois -c ua freebsd.org.ua (use -- whois.net.ua) whois -Q freebsd.org.ua > Resume: with this patch included to add new country's whois server > we'll need to add only one string to text file, not to modify > whois(1) code as it has been done by Andrey for '-R' and as > some pending PR's proposed to do. This list is already maintained in the whois-servers.net zone. Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: services...
On Thu, Apr 19, 2001 at 12:30:37PM -0300, leal wrote: > thanks, > but what the point of this forum??? See: http://www.freebsd.org/doc/en_US.ISO_8859-1/books/handbook/eresources.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: IL0VEY0U worm (fwd)
In the interests of putting the ILOVEYOU thread to death, here's a concise description of the worm from bugtraq. -- Forwarded message -- Date: Thu, 4 May 2000 11:09:32 -0700 From: Elias Levy <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: IL0VEY0U worm A quick update with some more information and quick fixes. I am reproducing my original message in full bellow as some people are filtering messages with a subject line of ILOVEYOU. There is a good description of how to disinfect a system manually at http://www.thepope.org/index.pl?node_id=140 skyinet.net seems to be off the net. It seems they are being blackholed by someone. The worm has a comment that may or may not indicate the author: rem barok -loveletter(vbe) rem by: spyder / [EMAIL PROTECTED] / @GRAMMERSoft Group / Manila,Philippines I did not make it clear, but the worm does infect files in mapped network drives, so it can spread across the network via file shares by infecting the files I reported. When someone opens those files the worm will execute and infect their system. It seems the WIN-BUGFIX.exe file will email any cached passwords to [EMAIL PROTECTED] To stop the spread download updates for your antivirus product for your vendor. They all have some type of fix by now, but most antivirus vendor websites seems to be unavailable under the high load. Some I could reach: NAI: http://download.mcafee.com/extrafiles/love-4.zip Datafellows: http://www.datafellows.com/download-purchase/updates.html TrendMicro: http://www.antivirus.com/download/pattern.asp Sophos: http://www.sophos.com/downloads/ide/index.html#loveleta You should also not open visual basic attachments in email (.VBS), not accept DCC's on IRC from strangers (or friends for that matter) unless you known what you are receiving. If you control your mail server you should try to configure it to stop messages with attachments ending in .vbs. There seems to be some patches to sendmail from when Melissa came out that does this. You may also want to filter all email going out to [EMAIL PROTECTED] and stop the download of WIN-BUGFIX.exe in your HTTP proxy. * Elias Levy ([EMAIL PROTECTED]) [000504 17:02]: > A new VB worm is on the loose. This would normally not be bugtraq > material as it exploits no new flaws but it has spread enough that it > warrants some coverage. This is a quick and dirty analysis of what it does. > > The worm spreads via email as an attachments and via IRC as a DCC download. > > The first thing the worm does when executed is save itself to three > different locations. Under the system directory as MSKernel32.vbs and > LOVE-LETTER-FOR-YOU.TXT.vbs and under the windows directory as > Win32DLL.vbs. > > It then creates a number of registry entries to execute these programs > when the machine restarts. These entries are: > > HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run\MSKernel32 > HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices\Win32DLL > > It will also modify Internet Explorer's start page to point to a web page > that downloads a binary called WIN-BUGSFIX.exe. It randomly selects between > four different URLs: > > >http://www.skyinet.net/~young1s/HJKhjnwerhjkxcvytwertnMTFwetrdsfmhPnjw6587345gvsdf7679njbvYT/WIN-BUGSFIX.exe > >http://www.skyinet.net/~angelcat/skladjflfdjghKJnwetryDGFikjUIyqwerWe546786324hjk4jnHHGbvbmKLJKjhkqj4w/WIN-BUGSFIX.exe > >http://www.skyinet.net/~koichi/jf6TRjkcbGRpGqaq198vbFV5hfFEkbopBdQZnmPOhfgER67b3Vbvg/WIN-BUGSFIX.exe > >http://www.skyinet.net/~chu/sdgfhjksdfjklNBmnfgkKLHjkqwtuHJBhAFSDGjkhYUgqwerasdjhPhjasfdglkNBhbqwebmznxcbvnmadshfgqw237461234iuy7thjg/WIN-BUGSFIX.exe > > I've not been able to obtain copy of the binary to figure out what it does. > This does mean the worm has a dynamic components that may change its > behavior any time the binary is changed and a new one downloaded. > > The worm then changes a number of registry keys to run the downloaded binary > and to clean up after itself. > > HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run\WIN-BUGSFIX > HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\Start Page > about:blank > > The worm then creates an HTML file that helps it spread, > LOVE-LETTER-FOR-YOU.HTM. This is the file DCC'ed to others on IRC. > > The worm then spreads to all addresses in the Windows Address Book by > sending the file LOVE-LETTER-FOR-YOU.TXT.vbs as an attachment. The > email starts: > > kindly check the attached LOVELETTER coming from me. > > Then the virus searches for attached drives looking for files with > certain extensions. It overwrites files ending with vbs, and vbe. > It overwrites files ending with js, jse, css, wsh, sct, and hta, and > then renames them to end with vbs. It overwrites files ending with jpg > and jpeg and appends .vbs to their name. It finds files with the name > mp3 and mp3, creates vbs files with the same name and sets the hidden > attribute in the original mp*
Re: Is FreeBSD dead? Well, not in theory...
On Mon, Mar 13, 2000 at 03:44:04AM -0500, Dennis wrote: > At 07:32 PM 3/12/00 +0100, Jeroen Ruigrok/Asmodai wrote: > >That's also why I am wasting my time slowly documenting the FreeBSD > >internals in my spare time. > > "slowly" is the key word here. Real products are documented before they are > in commercial use. Plus by the time you're done they will be > outdated...another common problem. I have yet to find a "real product" with good documentation. > Why are you arguing this point? Is there anyone that believes that Linux > and FreeBSD are well documented? Yes. > Please. The books are out of date before they hit the stores. Books? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Is FreeBSD dead? Well, not in theory...
On Sat, Mar 11, 2000 at 01:36:31PM -0500, Dennis wrote: > Not realistically. First of all, most "scruffy unshaven hackers" are not > qualified to make serious changes to important drivers. they might be able > to find a stray pointer, but not to make structural improvement. This is just silly. > Another point is that Open Source is virtually synonomous with "Totally > undocumented". This is sillier. > My point was that because of open source you have an unfinished product > that never gets finished. That's the description of a product that is still alive. A product on which development stops is a dead product. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Tuning TCP/IP Performance
On Sat, Mar 04, 2000 at 08:21:20PM +, Paul Robinson wrote: > I've been trying to get TCP/IP performance as fast as possible by playing > around with sysctl (playing in the net.inet area) and so on, and was > wondering if there were any comprehensive resources on this that I've > missed. I haven't heard of any algorithms to tune TCP automagically. When I work with people who have satellite hops in their network, we usually have to tune the TCP knobs by hand, trying a large number of transactions and statistically minimising transaction time. > Whenever I do a sysctl -d -a to get a list of descriptions, I get > the following on 3.2-RELEASE: > > sysctl: sysctl name -1 1024 2: No such file or directory I get that too, but I had never noticed because I didn't know about the "d" flag :) FreeBSD 3.3-RELEASE FreeBSD 3.3-RELEASE #1: Sat Dec 4 15:21:53 NZDT 1999. > Any idea as to what's going on here? > > Also, I seem to remember hearing about a method used on SunOS to send the > first four bytes of the data payload back with the SYN ACK which gives the > appearance of improved performance on benchmarks. Does anybody know as to > whether this is possible under any version of FreeBSD? I'll move to 4.0 if > I have to. :) This is what I generally do before I try to tune anything further: # turn on RFC1323 extensions (timestamps, PAWS, window scaling, etc) These # seem to be on by default in 3.3, YMMV for 3.2. sysctl -w net.inet.tcp.rfc1323=1 # open up the send and receive windows to 131072 bytes; the default # 16k is too small for people living oceans away from the majority of # their content sysctl -w net.inet.tcp.sendspace=131072 sysctl -w net.inet.tcp.recvspace=131072 # If 4.0 (or later 3.x's) support SACK, turn that on here too. SACK is # cool :) This is what I use on OpenBSD: sysctl -w net.inet.tcp.sack=1 # If you want to try transactional TCP (T/TCP, RFC1644) which is the # thing you mentioned with the single segment with SIN, ACK, FIN + payload, # turn this on: sysctl -w net.inet.tcp.rfc1644=1 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Eclipse/BSD
This may be old news, but I follow -hackers, -arch and -current and I hadn't seen it before: http://www.bell-labs.com/project/eclipse/release/ Would be interested to hear informed opinion as to whether these changes might find a permanent home in FreeBSD at some point in the future. ... The Eclipse Operating System is a testbed for Quality of Service (QoS) that is being developed at Information Sciences Research Center in Bell-Labs, Lucent Technologies. The current version of Eclipse, which we refer to as Eclipse/BSD, is based on FreeBSD version 3.4., and is compatible with FreeBSD, thus supporting the same system calls, protocols, device drivers and applications. Eclipse provides flexible and fine-grained QoS support for applications. Its design allows legacy or Eclipse-unaware applications to provide QoS without the need of modification or recompilation. A simple API is provided for (new) applications to take addvantage of the fine-grained QoS support. Currently, the Eclipse project targets QoS support for server applications, in particular, to differentiate the performance of different web sites hosted on the same platform (see the Apache examples). We have implemented: + hierarchical proportional-share cpu, disk and link schedulers, + the /reserv file system providing an API to manipulate "reservations", + a tagging mechanism for the association of reservatios with schedulable operations. The schedulers, such as network, cpu or disk, can easily be replaced by others that implement different algorithms by just implementing the Eclipse scheduler API functions. ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: downed IP addresses/redundancy
On Sat, Jan 29, 2000 at 01:19:53AM +, Tony Finch wrote: > I'd be interested to know of a free implementation of VRRP for the BSD > network stack. I started to look at this a while back, but started to flounder when I looked for an existing interface to allow me to source frames on a local ethernet with a userland-specified MAC address. Actually, I think I looked on OpenBSD, and can't remember whether I looked on FreeBSD too. If anybody has a good idea about how to send and receive frames on a local ethernet interface using one of several possible local MAC addresses (most user-specified) I can probably resurrect the code. Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Encryption rules changes coming up - win for open source
On Thu, Jan 13, 2000 at 03:01:01AM +0100, Oliver Fromme wrote: >People posting ``open source'' programs would be required >to send the code, or a Web site address where the code was >displayed, to the government. > > Basically, does this mean something like > tar cf - /usr/src/crypto | mail [EMAIL PROTECTED] > ? :-) Oh, be nice. Put "uuencode" in that pipeline somewhere, at least :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Upgrading rdist to v6.1.5 in -CURRENT?
On Tue, Dec 07, 1999 at 10:13:34PM -0500, C. Stephen Gunn wrote: > Since rdist 6.1.5 is back under a BSD Style license, should we work > towards updating it in -CURRENT, and perhaps -STABLE. It has several > bug fixes and enhancements to the current supplied rdist. Yaay. That's a good thing. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
NFS server bound to specific local address
Hi, I've just noticed that (on STABLE, at least) it doesn't seem possible to run an NFS server on a machine, and have it service requests from clients talking to anything other than the base address. For example, if I ifconfig fxp0 inet 192.168.0.11 ifconfig fxp0 inet 192.168.0.16 alias and then have clients attempt to mount 192.168.0.16:/foo, the clients will not successfully mount the shared volume; this is (according to some posts on the subject I found in the -questions archive) because the client is expecting replies from 192.168.0.16, but the server is sending them from 192.168.0.16. This is correct behaviour by the client, since trusting NFS replies from any old address would be silly. It seems to me that _my_ requirements would be satisfied if an NFS request from a client could have its destination address recorded, so that any replies to that specific request could be sourced from the address expected by the client. Would this obviously break anything else? Would this be a security-conscious modification? Does -current already do this? If "no, yes, no" I'll have a look myself. Just keen not to overlap with anybody else's effort. -- Ua lawa küpono ka hakahaka pä o këia pä malule To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: why FFS is THAT slower than EXT2 ?
On Wed, Oct 27, 1999 at 04:22:20PM -0500, David Scheidt wrote: > On Thu, 28 Oct 1999, Joe Abley wrote: > > > On Wed, Oct 27, 1999 at 10:29:54AM -0600, Ronald G. Minnich wrote: > > > To put it slightly more strongly: as far as I'm concerned ext2 is not a > > > serious fs if you really care about handling power failures and other such > > > fun things. > > > > I'm not sure I've ever really understood this position. In cases where > > data integrity is vital to retain, there is no excuse for not using > > machines with multiple power supplies, each fed from independent, clean > > power sources, with multiple fans, running a stable, tested OS release. > > I take it you never have had anyone hit the Big Red Button, a fire, > a flood, or a random panic, a clueless tech, or a hardware failure? > I see one of my machines go down along these lines every six weeks or so. A > hosed filesystem would (really!) ruin my day. Actually, no, at least not in the past six years I've been working with carriers and high-spec datacentres. But I take your point :) Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: why FFS is THAT slower than EXT2 ?
On Wed, Oct 27, 1999 at 10:29:54AM -0600, Ronald G. Minnich wrote: > To put it slightly more strongly: as far as I'm concerned ext2 is not a > serious fs if you really care about handling power failures and other such > fun things. I'm not sure I've ever really understood this position. In cases where data integrity is vital to retain, there is no excuse for not using machines with multiple power supplies, each fed from independent, clean power sources, with multiple fans, running a stable, tested OS release. Of course, double-point failures _do_ occur. But really, not very often. Paranoia with FS writes can seem extreme considering that the network which attaches that machine to the outside world is probably not engineered to the same degree of fault protection. Just my $0.02. I'm not saying that FFS should throw caution to the wind (especially not in the default configuration) but to argue that async writes are only ever used by stupid people is a little unfair :) Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Apple's planned appoach to permissions on movable filesystems
On Wed, Oct 06, 1999 at 11:18:59PM +0900, Daniel C. Sobral wrote: > One would better assume that files available over NFS will be read > by anyone who wants, and, likewise, that files available on > removable media will be read by anyone who wants. That side of the > problem does not belong to this discussion. > > [...] > > The question here is how to minimize the cost/benefit ratio of > letting users mount external file systems on their own. At the very > least, the system must never trust that data. Ergo, no suid/sgid. Show me a disk that's _not_ removable. By your logic we would have _no_ sguid/sgid binaries _ever._ Physical access to a machine is always a security risk. Why would you treat easily-removable media any differently to slightly-harder-to-remove media? You still need to break into the vault to remove them. Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Developer assessment (was Re: A bike shed ...)
On Mon, Oct 04, 1999 at 09:44:00PM -0600, Wes Peters wrote: > > [common courtesy] > > This is and has been common courtesy on Usenet newsgroups and Usenet, > later Internet mailing lists, since I've had Usenet access - about 1985. > If you don't know that, you don't even belong on the net, let alone this > newsgroup. I think you may have identified a wider problem than just freebsd-hackers :) Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Cosmetic changes to whois(1)
I've just made two very minor (cosmetic) modifications to whois(1): 1. Added -m option, which selects whois.ra.net as the whois server. This server publishes routing policy for a large number of network operators, and is currently run by Merit (see www.ra.net for more details). 2. Added -q option, which constructs a whois server to use based on the TLD of the (single) argument, with ".whois-servers.net" appended. The whois-servers.net zone is run by the people at ultradns.com. This allows, for example, queries like whois -q patho.gen.nz whois -q microsoft.com whois -q nasa.gov whois -q nic.fr whois -q demon.co.uk to all provide meaningful output without having to worry about different whois switches for different registries. Small, simple patch included in bin/14095. Comments welcome :) Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PAM & LDAP in FreeBSD
On Mon, Jul 19, 1999 at 06:00:26PM -0600, Oscar Bonilla wrote: > I agree. In solaris (and linux by the way) all you do is set > passwdldap files > in /etc/nsswitch.conf > and that's it. In Solaris, it's passwd: ldap files ^ nsswitch.conf(4), SunOS 5.5.1: ... There is an entry in /etc/nsswitch.conf for each database. Typically these entries will be simple, such as "protocols: files" or "networks: files nisplus". However, when multiple sources are specified it is sometimes necessary to define precisely the circumstances under which each source will be tried. A source can return one of the following codes: Status Meaning SUCCESS Requested database entry was found UNAVAIL Source is not responding or corrupted NOTFOUNDSource responded "no such entry" TRYAGAINSource is busy, might respond to retries For each status code, two actions are possible: Action Meaning continueTry the next source in the list return Return now The complete syntax of an entry is ::= ":" [ []]* ::= "[" + "]" ::= "=" ::= "success" | "notfound" | "unavail" | "tryagain" ::= "return" | "continue" ... Actually, this message is now bordering on the useful, when all I meant to be was pedantic. I'll stop now, before I go too far; suffice to say the Solaris implementation has some other elements worthy of consideration if compatability is worth aiming for. It's maybe worth mentioning that /etc/host.conf might be a candidate for the attic if the Solaris implementation was adopted on a wholesale basis (i.e. including the "hosts:" key). Joe To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: PAM & LDAP in FreeBSD
On Mon, Jul 19, 1999 at 06:00:26PM -0600, Oscar Bonilla wrote: > I agree. In solaris (and linux by the way) all you do is set > passwdldap files > in /etc/nsswitch.conf > and that's it. In Solaris, it's passwd: ldap files ^ nsswitch.conf(4), SunOS 5.5.1: ... There is an entry in /etc/nsswitch.conf for each database. Typically these entries will be simple, such as "protocols: files" or "networks: files nisplus". However, when multiple sources are specified it is sometimes necessary to define precisely the circumstances under which each source will be tried. A source can return one of the following codes: Status Meaning SUCCESS Requested database entry was found UNAVAIL Source is not responding or corrupted NOTFOUNDSource responded "no such entry" TRYAGAINSource is busy, might respond to retries For each status code, two actions are possible: Action Meaning continueTry the next source in the list return Return now The complete syntax of an entry is ::= ":" [ []]* ::= "[" + "]" ::= "=" ::= "success" | "notfound" | "unavail" | "tryagain" ::= "return" | "continue" ... Actually, this message is now bordering on the useful, when all I meant to be was pedantic. I'll stop now, before I go too far; suffice to say the Solaris implementation has some other elements worthy of consideration if compatability is worth aiming for. It's maybe worth mentioning that /etc/host.conf might be a candidate for the attic if the Solaris implementation was adopted on a wholesale basis (i.e. including the "hosts:" key). Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 'rtfm' script
On Mon, Jul 05, 1999 at 05:11:57AM -0500, Chris Costello wrote: >I've been encountering people recently who, for one reason or > another, are unable to find information for themselves when they > have a question on FreeBSD. > >I propose an rtfm(1) command, and I've got some Perl code that > works. If people are interested, I will continue with it, and > write a man page. > >The source is attached. It would be good if you could use fetch(1) instead of forming the HTTP request yourself. That way people who already have fetch working through proxies don't have to modify anything to use rtfm. Is there a particular reason you're writing it in perl? Joe To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: 'rtfm' script
On Mon, Jul 05, 1999 at 05:11:57AM -0500, Chris Costello wrote: >I've been encountering people recently who, for one reason or > another, are unable to find information for themselves when they > have a question on FreeBSD. > >I propose an rtfm(1) command, and I've got some Perl code that > works. If people are interested, I will continue with it, and > write a man page. > >The source is attached. It would be good if you could use fetch(1) instead of forming the HTTP request yourself. That way people who already have fetch working through proxies don't have to modify anything to use rtfm. Is there a particular reason you're writing it in perl? Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: fetch(1) / fetch(3) patchkit available
On Fri, May 28, 1999 at 11:27:20AM +0100, Brian Somers wrote: > What about a non-interactive command for pushing stuff via ftp/http ? > This has always been lacking IMHO (``ftp -n < gotchas). > > I haven't actually looked at libfetch, but I would think that the > functionality should be there. If we're throwing in the kitchen sink, then the ability to do a POST via HTTP would also be really useful. Every second device I throw into the network comes with a lovely-looking web interface that is a pain to retrieve stats from automagically. Being able to do this with a fetch would be marvelous ;) Joe To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: GPS receivers for xntpd (off-topic)
On Wed, May 19, 1999 at 12:30:38PM +0200, Ladavac Marino wrote: > [ML] Back to my olden telco days some 10+ years ago when SDH > was on paper only and ATM was on benches, this sounds like 2MHz H1* > clock synchronized to GPS. Since transmission does not need the time of > day info (at least it did not need it last time I had any contact with > it, ages ago), I don't think there is any time of day info in that clock > output which would make this particular GPS receiver useless for NTP > purposes. Unless, of course, there is another output on the receiver > which provides the time of day info as well. I had kind of assumed the same thing; however, I was hoping I could T off a feed from the GPS antenna to a new receiver with different outputs, which we would purchase to provide time-of-day synchronisation rather than 1/2000 second synchronisation. It seems that there are a number of receivers that will do the job, but people are mentioning async interfaces and ethernet interfaces, and I am confused :) More random off-topic questions: a GPS synchronised clock is stratum-2, right? The caesium clock which provides synchronisation to the GPS is stratum-1? Sorry for the wasted bandwidth. Feel free to divert me privately to a FAQ on this, rather than cluttering up -hackers (I looked but couldn't find one). > [ML] * I think it's H1 I'm talking about: 30+2 channels of > 64kbps. European equivalent of T1. Approx. 2MHz. E1. Joe To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
GPS receivers for xntpd (off-topic)
On Tue, May 18, 1999 at 11:02:38PM -0700, Matthew Dillon wrote: > [various GPS chat] I have been meaning to do some research on this kind of stuff for a while. We have GPS receivers in the machine room that supply clock for some of the transmission network, but when I ask the telco guys about the output of these receivers they just frown confusedly and say "it's a 2 meg clock". I haven't mentioned NTP, because I can't be bothered to spell it for them :) So, we have an RF GPS source in the next rack which we can split and run into our racks on coax. What kind of receiver do we need to provide a synch source for xntpd to chime off? We have Ultra 2s and x86/FreeBSD boxes available which are running xntpd, but which are currently chiming of stratum-2 sources on the other side of the planet, which just seems sub-optimal :) Joe To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: VMware--anyone playing with it?
On Mon, May 17, 1999 at 03:22:31PM -0600, Charles Randall wrote: > http://www.connectix.com/html/connectix_virtualpc.html But this only runs on the Mac, right? > -Original Message- > From: Jacques Vidrine [mailto:n...@nectar.cc] > Sent: Monday, May 17, 1999 3:12 PM > To: Jason Thorpe > Cc: John & Jennifer Reynolds; freebsd-hackers@FreeBSD.ORG > Subject: Re: VMware--anyone playing with it? > > > On 17 May 1999 at 8:19, Jason Thorpe wrote: > > I think the Connectix Virtual PC is cooler; VMware only runs on Linux > > and NT because it requires gross hacks to redirect e.g. I/O space access. > > I haven't seen it... do you have a reference? > > Jacques Vidrine / n...@nectar.cc / nec...@freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
3.1 binaries, 3.2 binaries...?
My stable machine now calls itself: FreeBSD buddha.clear.net.nz 3.2-BETA FreeBSD 3.2-BETA #11: Fri May 14 19:24:02 NZST 1999 jab...@buddha.clear.net.nz:/usr/src/sys/compile/TIMELORD i386 In other words, the release version number has wrapped to 3.2 from 3.1 following a sup and build the other day. I have been building the setiathome clients for 3.1 and 4.0 -- the 3.1 binary was previously built on this machine. Presumably there have been _some_ changes between 3.1-RELEASE and 3.2-BETA that would cause binaries compiled on 3.2 to have problems on 3.1. Does anybody fancy (a) testing a 3.2-compiled setiathome binary I just rolled, on a 3.1-RELEASE machine? (b) taking over builds for FreeBSD 3.1 binaries, if it transpires there is an incompatability? (I don't have a 3.1 machine any more) Joe To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Seti project / stats reset, new version available
On Fri, May 14, 1999 at 04:57:30PM -0700, Matthew Jacob wrote: > > So do I. I would like them to make the source available. I have *lots* of > machines available that are sitting doing nothing. But they don't run > FreeBSD (yet). I have at least 3 alpha 8200s and 4 Alpha 4100s that are > running NetBSD now and mostly quiescent. If people have been having problems with proxy support in the 1.1 client on FreeBSD, let me know and I'll mail you a new binary to test. If you have other platforms you'd like to compile for, contact David Anderson and he'll more than likely thank you and point you towards the source. As I understand it, the reasons for not publishing the source include: + the analysis repository might get polluted with inacurrate results from un-tested clients + distributing binaries for platforms where source dists are not the norm (e.g. Mac, Windows) might encourage people to stuff them full of trojans. Anyway, I have nothing to do with SETI so I'll shut up now :) Joe To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: Seti project / stats reset, new version available
On Fri, May 14, 1999 at 04:56:05PM -0700, Matthew Dillon wrote: > :>http://setiathome.ssl.berkeley.edu/ > : > : Now available at ftp://ftp.cdrom.com/pub/setiathome/ > : > :-DG > : > :David Greenman > :Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org > :Creator of high-performance Internet servers - http://www.terasolutions.com > > Yah, but I spoke too soon.. their 1.1 client is coughing chunks. It's > seriously broken. Growl. How annoying, I hope they fix it ASAP! I compiled the 1.1 client for FreeBSD3.1 -- what seems to be the problem with it? [It seemed to work ok for me, but I admit I didn't test it very exhaustively]. Joe To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: ifconfig: changing mac address
On Sat, May 15, 1999 at 03:42:35AM -0400, Matthew N. Dodd wrote: > You want a sort of 'virtual' interface that allows the attachment of other > real (or maybe other 'virtual' interfaces) beneath it. This interface > implements a number of policies regarding how it routes packets addressed > to it. > > The two distinct policies I can think of at this time are: > > - channel bonding/trunking > - redundant link VRRP support would be nice (a la RFC2338 -- it's an openly-specified version of cisco's HSRP). I keep meaning to delve into the specifics of this, but if it's like HSRP it supports two address alias strategies -- one moves the "virtual router" IP address between two real routers' MAC addresses (by re-ARPing) and the other shifts the virtual router MAC address between the real routers. Moving the MAC address generally works better on ciscos, and is the default behaviour if the routers involved have firmware that supports soft ethernet addresses. But that's quite possibly due to the rather broken cisco ARP implementation (at least in interop with suns). This is perhaps another application for (a) soft MAC addressing on cards that support it, and (b) the idea of a "virtual"-type interface, perhaps tied to a specific driver. Joe To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD native xanim (was Re: Native Applixware for FreeBSD -- When? )
On Tue, May 11, 1999 at 11:50:04AM -0700, Ted Faber wrote: > > [xanim modules for Linux only, author lacks a build env] > There are a couple of people with shell accounts on my machines, who use them to compile FreeBSD versions of things. I'm more than happy to provide more (although some of the machines are laboriously slow). They're all in New Zealand, which isn't as far from the west coast USA in network terms as you might think. It just occurs to me that a list of people prepared to offer compilation environments to people who insist in distributing binaries might be helpful. Here's a start, anyway: Joe Abley , 4.0-CURRENT, 2.2.8, 3.1 Joe To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
