Move u2f-devd into base?

We have FIDO/U2F support for SSH in base. We also have a group "u2f", 116, in the default /etc/group file. Why do we keep the devd configuration (to chgrp the device nodes) in a port, security/u2f-devd? Can't we just add this to base, too? It's just another devd configuration file. -- Christia

Re: Did clang 14 lose some intrinsics support?

Dimitry Andric: > > See https://github.com/llvm/llvm-project/commit/e5147f82e1cb > > > > - Instead of __builtin_ia32_pabsd128 maybe use _mm_abs_epi32 > > - Instead of __builtin_ia32_pabsd256 maybe use _mm256_abs_epi32 > > I'm wondering why this rather fragile method is chosen? If you want to > k

Re: [HEADSUP] making /bin/sh the default shell for root

Dirk Meyer: > Migration of aliase will be painful as ">&" and "|&" is not supoported. csh sh >& foo >foo 2>&1 |& foo 2>&1 | foo -- Christian "naddy" Weisgerber na...@mips.inka.de

Re: Git and complementary web interfaces (some fast but basic, others fuller-featured)

On 2021-01-07, Graham Perrin wrote: > cgit describes itself as "hyperfast" with > "basic repository browsing" > as a feature. > > Beyond those basics, I guess that it will be appropriate to ensure > awareness of complementary web-based repository bro

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

On 2021-01-01, Shawn Webb wrote: > This is why I asked FreeBSD to provide anonymous read-only ssh:// > support for git. I'm very grateful they support it. > > One thing that I need to do with the HardenedBSD infrastructure is > publish on our site the ssh pubkeys of the server (both RSA and > ed2

Re: git and the loss of revision numbers

monochrome: > the g is also in the uname output: > > main-c421-gf20c0e331-dirty It's the brand new format: -c-g[-dirty] https://cgit.freebsd.org/src/commit/sys/conf/newvers.sh?id=8d405efd73d3991fe1647f91a2b7c9989dd5f18f -- Christian "naddy" Weisgerber na...@mips.inka.d

Re: git and the loss of revision numbers

Michael Grimm: > If I do understand it correctly, the switch from svn to git comes with a loss > of continuously increasing revision numbers. Correct. > Correct? If so I wonder how future security advisories and errata notices > will be composed. Will there be a date of the commit besides its

Re: git tools for building in base?

On 2020-11-25, Warner Losh wrote: >> Shouldn't it be in base before the move to git? > > We will have got (from OpenBSD: Game Of Trees) in the future. It isn't > quite there yet, however, so it's not in base. Since got can't fetch from http(s) yet, there was talk of setting up anon-ssh access.

Re: Plans for git

On 2020-09-21, Pete Wright wrote: > I believe the most detailed report on this was in the 2020-04 quarterly > status report: > https://www.freebsd.org/news/status/report-2020-04-2020-06.html#Git-Migration-Working-Group I saw that at the time. It basically says that the conversion of the reposi

Re: Plans for git

On 2020-09-21, Alexander Leidinger wrote: > In my opinion the people which drive this didn't keep it behind > closed curtains, and they went step by step more public, as they > made progress. To me it looks like now, that they have something > which is presentable to the world (and not only to c

Re: Plans for git

On 2020-09-19, Zaphod Beeblebrox wrote: > Hrm. Maybe what I hear others saying, tho, and not entirely being replied > to is just a nice concise document of the why. What I hear you saying is > that GIT has momentum and that it's popular... (and I accept that --- it is > evidently true), but the

Re: Plans for git

Kyle Evans: > > > This is probably better for a separate thread, but any idea if there > > > > I'm going to regret asking, but what would you need this feature > > for? > > It's not necessarily that bad -- I used to use it for a poor > substitute for git-worktree before I learned about that, for

Re: Plans for git

Kyle Evans: > > FWIW, I just committed a Got port (devel/got). > > This is probably better for a separate thread, but any idea if there > are plans to eventually support local filesystem cloning in got? I wouldn't know. I'm going to regret asking, but what would you need this feature for? --

Re: Plans for git

