On Sun, Jan 30, 2000 at 09:06:33AM +0900, Jun Kuriyama wrote:
I found difference between "rm -rf" for non-exist file on readonly nfs
and usual non-writable directory.
In this example, /usr/src is readonly nfs mounted and /usr/bin is
normal filesystem but not writable. And file "a" is not
On Sun, Jan 30, 2000 at 02:50:22PM +0900, Daniel C. Sobral wrote:
Jean-Marc Zucconi wrote:
With a new installed world I get this message at boot:
\ Loader.rc
Loader.rc: unknown command
Fortunately this does not prevent the machine to boot :-)
Any clue?
The \ command is not
:This happens on either NFS-mounted or real directories. It think that since
:the manual of rm(1) says:
:
: -f Attempt to remove the files without prompting for confirma-
: tion, regardless of the file's permissions. If the file does
: not exist, do not display a
On Sun, 30 Jan 2000, Jun Kuriyama wrote:
I found difference between "rm -rf" for non-exist file on readonly nfs
and usual non-writable directory.
In this example, /usr/src is readonly nfs mounted and /usr/bin is
normal filesystem but not writable. And file "a" is not exist.
-
% rm
Whichever system they run on. This can be the host machine even for
cross-compiling, if the target root is remote mounted. The main problem
with this in -current is that some install rules put ${DESTDIR} in the
installed files. perl is the main offender.
Which install rules? I'd like to
It seems Kris Kennaway wrote:
My CDROM still refuses to work with cdcontrol, although the 30-seconds of
kernel spinning is now fixed.
Trying to play a track gives:
acd0: PLAY_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=04
I'll bet this drive doesn't support PLAY_BIG but only PLAY_MSF.
The
On Sat, 29 Jan 2000, Alex Zepeda wrote:
On Sun, 30 Jan 2000, kibbet wrote:
/me looks at the bunch of 386 mobo's... lets not go there.. :)
/me looks at the stack of 386sx chips he has and wonders why no-one did 8
way SMP with these!
uky.edu once had a Sequent Symmetry with twenty-six
Matthew Dillon wrote:
When the new parallel port stuff was put several months ago, my
machine stopped working. I had to set flags to 0x40 to make it
work again. Flags of 0x40 force the driver to use the most
basic probes possible. It was put in because a number of people's
On Sun, 30 Jan 2000, Mark Murray wrote:
Whichever system they run on. This can be the host machine even for
cross-compiling, if the target root is remote mounted. The main problem
with this in -current is that some install rules put ${DESTDIR} in the
installed files. perl is the main
On Sun, 30 Jan 2000, Soren Schmidt wrote:
Trying to play a track gives:
acd0: PLAY_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=04
I'll bet this drive doesn't support PLAY_BIG but only PLAY_MSF.
The problem here is that PLAY_MSF's parameters are either in
binary or in BCD, but you dont
It seems Kris Kennaway wrote:
On Sun, 30 Jan 2000, Soren Schmidt wrote:
Trying to play a track gives:
acd0: PLAY_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=04
I'll bet this drive doesn't support PLAY_BIG but only PLAY_MSF.
The problem here is that PLAY_MSF's parameters are
Kris Kennaway [EMAIL PROTECTED] wrote:
This commit causes my P5 to panic at boot:
kato2000/01/28 23:49:03 PST
Modified files:
sys/i386/i386identcpu.c
Log:
Simplify messages of Pentium II, Pentium II Xeon, Celeron, Pentium III
and Pentium III Xeon CPUs. If
If I put INET6 in my kernelconfig my network stops working. Even IPv4. I have
a Intel EtherExpress Pro 10/100B Ethernet (fxp) card. I found a fix for
FreeBSD on an OpenBSD mailinglist :-)
http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html
Something
To go from
pcic-pci0: TI PCI-1131 PCI-CardBus Bridge irq 9 at device 19.0 on pci0
pcic-pci0: driver is using old-style compatability shims
pcic-pci1: TI PCI-1131 PCI-CardBus Bridge irq 9 at device 19.1 on pci0
pcic-pci1: driver is using old-style compatability shims
to
pcic-pci0: TI PCI-1131
I've had the following problem with several recent versions of
current. (dmesg of maching included below)
Typing `reboot' kills everything but doesn't reboot machine. And then
when I break into DDB and type panic twice it tries to dump but then
it fails and goes into an infinite loop of `ad0:
I'm seeing the following failure on my -current box with sources cvsupped last
night about 11:30 est.
=== bin/ps
install -C -c -s -o root -g wheel -m 555 ps /bin
install -C -c -o root -g wheel -m 444 ps.1.gz /usr/share/man/man1
=== bin/pwd
install -C -c -s -o root -g wheel -m 555 pwd /bin
On Sat, Jan 29, 2000 at 09:49:40PM -0600, Chris Costello wrote:
On Saturday, January 29, 2000, David Gilbert wrote:
When this happens, the entire machine freezes until someone feeds the
printer --- the momment it starts printing again, the computer
unfreezes.
Could it be a
On Sat, Jan 29, 2000 at 10:59:15PM -0500, David Gilbert wrote:
"Chris" == Chris Costello [EMAIL PROTECTED] writes:
Chris On Saturday, January 29, 2000, David Gilbert wrote:
When this happens, the entire machine freezes until someone feeds
the printer --- the momment it starts printing again,
On 30-Jan-00 Mike Andrews wrote:
On Sat, 29 Jan 2000, Alex Zepeda wrote:
On Sun, 30 Jan 2000, kibbet wrote:
/me looks at the bunch of 386 mobo's... lets not go there.. :)
/me looks at the stack of 386sx chips he has and wonders why no-one did 8
way SMP with these!
uky.edu once had
On Sat, Jan 29, 2000 at 08:21:33PM -0800, Matthew Dillon wrote:
When the new parallel port stuff was put several months ago, my
machine stopped working. I had to set flags to 0x40 to make it
work again. Flags of 0x40 force the driver to use the most
basic probes possible. It
You need to manually recompile and install your "install" command.
It's source-dir is called "xinstall" btw.
Poul-Henning
In message [EMAIL PROTECTED], bush doctor writes:
I'm seeing the following failure on my -current box with sources cvsupped last
night about 11:30 est.
=== bin/ps
Out of da blue Poul-Henning Kamp aka ([EMAIL PROTECTED]) said:
You need to manually recompile and install your "install" command.
Thanxs. I had looked at this, but wasn't sure.
It's source-dir is called "xinstall" btw.
Why is the source called "xinstall"?
Poul-Henning
In message
I've had the following problem with several recent versions of
current. (dmesg of maching included below)
Typing `reboot' kills everything but doesn't reboot machine. And then
when I break into DDB and type panic twice it tries to dump but then
it fails and goes into an infinite loop of
In message Pine.BSF.4.20.0001301011280.843-10@localhost Nick
Hibma writes:
: pcic-pci0: TI PCI-1131 PCI-CardBus Bridge irq 9 at device 19.0 on pci0
: pcic-pci0: driver is using old-style compatability shims
: pcic-pci1: TI PCI-1131 PCI-CardBus Bridge irq 9 at device 19.1 on pci0
: pcic-pci1:
If you installed world after my libreadline header moving, you probably
have readline headers in /usr/include you'll want to rm.
Index: Makefile
===
RCS file: /home/ncvs/src/gnu/lib/libreadline/readline/Makefile,v
retrieving
On Sun, 30. Jan. 2000 at 14:50:22 +0900, Daniel C. Sobral wrote:
Jean-Marc Zucconi wrote:
With a new installed world I get this message at boot:
\ Loader.rc
Loader.rc: unknown command
Fortunately this does not prevent the machine to boot :-)
Any clue?
The \ command is not
Nick Hibma [EMAIL PROTECTED] writes:
Same message here, but after a panic of the USB subsystem. I blamed the
current spl. Until I did a 'call splx(0)' right before giving the
command panic. It still did not give me a dump.
There seems to be two problems here:
1) It hangs instead of rebooting
For what its worth, I am able to reproduce this problem on my system.
Simply submit something to lpr, wait for the printer light to blink,
and pull the paper tray. The system hangs hard as described and does
not return to normal until the paper tray is put back in. I haven't
been able to make
rename it libstdc++.so.1. Then you just have to modify your executable
so that it looks for libstdc++.so.1 instead of libstdc++.so.3
Why not just reinstall the problematic executables?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
On Fri, Jan 28, 2000 at 08:30:55PM -0500, John Baldwin wrote:
I don't think we should change yet another thing before a release. The
problem shouldn't have been created this close to a release in the first
place. We have to stop somewhere, and I think we should stop "fixing" right
here,
On Sun, 30 Jan 2000, KATO Takenori wrote:
It sounds strange. I didn't modify any P5 stuff.
I attached the patch from 1.79 to 1.80 diff in this mail.
- Could you try to this patch with the -R option?
Yes, when I back out this revision ( nothing else) I can boot fine :-)
- Please
On Fri, Jan 28, 2000 at 08:30:55PM -0500, John Baldwin wrote:
I don't think we should change yet another thing before a release. The
problem shouldn't have been created this close to a release in the first
place. We have to stop somewhere, and I think we should stop "fixing" right
On Sun, 30 Jan 2000, Brian Somers wrote:
I'm quite happy to DTRT(tm); I'm unsure that backing this change out
_is_ the right thing however. Can we discuss it some more first please?
I think that getflags()/setflags() should stay where they are, but I
can't comment on the namespace
On 30-Jan-00 Josef Karthauser wrote:
On Fri, Jan 28, 2000 at 08:30:55PM -0500, John Baldwin wrote:
I don't think we should change yet another thing before a release. The
problem shouldn't have been created this close to a release in the first
place. We have to stop somewhere, and I
On Sun, Jan 30, 2000 at 04:51:44PM -0500, John Baldwin wrote:
[cut]
With that in mind, the upgrade path is only going
to be broken for a few people who should be reading -current and thus
know how to work around the problem, so I repeal my request for the
changes to be backed out. My
Hi,
Is there something changed on BOOTP/diskless configuration?
This problem reappears some times and was fixed in August if I remember.
A hack was proposed before August, something like 'make root dev' call in
bootp_subr.c
Thanks,
Nicholas
bootpc_init: using network interface 'ed0'
Bootpc
This is on 3.4 Stable, Another "me too", BUT, with a "data point". NEC
SuperScript 870, ASUS
MB. Had the same problem when the BIOS was set to ECP+EPP on the parallel
port. Sinces it only a printer, I set the BIOS to Normal and deliberately
tried to introduce the problem (pull paper tray,
[EMAIL PROTECTED] wrote:
FWIW this doesn't happen with my card:
fxp0: Intel InBusiness 10/100 Ethernet port 0x1000-0x103f mem 0xf400-0xf40
f,0xf410-0xf4100fff irq 10 at device 15.0 on pci0
fxp0: Ethernet address 00:90:27:d1:83:6a
fxp0: supplying EUI64: 00:90:27:ff:fe:d1:83:6a
Kris Kennaway [EMAIL PROTECTED] wrote:
Yes, when I back out this revision ( nothing else) I can boot fine :-)
Hmm, I cannot know why you got panic On your CPU (P54C: 586-class
CPU), the part which I changed is not executed.
I have tested the change on:
- Intel MMX Pentium 166MHz
-
Please note, I'm attempting to upgrade from -stable to -current.
install-info --quiet --defsection="Programming development tools."
--defentry="* libcom_err: (com_err).A Common Error Description Library
for UNIX." com_err.info /usr/share/info/dir install-info: unrecognized option
For what its worth, I am able to reproduce this problem on my system.
Simply submit something to lpr, wait for the printer light to blink,
and pull the paper tray. The system hangs hard as described and does
not return to normal until the paper tray is put back in. I haven't
been able to
On Sun, 30 Jan 2000, you wrote:
I've re-cvsupped and noticed UPDATING was changed this time. Upon remaking
xinistall, I also discovered I had an incorrect version of libc. (it wanted
libc.so.4, I had libc.so.3).
Symlinked 3 to 4, we'll see what happens...
Please note, I'm attempting to
I make a new world today after reinstalling xinstall and thought that
along with recompiling my applications that are having problems that I
assume started with the c++ compiler change, but I have recompiled
several applications and still have the errors.
If someone would tell me what I am doing
On Sat, 29 Jan 2000, Warner Losh wrote:
In message [EMAIL PROTECTED] Greg Lehey writes:
: I did a make world on my PDP-11 yesterday. It took less than a day.
: But that's 2.11BSD.
Turns out that 12MB + 30MB of swap isn't enough to build world. I ran
out of swap and the machine rebooted
On Sun, 30 Jan 2000, Edwin Culp wrote:
I make a new world today after reinstalling xinstall and thought that
along with recompiling my applications that are having problems that I
assume started with the c++ compiler change, but I have recompiled
several applications and still have the
Looks like I have to cvsup again, it's not in my UPDATING from 11:40 PST
today. That was the first place I checked.
Sorry and thanks,
ed
"Chris D. Faulhaber" wrote:
On Sun, 30 Jan 2000, Edwin Culp wrote:
I make a new world today after reinstalling xinstall and thought that
along with
* From: Matthew Dillon [EMAIL PROTECTED]
* Ah, that's good. I still have one person reporting a panic with 1.56
* (which I have a core for). w/1.56 my own buildworld tests succeed
* and except for this one person everyone else is reporting their
* softupdates problems
I just got the new UPDATING and I seem to have done everything. Until I built
xinstall, I wasn't able to make world, made a new kernel and rebooted and built
a new version of mysql and am still getting the error. I'm going to build a
new world, just in case my cvsup timing was bad.
Thanks a
"Michael" == Michael Remski [EMAIL PROTECTED] writes:
Michael ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: SMC-like chipset
Michael (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with
Michael 16/16/7 bytes threshold lpt0: generic printer on ppbus 0
Michael lpt0: Interrupt-driven port
I
http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html
Something better than that is probably needed in the long run.
Let me confirm it.
Does this also fix your problem on your freebsd-current?
Yes. I have only tried ping6, but that works, and IPv4 works.
rename it libstdc++.so.1. Then you just have to modify your executable
so that it looks for libstdc++.so.1 instead of libstdc++.so.3
Why not just reinstall the problematic executables?
Yeap, we do that quite often in Linux 8)
Cheers
--
Amancio Hasty
[EMAIL PROTECTED]
To
i'm running world built on the 26th, and a kernel built immediately
afterwards..
machine is a chembook 3300.
if i suspend, upon resuming i get a brief flash of X, and then a black
screen. i have to kill X to get a display back.
also, while my 3c574 comes back up, it loses the configuration
A panic also occurred on my Pentium (P54C) 66MHz, but backing identcpu.c
to 1.79 didn't stop the panic. Here is the panic info, copied by hand. (I
hope there are no typos!)
Lots of 'ad1: timeout waiting for DRQ' followed by
Fatal trap 12: page fault while in kernel mode
fault virtual address
Well, with all problems with buildworld and building kernels, and my
limited time. I have only just gotten back to a point where I can
retest
the crash I was having. This time, no crash.
Apparently, my milage is varying...
-- Danny J. Zerkel
[EMAIL PROTECTED]
To Unsubscribe: send mail to
On Mon, 31 Jan 2000, Gary Palmer wrote:
/me looks at the stack of 386sx chips he has and wonders why no-one did 8
way SMP with these!
You never heard of the Sequent boxes, did you? :)
In fact I haven't.
But I also don't have DXs either. :)
- alex
To Unsubscribe: send mail to [EMAIL
On Mon, Jan 31, 2000 at 01:00:44AM -0500, TrouBle wrote:
: Geee lets see i have a 386 sx with a really tiny MFM in it still, its just
: sitting here, doing nothing, wonder if i can get current on it, the thought is
: killing me... : )) its got 8 megs of ram in it too ??? ~GRIN~
I'm running a
This fixes the error messages seen when attempting to use a SCSI cdrom
drive with
vmware. It is unclear to me whether this would do more harm than good,
since I don't
really know what the CDIOCREADSUBCHANNEL ioctl does. But it does look
righteous to me,
since without it, the 'track' variable in
57 matches
Mail list logo
