Re: I'm leaving the project
: :Does anyone know why this person is trying to (poorly) impersonate MD? Probably because I lambast him mercilessly for being such a whimp. It's kinda sad, actually. He's probably not making any friends with the people running the blind proxies he abuses to post, either. You know the person by name/alias, then? Who is it? Probably not. Anybody who fakes messages fits the above category :-) Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: sendmail + auth + ssl + freebsd
On Wed, 19 Dec 2001, Leo Bicknell wrote: After searching the archives and looking at the source, I find myself more confused. I've been asked to set up sendmail + ssl + SMTP auth on a FreeBSD host. A quick strings on the sendmail binary shows a number of SSL functions, so I'm thinking the SSL bits are in there, but I'm not quite sure how to take advantage of them. Issuing AUTH to a stock -STABLE sendmail gets command unrecognized though, so I don't think that is there. Do you have this in /etc/make.conf? # Add SMTP AUTH support to Sendmail SENDMAIL_CFLAGS+= -I/usr/local/include/sasl -DSASL -D_FFR_UNSAFE_SASL SENDMAIL_LDFLAGS+= -L/usr/local/lib SENDMAIL_LDADD+=-lsasl In sendmail.mc: TRUST_AUTH_MECH(`PLAIN LOGIN DIGEST-MD5 CRAM-MD5')dnl define(`confAUTH_MECHANISMS',`PLAIN LOGIN DIGEST-MD5 CRAM-MD5')dnl define(`confDONT_BLAME_SENDMAIL',`GroupReadableSASLFile')dnl in /usr/local/lib/sasl/Sendmail.conf: pwcheck_method: shadow This will at least give you AUTH. (I think you need to install ports/security/cyrus-sasl to make it work, but I'm not sure). If no one else has figured this mess out, I'll do it and write a page for the handbook. If someone else has, please clue me in, and if necessary I'll still write that handbook page. :-) It would be very nice if it was simple to make FreeBSD sendmail SSL and authenticate against the password file. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
SmartDisk USB CompactFlash reader
I've got such a device; it was nessecary, because my camera run out of batteries before I could retrieve 48MB of pictures over the normal serial port When I plug it in it displays: ugen0: SmartDisk Corp. SM/CF Combo USB Reader, rev 1.00/0.83, addr 2 Can this be read in FreeBSD? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: SmartDisk USB CompactFlash reader
On Tue, 24 Jul 2001, Alfred Perlstein wrote: * Leif Neland [EMAIL PROTECTED] [010724 19:18] wrote: I've got such a device; it was nessecary, because my camera run out of batteries before I could retrieve 48MB of pictures over the normal serial port When I plug it in it displays: ugen0: SmartDisk Corp. SM/CF Combo USB Reader, rev 1.00/0.83, addr 2 Can this be read in FreeBSD? Try compiling in the 'umass' driver, you may be out of luck, SanDisk produced a version of thier reader that didn't use the USB disk specification and requires a proprietary driver for it, you may be stuck using this from windows. Good news is that you can get one that works in freebsd for only about 20$. umass, scbus and da is in kernel. I'm out of luck... Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: XFree86
On Sat, 19 May 2001, Huff wrote: I can't get XFree86 to work. Using /stand/sysinstall I use the script and configure everything manually to the best of my knowledge. I can't find any specs on the monitor I'm using (The Monitor is from the Toshiba Infinia 7200) so I'm not sure of the Vertical and Horizontal refresh rates, If you can dualboot into windows, or have a windows machine nearby, you could try the different resolutions, and write down the frequencies from the on-screen display, if the monitor got one. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: x86-64 Hammer and IA64 Itainium
- Original Message - From: Sergey Babkin [EMAIL PROTECTED] To: Michael C . Wu [EMAIL PROTECTED] Cc: Jeremiah Gowdy [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Friday, April 27, 2001 4:09 AM Subject: Re: x86-64 Hammer and IA64 Itainium Anothing interesting point is that the optimisation for IA-64 seems to be highly processor-specific: the code optimized for Itanium won't be optimal for McKinley and vice versa. I've heard an estimation of about 1.5 times speed increase due to the model-specific optimisation. Perhaps commercial software will need to come in (encrypted) source and be compiled to the the current processor... Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: ppp showing radius message
- Original Message - From: Victor Ivanov [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, April 25, 2001 5:48 PM Subject: ppp showing radius message Hi, I made a simple (and ugly) patch to ppp to show the radius message when a radius reject is received. Great idea. It annoys me our radiusserver can send messages like You are already connected. Simultaneous connects not allowed or Access only allowed between 18:00 and 08:00, but M$ completely ignores it. So let's make Fbsd better in this respect too. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: device driver dev. book
On Fri, 16 Mar 2001, Bill Paul wrote: Some body just told me that williams Paul from Columbia University (Bill Paul @ Freebsd.org) has written that kind of book. But I can't get his exact email address at FreeBSD.org to ask him the reference. GR. Look, I have not now nor have I *ever* written a book of any kind. Whoever told you I had was wrong! Dead wrong, okay? Let me repeat: there is no book. Alright? Satisfied? Understand now? Good. Let us never speak of this again. Just to get the facts clear: Do you ever intend to write a book? Leif It appears you have been asked this before ... :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Extremely large (70TB) File system/server planning
On Mon, 5 Feb 2001, Michael C . Wu wrote: Hello Everyone, While talking to a friend about what his company is planning to do, I found out that he is planning a 70TB filesystem/servers/cluster/db. (Yes, seventy t-e-r-a-b-y-t-e...) Apparently, he has files that go up to 2gb each, and actually require such a horribly sized cluster. You later say some files may never be accessed after a week. How about a multi-level storage system, where the files eventually gets written onto dvd's. And either a robot or student :-) to put the requested disks online? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: how to test out cron.c changes? (was: cvs commit: src/etc crontab)
One of the things that would need to be documented is what will happen to the new algorithm in the situation where cron is stopped and re-started during one of the time periods that gets repeated. Oh, you bring up an absolutely new datapoint it seems! Since all the information vixie cron (in its original form as well as the OpenBSD variant) keeps its state in is held in memory (the time it went to sleep, the time it expects to wake up again, the time it is collecting jobs for -- usually somewhere between the time it went to sleep and the time it woke up at, catching up towards the current time) it wouldn't know that it does repeat an hour it just has passed few minutes ago in case there's been a restart in between. Oh no. If this "clock-slewing" was implemented, I'd expect killing and restarting cron be a way to forget everything which had happened. I.e. if I wanted to test a schedule, I might want to stop cron, reset time and start cron again. Cron usually doesn't die by itself. If it gets killed, it is usually for a reason. Don't complicate this proposed change with also having to add persistance over a kill and restart. Does anacron handle this DST issue better? Could it be added to ports if so, and a knob NO_CRON in make.conf? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: how to test out cron.c changes? (was: cvs commit: src/etc crontab)
In summary: I do not see a valid argument for not having the bugfix at all, available as an option. I do see the argument for not changing the default. I also see that everyone who opposes seems to believe that it is only people without major skills that get confused by all this, since people with major skills know not to rely on any behaviour over DST changes. 66% of them agree (33% haven't expressed an opinion) without provocation that those people with major skills will read the release notes. Common sense indicates that they are able to use a command line option that disable the new reliable behaviour. There has been expressed a need for testing. That is dealt with by three years in OpenBSD, and a period of time in the development branch, as per most development. If this is turning into a vote: I'm for the new colour of the bikeshed. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Boot process robustness
If an fsck fails, ifconfig the interfaces and start an sshd so people can get in remotely and fsck... What if an fsck on /usr fails? Other than that, I love the idea! Force-mount it read-only if necessary, or simply copy a static sshd into /sbin. Runnning fsck -y is the wrong solution, since if fsck can't fix an error automatically, something pretty bad has happened (physical media error, someone dd'ing onto the raw disk, etc).. Even so, unless the machine contains invaluable data, I guess 99% still does a fsck -y if fsck fails. I'd rather have my remote boxes do that by themselves, and perhaps email me, than I either have to drive there, or give somebody the root password, and remote control that person to just do fsck -y. In almost all cases, when a machine can't fsck itself after a power failure, a fsck -y fixes it. But then, most of the disk is either squid's cache, or unused stuff like termcaps, kernel source, man pages etc. Most stuff is there just because it could be handy one day, and it is not worth the trouble pruning it. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: post-install of kernal sources, maxusers max?
On Wed, 8 Nov 2000, Len Conrad wrote: Sorry to bother you hackers, but -questions isn't responding, and the handbook and Complete/Lehey don't, afaics, cover this situation explicitly. I can't really afford to screw up this production machine and start over from fresh disk, nor futz around for hours guessing what magik combo of post-install choices will do the trick. == I'm working, remotely, on a 4.1 system with only a binary install from cdrom. Now I need to do a custom kernal. Can the /stand/systinstall post-config option be used to put on all the developer source pkg without bothering the current config? which choice (I don't want X, just enough to build a custom kernal) Install cvsup-binary from ports, and cvsup the sources. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Filesystem holes
Hmm... Perhaps you're still missing my original point? I'm talking about a file with 96GB in addressable bytes (well, probably a bunch of files, given logical filesize limitations, but let's say for simplicity's sake that we have a single file). It's actual "size" (in terms of allocated blocks) will be only a bit larger than 2.1GB. (Directly proportional to the used size of the dataset. Discrepancies only come into play when record size != block size, but that can be worked around somewhat) In other words, ls -ls will report the "size" as some ridiculously large number, will show a much smaller block count. So, assuming four records are added to the file on block boundaries, the file will actually only use four blocks... nowhere near 96GB! In the UNIX filesystem (ya, I know.. just pick one :-), size of file != space allocated for file. Thus, my original questions were centered around filesystem holes. I.e., non-allocated chunks in the middle of a file. When trying to READ from within a hole, the kernel just sends back a buffer of zeros... which is enough to show that the record is not initialized. Actually, something like an "exists" function for a record wouldn't touch the disk at all! When writing to a hole, the kernel simply allocates the necessary block(s). This is really fast, too, for creation, as the empty set can be written to disk with touch(1), and uses far less memory than virtual initialization or memory structures ;-) What will happen, if somebody (possibly you, as mahordomo says), tries to make a backup of that file. Will the copy also be with holes, or would that file suddenly use all 96GB? It will at least do so, if one does cat filefile.bak Probably tar will do the same. I'd be afraid to create something which could easily blow up by having normal operations applied to it. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: can't build custom kernel
First thing: read /usr/src/UPDATING. The proper procedure to build a kernel is in there. To save you some time: cd /usr/src make buildkernel KERNEL=your kernel name make installkernel KERNEL=your kernel name If the build still fails, then yes, you have a legitimate problem. At least when the normal (faster) config MYKERNEL;; cd ../../compile/MYKERNEL;make depend make make install fails. I also couldn't build a kernel the normal way, but the buildkernel cleaned something, so my preferred method worked again. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD vs. Linux
Hi all again, Speaking of this subject again, I have read in the archives that FreeBSD has a method of building the whole source tree using the "make world" command. Although this is a nice feature, but isn't too much risky to upgrade the whole system in one shot? What if something breaks down after you've recompiled? Your system would be dead. In Linux, on the contrary, there's no such feature and you'll need to take the server anyways to upgrade it, which seems as a good way of doing things. In the meantime, another backup server can take its position. I guess in this fashion, Linux is better than FreeBSD... or did I miss something here? The make world is done in two steps: first is everything compiled to /var/obj, then everything is installed. Per definition production servers run freebsd-stable, which by definition are never broken :-). By definition freebsd-current are not for production and are allowed to be broken. You could compile on a testserver; when you are satisfied it works, you can install other servers from that via nfs. I have updated servers while they were online without problems. An OS shouldn't limit you from taking the risc of shooting yourself in the foot if you feel you have a legitimate reason to do so. Leif /John Sergey Babkin wrote: By the way, speaking of that, things in FreeBSD tend to be more synchronous with docs than in Linux. Also FreeBSD has much better backwards compatibility (though alas still not as good as commercial systems). In Linux the applications tend to break and require recompilation when the kernel is upgraded to the next second-digit version. -SB -- Regards, phpStop.com http://www.phpstop.com/ stop here. start everywhere. mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Question about -Wchar-subscripts
- Original Message - From: "Dan Nelson" [EMAIL PROTECTED] To: "Larry Lile" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, October 03, 2000 9:49 PM Subject: Re: Question about -Wchar-subscripts In the last episode (Oct 03), Larry Lile said: ...we get scores of warnings about using characters as subscripts to an array (-Wchar-subscripts), which generates so much noise as to mask real warnings burried within. Therefore, I would like to suppress this warning unless someone can explain why using a char as an array subscript is in any way an illegitimate thing to do. As far as I can tell, getting rid of the warning by changing the code would require adding a large number of frivolous casts to scores of source files... So why is using a "char" as an array subscript wrong? I had always avoided it because the compiler complained and that was good enough for me. Because your char value could be negative and end up referencing memory before your array start. Mainly a problem with the ctype macros and high-ascii characters. How about unsigned char? Could that be used for index? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
traceroute using tcp to a port?
If I understand correctly, traceroute works by sending pings with ttl=1, ttl=2,ttl=3 etc and records the names of the routers where the ttl reaches zero. However, an increasing number of sites believes in security by obscurity, and blocks for pings. Would the same technique work for making a telnet to port 80 with ttl=1, ttl=2 etc? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: localhost cannot be resolved
On Fri, 11 Aug 2000, Alexander Anderson wrote: Hello everyone! I sent this question to freebsd-questions, but no one had replied, so I decided to try my luck here. I'm having trouble resolving "localhost" for telnet and fetchmail. All other programs (ftp, rlogin, rsh, ping, lynx) seem to understand "localhost". I "me too"; but telnet can't resolve anything, while the others work. I have a current workstation, which makes world almost every night. It resolves ok. I then have my gateway/ppp/proxy which I regularly updates by nfsmounting /usr/src and /usr/obj from the workstation, and then make installworld. However, something must have happened, because as mentioned telnet won't resolve anything. (And perl 5.6 won't install either...) Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
2 inetd's with 2 nics
Is it possible and a good idea to have one inetd for the inside nic and another with fewer services for the outside on a gateway machine, or should I just use ipfw/ipchain for this? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 2 inetd's with 2 nics
- Original Message - From: "Chris Costello" [EMAIL PROTECTED] To: "Leif Neland" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, August 13, 2000 6:31 PM Subject: Re: 2 inetd's with 2 nics On Sunday, August 13, 2000, Leif Neland wrote: Is it possible and a good idea to have one inetd for the inside nic and another with fewer services for the outside on a gateway machine, or should I just use ipfw/ipchain for this? From the inetd man page: -a Specify a specific IP address to bind to. Alternatively, a host- name can be specified, in which case the IPv4 or IPv6 address which corresponds to that hostname is used. Usually a hostname is specified when inetd is run inside a jail(8), in which case the hostname corresponds to the jail(8) environment. Yes, I know this. But is it a good idea to have separate inetd's for inside and outside? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Make world in traditional make-mode
Is there an option in make world to work like a traditional make works? i.e. just recompile if the source has changed. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: IrDA InfraRed Drivers. Would anyone use them?
Talking about IrDA, how much hardware is needed on a Asus P2B ? Is it something which can be build from parts from the local electronics dealer? Is a schematic available? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
one ups, many machines
How does handle it when one ups drives many machines? Wire the ports in parallel, and have an ups-daemon on each? Or just connect the ups port to one machine, and have this send a message to the others when the power is failing? And after a suitable time, turn off the ups regardless if the mains is ok, and turn it on again when the mains is ok? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Post-shutdown hook for UPS shutdown?
How do you control the shutdown? If it is a simple logical signal, i.e. either high or low voltage, perhaps the easiest way would be a hardware solution. It could be as simple as a diode, a large capasitor and a resistor. Your local electronic supplyer could probably build a delay circuit for a few ? or £ ... Leif - Original Message - From: "Cillian Sharkey" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 19, 2000 6:00 PM Subject: Post-shutdown hook for UPS shutdown? Hi Folks, I need to execute a script (which tells the UPS to turn off) *after* the system has come to a safe halt from shutdown -h. I can't place the commands in /etc/rc.shutdown because this is too early in the shutdown sequence. Unfortunately, the UPS in question (APC Back-UPS 650) is not a "smart" one, (i.e. it doesn't have an in-built delay when a shutdown signal is received which gives time for all attached devices to shutdown) and I'm pretty much stuck with it. The software is the Network UPS Tools (NUT) package. Basically, is there currently any way to execute a post-shutdown script once the system has "halted" ? If not, is this feature possible to add ? Thanks in advance, -- Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Turning on a relay.
I'd like to turn on a relay to the power for my laserprinter 3 rooms away where the server is located. I have an i/o board with a 8255 24 bit i/o port.(IIRC) So I wrote a simple userland program to do inb/outb, but it dumped core with BUSERR, I presume because userland is not supposed to do i/o to the hardware. I guess I have these options: A: write a driver/kernel module to access the port. B: use an extra parallel port. (I use 2 at the moment) C: use a serial port; I have 3-4 available. What would be the simplest to interface from a shellscript, i.e. the spooler to turn on and off the printer? (The relay has a turn-off delay, so I don't have to worry about turning off the power after everything has been sent, but the printer not finished, or turning off/on between printjobs) Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: bind and the limit of serial number ???
On Sun, 23 Apr 2000, Evren Yurtesen wrote: Hello, is the bind have 32 bit unsigned integer variable for the serial number part of the dns records? if yes, it means that we cant have a number bigger than 4294967296 right? Somewhere I read something like: "The format MMDDnn" is often used for the serial number. We know this wil break in the year 4294, but we are not worried about that." what happens if we have a bigger number? then bind takes it like modulus 2^32? I once put in an extra digit in the serial number. This made a secondary use a serial number, which was larger than mine, and could probably be the modulus 2^32. I had to call the hostmaster there (A "3.rd secondary" hosted at our uplink) to get the zonefile removed, so the right one would be reloaded. or it is forbidden to have a bigger number? Not only forbidden, impossible... Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: bind and the limit of serial number ???
You can not be sure your secondary dns servers are picking up your zonefile, when you update the primary. On Sun, 23 Apr 2000, Evren Yurtesen wrote: well ours is still working fine ! thats why I asked this question, we did not realize that it went over 32 bit boundary how can I understand if there is a problem or not? Evren On Sun, 23 Apr 2000, Dave Dunaway wrote: Put a number bigger than 2^32 and it will overflows. is the bind have 32 bit unsigned integer variable for the serial number part of the dns records? if yes, it means that we cant have a number bigger than 4294967296 right? what happens if we have a bigger number? then bind takes it like modulus 2^32? or it is forbidden to have a bigger number? -- Dave. Dave Dunaway [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: shell issue
On Fri, 24 Mar 2000, Dungeonkeeper wrote: Hi there, First of all: I want to apologise for my poor english. Today me and a few friends of mine discussed the shells' (well, shell is actualy one of: sh/bash/csh/tcsh... not tested for ksh) command line expansion routines, mainly because of a problem discovered by one of my friends. I'm not sure if this is something new... So, let me explain what he found. It seems that the shell wants to allocate enough memory to hold the entire command line when expanding all of the arguments and we can force it to allocate hudge ammount of memory with a tricky command like this: carnivoro# /bin/csh -c `cat /dev/urandom` (I use tcsh here (the carnivoro# prompt), but the same thing happens when testing with sh/bash/tcsh) In this situation, the shell tries to allocate enough memory to hold what it reads from /dev/urandom, because it must be passed as a command line argument to /bin/csh ( actually, any command will be ok ). So, the shell eats more and more memory (on my machine (3.4-STABLE) - 251 MB) before the kernel decided to take some action (like killing some processes... started by other users? system services? or... in my case... crash :). My friend said that he sent a mail to bugtraq describing this problem. Those who are interested can read it. I tried this too: /bin/csh -c `cat /dev/urandom` My shell grew to around 260MB, then "bash: xrealloc: cannot reallocate 134217728 bytes (0 bytes allocated)" Then it exited to the logon prompt. The rest of the system didn't notice. Happened both as root and normal. I tried this with ridiculously 8GB swap (just for fun...). With 128MB swap, the system complained when the swap got full, but then only killed the shell, returning me to the logonprompt on that window. No other problems either. Leif I believe that the shells have a maximum command lenght, so... I'm trying now to make the shell use the same command lenght when expanding such commands. I think this is the best way to avoid this problem. Any ideas? Best regards: zethix What is worth doing is worth the trouble of asking somebody to do. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Why not gzip iso images?
- Original Message - From: "Eric D. Futch" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, March 15, 2000 8:58 PM Subject: Re: Why not gzip iso images? I think people are forgetting that you do not necessarily need to download the entire ISO image in order to make a fresh install of FreeBSD. Back when I started using FreeBSD somewhere around version 2.1, I remember donwloading the boot floppies, then installing the whole deal over FTP, all on a 28.8 modem. When you install via FTP you only have to download what you need and nothing more. Sure this is a pain for installing/upgrading a bunch of machines, since you would be downloading the same things over and over again for each machine. Then download the individual parts (eg bin.aa to bin.bf) and then install from a local ftp-server. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
pptpd / ppp trouble
On Wed, 8 Mar 2000, Leif Neland wrote: I'm trying to use MS-VPN using poptop. (pptpd) It works nicely from home to my current at home, where both hosts are on the same network, ,but not where the two hosts are on different networks. Followup: From work to current at home fails too: ppp.log says repeately: Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: ACFCOMP[2] Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: PROTOCOMP[2] Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: ACCMAP[6] 0x Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: MRU[4] 1500 Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: MAGICNUM[6] 0x469c1c68 Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Mar 9 06:25:35 ns ppp[88344]: tun0: LCP: deflink: State change Stopped -- Req-Sent Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: deflink: SendConfigReq(1) state = Req-Sent Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: ACFCOMP[2] Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: PROTOCOMP[2] Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: ACCMAP[6] 0x Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: MRU[4] 1500 Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: MAGICNUM[6] 0x469c1c68 Mar 9 06:25:38 ns ppp[88344]: tun0: LCP: AUTHPROTO[4] 0xc023 (PAP) Mar 9 06:25:41 ns ppp[88344]: tun0: LCP: deflink: SendConfigReq(1) state = Req-Sent The windows machine just says "Verifying username and password". default: set server 5431 qwerty set log Phase Chat Connect LCP IPCP CCP tun command tcp/ip set device /dev/cuaa0 set speed 115200 set redial 5+30-999 2 deny lqr set openmode active 2 pptp: enable chap enable proxy set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
A can ping C, but not B
I got 4 machines at home on an Ethernet coax. A-B-C-D. B is FreeBSD server (samba), the rest is win98 (C is split win/fbsd). C and D talks fine to B. A talks nicely to C (haven't tried to D), but very poorly to B. I got ping losses of 1 out of 3 to 4 from A to B, but no loss A to C. I then took the T-plug from A and put it on a hub, and UTP from hub to A. Still 100% from A to C, but now no ping at all from A to B! What's going on? Standing waves? I got proper terminators either end. The cable is assembled of well 10 shorter pieces with "empty" T-plugs, could that be a problem? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Spontaneous reboot
On Sat, 5 Feb 2000, Wes Peters wrote: Next time, just become root and ping -f that Win98 machine. Running lots of pings isn't going to get you what you're trying for, even if you don't crash your FreeBSD machine. Another great program for offing Windows boxes is spray. A spray on a windows-box just hangs; no network activity is seen. A spray on a FreeBSD-box: spray: RPC: Program not registered. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Serial boot prompt messages and a modem
On Sun, 26 Dec 1999, Daniel C. Sobral wrote: Leif Neland wrote: Just configure it correctly. Don't tell it to talk to a serial device that will be sending it gibberish. A hack would be to have the loader emit ATE0 to protect itself from echoing modems. AFAIK, it would not protect against all modems. I think Winmodems, for instance, won't recognize that command. A: AFAIK, winmodems are not connected to a serial port, they are internal boards. B: Real men don't use anything marked win* for Real Computing. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Sv: Strange SCSI sickness
If it already hasn't been done, we should capture the procedure that Jordan posted, added to by Matt and maybe post it to the troubleshooting part of the guide(s). Unlike some of us who've been fooling with computers since pre-1985, this standard operating procedure may not be second nature. Perhaps the order of checking could be weighted(sp?) against the price of equipment, eg feeling the temperature of the drive before replacing a $0.50 termpwr fuse before replacing $xx cable or a $xxx diskdrive... Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
making users modem dial from webpage
I've been asked if this is possible: Having a webserver running a database of some sort. User clicks a button on a form, a cgi-script runs, determines the ip of the user, and sends a command to "something" on the users pc, which then sends commands to a modem, making it dial a number. So our salespeople can dial directly from the database. This "something", could this be a java-applet, or should it be an active-x? Or something completely different? I probably could install Back Orifice, and send commands to that :-) Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Sv: mrtg, user-ppp
- Original Message - From: Brian F. Feldman [EMAIL PROTECTED] To: Leif Neland [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, October 10, 1999 3:49 PM Subject: Re: mrtg, user-ppp On Sun, 10 Oct 1999, Leif Neland wrote: I'd like to plot uptime and number of calls from ppp to mrtg. Any 'easy' way to ask ppp for these values, getting the answer for number of seconds online since last asked? Store the time from the previous call after each call, as with a (non-thread-safe) "static" variable in C. You can accomplish reading the time up pretty reasonably using either pppctl or just working directly with the ppp socket in the program. I can't seem to find an accumulated off-hook time. pppctl only lists the off-hook time of the last call. So 3 calls of one minute will only be shown as one minute when queryed by mrtg. Looking into the code, no such accumulated timer exists. I either have to write a "proxy" querying ppp every 30 secs (faster than idle timeout), accumulating the values for mrtg to query every 5 minutes, or modify ppp itself. Perhaps a "pppctl show mrtg", giving output directly in the format mrtg likes... Leif Leif -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
mrtg, user-ppp
I'd like to plot uptime and number of calls from ppp to mrtg. Any 'easy' way to ask ppp for these values, getting the answer for number of seconds online since last asked? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
mrtg,FreeBSD, asus p2b temperature
Does anybody have any tips for using the above combination for graphing temperatures? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Sv: panic() the system from the console (was: Re: kern/13721: There is no way to force system panic from console)
That was exactly the suggestion the original poster made in his PR. He also believed that assiging the PANIC function to a key is no worse than having the DDB function key. I think that's a valid statement. Sure, you can return from ddb, whereas you can't from panic, but any abuse would be more likely to be accidental. I'd hope we could think of a *very* difficult key combination to press accidentally. I'd expect at least all of ctrl-alt-shift and some unusual character such as F13. This is sufficently difficult to hit accidentially. My keyboard doesn't have a F13 :-) Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
USB cameras
A simple question: Are USB cameras supported? Is anybody working on it? Oh, btw, how long can USB be extended? Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Please review: rc file changes
On Fri, 27 Aug 1999, Sheldon Hearn wrote:
Hi folks,
What follows is a diff that presents Doug's changes (which must have
required quite a bit of effort, thanks!) in a slightly different format
which I think the grumpies here might prefer.
Specifically, case statements look more like what a lot of folks are
used to seeing, and conditionals that don't need to be case sensitive
have not been converted to case statements.
I think the effort which Doug has put into this is great and would make
for a better rc. It's a pity that a few cosmetic issues generated so
much pooh-pooh'ing. :-(
It seems to me the changes are mostly cosmetic anyway, so naturally people
complain about the cosmetics.
I don't thing the [Yy][Ee][Ss] stuff is really nessecary. This is unix,
and unix is case-sensitive. It should be obvious that the options is
either YES or NO.
Anyway, if it is so, I think readability (if that's important) could be
made by adding two functions: isyes and isno, to be used as
if isyes ${thisvariable}
case $1 of
[Yy][Ee][Ss])
exit 0
;;
*)
exit 1
;;
esac
Leif
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Please review: rc file changes
On Fri, 27 Aug 1999, Sheldon Hearn wrote:
Hi folks,
What follows is a diff that presents Doug's changes (which must have
required quite a bit of effort, thanks!) in a slightly different format
which I think the grumpies here might prefer.
Specifically, case statements look more like what a lot of folks are
used to seeing, and conditionals that don't need to be case sensitive
have not been converted to case statements.
I think the effort which Doug has put into this is great and would make
for a better rc. It's a pity that a few cosmetic issues generated so
much pooh-pooh'ing. :-(
It seems to me the changes are mostly cosmetic anyway, so naturally people
complain about the cosmetics.
I don't thing the [Yy][Ee][Ss] stuff is really nessecary. This is unix,
and unix is case-sensitive. It should be obvious that the options is
either YES or NO.
Anyway, if it is so, I think readability (if that's important) could be
made by adding two functions: isyes and isno, to be used as
if isyes ${thisvariable}
case $1 of
[Yy][Ee][Ss])
exit 0
;;
*)
exit 1
;;
esac
Leif
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Sv: K6/3 on 3.2-STABLE - PROBLEM SOLVED
After rechecking all the jumpers it turns out that the supplier had set the core voltage to 2.2V instead of 2.4V! Interesting that the error was reproducible, if this was the cause of it. The problem never varied from that exact point? I'd like to say that I find that a testament to the precision of modern computer hardware, but I'm still having trouble believing that the incorrect voltage setting caused a specific, always-reproducible problem. Greg Back around 1980, I overclocked my 5MHz z80 to 6MHz. It worked without problems, except that for-next loops in comal didn't exit as expected. That was also reproducible... Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Sv: K6/3 on 3.2-STABLE - PROBLEM SOLVED
After rechecking all the jumpers it turns out that the supplier had set the core voltage to 2.2V instead of 2.4V! Interesting that the error was reproducible, if this was the cause of it. The problem never varied from that exact point? I'd like to say that I find that a testament to the precision of modern computer hardware, but I'm still having trouble believing that the incorrect voltage setting caused a specific, always-reproducible problem. Greg Back around 1980, I overclocked my 5MHz z80 to 6MHz. It worked without problems, except that for-next loops in comal didn't exit as expected. That was also reproducible... Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: vnc on nat-proxy/firewall
The main problem is to get past the firewall. On Mon, 16 Aug 1999, Julian Elischer wrote: vnc is cool, but also check out back-orafice (not sure where you get it but the new one can take over NT as well as W95) On Tue, 17 Aug 1999, Leif Neland wrote: I need to remote-control an NT behind a unix-box running nat-proxy/firewall/gateway. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: vnc on nat-proxy/firewall
On Tue, 17 Aug 1999, Julian Elischer wrote: going in or going out? (draw picture) vnc server ++ +---+ NT | +-+ +-+ ISDN +--+ | ++ | Vnc client |---+--| RAS |-Z| NAT/Firewall |---| +-+ | +-+ +--+ | ++ | +---+ PC | Internet | ++ Private Lan I need to remote-control an NT behind a unix-box running nat-proxy/firewall/gateway. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: vnc on nat-proxy/firewall
The main problem is to get past the firewall. On Mon, 16 Aug 1999, Julian Elischer wrote: vnc is cool, but also check out back-orafice (not sure where you get it but the new one can take over NT as well as W95) On Tue, 17 Aug 1999, Leif Neland wrote: I need to remote-control an NT behind a unix-box running nat-proxy/firewall/gateway. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: vnc on nat-proxy/firewall
On Tue, 17 Aug 1999, Julian Elischer wrote: going in or going out? (draw picture) vnc server ++ +---+ NT | +-+ +-+ ISDN +--+ | ++ | Vnc client |---+--| RAS |-Z| NAT/Firewall |---| +-+ | +-+ +--+ | ++ | +---+ PC | Internet | ++ Private Lan I need to remote-control an NT behind a unix-box running nat-proxy/firewall/gateway. Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
vnc on nat-proxy/firewall
I need to remote-control an NT behind a unix-box running nat-proxy/firewall/gateway. Would it be possible first to connect from the outside to a vnc-server on gateway, then to run vnc-client on the gateway to connect to a vnc-server on the nt? Or is it possible to have a vnc-proxy on the gateway to redirect to the nt? Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: BSD XFS Port BSD VFS Rewrite
[Regarding GPL] If a company sell or lease us a mailserver based on Linux, where we only have smtp and pop3-access to, can we say "Hey, this is GPL'ed, give us the source"? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BSD XFS Port BSD VFS Rewrite
[Regarding GPL] If a company sell or lease us a mailserver based on Linux, where we only have smtp and pop3-access to, can we say Hey, this is GPL'ed, give us the source? Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Solution for mail pseudo-users?
Then again, SQL seems to be the current buzz... Having SQL-based access is cool/manageable (a friend generates the MySQL db from his Radius users file). And we do it the other way: Generate the users file from mysql. I rather prefer it like that; then I can still auth users, if mysql goes down. Also, it saved my a$$ once; mysql lacking commit and rollback. I was disturbed into firing off an update command before having typed the where-clause. I then locked the password of every user, instead of only the users belonging to a single client... Luckily, I dump the database every hour, and rcs it, so I can recreate the database at any hourly version the last few months. Leif As usual, there's more than one way to skin a cat. Yeah.. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Solution for mail pseudo-users?
Then again, SQL seems to be the current buzz... Having SQL-based access is cool/manageable (a friend generates the MySQL db from his Radius users file). And we do it the other way: Generate the users file from mysql. I rather prefer it like that; then I can still auth users, if mysql goes down. Also, it saved my a$$ once; mysql lacking commit and rollback. I was disturbed into firing off an update command before having typed the where-clause. I then locked the password of every user, instead of only the users belonging to a single client... Luckily, I dump the database every hour, and rcs it, so I can recreate the database at any hourly version the last few months. Leif As usual, there's more than one way to skin a cat. Yeah.. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Sv: softupdates on root partition, no floppy
From: Stephen McKay [EMAIL PROTECTED] On Saturday, 17th July 1999, Matthew Dillon wrote: :Is there any way to force softupdate on on a mounted system, or do I have to :either move the / to another machine, or move a floppydrive to this machine? If you boot single-user, root will be mounted read-only and you should be able to 'tunefs -n enable /dev/rda0a' and reboot. I gave up using soft updates on root because of the delayed delete behaviour. I kept filling up root while updating kernels. It doesn't gain you much on little used file systems anyway. So, I recommend people leave root alone. Well, this disk is 4G and has only one partition, containing both / and /usr, so I think I may benefit from softupdates. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
speed of file(1)
While trying to port amavis, the virusscanner for mail, http://aachalon.de/AMaViS/amavis-0.2.0-pre4.tar.gz ) I noticed it used the file(1) several times for each file, and it took rather long time, causing bb to report red for high CPU-load each time I collected a batch of mail. So I compared it with a Linux box: My 60MHz Pentium, FreeBSD time file /usr/home/leif/vnc-3.3.2r /usr/home/leif/vnc-3.3.2r3_unixsrc.tgz: gzip compressed data, deflated, original filename, last modified: Thu Jan 21 19:23:21 1999 real0m1.237s user0m0.758s sys 0m0.394s 133MHz Pentium II, Linux time file vnc-3.3.2r3_unixsrc.tgz vnc-3.3.2r3_unixsrc.tgz: gzip compressed data, deflated, original filename, last modified: Thu Jan 21 19:23:21 1999, os: Unix real0m0.036s user0m0.010s sys 0m0.030s While I realise 60MHz is less than 133MHz, a factor 34 in difference of real time seems suspect. The magic file is different, but almost the same size. Why is FreeBSD's file so much slower? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Sv: speed of file(1)
From: Matthew Dillon [EMAIL PROTECTED] Check the size of the magic files on your FreeBSD and Linux boxen. file was never really designed to be efficient. FreeBSD's magic file is /usr/share/misc/magic - around 164K. -Matt : : :The magic file is different, but almost the same size. : Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Sv: softupdates on root partition, no floppy
From: Stephen McKay sys...@detir.qld.gov.au On Saturday, 17th July 1999, Matthew Dillon wrote: :Is there any way to force softupdate on on a mounted system, or do I have to :either move the / to another machine, or move a floppydrive to this machine? If you boot single-user, root will be mounted read-only and you should be able to 'tunefs -n enable /dev/rda0a' and reboot. I gave up using soft updates on root because of the delayed delete behaviour. I kept filling up root while updating kernels. It doesn't gain you much on little used file systems anyway. So, I recommend people leave root alone. Well, this disk is 4G and has only one partition, containing both / and /usr, so I think I may benefit from softupdates. Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
speed of file(1)
While trying to port amavis, the virusscanner for mail, http://aachalon.de/AMaViS/amavis-0.2.0-pre4.tar.gz ) I noticed it used the file(1) several times for each file, and it took rather long time, causing bb to report red for high CPU-load each time I collected a batch of mail. So I compared it with a Linux box: My 60MHz Pentium, FreeBSD time file /usr/home/leif/vnc-3.3.2r /usr/home/leif/vnc-3.3.2r3_unixsrc.tgz: gzip compressed data, deflated, original filename, last modified: Thu Jan 21 19:23:21 1999 real0m1.237s user0m0.758s sys 0m0.394s 133MHz Pentium II, Linux time file vnc-3.3.2r3_unixsrc.tgz vnc-3.3.2r3_unixsrc.tgz: gzip compressed data, deflated, original filename, last modified: Thu Jan 21 19:23:21 1999, os: Unix real0m0.036s user0m0.010s sys 0m0.030s While I realise 60MHz is less than 133MHz, a factor 34 in difference of real time seems suspect. The magic file is different, but almost the same size. Why is FreeBSD's file so much slower? Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Sv: speed of file(1)
From: Matthew Dillon dil...@apollo.backplane.com Check the size of the magic files on your FreeBSD and Linux boxen. file was never really designed to be efficient. FreeBSD's magic file is /usr/share/misc/magic - around 164K. -Matt : : :The magic file is different, but almost the same size. : Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: poor ethernet performance?
On Sat, 17 Jul 1999, Vincent Poy wrote: Ah, you have a point there. The problem is we have so many wires, we don't know which port goes to what on the Catalyst so we had it on autodetect and FreeBSD does boot up with fxp0 showing 100Mbps Full Duplex. Cisco's can show you which mac-adresses are on which port. Probably Catalyst's can too. Or have somebody pull the cable in and out of the pc, and watch for the light go on and off on the switch :-) Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: poor ethernet performance?
On Sat, 17 Jul 1999, Vincent Poy wrote: Ah, you have a point there. The problem is we have so many wires, we don't know which port goes to what on the Catalyst so we had it on autodetect and FreeBSD does boot up with fxp0 showing 100Mbps Full Duplex. Cisco's can show you which mac-adresses are on which port. Probably Catalyst's can too. Or have somebody pull the cable in and out of the pc, and watch for the light go on and off on the switch :-) Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Sv: poor ethernet performance?
- Original Message - From: Vincent Poy [EMAIL PROTECTED] To: Karl Pielorz [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, July 18, 1999 12:22 AM Subject: Re: poor ethernet performance? There again, any network installer worth their salt will test the cable when in-situ, after the 'dust' has settled... Testing after the dust has settled and while it is in use is different since conditions do change. The testers only tests for continuity, not the impedance or any other electrical properties of the cable. Depends on the tester. Our electrician had a $1500 tester, which gave a printout of several electrical properties of each installed cable; this was included in the documentation of the network, which also included nice cad-drawings of the location of every outlet. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
softupdates on root partition, no floppy
I have a machine with two scsi disks, one with /, one with /usr, and no floppy. I have turned on softupdates on /usr while usr was unmounted, but I can't turn on softupdates on /, because it is always mounted. Normally the answer would be to boot on a floppy, but the machine doesn't have a floppydrive. Is there any way to force softupdate on on a mounted system, or do I have to either move the / to another machine, or move a floppydrive to this machine? Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Sv: poor ethernet performance?
- Original Message - From: Vincent Poy vi...@venus.gaianet.net To: Karl Pielorz kpiel...@tdx.co.uk Cc: sth...@nethelp.no; t...@storm.digital-rain.com; freebsd-hackers@FreeBSD.ORG Sent: Sunday, July 18, 1999 12:22 AM Subject: Re: poor ethernet performance? There again, any network installer worth their salt will test the cable when in-situ, after the 'dust' has settled... Testing after the dust has settled and while it is in use is different since conditions do change. The testers only tests for continuity, not the impedance or any other electrical properties of the cable. Depends on the tester. Our electrician had a $1500 tester, which gave a printout of several electrical properties of each installed cable; this was included in the documentation of the network, which also included nice cad-drawings of the location of every outlet. Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Budget on user-ppp
It could be nice with some sort of budget control in ppp. A few days ago I found out bb caused a dialup every 5 minutes. Today I found I had been online 27 hours uninterrupted. Some dialup-routers allows a setup of max a connects/b minutes online over c hours. Also, I know it is possible to have a longer and longer retry wait between unsuccessful calls, but this is (as far as I can see) not documented anywhere. (Except perhaps archives) Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Sv: cvs commit: src/usr.bin/ftp Makefile fetch.c ftp.1 ftp.c ftp_var.h main.c util.c
- Original Message - From: David O'Brien [EMAIL PROTECTED] To: Dag-Erling Smorgrav [EMAIL PROTECTED]; Ruslan Ermilov [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, July 03, 1999 2:15 AM Subject: Re: cvs commit: src/usr.bin/ftp Makefile fetch.c ftp.1 ftp.c ftp_var.h main.c util.c ... compared to the sources as of today. This gives minimal semantic difference from the way it worked before the change (which was that if FTP_PASSIVE_MODE existed, ftp used passive mode). I have to agree with Eivind, I know of people in my lab that have FTP_PASSIVE_MODE defined to nosense values since that is all that was required before. Now what are these poor souls to do when they upgrade to 3.3-R and their environment stops working If there was someplace nice to put it: ERROR! ^G^G^G^G^GFTP_PASSIVE_MODE must be either "yes" or "no" Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Sv: cvs commit: src/usr.bin/ftp Makefile fetch.c ftp.1 ftp.c ftp_var.h main.c util.c
- Original Message - From: David O'Brien obr...@freebsd.org To: Dag-Erling Smorgrav d...@flood.ping.uio.no; Ruslan Ermilov r...@freebsd.org; hack...@freebsd.org Sent: Saturday, July 03, 1999 2:15 AM Subject: Re: cvs commit: src/usr.bin/ftp Makefile fetch.c ftp.1 ftp.c ftp_var.h main.c util.c ... compared to the sources as of today. This gives minimal semantic difference from the way it worked before the change (which was that if FTP_PASSIVE_MODE existed, ftp used passive mode). I have to agree with Eivind, I know of people in my lab that have FTP_PASSIVE_MODE defined to nosense values since that is all that was required before. Now what are these poor souls to do when they upgrade to 3.3-R and their environment stops working If there was someplace nice to put it: ERROR! ^G^G^G^G^GFTP_PASSIVE_MODE must be either yes or no Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Xfree86 v 3.3.4
Does anyone have any inside information on subj? The website still claims: "We are planning to release 3.3.4 some time in June 1999" I'm longing to get support for my S3 Trio3D. Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Xfree86 v 3.3.4
Does anyone have any inside information on subj? The website still claims: We are planning to release 3.3.4 some time in June 1999 I'm longing to get support for my S3 Trio3D. Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Killing NIC's
I seem to have killed my 2.NIC. Both probe and init as usual, and can read from the net (trafshow) but can't transmit. I removed both from the pc, without removing the netcable. (Trying to resolve an IRQ-conflict) Is this a bad-thing (tm) ? If something went broke from this, I would expect it to be something other than the transmitter. Leif To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
