Re: vinum still not working

On Sunday 23 November 2003 23:50, you wrote: > > Yes. The fix wasn't enough. I was holding off committing until I > could test it. Thanks for YOUR commit! :-) All works fine here now... -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and

vinum still not working

Hello, I just built a new world+kernel after the commit of grogs corrections but I still get: [EMAIL PROTECTED] - ~ 503 # vinum start ** no drives found: No such file or directory -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F

Re: grub on -current?

from there. Ahm, nearly. There seems to be a sysctl (...geom.debug=16 ?) which allows to write the bootsector, but you better ask phk directly - I'm not sure... -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F ___

Re: suddenly bind and access to NNTP server (localhost) doesn't work

rking current until last Saturday was from Okt 25... Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Vim: Caught deadly signal BUS (after -current update with newgcc)

are able to analyze the correctness of that patch... -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) PGP-Key at and ID: 0xDDFB0A5F ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: several background fsck panics

disks. SCSI-disks don't need it because of Tagged Queuing and only those ATA-Disks that *have* TQ can/should be operated 'the fast way' - hoping that Soeren gets it working again... :-/ -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powered by FreeBSD 5.0-

Re: softupdates && write cache && ata tags topic

Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powered by FreeBSD 5.0-CURRENT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

ATA Tagged Queuing working again?

only thing I saw were 1,2 stops of about 500ms during the listing of the tar-command but nothing worse happened. With earlier Kernels this indicated a soon lock and switch to PIO... Fine! I hope this stabilizes... -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powered

Re: Grub 0.92 fails to recognise disks on FBSD5

against 'booteasy', it does the job - but it looks ugly :-) And I can't imagine that the majority of FreeBSD-Users all have a bunch of disks in their systems - especially if I think of the giant sizes of HDs nowadays... -- Ciao/BSD - Matthias Matthias Schuendehuette , Berli

Re: dump(8) + UFS2

er... Great Job! Thanks a lot! -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powered by FreeBSD 5.0-CURRENT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

cdrecord/SCSI problems

finished after 0.003s timeout 200s write CD-Text data: error after 0 bytes cdrecord: Could not write Lead-in. Are these error messages of any use for anybody? -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powered by FreeBSD 5.0-CURRENT To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: dump(8) + UFS2

ng (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: SIGSEGV: ABORTING! Speicherschutzverletzung (core dumped) Or is it a SCSI-problem? Did you dump from an ATA or SCSI-Disk? To an ATA or SCSI tape-device? Astonishing... -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (G

Re: Actual probs with 'ipfw'

nt to delay an installworld until you are comfortable that your newer kernel builds are satisfactory." from: Message-ID: <[EMAIL PROTECTED]> But my new kernel build *is* satisfactory now :-) -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powered by FreeBSD 4.7-STABLE To

Re: Actual probs with 'ipfw'

On Saturday 26 October 2002 21:48, you wrote: > No, the problem is that you need to installworld to have an updated > ipfw(8) binary. Confirmed! Thanks a lot! PS: So the HEADSUP-strategy has its limitations... ;-) -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powe

Actual probs with 'ipfw'

ve 52 want 40) This happens every time I run 'sh /etc/rc.firewall open'. Not to mention, that the firewall is closed perfectly :-/. I didn't run 'mergemaster' because of no installworld. Is that the problem? -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin

Another 'buildworld' showstopper

ommon-s. Stop *** Error code 2 Stop in /usr/src/gnu/usr.bin/groff. *** Error code 1 Stop in /usr/src. *** Error code 1 PS: ... and it's an i386 and no alpha (see UPDATING) -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powered by FreeBSD 4.7-STABLE To Unsubscribe: se

Re: Journaled filesystem in CURRENT

f), whereas SU *does* guarantee data consistency (admittedly with a time lag) because of that nesting from data with metadata. I'm far away from beeing able to follow this discussion in every detail, but please correct me if I'm wrong... -- Ciao/BSD - Matthias Matthias Schuendehu

