Re: mouse question....
Gary Kline wrote: > > Hi, Y'all, > > This is a long shot, but here goes. --On my other FBSD system > which is as 4.0, the mouse won't work. A friend just checked > the hardware ports, switched the mouse from COM1 to COM2. (COM2 > or, in the case of my modem, /dev/cuaa1, is working.) Zip; > nothing. He tried the mouse on this system on the other. Again, > nothinng. He thinks that in my upgrading to 4.0, part of my > mouse software may have been hosed. > > Any suggestions how I can diagnose the software side of this? I have always use the configure option of sysinstall to figure my mice out. Kent > > I'm stumped. > > thanks, > > gary > > -- >Gary D. Kline [EMAIL PROTECTED] Public service Unix > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
mouse question....
Hi, Y'all, This is a long shot, but here goes. --On my other FBSD system which is as 4.0, the mouse won't work. A friend just checked the hardware ports, switched the mouse from COM1 to COM2. (COM2 or, in the case of my modem, /dev/cuaa1, is working.) Zip; nothing. He tried the mouse on this system on the other. Again, nothinng. He thinks that in my upgrading to 4.0, part of my mouse software may have been hosed. Any suggestions how I can diagnose the software side of this? I'm stumped. thanks, gary -- Gary D. Kline [EMAIL PROTECTED] Public service Unix To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Humblest apologies
Sorry about that. I sent it to the wrong list. :P To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
No Subject
subscribe Ryan D. Walberg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
ATAPI_STATIC_ID
I tried to build a kernel that had the ATAPI_STATIC_ID option, but config said that the option no longer exists. Huh? I've had this option since 4.0, and saw in both GENERIC and LINT that ATAPI_STATIC_ID does seem to exist. Can someone explain this to me. -- David Kanter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Upcoming rc.conf changes not loading certain currently loaded daemons
In message <[EMAIL PROTECTED]> "Francisco Reyes" writes: : UPDATING and I guess that I didn't have it at that point.. I am I guess it doesn't help that the UPDATING file says to read the whole UPDATING file before proceeding :-) On a more serious note, the UPDATING file is now mentioned in the handbook, but old timers need to learn to use it. warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons)
In message <[EMAIL PROTECTED]> James Housley writes: : blaine wrote: : > Umm, why not just use openbsd if security is the primary concern? : > : Why shouldn't we provide the best level of security possible, using : OpenBSD as a target? We should be targetting things at a much higher level than OpenBSD :-) Otherwise we run the risk of being an "also ran" in the security area. theo and folks over there have done a good job, and we need to do better. We're not there yet, however. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Requesting input for a handbook section entry
In message <[EMAIL PROTECTED]> Chris BeHanna writes: : I thought the pnp command went away in 4.x. Is it back for 4.1? It is gone in 4.x. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons)
In message <[EMAIL PROTECTED]> Vivek Khera writes: : Wow! If voting is considered, I vote for such a patch to be included. : It makes sense considering that ssh is now part of the core system. Actually, it turns out to be a bad idea and we should use, I think, the more generic rcmdsh from OpenBSD plus tweaks to rcmd_af. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons)
In message <[EMAIL PROTECTED]> Nathan Ahlstrom writes:
: This PR may be of interest.
: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=15830
Actually, no. It isn't that interesting. More interesting would be
something like the following which does it for all rcmd based things.
It is out of OpenBSD, and likely needs a couple of tweaks before it
can be committed. Much more generic. :-)
Comments?
Warner
Index: net/Makefile.inc
===
RCS file: /home/imp/FreeBSD/CVS/src/lib/libc/net/Makefile.inc,v
retrieving revision 1.37
diff -u -r1.37 Makefile.inc
--- net/Makefile.inc2000/07/05 02:13:14 1.37
+++ net/Makefile.inc2000/08/25 03:21:51
@@ -16,7 +16,7 @@
inet_pton.c ip6opt.c linkaddr.c map_v4v6.c name6.c ns_addr.c \
ns_name.c ns_netint.c \
ns_ntoa.c ns_parse.c ns_print.c ns_ttl.c nsap_addr.c \
- rcmd.c recv.c res_comp.c res_data.c res_debug.c \
+ rcmd.c rcmdsh.c recv.c res_comp.c res_data.c res_debug.c \
res_init.c res_mkquery.c res_mkupdate.c res_query.c res_send.c \
res_update.c rthdr.c send.c vars.c
# not supported: iso_addr.c
Index: net/rcmd.c
===
RCS file: /home/imp/FreeBSD/CVS/src/lib/libc/net/rcmd.c,v
retrieving revision 1.29
diff -u -r1.29 rcmd.c
--- net/rcmd.c 2000/08/10 17:10:57 1.29
+++ net/rcmd.c 2000/08/25 03:21:54
@@ -47,6 +47,7 @@
#include
#include
#include
+#include
#include
#include
#include
@@ -99,9 +100,27 @@
long oldmask;
pid_t pid;
int s, aport, lport, timo, error;
- char c;
+ char c, *p;
char num[8];
static char canonnamebuf[MAXDNAME]; /* is it proper here? */
+
+ /* call rcmdsh() with specified remote shell if appropriate. */
+ if (!issetugid() && (p = getenv("RSH"))) {
+ struct servent *sp = getservbyname("shell", "tcp");
+
+ if (sp && sp->s_port == rport)
+ return (rcmdsh(ahost, rport, locuser, remuser,
+ cmd, p));
+ }
+
+ /* use rsh(1) if non-root and remote port is shell. */
+ if (geteuid()) {
+ struct servent *sp = getservbyname("shell", "tcp");
+
+ if (sp && sp->s_port == rport)
+ return (rcmdsh(ahost, rport, locuser, remuser,
+ cmd, NULL));
+ }
pid = getpid();
Index: net/rcmdsh.3
===
RCS file: rcmdsh.3
diff -N rcmdsh.3
--- /dev/null Thu Aug 24 20:04:33 2000
+++ rcmdsh.3Thu Aug 24 20:21:54 2000
@@ -0,0 +1,103 @@
+.\"$OpenBSD: rcmdsh.3,v 1.6 1999/07/05 04:41:00 aaron Exp $
+.\"
+.\" Copyright (c) 1983, 1991, 1993
+.\"The Regents of the University of California. All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"notice, this list of conditions and the following disclaimer in the
+.\"documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"must display the following acknowledgement:
+.\"This product includes software developed by the University of
+.\"California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"may be used to endorse or promote products derived from this software
+.\"without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.Dd September 1, 1996
+.Dt RCMDSH 3
+.Os
+.Sh NAME
+.Nm rcmdsh
+.Nd return a stream to a remote command without superuser
+.Sh SYNOPSIS
+.Fd #include
+.Ft int
+.Fn rcmdsh "char **ahost" "int inport" "const char *locuser" "const char *remuser"
+"const char *cmd" "char *rshprog"
+.Sh DESCRIPTION
+The
+.Fn rcmdsh
Re: Upcoming rc.conf changes not loading certain currently loaded daemons
On Thu, 24 Aug 2000 15:07:15 +0200, Neil Blakey-Milner wrote: >(and when I'm through with it, sendmail won't be listening on port 25 by >default either *evil.grin*) So where will it be listening? Any plans on moving this part of stable on the long term? francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Upcoming rc.conf changes not loading certain currently loaded daemons
On Thu, 24 Aug 2000 15:41:45 +0100, Nik Clayton wrote: >> I know this is currently in "current", but won't this eventually >> make it to stable? > >Maybe. I would have thought that's unlikely though. However, even if >it is, there'll be a HEADS UP posted to this mailing list, so you'll be >aware that it's an issue. Not all things make it to "HEADS UP" messages. I recall a few months back I found something which there had not been such message and the email I got was ... yes, but it is on the UPDATING document. It is a matter of experience to know to check UPDATING and I guess that I didn't have it at that point.. I am also sure many others new to tracking stable may not know of such file. Perpahs we could have a monthly "Staying stable file". Any opposition for such file? francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: nuking "unsafe" protocols (was Re: Upcoming rc.conf changes not loading certain currently loaded daemons)
In message <[EMAIL PROTECTED]> Vivek Khera writes: : s> Surely rmt could work over ssh? : : Apparently not with its current implementation. It also must fallback : to using rcmd(3) for compatibility with other systems, if one were to : implement the ssh layer. OpenBSD's dump has this functionality. Actually, it is in the rcmd library call. Looks like it would be relatively easy to bring into FreeBSD. Any takers? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Kernel won't compile (device xl)
On Thu, Aug 24, 2000 at 07:55:21PM -0400, Bill Fumerola wrote: > On Thu, Aug 24, 2000 at 06:05:42PM -0500, David J. Kanter wrote: > > I've added support for a new Ethernet card, with device miibus and device > > xl. But when the kernel is compiling I get this error: [snip] > put 'device ether' back in your kernel? ---end quoted text--- This was the problem. I was confused because I added the xl device since I'm getting DSL over PPPoE, but since it's not a "real" Ethernet I wasn't sure if I needed it...after all, I will be using the tunneling device. My goof. Thanks. -- David Kanter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Upcoming rc.conf changes not loading certain currently loaded daemons
On 24-Aug-2000, Francisco Reyes wrote: > On Thu, 24 Aug 2000 10:11:03 +0200 (SAST), fingers wrote: > >but the first thing I do is disable them and kill 'em dead. > > Perhaps this could be an installation flag. Personally, I think the change is a wonderful move. I frankly find it to be a bit of an embarassment to see FreeBSD installing out of the box with such protocols as telnet and rexec running by default. Ideally, I'd like to see the installer properly force the determination of USA_RESIDENT and install the appropriate rsaref / librsaintl libraries so a fresh install could sshd_enable="YES" in /etc/defaults/rc.conf If someone insists on using those antiquated and unsafe protocols like telnet and the r* services, we should at least make sure they're doing it on purpose and not just leaving the defaults in place out of ignorance. -- |David McNett |To ensure privacy and data integrity this message has| |[EMAIL PROTECTED]|been encrypted using dual rounds of ROT-13 encryption| |Birmingham, AL USA|Please encrypt all important correspondence with PGP!| To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
cyrus imapd problems resolved..
I'm crossposting this to freebsd-stable since the people responsible for this kind of thing usually are listening there... Thanks to a little elbow grease and a thanks to retch, I have managed to get cyrus running on my 3.5-Stable box. For those that didn't see my post -questions, in short, I tried to get cyrus up and running today but the sasl port was/is broken (/usr/ports/security/cyrus-sasl) which is required for authenticating users. It looks like the only problem with that is an incorrect MD5 hash. In my headsmashing though, I uncovered some things to update both that port, and /usr/ports/mail/cyrus as well to the latest version.. here are my notes.. hopefully they fall into the hands of whoever is responsible. Notes for /usr/ports/mail/cyrus : ./Makefile change version string to 1.6.24 (latest version).. always a good thing, and as it is now fetch will try about five different servers until it finds the old version. ./files/MD5 : Replace contents of file with : MD5 (cyrus-imapd-1.6.24.tar.gz) = 490a246e787581e0bbc558788ff5f562 --after fetch-- ./work/cyrus-imapd-1.6.24/sieve/comparator.h: Add "#include " before -- it's not included in the distribution for some reason, and breaks on compile on this file without it. Notes for /usr/ports/security/cyrus-sasl ./files/MD5 : Replace contents of file with : MD5 (cyrus-sasl-1.5.24.tar.gz) = ac3837c071c258b80021325936db2583 Notes general. After installation of the port, the user needs to run /usr/local/sbin/saslpasswd to create an entry in the sasl password database. The user they create (just to get things going here) should also have their name listed as an "admin" in imapd.conf. The first run of saslpasswd will create /usr/local/etc/sasldb.db which must be owned by cyrus:cyrus for auth to function.. so either saslpasswd must be run after suing to cyrus, the file must be chowned after being run by another user (which is what I did). I only mention this because the Cyrus documentation REALLY SUCKS and it was only after hours of scouring usenet that I came across this tidbit posted in an OpenBSD newsgroup where someone else was having similar problems. --prologue-- cyrus finally seems to be working for me.. at least it let's me auth and mess around with cyradm which it wouldn't even do before. On the down side, I still get this weird error whenever I use imtest to check things out, although I think it may only be because I have not created any mailboxes yet. The error is... S: C01 OK Unknown error: -1904809442 .. then after I have entered the password, then done '. logout'... * BYE Unknown error: -1904809443 . OK Unknown error: -1904809442 I'll be checking that part out soon.. but hey, this is progress... hope this helps some people. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Numbering of fxp devices
On Wed, 23 Aug 2000, Chris Dillon & others wrote:
>
> > I also wonder if there woudl be a way to map cards based on their
> > MAC addresses, or is the MAC address discovery done way too late?
>
> Way too late, I think, since the driver would have to attach before it
> could even query the card for its MAC address. If it were able to get
> the MAC, detach, re-attach, etc. until the right order was reached,
> that might work.
>
> > Hmm.. maybe some sort of aliasing? A conf file could list device
> > numbers and MAC addresses, so once the kernel finished finding
> > everything, it could look through the cards and asign /dev/ether0
> > to one, /dev/ether1 to another, ect.
>
> Thats an idea, too...
I think you're making this way harder than it needs to be. I use the
following in /etc/rc.conf:
ether=$(ifconfig ed1 |grep ether |cut -c 8-24)
echo Ethernet address is ${ether}
case ${ether} in
00:e0:29:32:67:7c)
hostname="rig1.vnltest"
ifconfig_ed1="inet 10.5.0.101 netmask 0xff00"
;;
00:e0:29:32:67:7f)
hostname="rig2.vnltest"
ifconfig_ed1="inet 10.5.0.102 netmask 0xff00"
;;
00:e0:29:32:6f:0d)
hostname="rig3.vnltest"
ifconfig_ed1="inet 10.5.0.103 netmask 0xff00"
;;
*)
echo "Unexpected ethernet address $ether - assuming rig4"
hostname="rig4.vnltest"
ifconfig_ed1="inet 10.5.0.104 netmask 0xff00"
;;
esac
This particular example is for a single interface - I use it on a bootable
CD, so that I can just duplicate a single CD image for a bunch of
machines, and have each of them come up with their individual
configuration. For the multiple interface situation you've been talking
about, a similar trivial piece of shellscript would let you assign
ifconfig_xxx variables according to the MAC address.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Problem changing ownership of a link
On Thu, Aug 24, 2000 at 07:22:10AM -0500, Stephen Montgomery-Smith wrote: > If xxx is a soft link, I am finding that the chown > command has no effect in changing ownership of xxx: > > if xxx is owned by bob, then > chown fred xxx > seems to have no effect at all. % chown -h user symlink This should have been asked on -questions. -- Jon Parise ([EMAIL PROTECTED]) . Rochester Inst. of Technology http://www.csh.rit.edu/~jon/ : Computer Science House Member To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Problem changing ownership of a link
If xxx is a soft link, I am finding that the chown command has no effect in changing ownership of xxx: if xxx is owned by bob, then chown fred xxx seems to have no effect at all. Is this how it should be? I'm finding this a bit frustrating. -- Stephen Montgomery-Smith [EMAIL PROTECTED] http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Upcoming rc.conf changes not loading certain currently loaded daemons
On Thu, 24 Aug 2000 10:13:52 +0100, Nik Clayton wrote: >> What was the reason for these daemons been set to not start? > >Now, if you have an empty /etc/rc.conf then (in theory) no network services >are running. This also means that if you want to find out what services are >started at boot time you only have to look in /etc/rc.conf, rather than >having to look at /etc/defaults/rc.conf as well. Then shouldn't we add the current programs which get started to /etc/rc.conf? >> Wouldn't this "break" working machines? > >Only if you (1) Are running -current, and (2) don't read the mailing lists >and the diffs mergemaster shows you. > >If both (1) and (2) are true then you shouldn't be running -current anyway. I know this is currently in "current", but won't this eventually make it to stable? francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Upcoming rc.conf changes not loading certain currently loaded daemons
On Thu, 24 Aug 2000 10:11:03 +0200 (SAST), fingers wrote: >Hi > >> What was the reason for these daemons been set to not start? >> Wouldn't this "break" working machines? > >I don't know what percentage of installers are doing the same, That is the problem. Most likely nobody knows the percentage of people that use them vs the percentage that turns them off. >but the first thing I do is disable them and kill 'em dead. Perhaps this could be an installation flag. francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: help with restoring sh
Boot from a fix-it floppy and copy it there from the floppy... (and make sure the permissions are correct)... Scot On Thu, 24 Aug 2000, Theo PAGTZIS wrote: > Hi all, > >I have been upgrading from 3.4 to 4.1 and during the reboot I get a > permission denied when it tries to exec the /bin/sh. I am trying to > restore the file with one that is functioning properly..however I do not > know how I should go about correcting my problem. I would appreciate any > help as I am stranded with a server that is down at the moment... > > > Thanks > > Theo > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Upcoming rc.conf changes not loading certain currently loaded daemons
On Thu, Aug 24, 2000 at 01:03:50AM -0400, Francisco Reyes wrote: > On a recent email Peter Jeremy wrote: > > >..., rc.conf was recently changed (in -current) to not > >start inetd, portmap or sendmail. If you are actually relying on > >any of these daemons, and you actually notice the differences in > >/etc/defaults/rc.conf, you will be able to update /etc/rc.conf > >without a period of head-scratching when they don't start. > > What was the reason for these daemons been set to not start? Now, if you have an empty /etc/rc.conf then (in theory) no network services are running. This also means that if you want to find out what services are started at boot time you only have to look in /etc/rc.conf, rather than having to look at /etc/defaults/rc.conf as well. > Wouldn't this "break" working machines? Only if you (1) Are running -current, and (2) don't read the mailing lists and the diffs mergemaster shows you. If both (1) and (2) are true then you shouldn't be running -current anyway. N -- Internet connection, $19.95 a month. Computer, $799.95. Modem, $149.95. Telephone line, $24.95 a month. Software, free. USENET transmission, hundreds if not thousands of dollars. Thinking before posting, priceless. Somethings in life you can't buy. For everything else, there's MasterCard. -- Graham Reed, in the Scary Devil Monastery To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
filename too long???
Hi, I have the following fstab file # DeviceMountpoint FStype Options Dump Pass# /dev/wd0s1b noneswapsw 0 0 /dev/wd0s1a / ufs rw 1 1 /dev/wd0s1f /usrufs rw 2 2 /dev/wd0s1e /varufs rw 2 2 /dev/wcd0c /mnt/cdrom cd9660 ro,noauto 0 0 /dev/fd0/mnt/floppy msdos rw,noauto 0 0 proc/proc procfs rw 0 0 # you want to get the essential ports in one place to do one build and multi installs - faster starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/essential_port_pool /usr/pool nfs rw 0 0 starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/master_distfiles_ports /usr/ports/distfiles nfs rw0 0 # this needs a soft link on the mounted folder, on the root dir starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/essential_config/elikonas /backupETC nfs rw 0 0 When I try to mount these stores I get : nfs: starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/essential_port_pool: File name too long nfs: starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/master_distfiles_ports: File name too long nfs: starship:/cs/research/mice/freebsd2/starship/Machines/freebsd/essential_config/elikonas: File name too long This was not the case with Fbsd 3.4 Why is this happening? Is it because of the device name change because the machine boots fine without asking for an ad0 device set Theo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
help with restoring sh
Hi all, I have been upgrading from 3.4 to 4.1 and during the reboot I get a permission denied when it tries to exec the /bin/sh. I am trying to restore the file with one that is functioning properly..however I do not know how I should go about correcting my problem. I would appreciate any help as I am stranded with a server that is down at the moment... Thanks Theo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: WTF
On Wed, 23 Aug 2000, Chris Byrnes wrote: > I'm running 3.5-STABLE. > > Recently, my server has started rebooting, at random times, usually > actually quite religiously about every 2 days. > > I thought it might be a RAM problem. Replaced with brand new RAM. > Same problem. > > Any ideas, at all? Pease. I've had the same problem on a 4.X-STABLE machine for some time. In my case, it rebooted regularly and failed to compile larger stuff, such as kernels or make worlds, quite often. It stayed, even though I replaced the RAM. In my case, it was due to a faulty cache module (it's a board that still uses old COAST modules). It's running cacheless now, but it's running. Time to go looking for COAST modules, though :-) Philipp To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Upcoming rc.conf changes not loading certain currently loaded daemons
Hi > What was the reason for these daemons been set to not start? > Wouldn't this "break" working machines? I don't know what percentage of installers are doing the same, but the first thing I do is disable them and kill 'em dead. --Rob To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADSUP: 4.1S installworld broken
> [EMAIL PROTECTED] wrote: > > > > STRICTTMPPATH does not contain cp/ > > > > ===> gnu/usr.bin/binutils/doc > > cp -p /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/binutils/instal > l.sh > > install > > cp:No such file or directory > > *** Error code 1 > > Grrr, it worked here during my test build and install. :( You should just > be able to add 'cp' to the list of files to copy in the 'installworld' > target in src/Makefile.inc1. I'll try it again to see if I can reproduce > the breakage. That should fix it. My full build environment is in pr=20815. I worked around the problem but felt a HEADSUP was warranted. Mark > > -- > > John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ -- Mark Andrews, Nominum Inc. 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Update magic file
> The "file" command is unable to properly identify EPS binary files. The > following patch, taken from the magic file included in the Slackware Linux > distribution, fixes the problem. Picking up the latest version of "file" from ftp://ftp.astron.com/pub/file/file-3.32.tar.gz (or a later version, if one comes out after my message arrives) will also fix the problem, and probably add other improvements as well. When last I picked up stuff from the FreeBSD "file" to merge into "file" as maintained by Christos Zoulas at Astron (he's now maintaining the "Ian Darwin" implementation of "file" that the BSDs and Linux distributions have picked up), it was a bit of a pain as, if I remember correctly, some files in the "Magdir" subdirectory of the source directory for "file" had different names in FreeBSD and in Christos' version. If anybody updates "file" in FreeBSD, they might want to try to minimize the differences between the file names, etc. (and send back to Christos any patches from FreeBSD). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