On 2020-09-02, Mason Loring Bliss wrote: > Just to throw it out there, https://gameoftrees.org/ would be interesting > to explore for this. FWIW, I just committed a Got port (devel/got). -- Christian "naddy" Weisgerber na...@mips.inka.de ___

Re: Sound lag over HDMI

Alexander Motin wrote: > I don't know what to say. I am now using HDMI audio from NVIDIA card to > quite old external 5.1 receiver with XBMC every day, and I haven't > noticed lags. > > The only potentially related effect I have noticed is that my receiver > eats first second or about that of

Re: CVS removal from the base

Max Khon wrote: > As soon as ports/ (and doc/) are moved to SVN I do not see any > compelling reasons for keeping CVS in the base system. > Those who still use it for development can install ports/devel/opencvs Rather ports/devel/cvs-devel. Maybe we still need a regular cvs port. -- Christian

Re: groff -ms -Tascii (nroff?) strange output

Anton Shterenlikht wrote: > BUZI> groff -ms -Tascii try.1 | more > > ESC[1mSome titleESC[0m > > How can I get a plain text rendering > from a troff document with ms macros? With nroff, use the -c flag: nroff -ms -c -Tascii The groff frontend has a more convoluted s

Re: nroff -mandoc | more no longer works

Robert Watson wrote: > I'm guessing this relates to nroff/groff tweaks, but I was a bit unhappy to > learn that the command I've used for the last decade to render man pages > while > editing them (nroff -mandoc foo.1 | more) no longer works (output below). nroff -c -mandoc foo.1 should work

Re: Forward: HEADS UP! Default value of ip6_v6only changed

Hajimu UMEMOTO <[EMAIL PROTECTED]> wrote: > Our default of net.inet6.ip6.v6only was off in 4.X, and was changed to > on on 5.X to follow NetBSD's practice. This behavior on 5.X breaks > RFC2553/3493, and the change was intentional from security > consideration. But, NetBSD changed it off by defa

Re: Forward: HEADS UP! Default value of ip6_v6only changed

Hajimu UMEMOTO <[EMAIL PROTECTED]> wrote: > Our default of net.inet6.ip6.v6only was off in 4.X, and was changed to > on on 5.X to follow NetBSD's practice. This behavior on 5.X breaks > RFC2553/3493, and the change was intentional from security > consideration. But, NetBSD changed it off by defa

Re: Darwin/OSX Bluetooth code

Peter Pentchev <[EMAIL PROTECTED]> wrote: > You've done some great work on BlueTooth. IMHO, it would be a mistake > to try to un-NetGraph it; there have been lots of rumours about people > porting the NetGraph framework to other OS's, and if BlueTooth support > will provide yet one more reason fo

idprio safe?

Is it safe nowadays to run a process at idle priority? Or is there still the danger of priority inversion / a deadlock? On FreeBSD 4.x you can run a process, such as setiathome, at nice level 19 and it will (almost) only ever get CPU time when no process of normal priority competes with it. Free

Re: Improvements to fsck performance in -current ...?

Lukas Ertl <[EMAIL PROTECTED]> wrote: > It's not just the fsck application itself, background fsck basically needs > file system snapshots, which are only available on UFS2, and I'm not sure > if they can be backported to UFS1 at all. Huh? Snapshots are available for both UFS1 and UFS2, but only

Re: Initial list of ports that fail due to -pthread

Kris Kennaway <[EMAIL PROTECTED]> wrote: > mp3blaster-3.1.3 I have a patch, will talk to maintainer. -- Christian "naddy" Weisgerber [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listin

Re: NANO core dump on Current

Tim Aslat <[EMAIL PROTECTED]> wrote: > I don't know if I'm the only one with this problem, but here goes. > I use Nano (/usr/ports/editors/nano) as my primary text editor, however > Iv'e noticed that any time I use -CURRENT (on my notebook) it core dumps > when saving a file. This is due to a b

Re: make -U

Juli Mallett <[EMAIL PROTECTED]> wrote: > Why go thru those contortions? I sometimes use "make FOO=" to define > things. -U obviously has a place, if it not existing means I have to > have all these contortions to do a fairly obvious thing, yeah? What are the exact semantics of -U supposed to b

Re: Annoucning DragonFly BSD!

Julian Stacey <[EMAIL PROTECTED]> wrote: > Periodicaly someone masquerades as Matt Dilllon. [...] > Maybe this time the poster is the real Matthew Dillon, but I doubt it. Well, I fetched the DragonFly repository, and if this is a hoax, somebody went through an awful lot of work to make it look re

restore(8) triggers panic

I decided to dump, newfs -O2, and restore -r some filesystems on my -CURRENT/alpha box. restore reliably triggered a panic such as this: free inode /var/64 has 27384711479296 blocks bad block 1043841974, ino 64 pid 51 (restore), uid 0 inumber 64 on /var: bad block free inode /var/64 had -

Re: sym disabling controller LED?

Michael Nottebrock <[EMAIL PROTECTED]> wrote: > I have a Dawicontrol 2975U SCSI controller, which is handled by the sym > driver: > > sym0: <875> port 0xac00-0xacff mem > 0xe3201000-0xe3201fff,0xe3203000-0xe32030ff irq 10 at device 8.0 on pci0 > sym0: No NVRAM, ID 7, Fast-20, SE, parity checki

Re: groff and X11 broken (before gcc3.2)

Christian Weisgerber <[EMAIL PROTECTED]> wrote: > It's actually nroff (groff) that aborts. Even a simple "groff --version" or "groff --help" will produce the "out of memory" error. -- Christian "naddy" Weisgerber [

Re: 'gmake' port broken after (due to ?) GCC 3.2 import

Alexander Kabaev <[EMAIL PROTECTED]> wrote: > Not a GCC fault. The bug is in internal gettext library gmake is linked > with. I looked into read_alias_file function and I simply cannot believe > what I am seeing there. PR ports/41075. -- Christian "naddy" Weisgerber [E

Re: groff and X11 broken (before gcc3.2)

Eric Anholt <[EMAIL PROTECTED]> wrote: > > $ startx > > [...] > > xinit: No such file or directory (errno 2): unable to connect to X server > > xinit: No such process (errno 3): Server error. Of course those xinit errors are useless; I should have looked at XFree86.0.log. > You need to eith

groff and X11 broken (before gcc3.2)

I just finished updating my alpha box to shortly before the gcc3.2 import and now I'm seeing some weird breakage: $ man ls out of memory It's actually nroff (groff) that aborts. Also: $ startx [...] xinit: No such file or directory (errno 2): unable to connect to X server xinit: No such proc

Re: port upgrade problem

Maxim M. Kazachek <[EMAIL PROTECTED]> wrote: > "/usr/ports/Mk/bsd.port.mk", line 2580: warning: duplicate script for > target "patch-message" ignored One of the recent changes in make (revision 1.38 of parse.c) causes it to emit this type of warning. This causes heaps of apparently harmless war

Re: current buildworld failure on Alpha?

Wilko Bulte <[EMAIL PROTECTED]> wrote: > ds10#make > Segmentation fault (core dumped) > "/usr/src/Makefile.inc1", line 140: warning: "make -f /dev/null -m > /usr/src/share/mk CPUTYPE=ev56 -V CPUTYPE" returned non-zero status There was a time window when "make -V ..." was broken on 64-bit archs,

Re: What happened to sound?

Christian Weisgerber <[EMAIL PROTECTED]> wrote: > -CURRENT/alpha as of 1..2 days ago. I can load my sound modules > just fine but they don't show up in the kernel messages, and the > corresponding devices under /dev don't exist. Must have been a fluke. Everything is

What happened to sound?

-CURRENT/alpha as of 1..2 days ago. I can load my sound modules just fine # kldstat ... 223 0xfe00031aa000 3snd_pcm.ko 232 0xfe00031da000 16000snd_sbc.ko 241 0xfe00031f 16000snd_sb16.ko but they don't show up in the kernel messages, and the correspond

Re: Xmms

Andrzej Kwiatkowski <[EMAIL PROTECTED]> wrote: > I've upgrade my FreeBSD 5.0 two days ago. > Yesterday when i have compile XMMS from ports, Threads were broken. Update and try again. -- Christian "naddy" Weisgerber [EMAIL PROTECT

Re: LP64: (int)signal()

Mike Barcroft <[EMAIL PROTECTED]> wrote: > You might want to get rid of the other misuse of `rc' above this and > just remove the variable. The use of an gratuitous int variable rc to capture return values is rampant throughout this code. In fact, not using it is something of a violation of the

LP64: (int)signal()

I would like to clean up the last instances of (int)signal(...) in the tree. Any objection to the changes below? Other occurrences not worth touching: - contrib/opie/opieftpd.c: contrib, not used - libexec/bootpd/bootpd.c: #ifdef'ed out in favor of sigaction(). Index: atmarpd/atmarpd.c ==

Re: State of the ports collection

Kris Kennaway <[EMAIL PROTECTED]> wrote: > It seems like ports committers are not able to keep up with the > rate at which ports are being broken by -current changes: Since I originally stated that I would work on fixing ports on alpha and I have clearly failed to do so, I would like to point ou

ppc(4) vs. ppbus(4) module?

So far, I've had device ppc device ppbus device lpt in my KERNEL file to provide parallel printer support. Now I've noticed that ppbus and lpt are also available as modules. However, when I try to build a kernel with just device ppc (intending to load ppbus.ko and lpt.ko later), the build ab

Re: Serial break into debugger broken from 'cu' on -CURRENT?

Wilko Bulte <[EMAIL PROTECTED]> wrote: > It could be that the DS10 was sufficiently catatonic to not react to > a break (how likely is that in the first place? I was looking at a hard > lockup). If you experience one of the lockups that currently plague -CURRENT/alpha, the machine won't react to

Re: Serial break into debugger broken from 'cu' on -CURRENT?

Robert Watson <[EMAIL PROTECTED]> wrote: > (1) Is serial break currently broken in -CURRENT I can drop just fine into ddb with a serial break on my -CURRENT AlphaPC164. My kernel configuration has option BREAK_TO_DEBUGGER. > (2) Is serial break currently broken in 'cu'? Works just fine from a

Re: Non 386 testers REALLY NEEDED

Wilko Bulte <[EMAIL PROTECTED]> wrote: > C'mon guys: it is not so long ago (days..) that the Alpha started > buildworlding -current again. I tried, and the new kernel blew up at start-up with an unaligned access. GENERIC went farther, but died when /etc/rc redundandly tried to load the osf1 mod

Re: buildworld fails in pam on Alpha

Wilko Bulte <[EMAIL PROTECTED]> wrote: > Now that current on Alpha builds a lot better than a > few days back it fails in: > /usr/src/lib/libpam/libpam/pam_get_pass.c:60: warning: type mismatch in > implicit declaration for built-in function `memset' > /usr/src/lib/libpam/libpam/pam_get_pass.c:6

Re: Anonymous FreeBSD CVS Servers

Glenn Gombert <[EMAIL PROTECTED]> wrote: > Are there any FreeBSD 'Anonymous' FreeBSD Servers avaiable besides: > ":pserver:[EMAIL PROTECTED]:/home/ncvs" , anoncvs.de.openbsd.org -- Christian "naddy" Weisgerber [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PR

Re: cp in INSTALLTMP?

John Baldwin <[EMAIL PROTECTED]> wrote: > Yes, I've seen this. I'm betting it is timing related, and that dfr's fix to > pmap.c will fix this. Indeed it is gone now. "make installworld" works fine without cp. -- Christian "naddy" Weisgerber [EMAIL PROTECTED] To Uns

Re: cp in INSTALLTMP?

Bruce Evans <[EMAIL PROTECTED]> wrote: > > I don't know why nobody else seems to be seeing this, but cp is > > This might be caused by having the sources and objects on different > machines with inconsistent clocks. No, it's all local on a single machine. FWIW, I'm on alpha. > > ===> gnu/usr.b

cp in INSTALLTMP?

I don't know why nobody else seems to be seeing this, but cp is used several times during installworld, which consequently fails for me unless cp is added to INSTALLTMP. ... ===> gnu/lib/libreadline/history install -c -o root -g wheel -m 444 libhistory.a /usr/lib install -c -o root -g wheel -m

Re: more anoncvs servers Re: none

David O'Brien <[EMAIL PROTECTED]> wrote: > > - You need a pretty powerful machine to handle even, say, 4-6 clients > > at a time. Anonymous CVS is a hog like you wouldn't believe. > > I have to wonder if there are tricks one can use. No. Get a gig of memory, and put ~anoncvs/tmp on a memory

Re: more anoncvs servers Re: none

David O'Brien <[EMAIL PROTECTED]> wrote: > What is the right mailing list to plead for more anoncvs mirrors? grappa.unix-ag.uni-kl.de provides anoncvs, among other services. (See http://.../ for a list.) However, - the box runs on OpenBSD, and since all three BSDs appear to use incompatible e

buildworld fails in src/lib/libc/posix1e

... cc -nostdinc -O -pipe -mcpu=ev56 -mcpu=ev56 -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -DLIBC_MAJOR=5 -D__DBINTERFACE_PRIVATE -DINET6 -I/home/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUIL

Re: What's touching my executables?

I wrote: > An increasing number of executables on that box are sporting ever > newer mtimes. This appears to have been going on ever since the > Jul 25 update. There is no clear pattern which executables are > touched. md5 comparisons with previous backup levels (using a Jul 13 > copy of md5)

What's touching my executables?

-CURRENT (Jul 25), alpha. An increasing number of executables on that box are sporting ever newer mtimes. This appears to have been going on ever since the Jul 25 update. There is no clear pattern which executables are touched. md5 comparisons with previous backup levels (using a Jul 13 copy o

Re: What's touching my executables?

Will Andrews <[EMAIL PROTECTED]> wrote: > Probably the recent change (IIRC) that someone turned running an > executable into a mtime change. That was about _atime_ and the discussion was still going on after I last updated the box. Besides, I verified that simply running an executable does not

Re: Anoncvs support

Will Andrews <[EMAIL PROTECTED]> wrote: > A service which, IMO, is still not very well supported. That's probably > one reason why it's hard to get new developers (not everyone feels like > syncing the entire repo). But then again, I wonder how much load there > is on anoncvs.freebsd.org. Stil

Re: new breakage in mounting root? a devfs issue?

Andrea Campi <[EMAIL PROTECTED]> wrote: > Seriously, if it's a new breakage, it's not breaking for everybody. As I already reported to -alpha, it's breaking for me (sources as of ~March 10) with a custom kernel. Doesn't happen with GENERIC. -- Christian "naddy" Weisgerber

Re: tape device names and devfs

Steve Kargl <[EMAIL PROTECTED]> wrote: > The "r" in tape device names has traditionally meant "r"ewind. No. We've been over this before. If you check the old 4.xBSD releases, the 'r' clearly means "raw device". Once upon a time there were tape block devices. > The rewind and non-rewind tape d

Re: tape device names and devfs

Steve Kargl <[EMAIL PROTECTED]> wrote: > > > dump.8 and dump(8) both refer explicitly to rsa0 and nrsa0 whereas > > > sa0 and nsa0 are the actual device names in -current. > > > > Then this should be fixed. > > But, what is the correct fix? Add symlink magic to rc.devfs? > Change dump(8)? Yes

Re: tape device names and devfs

Steve Kargl <[EMAIL PROTECTED]> wrote: > dump.8 and dump(8) both refer explicitly to nsa0 and nrsa0 whereas > sa0 and nsa0 are the actual device names in -current. Then this should be fixed. The non-'r' device names have been standard in -CURRENT for quite some time. MAKEDEV only creates 'r'-na

Re: dump(8) segfaults

Matthew Jacob <[EMAIL PROTECTED]> wrote: > Yup. Looks like it got broken. File a PR- Done. > or if you can, find out who made recent changes to dump and ask > them about it. phk did, but those changes look harmless. In fact, I just backed them out and dump still segfaults. This problem is tr

dump(8) segfaults

This is on alpha--does anybody see this on i386 as well? naddy@kemoauc[~] dump 0af /dev/null /dev/da0a DUMP: Date of this level 0 dump: Sun Feb 25 15:33:49 2001 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/da0a (/) to /dev/null DUMP: mapping (Pass I) [regular files] DUM

Re: RFC: user-config alt path in Linux emulation

Andrea Campi <[EMAIL PROTECTED]> wrote: > The net effect is that there is no way to, for instance, back up the > real /usr from Tivoli, etc... as there is no way to get to a real path > if there is anything with the same name inside /compat/linux. Loopback NFS mount. -- Christian "naddy" Weisg

Re: weird cvs update problem

Brian Somers <[EMAIL PROTECTED]> wrote: > ISTR Christian Weisgerber <[EMAIL PROTECTED]> was having this problem > too. Sorry, you're misremembering. I've never seen anything like this. -- Christian "naddy" Weisgerber [EMAIL PROT

Re: mergemaster and $FreeBSD$

Archie Cobbs <[EMAIL PROTECTED]> wrote: > even worse, mergemaster in some cases seems to be comparing only > the $FreeBSD$ strings and incorrectly concluding that certain > files don't need upgrading, when in fact they do. If the -s switch isn't specified, mergemaster compares id strings first,

Re: tar : needs some attention?

John W. De Boskey <[EMAIL PROTECTED]> wrote: > tar: cdrom/disc2/dev/acd0t39: minor number too large; not dumped > >Is this the expected behaviour, Expected behavior; you can't store 32-bit minor numbers in tar's archive format. -- Christian "naddy" Weisgerber [EMA

Re: -Current + X 4.0.1 = mouse problems

Doug Barton <[EMAIL PROTECTED]> wrote: > Previously I had X + moused working just fine, so I had the best > of both worlds. With X 4.0.1 if I use moused I get no response from the > mouse in X at all. Make sure you use Option "Protocol" "MouseSystems" Protocol "Auto" is not

Re: "fetch | sh" panics system

Christian Weisgerber <[EMAIL PROTECTED]> wrote: > The following, completely innocuous command line > $ fetch -o - http://sites.inka.de/mips/unix/freebsd/xterm.shar | sh > executed as a non-priviledged user, reproducibly panics the machine. It's caused by fdesc mounted on /de

Re: "fetch | sh" panics system

Christian Weisgerber <[EMAIL PROTECTED]> wrote: > The following, completely innocuous command line > $ fetch -o - http://sites.inka.de/mips/unix/freebsd/xterm.shar | sh > executed as a non-priviledged user, reproducibly panics the machine. Some people have mailed that this par

"fetch | sh" panics system

5.0-CURRENT from ~May 17, dual ppro. The following, completely innocuous command line $ fetch -o - http://sites.inka.de/mips/unix/freebsd/xterm.shar | sh executed as a non-priviledged user, reproducibly panics the machine. - #0 boot (howto=256) at ../../kern/kern_shutdown.c:30

Re: Internal USR I-modem & current?

Timo Geusch <[EMAIL PROTECTED]> wrote: > I recently got my hands on an internal Courier I-Modem. [...] > Any ideas where I need to look to get this card configured by the PnP > mechanism? Have you jumpered the card correctly? I don't know whether those details were changed over the lifetime of

Re: Anyone else seeing jumpy mice?

Stijn Hoop <[EMAIL PROTECTED]> wrote: > I do have /dev/psm0 in my XF86Config. You're saying it is better to > use /dev/sysmouse, Protocol moused? If you have moused running, set XF86Config to /dev/sysmouse, protocol "MouseSystems". -- Christian "naddy" Weisgerber [EMAI

Re: Wide-char support and libc

(This should move to freebsd-i18n.) Donn Miller <[EMAIL PROTECTED]> wrote: > Anyone like the idea of adding wide char support to our libc? I'd like the idea of somebody explaining where/how I can get an overview of what's missing in the first place. > Maybe we could port it over from {Net,Open

Re: cvsup on recent -CURRENT

(My original question should have gone out last Thursday but had been stuck in a mail queue since.) Nick Hibma <[EMAIL PROTECTED]> wrote: > > TreeList failed: Network write failure: Connection closed > > Which host are you pilling from? I am slurping things out of > cvsup.uk.freebsd.org and see

cvsup on recent -CURRENT

On this machine which runs -CURRENT from two days ago or so, I'm seeing frequent cvsup client failures of this type: TreeList failed: Network write failure: Connection closed I don't recall ever running into this before. -- Christian "naddy" Weisgerber [EMAIL PROTECTED] T

unknown:

I just updated an i386 machine after a month to the latest 5.0-CURRENT, and I now get some strange boot messages: isa0: too many memory ranges ... unknown0: at port 0x20-0x21,0xa0-0xa1 irq 2 on isa0 unknown1: at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 unknown2: a

Re: Undocumented tape devices in pax(1)

Greg Lehey <[EMAIL PROTECTED]> wrote: > I suspect that's an assumption on your part. I think we've come up > with enough man pages to support naddy's statement. Which, btw, was drawn from inspection of MAKEDEV in the various 4.xBSD releases in the CSRG archives (Kirk's CD set). Personally, I ta

Re: Undocumented tape devices in pax(1)

Mike Smith <[EMAIL PROTECTED]> wrote: > The 'r' prefix for tape devices is entirely unrelated to the 'r' prefix > for disk devices. I'd like to see some backup for this assertion. Historically, BSD (up to 4.4) used to have mt block device, rewinding nmt block device, non-rewinding

Re: Undocumented tape devices in pax(1)

Kris Kennaway <[EMAIL PROTECTED]> wrote: > Can someone explain to me why pax(1) has (undocumented) switches which > select some tape devices, but apparently randomly numbered ones: Note that these switches appear only in pax' tar compatibility personality, which isn't used in FreeBSD. And the re

Re: gcc -Os optimisation broken (RELENG_4)

David O'Brien <[EMAIL PROTECTED]> wrote: > What??? 'pentiumpro' code isn't going to be very optimized for a Pentium > (if it even runs at all). According to the gcc(1) man page, -mpentiumpro is synonymous to -mcpu=pentiumpro, which only affects instruction scheduling but not the actual instruct

Re: gcc -Os optimisation broken (RELENG_4)

Doug Barton <[EMAIL PROTECTED]> wrote: > Hmm... If I have a PII (Actually celeron 300A) or a PIII, which is > better, 'pentium' or 'pentiumpro'? I would think the latter, but I've I have to admit that I kind of lost track of Intel's Pentium du jour offerings after the PPro, but I think PII

Re: gcc -Os optimisation broken (RELENG_4)

Maxim Sobolev <[EMAIL PROTECTED]> wrote: > I've just upgraded my production server to the 4.0-RELEASE and found that > squid23 when compiled with -Os option dying with signal 11 on each attempt to > load page. When I recompiled it with -O fault disappeared. Which brings us back to the popular to

Re: ssh strangeness in -current...

Sheldon Hearn <[EMAIL PROTECTED]> wrote: > What about the off-by-one hostkey length problem? The client gives a warning when you connect to an old server with this problem. > Is it supposed to be possible to drop a "1024-bit" host key from > the old ssh1 port into /etc/ssh ? I have switched se

Re: ssh strangeness in -current...

Brad Knowles <[EMAIL PROTECTED]> wrote: > I've been following this thread for a while, and I'd like to ask > a related question -- can anyone else successfully use scp with > OpenSSH? An emphatic YES--for incrementally improving versions of OpenSSH over the last couple of months, on Free

Re: ssh strangeness in -current...

Oliver Fromme <[EMAIL PROTECTED]> wrote: > I can't cvsup on that -current box, it's too small for a > "make world" (and probably too slow, too). I just downloaded > the 2228-current snapshot and installed it. In that case: See section 6.5 of the handbook. -- Christian "naddy" Weisgerber

Re: openssh question

William Woods <[EMAIL PROTECTED]> wrote: > Now that openssh is in the base system, I assume it will no longer > be in the ports. I expect the port to be maintained for the remaining lifetime of the 3.x branch. This is of no concern to 4.x users, of course. > How do we update it, ie, when a upda

Re: openssl in -current

Jeffrey J. Mountin <[EMAIL PROTECTED]> wrote: > My big question is - Do we really want to force a 'make world' on the those > that want RSA support in openssl? We don't want to and WE DON'T DO. > That would be ugly, when before it was simply the matter of building only > two ports. binary inst

Re: openssl in -current

David O'Brien <[EMAIL PROTECTED]> wrote: > While I don't know is how OpenBSD builds the two sets of bits, I do know > how easy it was for me as a user to install 2.6 and get a RSA enabled > crypto lib. Alas, if I understand Jordan correctly, he objects exactly to this additional installation st

Re: openssl in -current

David O'Brien <[EMAIL PROTECTED]> wrote: > How does OpenBSD deal with it? Why is it so easy for them? 0. RSA situation In the USA, the RSA algorithm(!) is patented by RSA Inc. It doesn't matter where the actual code is from, any use of RSA needs permission by the patent holder. RSA Inc. provid

Re: annoying problem with ncurses, acs_chars and xterm

Jose M. Alcaide <[EMAIL PROTECTED]> wrote: > I found an annoying problem: the line drawing chars are not drawn > in xterms. I haven't examined this issue in detail, but the line drawing works fine with a current xterm instead of the stale one shipping with XFree 3.3.6, so it can't be purely a te

Re: /usr/src/Makefile.inc1: make update

Bill Fumerola <[EMAIL PROTECTED]> wrote: > As the person who implemented PORTSSUPFILE, I'd object. Originally > SUPFILE2 was set to the ports-supfile, so to preserve original > behavior (that is, updating ports along with src/) that stayed in. Very well. > To some of us, updating both at the sa

/usr/src/Makefile.inc1: make update

Why does "make update" in /usr/src also include a cvsup of /usr/ports? Since /usr/ports and /usr/docs have Makefiles and "update" targets of their own, and the alternative update by cvs doesn't cover /usr/ports either, I suggest to remove the /usr/ports cvsup from Makefile.inc1's "update" target.

Re: So, tell me again why we can't read audio CDs in SCSI drives?

Jordan K. Hubbard <[EMAIL PROTECTED]> wrote: > Any other SCSI CD owners here currently using tosha? I'd be > quite interested to know if this is drive-specific. Works for me. 4.0-CURRENT from December 19, Toshiba CD-ROM XM-3601TA 0175, tosha-0.6. -- Christian "naddy" Weisgerber

Re: OpenSSL update

Kris Kennaway <[EMAIL PROTECTED]> wrote: > I have it building fine, although compiling without RSA seems > broken in openssl 0.9.4. Well, it works fine in the OpenBSD tree. You might want to take a look at what's been done there. -- Christian "naddy" Weisgerber [EMAIL PROTECTE

Re: Netscape core dump, happily :-)

Chris Piazza <[EMAIL PROTECTED]> wrote: > Disable Javascript and the problem will go away (ugh). I have JavaScript disabled by default. Still, navigator frequently crashes on close or (I couldn't care less) exit. -- Christian "naddy" Weisgerber [EMAIL PROTECTED] To Unsubscr

Re: Netscape core dump, happily :-)

Gianmarco Giovannelli <[EMAIL PROTECTED]> wrote: > Is there anyone who is experienced Netscape crashes with 4.0-CURRENT when > the close button is pressed (not always, but very often) ? Same here. Navigator 4.61. Previous versions didn't show this behavior. -- Christian "naddy" Weisgerber

Re: ES1370 Sound problems

Joe Clarke wrote: > I currently re-added my es1370-based Ensoniq soundcard to my FreeBSD 3.2 > system with the hope of getting Luigi's sound driver working with it. > > es1: rev 0x00 int a irq 10 on pci0.15.0 ^^^ > pcm1: using I/O space register mapping at 0x1800 At least with 4.0-CURRENT th

Re: buildworld failure as of 1999-03-08

Hmm, must have been a gremlin. cvsup'ed again yesterday (didn't look like anything related to the problem had changed), did another buildworld, and this time it worked. Oh, well. -- Christian "naddy" Weisgerber na...@mips.rhein-neckar.de >H Deutsche Transhumanismus-Mailinglist

buildworld failure as of 1999-03-08

I cvsup'ed the latest source yesterday evening/this morning and started a "make buildworld". ===> gnu/usr.bin/perl/perl ... Writing Makefile for Fcntl mkdir /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/Fcntl mkdir /usr/obj/usr/src/gnu/usr.bin/perl/perl/build/Fcntl/auto mkdir /usr/obj/usr/src/gnu/u

  1   2   >