Re: no openssh after build
On Wed, 08 Mar 2000 09:56:56 PST, Doug Barton wrote: mm only knows about what's in /usr/src/etc/Makefile. ssh_config and sshd_config are in there, so if you run mm and you have those bits in your tree it'll install them. Looks like mergemaster is much cleverer than I thought. Being called Mr Barton certainly _is_ a compliment! :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
$B%0%l!<%H%8%c!<%K!<(BNEWS$B!J(B03091004$B!K(B
$B(B $B!!%0%l!<%H%8%c!<%K!<(BNEWS $BFMA3$N%a!<%kAw?.$9$k;v$r$*5v$7$/$@$5$$!#(B $B9%I>$KIU$-!!Bh#2CF!*!*?7=U%-%c%s%Z!<%s$G$9!#(B $B!A%@%$%P!
Re: bridging broken in -current AND -stable
On Thu, Mar 09, 2000 at 07:26:52AM +0100, Luigi Rizzo wrote: let me doubt it. i have had a fair amount of trouble with these nics, maybe it's driver's fault, but still... anyways, the driver is not as easy to work on as others. For future investments: which nics do you recommend? (stable driver, speed...) fxp? at 10Mbit the ed does a reasonable job considering todays machines. will try and have a look at the de driver some time in the future. ok. Which nics are capable for bridging now in -current? ed, fxp, ...? To prevent the page faults in the upcomping release the bridging support should be disabled in if_de. Maybe the manpage should note the real supported nics. Boris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 RC3 install problem from ftp.FreeBSD.org
Good point, I forgot the link. Fixed! - Jordan Says, it can't chdir into the 4.0-2307-CURRENT directory. It does work from current.FreeBSD.org. Looking on ftp.freebsd.org I do not see a link under /pub/FreeBSD/releases/i386/ ? that maybe the missing link ? -- Regards, Ulf. - Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More ld-elf.so.1: assert failed messages
The other possibility would be to fix the wine port so it calls dllockinit() to set up locking. I don't know for sure how hard that would be, but it's probably a feasible solution. To be honest, I'd be the most comfortable with this solution but also trust John's skills with the linker (certainly far more than I trust mine :) to say that whatever he's comfortable with, I'm comfortable with. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bridging broken in -current AND -stable
let me doubt it. i have had a fair amount of trouble with these nics, maybe it's driver's fault, but still... anyways, the driver is not as easy to work on as others. For future investments: which nics do you recommend? (stable driver, speed...) fxp? probably, yes, though the whole bunch of drivers contributed by Bill Paul look interesting as well (i have no idea on how good is the hardware, e.g. the rl 8139 is not such a good card). Which nics are capable for bridging now in -current? ed, fxp, ...? and 'rl' i think. To prevent the page faults in the upcomping release the bridging support should be disabled in if_de. Maybe the manpage should note the real supported nics. wish i had more time. cheers luigi Boris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current lockups
On 2000-Mar-09 10:05:21 +1100, Peter Dufault [EMAIL PROTECTED] wrote: There's no difference between rtprio and P1003.1B scheduling other than the name. rtprio is the same as P1003.1B "SCHED_RR". I wasn't aware of that. I'd like to remove the rtprio call from ntpd. I think we ought to do it now before 4.0 ships. Given there is a known a priority inversion bug related to realtime (or idle) scheduling, it would seem wise not to use it in any system utilities. The relevant patch would appear to be (untested): --- /usr/src/usr.sbin/ntp/config.hTue Feb 1 13:56:05 2000 +++ /tmp/config.h Thu Mar 9 11:46:11 2000 You have to do something in the "./configure" stuff. Hopefully someone in the know can suggest the "--with-no-foobar" option needed on the command line so I don't have to wade into it. Autoconfiguring POSIX realtime is a bad, bad idea because: 1. You don't know if it is available in all environments; 2. You don't know who is allowed to use it; 3. You don't know what the heck it does. It decidedly does not mean "run as fast as you can". Peter -- Peter Dufault ([EMAIL PROTECTED]) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: building ports
well, on the advice of someone, i manually edited these files changing the date in them to 2201, before changing it it was 19990308. i dunno if its significant, but i rebuilt using make buildworld, make installworld. and i did run mergemaster afterwards. what date is supposed to be in this file btw? Jeremy You just did make world and still got this error? That's not supposed to happen. What do ls -l /var/db/port.mkversion cat /var/db/port.mkversion say? Satoshi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XDM login using sessreg and last, uptime, w and so on...
In [EMAIL PROTECTED] "Sean O'Connell" [EMAIL PROTECTED] wrote: On FreeBSD it was successful and there seems no problem. Sean One out of two is not bad :) I think so too. :-) Sean Could your path be set in such a way that it is exec'ing 3.X Sean versions of fileutils or finger or something like that in Sean /usr/local/bin rather than updated ones in /usr hierarchy. No. These tools are all in /usr/bin. Sean Did you run mergemaster on /etc and/or update all the various Sean rc files? Yes. I have just run mergemaster and reboot the system. Sean The /usr/X11R6/bin/X symlink really points to an updated Sean XF86_ like you didn't switch for using XF86_S3 to XF86_SVGA Sean (only built this) but the symlink for X is still pointing to Sean XF86_S3. I'm using X-TT server on both FreeBSD and FreeBSD(98). This morning, I recompiled X-TT of FreeBSD(98) and there still is 'w: /dev/:0: No such file or directory'. X is properly linked to XF98_MGA.xtt. Sean Curious... love a good mystery. Yes, this is a mystery but not so serious... Ok, I'll ask about this problem to FreeBSD(98)'s mailing list. It may be pc98's problem... Thank you all very much for your help. -- NAKAJI Hiroyuki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RC3-ISO doesn´t recognize Thinkpad 600E CD-ROM Drive
Hi, when booting off the RC3 ISO, I the the error: Can´t work out which disk we are booting from. Guessed BIOS device 0x8b not found by probes, defaulting to disk0: The ISO only found my floppy as disk0 and my FAT partition as disk1. Not the CD-ROM drive it booted off. It works just fine when booting off the floppies. But if the RC3-ISO CD is in the Cd-ROM while booting off the disks I still get the above error, although everything works fine, because I boot off the floppies. It´s like the bootloader cannot recognize the CD-ROM drive, but the GENERIC can. I have a IBM Thinkpad 600E, with the DVD drive. /\/\orten $eeberg, Systems Consultant @ Merkantildata - Enterprise Solutions #echo 'System Administrators suck :)' /dev/console To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: building ports
On Mon, Mar 08, 1999 at 09:44:26PM -0600, Ishmael wrote: : Your system is too old to use this bsd.port.mk. According to the mail headers, your system clock is about one year behind actual time. That might have screwed up the `make'... Best regards, -- Edwin H. Kremer, senior systems- and network administrator. [EMAIL PROTECTED] Dept. of Computer Science, Utrecht University, The Netherlands [WHOIS: ehk3] http://www.cs.uu.nl/people/edwin/ --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Please review: fdisk -e - -I
OK!
You have my OK to change the option, but you'll need Jordans
OK to commit it.
Poul-Henning
In message [EMAIL PROTECTED], Warner Losh writes:
Given that OpenBSD had the -e flag to fdisk first, and that it means
edit there and that disklabel -e means edit, I'd like to apply the
following patch to -current before it becomes 4.0. If we wait, we'll
have compatibility problems. Right now it is too easy to shoot
yourself in the foot with this.
When this was hashed out here, the idea was met with wide spread
support, even fiven the advanced nature of the freeze. I take that
support to mean that this is something that would be a good idea to do
for 4.0.
Comments?
Warner
Index: fdisk.8
===
RCS file: /home/imp/FreeBSD/CVS/src/sbin/i386/fdisk/fdisk.8,v
retrieving revision 1.16
diff -u -r1.16 fdisk.8
--- fdisk.8 1999/08/28 00:13:01 1.16
+++ fdisk.8 2000/03/02 20:29:12
@@ -8,7 +8,7 @@
.Nd PC partition table maintenance program
.Sh SYNOPSIS
.Nm fdisk
-.Op Fl Baeitu
+.Op Fl BIaitu
.Op Fl b Ar bootcode
.Op Fl 1234
.Op Ar disk
@@ -62,7 +62,7 @@
if
.Fl f
is given.
-.It Fl e
+.It Fl I
Initialize the contents of sector 0 with one FreeBSD slice covering the ent
ire disk.
.It Fl f Ar configfile
Set partition values using the file
Index: fdisk.c
===
RCS file: /home/imp/FreeBSD/CVS/src/sbin/i386/fdisk/fdisk.c,v
retrieving revision 1.34
diff -u -r1.34 fdisk.c
--- fdisk.c 2000/02/11 11:25:23 1.34
+++ fdisk.c 2000/03/02 20:31:56
@@ -120,7 +120,7 @@
static int B_flag = 0; /* replace boot code */
static int a_flag = 0; /* set active partition */
static char *b_flag = NULL; /* path to boot code */
-static int e_flag = 0; /* use entire disk for FreeBSD */
+static int I_flag = 0; /* use entire disk for FreeBSD */
static int i_flag = 0; /* replace partition data */
static int u_flag = 0; /* update partition data */
static int t_flag = 0; /* test only, if f_flag is given */
@@ -216,7 +216,7 @@
{
int c, i;
-while ((c = getopt(argc, argv, "Bab:ef:ituv1234")) != -1)
+while ((c = getopt(argc, argv, "BIab:f:ituv1234")) != -1)
switch (c) {
case 'B':
B_flag = 1;
@@ -227,8 +227,8 @@
case 'b':
b_flag = optarg;
break;
-case 'e':
-e_flag = 1;
+case 'I':
+I_flag = 1;
break;
case 'f':
f_flag = optarg;
@@ -292,7 +292,7 @@
printf("*** Working on device %s ***\n",disk);
-if (e_flag)
+if (I_flag)
{
struct dos_partition *partp;
@@ -648,7 +648,7 @@
if ( !(st.st_mode S_IFCHR) )
warnx("device %s is not character special", disk);
if ((fd = open(disk,
-a_flag || e_flag || B_flag || u_flag ? O_RDWR : O_RDONLY)) == -1) {
+a_flag || I_flag || B_flag || u_flag ? O_RDWR : O_RDONLY)) == -1) {
if(errno == ENXIO)
return -2;
warnx("can't open device %s", disk);
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: poptop+ppp, ok in current, not stable
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, but not to my stable at work. 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". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More ld-elf.so.1: assert failed messages
In article [EMAIL PROTECTED], Jordan K. Hubbard [EMAIL PROTECTED] wrote: The other possibility would be to fix the wine port so it calls dllockinit() to set up locking. I don't know for sure how hard that would be, but it's probably a feasible solution. To be honest, I'd be the most comfortable with this solution Me too, for 4.0. Given Donn's reports of trouble with my patches, I think the timing is just wrong to try and do anything major with the dynamic linker between now and Monday. It's too hard to test it. All the troublesome ports are _huge_ (Mozilla, Wine, ...), and the failures are timing-dependent and not so easy to reproduce. Obviously I'll strive to fix the remaining problems after 4.0 has been tagged. As far as I know, Wine is the only port that has problems with the version of the dynamic linker that's in -current at present. I've looked into adding the dllockinit() stuff to Wine, but could use some help from somebody who knows its internals better. I found the threads primitives, etc., but am not so sure where to place the dllockinit() call. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kdm display manager working anywhere with current?
On Thu, 9 Mar 2000, F. Heinrichmeyer wrote: I found no way to get kdm to work, it dumps core in a qt string find routine. wdm works kind of (the window manager menu is buggy but repairable). three day cvsup - kdm works fine. konqueror - that is the problem. :( To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FBSD4.0-RC3 install
Hi: I did an install of 4.0-RC3 last night and found the following: 1:Unable to transfer the local distribution from ftp://current.freebsd.org/pub/FreeBSD/Snapshots/i386 2:Unable to transfer the X9set distribution from ftp://current.freebsd.org/pub/FreeBSD/Snapshots/i386 3:The Ports collection took about 85 MB, not about 70 MB 4:The first option for configuring X in full screen graphic mode, which requires VGA16, did not work. So I picked option #3, which seemed like the next best option because it too mentioned a full-screen configuration. (I skipped over option #2: the shell-based configuration because the description said that that was more difficult -- the description doesn't mention the pros or cons of option #3.) Bad move. The next screen I saw was the next setup item (Ports). I thought that I had lost the opportunity to setup X but later I returned to the "Main Menu" where I could choose to setup X. 5:Something similar happened when I came to the account setup screen. Option #1 was to "Exit this menu (back to previous) but instead of going *back*, it seemed to go forward, bringing me to the screen to set password for root. 6:After Install was complete and a reboot, X would not start, when I tried 'startx', I got: /usr/libexec/ld-elf.so.1: shared object "libXThrStub.so.6" not found 7:I couldn't find PostgreSQL as a port (under 'database') during the install. It's definitely *there* in the installed Ports collection, though. Are other ports missing (it didn't seem like there were 3100+). Are the number of ports for the install purposely limited? QUESTIONS 1-Is #1 just a localization which is unnecessary for USA? 2-Are #2,#4, and #6 related? Was X9set missing in the distro? 3-Is it possible to include more documentation during install or online? I think there are several possible 'gotcha's' that may be avoided. For examples see above, but also: I had used FIPS to create a new partition before the install but had not deleted it. In the Install program, the type of this partition was "6" and the description was "FAT." The install program allowed me to change the type to ??? (the FreeBSD type) and the description now said "FreeBSD." But I hesitated to continue because the description explictly said that "unused" was to be changed to "FreeBSD." I exited the install, went back to Win95, fired up DOSCMD and used fdisk to delete the partition. Would the install have worked if I hadn't deleted the partition? or would it have damaged something? 4-How can I get 'startx' to work now? John __ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FBSD4.0-RC3 install
Hi: I did an install of 4.0-RC3 last night and found the following: 1:Unable to transfer the local distribution from ftp://current.freebsd.org/pub/FreeBSD/Snapshots/i386 Because it's not there. I listed the URLs I listed *very specifically* and that is the ONLY location you can get this from. Just ignore current.freebsd.org for the purposes of these release candidates please. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: FBSD 4.0-RC3 install
Hi: I should have added that I installed Gnome and Afterstep and later (before end of install), I also got IceWM from Ports. Is X confused about which WM to use? John __ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FBSD4.0-RC3 install
Hi: I got the install floppies from the ftp directory that you listed. When the install came to a point where it asked for the ftp site to get the distribution, it listed a "primary" site (ftp.freebsd.org, I believe) and several other mirror sites, one of which was the current snapshot site. The message on this screen said that only the primary site was guaranteed to have all releases, so I tried that. The install program returned immediately saying that it couldn't find the files. So I tried the snapshot site, and it worked. I believe that I may have even seen a March 8th date at somepoint also. In any case, I completely understand that special proceedures would be warranted for Release Candidates, resulting in a mismatch with the message on the "pick an ftp transfer site" screen -- and an erroneous assumption on my part that the snapshot site was the next best thing. My only desire right now is to get this right. So, I am now wondering: 1- What did I miss in not getting the "local distribution?" (I searched freebsd.org to no avail) and what else might I have missed? 2- Is there any easy and/or correct way to recover (/stand/sysinstall?, CVSup?), or should I just reinstall? John From: "Jordan K. Hubbard" [EMAIL PROTECTED] To: "John Daniels" [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: Re: FBSD4.0-RC3 install Date: Thu, 09 Mar 2000 09:01:37 -0800 Hi: I did an install of 4.0-RC3 last night and found the following: 1:Unable to transfer the local distribution from ftp://current.freebsd.org/pub/FreeBSD/Snapshots/i386 Because it's not there. I listed the URLs I listed *very specifically* and that is the ONLY location you can get this from. Just ignore current.freebsd.org for the purposes of these release candidates please. - Jordan __ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata, DMA and the install floppies
It seems John Hay wrote: Hi, I have been trying to install yesterday's 4.0 snap on a no-name brand motherboard with the VIA chipset, but I'm running in some problems. I suspect there is a problem with the DMA. The error I'm getting when the disk is newfs'ed is a repeating: ad0: WRITE command timeout - resetting ata0: resetting devices .. done ad0: WRITE command timeout - resetting ata0: resetting devices .. done ... It seems that it is just going on and on. Shouldn't it back down to non DMA mode after a while? Is there a way to disable the DMA on the install floppies? It should back down after 3 retries... But is is 3 retries pr request, so say it gets through on the 2 retry each time this will continue.. I dont know if there is access to the sysctl knobs from the emergency shell, but that would be a solution... Part of the probe looks like this: (written down by hand) atapci0: VIA 82C586 ATA33 controller port 0xe000 - 0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ... ad0: 6204MB ST36531A [13446/15/63] at ata0-master using UDMA33 Hmm, wierd, did this hardware run FreeBSD before ?? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata, DMA and the install floppies
| ad0: WRITE command timeout - resetting | ata0: resetting devices .. done | ad0: WRITE command timeout - resetting | ata0: resetting devices .. done | ... | | It seems that it is just going on and on. Shouldn't it back down to non | DMA mode after a while? Is there a way to disable the DMA on the install | floppies? How many times did it retry? It looks like everything is in place to default to PIO mode in this case, but you have allow it to try 3 times before it fallbacks to PIO. From ata-disk.c log: revision 1.59 date: 2000/03/05 16:52:23; author: sos; state: Exp; lines: +24 -24 [...] Update the timeout code to try fallback to PIO if problems arise in DMA mode. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata, DMA and the install floppies
On Thu, 9 Mar 2000, Samuel Tardieu wrote: This looks exactly like the problem I was having with my Compaq laptop, which could run 3.4 boot disks just fine but not 4.0 kernels. I was probably too lazy to wait until it reaches the 3 attempts, so I will try again :) What model laptop may I ask? I'm running 4.0-current since 1/11/2000 (last world rebuild 3/8/2000) on a Compaq Armada 7400 without incident. Kelly -- Kelly Yancey - [EMAIL PROTECTED] - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSDhttp://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FBSD4.0-RC3 install
I got the install floppies from the ftp directory that you listed. When the install came to a point where it asked for the ftp site to get the distribution, it listed a "primary" site (ftp.freebsd.org, I believe) and This should work now - it just needed some symlinks to be created. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata, DMA and the install floppies
I have been trying to install yesterday's 4.0 snap on a no-name brand motherboard with the VIA chipset, but I'm running in some problems. I suspect there is a problem with the DMA. The error I'm getting when the disk is newfs'ed is a repeating: ad0: WRITE command timeout - resetting ata0: resetting devices .. done ad0: WRITE command timeout - resetting ata0: resetting devices .. done ... It seems that it is just going on and on. Shouldn't it back down to non DMA mode after a while? Is there a way to disable the DMA on the install floppies? It should back down after 3 retries... But is is 3 retries pr request, so say it gets through on the 2 retry each time this will continue.. I dont know if there is access to the sysctl knobs from the emergency shell, but that would be a solution... Well it is been doing fsck for more than an hour now. :-) This is before the emergency shell is opened, but if I remember correctly, sysctl is not part of tools available. Part of the probe looks like this: (written down by hand) atapci0: VIA 82C586 ATA33 controller port 0xe000 - 0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ... ad0: 6204MB ST36531A [13446/15/63] at ata0-master using UDMA33 Hmm, wierd, did this hardware run FreeBSD before ?? A similar system did run FreeBSD-3.4, but I never enabled DMA on it. I'll try to install 3.4 on this one and see. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata, DMA and the install floppies
| What model laptop may I ask? I'm running 4.0-current since 1/11/2000 | (last world rebuild 3/8/2000) on a Compaq Armada 7400 without incident. Armada V300. I sent the full details here a few days ago. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildworld failure in cvs ...
Is anyone else seeing this. cvsupped from 12:00 noon EST ... cc -O -pipe -I/usr/src/gnu/usr.bin/cvs/cvs -I/usr/src/gnu/usr.bin/cvs/cvs/../lib -DHAVE_CONFIG_H -I/usr/src/gnu/usr.bin/cvs/cvs/../../../.. /contrib/cvs/src -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/lib -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/diff -DHA VE_KERBEROS -DHAVE_KRB_GET_ERR_TEXT -DENCRYPTION -I/usr/obj/usr/src/i386/usr/include -o cvs add.o admin.o buffer.o checkin.o checkout.o c lassify.o client.o commit.o create_adm.o cvsrc.o diff.o edit.o entries.o error.o expand_path.o fileattr.o filesubr.o find_names.o hardlink.o hash.o history.o ignore.o import.o lock.o log.o login.o logmsg.o main.o mkmodules.o modules.o myndbm.o no_diff.o parseinfo.o patch.o prepen d_args.o rcs.o rcscmds.o recurse.o release.o remove.o repos.o root.o rtag.o run.o scramble.o server.o status.o subr.o tag.o update.o vers_ts .o version.o watch.o wrapper.o zlib.o /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../lib/libcvs.a /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../libdiff/ libdiff.a -lgnuregex -lmd -lcrypt -lz -lkrb -lcrypto -lcom_err /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomUpdate' /usr/lib/libRSAglue.so.1: undefined reference to `R_GetRandomBytesNeeded' /usr/lib/libRSAglue.so.1: undefined reference to `RSAPrivateDecrypt' /usr/lib/libRSAglue.so.1: undefined reference to `RSAPublicEncrypt' /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomFinal' /usr/lib/libRSAglue.so.1: undefined reference to `RSAPrivateEncrypt' /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomInit' /usr/lib/libRSAglue.so.1: undefined reference to `RSAPublicDecrypt' *** Error code 1 Stop in /usr/src/gnu/usr.bin/cvs/cvs. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cvs. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. #;^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
I'm having the same problem. To overstate the obvious, it's related to compiling with MAKE_KERBEROS4=yes which require the des code in libcrypto. Anyone know how libRSAglue is getting pulled in? -Ben Greenwald Is anyone else seeing this. cvsupped from 12:00 noon EST ... cc -O -pipe -I/usr/src/gnu/usr.bin/cvs/cvs -I/usr/src/gnu/usr.bin/cvs/cvs/../ lib -DHAVE_CONFIG_H -I/usr/src/gnu/usr.bin/cvs/cvs/../../../.. /contrib/cvs/src -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/lib - I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/diff -DHA VE_KERBEROS -DHAVE_KRB_GET_ERR_TEXT -DENCRYPTION -I/usr/obj/usr/src/i386/us r/include -o cvs add.o admin.o buffer.o checkin.o checkout.o c lassify.o client.o commit.o create_adm.o cvsrc.o diff.o edit.o entries.o erro r.o expand_path.o fileattr.o filesubr.o find_names.o hardlink.o hash.o history.o ignore.o import.o lock.o log.o login.o logmsg.o main.o mkmo dules.o modules.o myndbm.o no_diff.o parseinfo.o patch.o prepen d_args.o rcs.o rcscmds.o recurse.o release.o remove.o repos.o root.o rtag.o run.o scramble.o server.o status.o subr.o tag.o update.o vers_ts .o version.o watch.o wrapper.o zlib.o /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/ ../lib/libcvs.a /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../libdiff/ libdiff.a -lgnuregex -lmd -lcrypt -lz -lkrb -lcrypto -lcom_err /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomUpdate' /usr/lib/libRSAglue.so.1: undefined reference to `R_GetRandomBytesNeeded' /usr/lib/libRSAglue.so.1: undefined reference to `RSAPrivateDecrypt' /usr/lib/libRSAglue.so.1: undefined reference to `RSAPublicEncrypt' /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomFinal' /usr/lib/libRSAglue.so.1: undefined reference to `RSAPrivateEncrypt' /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomInit' /usr/lib/libRSAglue.so.1: undefined reference to `RSAPublicDecrypt' *** Error code 1 Stop in /usr/src/gnu/usr.bin/cvs/cvs. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cvs. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. #;^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
On Thu, 9 Mar 2000, Bush Doctor wrote: Is anyone else seeing this. cvsupped from 12:00 noon EST ... cc -O -pipe -I/usr/src/gnu/usr.bin/cvs/cvs -I/usr/src/gnu/usr.bin/cvs/cvs/../lib -DHAVE_CONFIG_H -I/usr/src/gnu/usr.bin/cvs/cvs/../../../.. /contrib/cvs/src -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/lib -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/diff -DHA VE_KERBEROS -DHAVE_KRB_GET_ERR_TEXT -DENCRYPTION -I/usr/obj/usr/src/i386/usr/include -o cvs add.o admin.o buffer.o checkin.o checkout.o c lassify.o client.o commit.o create_adm.o cvsrc.o diff.o edit.o entries.o error.o expand_path.o fileattr.o filesubr.o find_names.o hardlink.o hash.o history.o ignore.o import.o lock.o log.o login.o logmsg.o main.o mkmodules.o modules.o myndbm.o no_diff.o parseinfo.o patch.o prepen d_args.o rcs.o rcscmds.o recurse.o release.o remove.o repos.o root.o rtag.o run.o scramble.o server.o status.o subr.o tag.o update.o vers_ts .o version.o watch.o wrapper.o zlib.o /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../lib/libcvs.a /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../libdiff/ libdiff.a -lgnuregex -lmd -lcrypt -lz -lkrb -lcrypto -lcom_err /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomUpdate' Did this come up as part of make world? It looks like you have a stale library. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
On Thu, 9 Mar 2000, Benjamin Greenwald wrote: I'm having the same problem. To overstate the obvious, it's related to compiling with MAKE_KERBEROS4=yes which require the des code in libcrypto. Anyone know how libRSAglue is getting pulled in? It shouldn't be..libRSAglue is an empty stub thesedays containing no symbols. Unless I've missed something nothing should even be looking for it, especially during make world, and especially not outside of the obj tree. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FBSD4.0-20000307 install floppies and VAIO PCG-Z505HS
Ran into an odd problem tring to install the 3/7 release of 4.0 onto my VAIO PCG-Z505HS. The install hung while probing for plug and play devices. I had the BIOS set to non plug and play OS. So just for grins I turned plug and play OS on in the bios and tried again. Installed without a hitch. Of course I had to then go back into the BIOS and turn off plug and play OS to get by USB devices working after the install. (-: Any thoughts? Larry -- Larry Baird| HTTP://www.gnatbox.com Global Technology Associates, Inc. | Orlando, FL Email: [EMAIL PROTECTED] | TEL 407-380-0220, FAX 407-380-6080 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
It was during a buildworld. I'm going to do a make world with MAKE_KERBEROS4=NO, and then do a buildworld after the reboot and see if it was somehow pulling the library from outside of /obj. -Ben On Thu, 9 Mar 2000, Benjamin Greenwald wrote: I'm having the same problem. To overstate the obvious, it's related to compiling with MAKE_KERBEROS4=yes which require the des code in libcrypto. Anyone know how libRSAglue is getting pulled in? It shouldn't be..libRSAglue is an empty stub thesedays containing no symbols. Unless I've missed something nothing should even be looking for it, especially during make world, and especially not outside of the obj tree. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
samba 2.0.6 crashing -stable
Hi, I've been having a recurring problem with samba on my freebsd machines. It began when I was running 3.2, and it appears to still be around with -stable. (and samba 2.0.3, and now 2.0.6) Basically, when copying large files, the FreeBSD file server appears to lose all of its network connectivity. It cannot be pinged, etc. You also cannot log in as root because it hangs after you type in `root' on console. (which might be concistent with all networking failing. I think, but have not verified this, that anything that does not use NIS or some such thing will continue to work. Has anyone heard of such problems? Any ideas? Thanks. Soren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sorry. Mistyped
I was thinking about -current something and wrote current. Please disregard my message. Soren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RC3 install floppies: panic: resource_list_alloc: resource entry is busy
Hi folks, I just tried to boot the RC3 install floppies on my Pentium 66 testbox. It gets through the config stage without trouble, but then panics immediately with: ... pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 atapci0: RZ 100? ATA controller !WARNING! buggy chip data loss possible port 0 x3f4-0x3f7,0x1f0-0x1f7 at device 1.0 on pci0 atapci0: Busmastering DMA not supported panic: resource_list_alloc: resource entry is busy I am also having this problem with 4.0-CURRENT kernels since February 18, both with my own custom kernel config and GENERIC. I have to revert to the ata driver of February 17 or earlier to get the system booting again, and then it runs perfectly. This machine has an Intel motherboard with a Mercury chipset, 64 Mbyte RAM, Matrox Millenium II, two Western Digital disks, and it ran all previous FreeBSD releases perfectly for almost five years. Anybody else having this problem ? And before I start digging, any idea where to look for a solution, if it makes sense at all ? Kind regards, Hans To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FBSD4.0-20000307 install floppies and VAIO PCG-Z505HS
In message [EMAIL PROTECTED] Larry Baird writes: : then go back into the BIOS and turn off plug and play OS to get : by USB devices working after the install. (-: : : Any thoughts? You should have turned off PNP OS in the BIOS to start with. That's the only setting that is supported. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
Out of da blue Kris Kennaway aka ([EMAIL PROTECTED]) said: On Thu, 9 Mar 2000, Bush Doctor wrote: Is anyone else seeing this. cvsupped from 12:00 noon EST ... cc -O -pipe -I/usr/src/gnu/usr.bin/cvs/cvs -I/usr/src/gnu/usr.bin/cvs/cvs/../lib -DHAVE_CONFIG_H -I/usr/src/gnu/usr.bin/cvs/cvs/../../../.. /contrib/cvs/src -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/lib -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/diff -DHA VE_KERBEROS -DHAVE_KRB_GET_ERR_TEXT -DENCRYPTION -I/usr/obj/usr/src/i386/usr/include -o cvs add.o admin.o buffer.o checkin.o checkout.o c lassify.o client.o commit.o create_adm.o cvsrc.o diff.o edit.o entries.o error.o expand_path.o fileattr.o filesubr.o find_names.o hardlink.o hash.o history.o ignore.o import.o lock.o log.o login.o logmsg.o main.o mkmodules.o modules.o myndbm.o no_diff.o parseinfo.o patch.o prepen d_args.o rcs.o rcscmds.o recurse.o release.o remove.o repos.o root.o rtag.o run.o scramble.o server.o status.o subr.o tag.o update.o vers_ts .o version.o watch.o wrapper.o zlib.o /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../lib/libcvs.a /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../libdiff/ libdiff.a -lgnuregex -lmd -lcrypt -lz -lkrb -lcrypto -lcom_err /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomUpdate' Did this come up as part of make world? It looks like you have a stale library. It's occurring during a buildworld. If you're referring to libRSAglue being stale it looks like that may be it. bantu.cl.msu.edu:dervish ls -l /usr/lib/libR* -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglue.so - libRSAglue.so.1 -r--r--r-- 1 root wheel5872 Jan 29 07:29 /usr/lib/libRSAglue.so.1 -r--r--r-- 1 root wheel 868 Feb 28 22:28 /usr/lib/libRSAglue_p.a Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] #;^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
I am not seeing the problem with a standard build, but I am not building Kerberos. Looking at the makefiles, there is no mentioned of libRSAglue anyplace. The link command doesn't even imply the use of libRSAglue. Also, a buildworld should not be using libraries outside of the build environment. Don't bother building with MAKE_KERBEROS4=NO. All of the tests look at the variable being defined and not its value. You might try removing your object directory and doing a make cleandir twice to make sure nothing is left in source tree that shouldn't be there. Jim Bloom [EMAIL PROTECTED] Bush Doctor wrote: Out of da blue Kris Kennaway aka ([EMAIL PROTECTED]) said: On Thu, 9 Mar 2000, Bush Doctor wrote: Is anyone else seeing this. cvsupped from 12:00 noon EST ... cc -O -pipe -I/usr/src/gnu/usr.bin/cvs/cvs -I/usr/src/gnu/usr.bin/cvs/cvs/../lib -DHAVE_CONFIG_H -I/usr/src/gnu/usr.bin/cvs/cvs/../../../.. /contrib/cvs/src -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/lib -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/diff -DHA VE_KERBEROS -DHAVE_KRB_GET_ERR_TEXT -DENCRYPTION -I/usr/obj/usr/src/i386/usr/include -o cvs add.o admin.o buffer.o checkin.o checkout.o c lassify.o client.o commit.o create_adm.o cvsrc.o diff.o edit.o entries.o error.o expand_path.o fileattr.o filesubr.o find_names.o hardlink.o hash.o history.o ignore.o import.o lock.o log.o login.o logmsg.o main.o mkmodules.o modules.o myndbm.o no_diff.o parseinfo.o patch.o prepen d_args.o rcs.o rcscmds.o recurse.o release.o remove.o repos.o root.o rtag.o run.o scramble.o server.o status.o subr.o tag.o update.o vers_ts .o version.o watch.o wrapper.o zlib.o /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../lib/libcvs.a /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../libdiff/ libdiff.a -lgnuregex -lmd -lcrypt -lz -lkrb -lcrypto -lcom_err /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomUpdate' Did this come up as part of make world? It looks like you have a stale library. It's occurring during a buildworld. If you're referring to libRSAglue being stale it looks like that may be it. bantu.cl.msu.edu:dervish ls -l /usr/lib/libR* -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglue.so - libRSAglue.so.1 -r--r--r-- 1 root wheel5872 Jan 29 07:29 /usr/lib/libRSAglue.so.1 -r--r--r-- 1 root wheel 868 Feb 28 22:28 /usr/lib/libRSAglue_p.a To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FBSD4.0-RC3 install
From: "Jordan K. Hubbard" [EMAIL PROTECTED] This should work now - it just needed some symlinks to be created. The link to the packages directory is wrong. It is pointing one to many directories back. packages - ../../../../ports/i386/packages-4-current it should be: packages - ../../../ports/i386/packages-4-current I also noticed one very small error on the screen for setting up the mouse. It says to choose option 4 to disable the mouse, it should be option 5. Scot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mount_cd9660+atapi-cd panic
ok, this was partly caused by dodgy hardware it seems, so don't worry too much, but it would be nice if a panic could be avoided. first, dmesg: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #12: Sun Mar 5 23:40:38 GMT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/PLATINUM Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 400909968 Hz CPU: AMD-K6(tm) 3D processor (400.91-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 67043328 (65472K bytes) avail memory = 62517248 (61052K bytes) Preloaded elf kernel "kernel" at 0xc0273000. npx0: math processor on motherboard npx0: INT 16 interface pcib0: AcerLabs M1541 (Aladdin-V) PCI host bridge on motherboard pci0: PCI bus on pcib0 pcib1: AcerLabs M5243 PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: ATI Mach64-GB graphics accelerator at 0.0 irq 11 isab0: AcerLabs M1533 portable PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 rl0: RealTek 8139 10/100BaseTX port 0xe000-0xe0ff mem 0xe8001000-0xe80010ff irq 10 at device 10.0 on pci0 rl0: Ethernet address: 00:e0:7d:74:66:7c miibus0: MII bus on rl0 rlphy0: RealTek internal media interface on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: supplying EUI64: 00:e0:7d:ff:fe:74:66:7c atapci0: AcerLabs Aladdin ATA33 controller port 0xf000-0xf00f irq 0 at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 ad0: 8063MB QUANTUM FIREBALLlct08 08 [16383/16/63] at ata0-master using UDMA33 acd0: MODE_SENSE_BIG command timeout - resetting ata1: resetting devices .. done acd0: MODE_SENSE_BIG DONEDRQ acd0: MODE_SENSE_BIG - ABORTED COMMAND asc=4e ascq=00 error=00 acd0: MODE_SENSE_BIG command timeout - resetting ata1: resetting devices .. done acd0: MODE_SENSE_BIG DONEDRQ acd0: MODE_SENSE_BIG - ABORTED COMMAND asc=4e ascq=00 error=00 acd0: MODE_SENSE_BIG command timeout - resetting ata1: resetting devices .. done acd0: MODE_SENSE_BIG DONEDRQ acd0: MODE_SENSE_BIG - ABORTED COMMAND asc=4e ascq=00 error=00 acd0: MODE_SENSE_BIG command timeout - resetting ata1: resetting devices .. done acd0: MODE_SENSE_BIG DONEDRQ acd0: MODE_SENSE_BIG - ABORTED COMMAND asc=4e ascq=00 error=00 ata1-master: MATSHITA CR-581/1.00 CDROM device - NO DRIVER! Mounting root from ufs:/dev/ad0s4a rl0: starting DAD for fe80:0001::02e0:7dff:fe74:667c IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging disabled rl0: DAD complete for fe80:0001::02e0:7dff:fe74:667c - no duplicates found rl0: starting DAD for fec0:56c0:60a7:1045:02e0:7dff:fe74:667c rl0: DAD complete for fec0:56c0:60a7:1045:02e0:7dff:fe74:667c - no duplicates found Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x8:0xc01bc0ad stack pointer = 0x10:0xc6047d30 frame pointer = 0x10:0xc6047d3c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 49742 (mount_cd9660) interrupt mask = none trap number = 12 panic: page fault syncing disks... 12 done Uptime: 2m50s dumping to dev #ad/0x50001, offset 278656 dump ata0: resetting devices .. done 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 dunno what's wrong with that drive, it worked fine after rebooting. As you can see, the panic occured when trying to mount the CD-ROM. Here's the backtrace: GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 2641920 initial pcb at 21c8a0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x8:0xc01bc0ad stack pointer = 0x10:0xc6047d30 frame
SMP on Alpha?
Hello! Will the -current version of FreeBSD run on a multi-CPU axp machine and use all of the CPUs? Would that be a reliable box (assuming the admin sometimes knows what he is doing)? Do I want to make a "production" server out of an axp box at all in the near future? Thanks! -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
I meant I was going to comment out MAKE_KERBEROS4, but thanks for the tip. Speaking of which, this is precisely what I did. I commented out MAKE_KERBEROS4, did a make world, uncommented MAKE_KERBEROS4, made the world again, and the second time everything was fine. There's probably a faster way to do this but I can attest that the above works. -Ben I am not seeing the problem with a standard build, but I am not building Kerberos. Looking at the makefiles, there is no mentioned of libRSAglue anyplace. The link command doesn't even imply the use of libRSAglue. Also, a buildworld should not be using libraries outside of the build environment. Don't bother building with MAKE_KERBEROS4=NO. All of the tests look at the variable being defined and not its value. You might try removing your object directory and doing a make cleandir twice to make sure nothing is left in source tree that shouldn't be there. Jim Bloom [EMAIL PROTECTED] Bush Doctor wrote: Out of da blue Kris Kennaway aka ([EMAIL PROTECTED]) said: On Thu, 9 Mar 2000, Bush Doctor wrote: Is anyone else seeing this. cvsupped from 12:00 noon EST ... cc -O -pipe -I/usr/src/gnu/usr.bin/cvs/cvs -I/usr/src/gnu/usr.bin/cvs/c vs/../lib -DHAVE_CONFIG_H -I/usr/src/gnu/usr.bin/cvs/cvs/../../../.. /contrib/cvs/src -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs /lib -I/usr/src/gnu/usr.bin/cvs/cvs/../../../../contrib/cvs/diff -DHA VE_KERBEROS -DHAVE_KRB_GET_ERR_TEXT -DENCRYPTION -I/usr/obj/usr/src/i 386/usr/include -o cvs add.o admin.o buffer.o checkin.o checkout.o c lassify.o client.o commit.o create_adm.o cvsrc.o diff.o edit.o entries. o error.o expand_path.o fileattr.o filesubr.o find_names.o hardlink.o hash.o history.o ignore.o import.o lock.o log.o login.o logmsg.o main. o mkmodules.o modules.o myndbm.o no_diff.o parseinfo.o patch.o prepen d_args.o rcs.o rcscmds.o recurse.o release.o remove.o repos.o root.o r tag.o run.o scramble.o server.o status.o subr.o tag.o update.o vers_ts .o version.o watch.o wrapper.o zlib.o /usr/obj/usr/src/gnu/usr.bin/cv s/cvs/../lib/libcvs.a /usr/obj/usr/src/gnu/usr.bin/cvs/cvs/../libdiff/ libdiff.a -lgnuregex -lmd -lcrypt -lz -lkrb -lcrypto -lcom_err /usr/lib/libRSAglue.so.1: undefined reference to `R_RandomUpdate' Did this come up as part of make world? It looks like you have a stale library. It's occurring during a buildworld. If you're referring to libRSAglue being stale it looks like that may be it. bantu.cl.msu.edu:dervish ls -l /usr/lib/libR* -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue. a lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglue. so - libRSAglue.so.1 -r--r--r-- 1 root wheel5872 Jan 29 07:29 /usr/lib/libRSAglue. so.1 -r--r--r-- 1 root wheel 868 Feb 28 22:28 /usr/lib/libRSAglue_ p.a To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
On Thu, 9 Mar 2000, Jim Bloom wrote: the variable being defined and not its value. You might try removing your object directory and doing a make cleandir twice to make sure nothing is left in source tree that shouldn't be there. Yes, thats a likely candidate. Can you try blowing away /usr/obj and see if the problem persist? Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FBSD4.0-20000307 install floppies and VAIO PCG-Z505HS
On Thu, 9 Mar 2000, Warner Losh wrote: In message [EMAIL PROTECTED] Larry Baird writes: : then go back into the BIOS and turn off plug and play OS to get : by USB devices working after the install. (-: : : Any thoughts? You should have turned off PNP OS in the BIOS to start with. That's the only setting that is supported. Yes, but he said this caused the system to panic at boot. Thats why he turned it off :) Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP on Alpha?
On 2000-Mar-10 12:06:18 +1100, Mikhail Teterin [EMAIL PROTECTED] wrote: Will the -current version of FreeBSD run on a multi-CPU axp machine and use all of the CPUs? Not yet, but Real Soon Now. Would that be a reliable box (assuming the admin sometimes knows what he is doing)? -current comes with all the usual `not for production use' caveats, and (without any slur on Doug Rabson, who's doing the work), you'd be very game taking FreeBSD's first cut at Alpha/SMP and putting it into production. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
I did try blowing away /obj. Didn't help. -Ben On Thu, 9 Mar 2000, Jim Bloom wrote: the variable being defined and not its value. You might try removing your object directory and doing a make cleandir twice to make sure nothing is left in source tree that shouldn't be there. Yes, thats a likely candidate. Can you try blowing away /usr/obj and see if the problem persist? Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
On Thu, 9 Mar 2000, Benjamin Greenwald wrote: I did try blowing away /obj. Didn't help. Hmm. I'll try running a buildworld at home tonight with stale libRSAglue libs in /usr/lib and see if I can reproduce this. I don't think it's anything in the source tree which is causing the breakage directly - although if it's picking up things outside /usr/obj during the course of the buildworld that needs to be fixed. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More ld-elf.so.1: assert failed messages
In article [EMAIL PROTECTED] you write: In article [EMAIL PROTECTED], Jordan K. Hubbard [EMAIL PROTECTED] wrote: The other possibility would be to fix the wine port so it calls dllockinit() to set up locking. I don't know for sure how hard that would be, but it's probably a feasible solution. To be honest, I'd be the most comfortable with this solution ... As far as I know, Wine is the only port that has problems with the version of the dynamic linker that's in -current at present. I've looked into adding the dllockinit() stuff to Wine, but could use some help from somebody who knows its internals better. Hm you could ask over in comp.emulators.ms-windows.wine... I found the threads primitives, etc., but am not so sure where to place the dllockinit() call. When does it need to be called, just when starting a new thread? (i have looked at the wine source before but never at ld-elf.so...) And would this be the same on -stable and 4.0? Currently you should be able to build a wine on a -stable box and it would still run on 4.0 (well it wouldn't run _worse_ than on -stable), at least thats the idea. Anyway if it should be called before a new thread becomes runnable for the first the i think it could go in THREAD_Create (in scheduler/thread.c), if it needs to be called from within the new thread itself it looks like it should go in THREAD_Start in the same source. HTH, -- Juergen Lock [EMAIL PROTECTED] (remove dot foo from address to reply) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
The pw command
Non-root users can use the pw command to get information from the master.passwd file e.g. ps showuser paul paul:*:1000:1000::0:0: Richards:/home/paul:/usr/local/bin/bash which shows the class, password expiry and account expiry. I'm not sure whether that's information that should be kept secure but it does seem like 'pw' is the only command that makes it available. The 'chsh' command doesn't show this information except when run as root for instance. Paul. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: More ld-elf.so.1: assert failed messages
NOTE: Take everything I say here as general info. I haven't used these thread packages, but have used others in the past. It should be called somewhere between the starting of the process and the creation of the second thread. There is no problem if there is only one thread. THREAD Create would be fine as long as it sets a variable accessible to all threads indicating dllockinit has been called. Another possible location would be a routine that initialize the multithreading for the process. This routine may not exist in all thread packages though. Jim Bloom [EMAIL PROTECTED] Juergen Lock wrote: In article [EMAIL PROTECTED] you write: In article [EMAIL PROTECTED], Jordan K. Hubbard [EMAIL PROTECTED] wrote: The other possibility would be to fix the wine port so it calls dllockinit() to set up locking. I don't know for sure how hard that would be, but it's probably a feasible solution. To be honest, I'd be the most comfortable with this solution ... As far as I know, Wine is the only port that has problems with the version of the dynamic linker that's in -current at present. I've looked into adding the dllockinit() stuff to Wine, but could use some help from somebody who knows its internals better. Hm you could ask over in comp.emulators.ms-windows.wine... I found the threads primitives, etc., but am not so sure where to place the dllockinit() call. When does it need to be called, just when starting a new thread? (i have looked at the wine source before but never at ld-elf.so...) And would this be the same on -stable and 4.0? Currently you should be able to build a wine on a -stable box and it would still run on 4.0 (well it wouldn't run _worse_ than on -stable), at least thats the idea. Anyway if it should be called before a new thread becomes runnable for the first the i think it could go in THREAD_Create (in scheduler/thread.c), if it needs to be called from within the new thread itself it looks like it should go in THREAD_Start in the same source. HTH, -- Juergen Lock [EMAIL PROTECTED] (remove dot foo from address to reply) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: building ports
On Thu, 09 Mar 2000, in a never-ending search for enlightenment, Edwin Kremer wrote: On Mon, Mar 08, 1999 at 09:44:26PM -0600, Ishmael wrote: : Your system is too old to use this bsd.port.mk. According to the mail headers, your system clock is about one year behind actual time. That might have screwed up the `make'... Best regards, -- Edwin H. Kremer, senior systems- and network administrator. [EMAIL PROTECTED] Dept. of Computer Science, Utrecht University, The Netherlands [WHOIS: ehk3] http://www.cs.uu.nl/people/edwin/ --- Ya think? -- Walter Brameld Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming, or what? Walter:Where the hell am I? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree86 4.0 in FreeBSD 4.0?
Hi, Just wondering if there are plans in the works to get Xfree86 4.0 into FreeBSD 4.0. I just noticed that X 4.0 has finally been released. -- Regards, Devin. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
Out of da blue Kris Kennaway aka ([EMAIL PROTECTED]) said: On Thu, 9 Mar 2000, Benjamin Greenwald wrote: I did try blowing away /obj. Didn't help. Hmm. I'll try running a buildworld at home tonight with stale libRSAglue libs in /usr/lib and see if I can reproduce this. I don't think it's anything in the source tree which is causing the breakage directly - although if it's picking up things outside /usr/obj during the course of the buildworld that needs to be fixed. Not that it directly relates to the problem, I wound up doing the following to get 'make buildworld' to work: 1. rm -rf ../obj/* make clean make cleandepend make cleandir make clean make update 2. cd secure;make obj;make depend make all install 3. rm -rf ../obj/* make clean make cleandepend make cleandir make cleandir make clean Again my libRSAglue libraries before the above were: bantu.cl.msu.edu:dervish ls -l /usr/lib/libR* -r--r--r-- 1 root wheel 810 Feb 28 22:28 /usr/lib/libRSAglue.a lrwxr-xr-x 1 root wheel 15 Jan 29 07:29 /usr/lib/libRSAglue.so - libRSAglue.so.1 -r--r--r-- 1 root wheel5872 Jan 29 07:29 /usr/lib/libRSAglue.so.1 -r--r--r-- 1 root wheel 868 Feb 28 22:28 /usr/lib/libRSAglue_p.a and after: bantu.cl.msu.edu:dervish ls -l /usr/lib/libR* -r--r--r-- 1 root wheel 810 Mar 9 18:02 /usr/lib/libRSAglue.a lrwxr-xr-x 1 root wheel 15 Mar 9 18:02 /usr/lib/libRSAglue.so - libRSAglue.so.1 -r--r--r-- 1 root wheel1616 Mar 9 18:02 /usr/lib/libRSAglue.so.1 -r--r--r-- 1 root wheel 868 Mar 9 18:02 /usr/lib/libRSAglue_p.a Unfortunately I blew away the old libraries, but would like to know what happens with your test ... Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] #;^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata, DMA and the install floppies
Hello, I was getting the same error, I have two HD's on a Addladin TXpro Chipset and two CD-ROM drives. I get ad1: READ command timeout -resetting ata0: resetting devices .. done ata0-slave: WARNING: WAIT_READY active=ATA_ACTIVE_ATA BUT I have no ATA hard drives. Another thing I noticed with the install, is when it is probing for devices, it was trying to find PC_card0: but I had disable PC Card support in the kernel config (the install conflict screen for the install floppies) Anyways, other then that, things are going ok with my 4.0 RC3 install. Cheers Shaun On Thu, 9 Mar 2000, John Hay wrote: Hi, I have been trying to install yesterday's 4.0 snap on a no-name brand motherboard with the VIA chipset, but I'm running in some problems. I suspect there is a problem with the DMA. The error I'm getting when the disk is newfs'ed is a repeating: ad0: WRITE command timeout - resetting ata0: resetting devices .. done ad0: WRITE command timeout - resetting ata0: resetting devices .. done ... It seems that it is just going on and on. Shouldn't it back down to non DMA mode after a while? Is there a way to disable the DMA on the install floppies? Part of the probe looks like this: (written down by hand) atapci0: VIA 82C586 ATA33 controller port 0xe000 - 0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ... ad0: 6204MB ST36531A [13446/15/63] at ata0-master using UDMA33 John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failure in cvs ...
At 17:16 09.03.2000 -0800, Kris Kennaway wrote: the variable being defined and not its value. You might try removing your object directory and doing a make cleandir twice to make sure nothing is left in source tree that shouldn't be there. Yes, thats a likely candidate. Can you try blowing away /usr/obj and see if the problem persist? Testa aslfdj slkdflaskdf lksflskf laksdflkas dflskf sldkfjsl lskdfj laskdjf lksdlks fskdjfls slkdfjs dlkasldk sjdlfkjs fskdjfl sdlfjslf sldjf sldfjs ldkfj To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Feedback on 4.0-RC3 (mostly good! :)
OK, finally had a chance to frag the hard drive and install 4.0-RC3 from cdrom and see how it went. Here's my observations on the good: 1) On the same hardware as I tested 4.0-RC and 4.0-RC2 on, now I no longer get those "long ATA probes"! This is awesome! Whatever was done, is great, now the machine boots very speedily. 2) The "Standard Installation" is much better than "Novice". It was good to rename this. 3) I chose the "A" option for partition/label and good, reasonable defaults were given to me. 4) The "Standard Install" went flawlessly (despite my best attempts at pilot error :). Now observations on a few nit-picky things: 1) There is a typo (spelling error) in one of the dialogs I was presented. I was trying to force pilot error into the situation :) and got a dialog that contained the following line: "You can also chose "No" at the next prompt and go back into the installation menus to try and retry whichever operations failed." The word "chose" should be "choose." I'd supply a patch, but I only installed kernel source :( 2) Again, while trying to inject pilot error, I created a FreeBSD partition of only 10Mb and gave that as the only slice the Label editor could deal with. When I hit 'A' to have it auto-decide, it came back with a dialog box: "Unable to create root partition. Too big?" I assume by what I gave to it, that it means to say "dummy, you didn't give me a big enough slice with which to work, try again." If that is the case, perhaps a small re-write of the dialog message is in order to help explain what has gone on and a possible course of action to correct the problem--like "give me a larger slice to work with here". In all honesty, I *meant* to create a 10Gb partition and typed so fast that my brain didn't snap that "10M" != "10G" ... and thus I presented a wierd situation to the Label editor. The system is fast, GNOME+E. desktop is usable, kernel config went like a charm. Looks *real* good from where I'm sittin'. Good work to all! Let's ship this puppy. :) -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation [EMAIL PROTECTED] My opinions are mine, not Intel's. Running [EMAIL PROTECTED] FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: The pw command
On 10-Mar-2000 Paul Richards wrote: | Non-root users can use the pw command to get information from the | master.passwd file e.g. | | ps showuser paul | paul:*:1000:1000::0:0: Richards:/home/paul:/usr/local/bin/bash | | which shows the class, password expiry and account expiry. I'm not sure | whether that's information that should be kept secure but it does seem | like 'pw' is the only command that makes it available. The 'chsh' | command doesn't show this information except when run as root for | instance. | pw(8) uses getpwuid(3) to retrieve a password entry from the world readable /etc/pwd.db. It doesn't open master.passwd, (well at least when run as a non-superuser). IMO, that information is not something that needs to be secured. / * Mike Heffner [EMAIL PROTECTED]* * Fredericksburg, VA -- ICQ# 882073* * Sent at: 10-Mar-2000 -- 00:58:18 EST * * http://my.ispchannel.com/~mheffner * / To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Feedback on 4.0-RC3 (mostly good! :)
Hello, You are using RC3 ? Hmm...I wonder why you are not getting the ATA prob problems like alot of us are. What is your system config? Yes it is FAST! and I love itI see that the 64MB memory problem has been fix at the install level. 3.x only reads 64MB of RAM at the floppy install. 4.0 reads all of my 128MB. Cheers Shaun On Thu, 9 Mar 2000, John Reynolds wrote: OK, finally had a chance to frag the hard drive and install 4.0-RC3 from cdrom and see how it went. Here's my observations on the good: 1) On the same hardware as I tested 4.0-RC and 4.0-RC2 on, now I no longer get those "long ATA probes"! This is awesome! Whatever was done, is great, now the machine boots very speedily. 2) The "Standard Installation" is much better than "Novice". It was good to rename this. 3) I chose the "A" option for partition/label and good, reasonable defaults were given to me. 4) The "Standard Install" went flawlessly (despite my best attempts at pilot error :). Now observations on a few nit-picky things: 1) There is a typo (spelling error) in one of the dialogs I was presented. I was trying to force pilot error into the situation :) and got a dialog that contained the following line: "You can also chose "No" at the next prompt and go back into the installation menus to try and retry whichever operations failed." The word "chose" should be "choose." I'd supply a patch, but I only installed kernel source :( 2) Again, while trying to inject pilot error, I created a FreeBSD partition of only 10Mb and gave that as the only slice the Label editor could deal with. When I hit 'A' to have it auto-decide, it came back with a dialog box: "Unable to create root partition. Too big?" I assume by what I gave to it, that it means to say "dummy, you didn't give me a big enough slice with which to work, try again." If that is the case, perhaps a small re-write of the dialog message is in order to help explain what has gone on and a possible course of action to correct the problem--like "give me a larger slice to work with here". In all honesty, I *meant* to create a 10Gb partition and typed so fast that my brain didn't snap that "10M" != "10G" ... and thus I presented a wierd situation to the Label editor. The system is fast, GNOME+E. desktop is usable, kernel config went like a charm. Looks *real* good from where I'm sittin'. Good work to all! Let's ship this puppy. :) -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation [EMAIL PROTECTED] My opinions are mine, not Intel's. Running [EMAIL PROTECTED] FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Feedback on 4.0-RC3 (mostly good! :)
[ On Thursday, March 9, Shaun (UNIX) wrote: ] Hello, You are using RC3 ? Hmm...I wonder why you are not getting the ATA prob problems like alot of us are. What is your system config? I'm using a P2B-DS Asus motherboard with BX chipset. Standard PIIX4 stuff. The drive is a Quantum Fireball 20.5Gb (don't have the exact model number handy). It's a UDMA66 drive but of course I'm only using UDMA33 to it ... I don't have the dmesg output handy from 4.0-RC3, but here's from 3.4-STABLE: chip0: Intel 82443BX host to PCI bridge rev 0x02 on pci0.0.0 chip1: Intel 82443BX host to AGP bridge rev 0x02 on pci0.1.0 chip2: Intel 82371AB PCI to ISA bridge rev 0x02 on pci0.4.0 Beats me, it's a pretty vanilla setup. All I know is that now when the thing boots from the cd (and after compiling a custom kernel) it doesn't sit there and "hang" for 30 seconds or so like it did before . ? Yes it is FAST! and I love itI see that the 64MB memory problem has been fix at the install level. 3.x only reads 64MB of RAM at the floppy install. 4.0 reads all of my 128MB. Yes, very fast ... I'm really looking forward to running it (I've been installing on a disc I can frag at will ... can't "take the plunge" until later :). -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation [EMAIL PROTECTED] My opinions are mine, not Intel's. Running [EMAIL PROTECTED] FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Port apps
Hello, I have a question regarding ports. I noticed there was compat3x distro files, is there going to be ports that are only for FreeBSD 4.0 and will I ever run into a problem with 3.x ports not working with 4.x it was just a thought. Cheers Shaun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Port apps
On Thu, 9 Mar 2000, Shaun (UNIX) wrote: I noticed there was compat3x distro files, is there going to be ports that are only for FreeBSD 4.0 Yes. and will I ever run into a problem with 3.x ports not working with 4.x You shouldn't do: that's what the compat3x libraries are for. Kris In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 4.0 in FreeBSD 4.0?
On Thu, 9 Mar 2000, Devin Butterfield wrote: Just wondering if there are plans in the works to get Xfree86 4.0 into FreeBSD 4.0. I just noticed that X 4.0 has finally been released. Looks a bit green for inclusion in a release not to mention that its list of supported devices is a bit short in some areas. There are 4.0 binaries for FreeBSD 4.0 and 3.x available on ftp.xfree86.org and other mirrors so you can play around with it if you like. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The pw command
On Fri, 10 Mar 2000, Paul Richards wrote: Non-root users can use the pw command to get information from the master.passwd file e.g. ps showuser paul paul:*:1000:1000::0:0: Richards:/home/paul:/usr/local/bin/bash % pw showuser kkenn kkenn:*:1000:0::0:0:Kris Kennaway:/home/kkenn:/usr/local/bin/tcsh % grep kkenn /etc/passwd kkenn:*:1000:0::0:0:Kris Kennaway:/home/kkenn:/usr/local/bin/tcsh % ls -l /usr/bin/pw -r-xr-xr-x 1 root wheel 53180 Mar 4 00:49 /usr/sbin/pw* In other words, pw(8) runs with no special privileges and can only read what the user can normally read. In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mount_cd9660+atapi-cd panic
It seems Ben Smithurst wrote: ok, this was partly caused by dodgy hardware it seems, so don't worry too much, but it would be nice if a panic could be avoided. aaiiighh! I knwo exactly what wrong, dont call make_dev early :) Thanks, that probably one of the most complete reports I've seen in a long time, makes bug hunting a breeze, thanks! Fix coming as soon as I've tested it... -Soren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
