Re: rm -rf question

2001-05-24 Thread J Wunsch
Alexander Langer [EMAIL PROTECTED] wrote: It's xargs job to workaround that: ls | xargs rm -rf rm -rf /home/gary/public_html/mrtg/david should have worked as well. It also removes the directory itself, yes, but since it's then rm(1) that does the directory handling, there's no longer a

Re: rm -rf question

2001-05-24 Thread Ceri
On Thu, May 24, 2001 at 10:40:46AM +0200, J Wunsch said: Alexander Langer [EMAIL PROTECTED] wrote: ls | xargs rm -rf rm -rf /home/gary/public_html/mrtg/david If you're running as root, neither of those do the same thing as rm -rf /home/gary/public_html/mrtg/david/* What if

Re: harddisk faillure or kernel problem ?

2001-05-24 Thread Stephan van Beerschoten
Oops, I accidently mailed this to -CURRENT. Sorry folks. I bounced it to -STABLE On Wed, 23 May 2001, Stephan van Beerschoten wrote: For a while now I keep having the following logentries in my messages file: May 23 13:59:40 enigma /kernel: ad0s1a: UDMA ICRC error reading fsbn 1704031 of

Re: rm -rf question

2001-05-24 Thread Peter Wemm
J Wunsch wrote: Alexander Langer [EMAIL PROTECTED] wrote: It's xargs job to workaround that: ls | xargs rm -rf rm -rf /home/gary/public_html/mrtg/david should have worked as well. It also removes the directory itself, yes, but since it's then rm(1) that does the directory

Re: Tonights panic: free_newdirblk+0x73: movl %eax,0x10(%e

2001-05-24 Thread Michael Harnois
On Wed, 23 May 2001 22:10:09 -0300 (ADT), The Hermit Hacker [EMAIL PROTECTED] said: Oops ... neat, now it just locked up solid and ctl-alt-esc doesn't even get me to debugger :( This has been my experience for about a week on the -current kernel ... I held out high hopes that these

Re: Tonights panic: free_newdirblk+0x73: movl %eax,0x10(%e

2001-05-24 Thread Edwin Culp
Quoting Michael Harnois [EMAIL PROTECTED]: On Wed, 23 May 2001 22:10:09 -0300 (ADT), The Hermit Hacker [EMAIL PROTECTED] said: Oops ... neat, now it just locked up solid and ctl-alt-esc doesn't even get me to debugger :( This has been my experience for about a week on the

Re: sbin/vinum broken

2001-05-24 Thread Ruslan Ermilov
On Thu, May 24, 2001 at 09:24:56AM +0930, Greg Lehey wrote: On Wednesday, 23 May 2001 at 16:56:39 +0300, Ruslan Ermilov wrote: Hi! src/sbin/vinum is broken at the moment. It doesn't build without -DVINUMDEBUG. *sigh*. I could have sworn I tested this, but it seems I did it in a

Re: Tonights panic: free_newdirblk+0x73: movl %eax,0x10(%e

2001-05-24 Thread John Baldwin
On 24-May-01 Michael Harnois wrote: On Wed, 23 May 2001 22:10:09 -0300 (ADT), The Hermit Hacker [EMAIL PROTECTED] said: Oops ... neat, now it just locked up solid and ctl-alt-esc doesn't even get me to debugger :( This has been my experience for about a week on the -current

Re: GENERIC kernel hangs at boot (uhci-related)

2001-05-24 Thread Warner Losh
In message [EMAIL PROTECTED] Nick Hibma writes: : 'It' in the second case refers to the PCI irq allocation code I presume? : An irq that is 0 or 255 is invalid and should not be allocated to a PCI : device. But speaking about rev1.32, how would you assign an interrupt as : is stated in the log

Re: GENERIC kernel hangs at boot (uhci-related)

2001-05-24 Thread Warner Losh
In message [EMAIL PROTECTED] [EMAIL PROTECTED] writes: : The problem is not that the PCI device is not initialised, but that the : device is assigned a bogus irq (0/255) by the BIOS. That's not true. They are the default values by the chip. The BIOS likely isn't initializing the chip at all.

Re: ** HEADS UP **: sys/miscfs file systems moved

2001-05-24 Thread Warner Losh
In message [EMAIL PROTECTED] Brian Somers writes: : It may also be worth mentioning that people should move /usr/include : to (say) /usr/include.not before their next installworld and nuke : /usr/include.not after it completes. Eh? that's a bug in the installation proceedure then. Warner To

Re: Date for a working -current?

2001-05-24 Thread Warner Losh
In message [EMAIL PROTECTED] Joseph Koshy writes: : I'm in the processing of bring a 5-current system of Oct 2000 vintage : more upto-date. May 18th, 2001 12:00:00 is what I've been using. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of

Re: Date for a working -current?

2001-05-24 Thread Peter Wemm
Warner Losh wrote: In message [EMAIL PROTECTED] Joseph Koshy writes: : I'm in the processing of bring a 5-current system of Oct 2000 vintage : more upto-date. May 18th, 2001 12:00:00 is what I've been using. Warner But you may want to cd sys/ufs/ffs; cvs update -A *softdep* straight

Re: sbin/vinum broken

2001-05-24 Thread Greg Lehey
On Thursday, 24 May 2001 at 18:28:19 +0300, Ruslan Ermilov wrote: On Thu, May 24, 2001 at 09:24:56AM +0930, Greg Lehey wrote: On Wednesday, 23 May 2001 at 16:56:39 +0300, Ruslan Ermilov wrote: Hi! src/sbin/vinum is broken at the moment. It doesn't build without -DVINUMDEBUG. *sigh*. I

Re: mount_mfs (Re: smbfs)

2001-05-24 Thread Kris Kennaway
On Thu, May 24, 2001 at 10:35:43PM -0400, Mikhail Teterin wrote: On 24 May, Kris Kennaway wrote: On Thu, May 24, 2001 at 06:13:21PM -0700, Gordon Tetlow wrote: Should there be a mount_smbfs to go with this? How does one mount smb shares otherwise? It's in the smbfs port. Shouldn't

Re: mount_mfs (Re: smbfs)

2001-05-24 Thread Dima Dorfman
Kris Kennaway [EMAIL PROTECTED] writes: --3MwIy2ne0vdjdPXF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 24, 2001 at 10:35:43PM -0400, Mikhail Teterin wrote: On 24 May, Kris Kennaway wrote: On Thu, May

Re: tail -f over NFS in -stable

2001-05-24 Thread Doug Barton
Blast from the past. This patch seemed reasonable to me at the time, but I notice you didn't commit it. Any reason why? The issue has just come up again on -questions. Doug Ben Smithurst wrote: Fred Gilham wrote: In 4.1-stable tail -f over NFS polls rather than blocking. Yes,

Re: ** HEADS UP **: sys/miscfs file systems moved

2001-05-24 Thread Doug Barton
Warner Losh wrote: In message [EMAIL PROTECTED] Brian Somers writes: : It may also be worth mentioning that people should move /usr/include : to (say) /usr/include.not before their next installworld and nuke : /usr/include.not after it completes. Eh? that's a bug in the installation

Re: Boot time memory issue

2001-05-24 Thread Valentin Nechayev
Sun, May 20, 2001 at 19:53:29, barry (Barry Lustig) wrote about Boot time memory issue: Do verbose boot (`boot -v') with large SC_HISTORY_SIZE (1000 at least, 2000 at most), and after boot check for SMAP ... lines at the very beginning of the kernel boot log at /dev/console. (They are not