Re: Journaled filesystem in CURRENT

ich has already under Linux a more than poor performance. The only reason for porting JFS is IMHO to be able to mount JFS Volumes under FreeBSD - if that's worth the effort... Why begging for 'Journaling' if you have 'Journaling next generation'? -- Ciao/BSD - Matthias M

Re: xdm-Problems with PAM

Am Dienstag, 13. August 2002 14:42 schrieb Alexander Leidinger: > On Mon, 12 Aug 2002 22:06:59 +0100 David Malone > <[EMAIL PROTECTED]> > > wrote: > > On Mon, Aug 12, 2002 at 10:19:00PM +0200, Matthias Schuendehuette > > > > wrote: > > > Aug 12 18:20:0

xdm-Problems with PAM

;_openpam_log"] Aug 12 18:20:02 current : adding faulty module: /usr/lib/pam_lastlog.so 'Known behaviour' or real problems? -- Ciao/BSD - Matthias Matthias Schuendehuette , Berlin (Germany) Powered by FreeBSD 4.6-STABLE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: ATA errors on recent -current

, but... I think, we'll wait for Soren's commit tonight. -- Ciao/BSD - Matthias Matthias Schuendehuette <[EMAIL PROTECTED]>, Berlin (Germany) Powered by FreeBSD 4.5-STABLE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: ATA errors on recent -current

t world (...puhh) and kernels are in place... ...'till later. -- Ciao/BSD - Matthias Matthias Schuendehuette <[EMAIL PROTECTED]>, Berlin (Germany) Powered by FreeBSD 4.5-STABLE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: ATA errors on recent -current

y UDMA-Mode no longer usable afterwards? Is the drive been reset or just switched back? What is the impact of a reset compared to a switch back? Well, just my thoghts, I'm no specialist at all -- Ciao/BSD - Matthias Matthias Schuendehuette <[EMAIL PROTECTED]>, Berlin (Germany) Powered by FreeBSD 4.5-STABLE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: ATA errors on recent -current

Hello, Am Mittwoch, 17. April 2002 03:14 schrieben Sie: > Matthias Schuendehuette wrote: > > I used 'atacontrol' to read the number of tags allowed: it is 31 > > (0x1F). Perhaps Soren could tell me how to force it to, say, 0x10? > > You have to modify the source

Re: ATA errors on recent -current

anagement yes yes advanced power management yes no 0/00 automatic acoustic management yes no 254/FE 128/80 That's it. -- Ciao/BSD - Matthias Matthias Schuendehuette <[EMAIL PROTECTED]>, Berlin (Germany) Powered by FreeBSD 4.5-STABLE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: ATA errors on recent -current

* - sorry, but it's true. And maybe it isn't related to tagged queuing and the DTLA at all - if I correctly understand Giorgos' mail... -- Ciao/BSD - Matthias Matthias Schuendehuette <[EMAIL PROTECTED]>, Berlin (Germany) Powered by FreeBSD 4.5-STABLE To Unsubscribe: send

make world stops...

/usr/src/gnu/usr.bin/groff/src/preproc. -- Ciao/BSD - Matthias Matthias Schuendehuette <[EMAIL PROTECTED]>, Berlin (Germany) Powered by FreeBSD 4.5-STABLE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: usb lpt borked?

e. */ Works for me as well. I can't say nothing about usb-printing but the mouse issue seems to be solved with this patch. I someone asks me - please commit it ASAP -- Ciao/BSD - Matthias Matthias Schuendehuette <[EMAIL PROTECTED]>, Berlin (Germany) Powered by FreeBSD 4.5-STABLE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

'moused' freezing system

0. At least, I can enjoy background-fsck on every startup... ;-) I have a . -- Ciao/BSD - Matthias Matthias Schuendehuette <[EMAIL PROTECTED]>, Berlin (Germany) Powered by FreeBSD 4.5-STABLE To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message