14 stable Guided Root-on-ZFS with 2 disk mirror

from just the second disk after copying the EFI partition from the first disk to the second. - Is this known/expected behaviour? I was expecting to be able to boot from the second disk without having to copy the efi partition. Thanks Mikhail

Re: freebsd-current Digest, Vol 789, Issue 3

Отмена 12 дек. 2018 г. 14:30 пользователь написал: Send freebsd-current mailing list submissions to freebsd-current@freebsd.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.freebsd.org/mailman/listinfo/freebsd-current or, via email, send a message with

Re: ipfilter fails to compile WITHOUT_INET6

On 22.06.2017 21:20, Cy Schubert wrote: Can you try the attached patch please? Yes, replacing: -#ifdef AF_INET6 +#ifdef USE_INET6 lets the build succeed. Is it Ok to modify stuff under contrib/ though?.. -mi ___ freebsd-current@freebsd.org

Re: logged errors with current drm stuff

On 07:32 22-Jan 2015 Adrian Chadd wrote: > Hi! > > I'm seeing this with your patch now: > > error: [drm:pid5:i915_gem_object_unbind] *ERROR* Attempting to unbind > pinned buffer > > Nothing seems to be problematic at the moment; but it does seem to > happen quite frequently. > > Any ideas? To

Re: CURRENT breaks build of x11/nvidia-driver: pkg-static: nvidia-driver-343.22 conflicts with libEGL-10.3.2

a-driver port. For now I deinstalled both libglesv2 and libEGL with pkg delete -f after that I was able to install nvidia-driver. -- Mikhail ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Locking console with Ctrl-S hangs various processes (ttydcd)

Hello! A fellow FreeBSD user was recently confounded by a problem: various processes on his 10.0 system were hanging or otherwise misbehaving: su, certain daemons, syslogd. They were all hung in the "ttydcd"-state. Searching for that revealed only

Re: md2 on current and 10.

On 08.01.2014 20:05, Peter Wemm wrote: > The path of least resistance is to make a libmd2 port. It's the only way I > can see you getting to use it on 10.0. *I* don't really care. *I* don't use md2 myself. I became aware of the problem by accident -- because one of my ports was affected (tcl-trf).

Re: md2 on current and 10.

On 08.01.2014 02:54, Peter Wemm wrote: >> > Could we, please, have MD2 resurrected before 10.0 is officially out? >> > Preferably in both -lmd and -lcrypto, but certainly in the former. Thank >> > you! Yours, > The time to bring this up was before the freeze for 10.0, a good 6+ > months ago. It is

Re: md2 on current and 10.

On 27.12.2013 10:50, Ulrich Spörlein wrote: >> In other words, /if you like your digest algorithm, you can keep it/. Yours, > Seconded. What should people use if some of their old data is using MD2 > for verification? How can they now easily check that their data (from > tape or whatever) still mat

Re: md2 on current and 10.

On 20.12.2013 13:38, olli hauer wrote: > md2 was deprecated in 2009 by the openssl project > > http://cvs.openssl.org/chngview?cn=18381 > CVE-2009-2409 > > As fas as I know some Linux based projects have removed md2 from > openssl-0.9.x in 2009. So, when are we removing sum(1) and cksum(1) -- im

Re: md2 on current and 10.

Thinking more about the MD2, I'd say, FreeBSD should not have removed the algorithm. Although no longer deemed sufficiently secure, it is still in use and people using it on FreeBSD-8.x and 9.x today may wish to continue doing so after upgrading to 10.x In the old "Mechanism vs. Policy" debate <

Re: md2 on current and 10.

On 20.12.2013 12:52, olli hauer wrote: > Hm the config script tests for md2 and sha1 ... > What happens if md2 support is removed from the code? Yes, the md2 can be removed from the set of digests made available by the port -- that's not a problem. What I wanted to know, was why? Maybe, the header

md2 on current and 10.

It would appear, neither nor are any longer available on FreeBSD current and 10.x This breaks the devel/tcl-trf port, which I maintain... Could someone, please, comment? Should I patch-up the port to disable the functionality? Or?.. Thank you! -mi _

patch -p broken on HEAD?

On 30.11.2013 13:24, pkg-fall...@freebsd.org wrote: > ===> Applying FreeBSD patches for xmdiary-3.0.3_3 > removing the malloc.h includes > /bin/sh /usr/ports/deskutils/xmdiary/scripts/nomalloc > /wrkdirs/usr/ports/deskutils/xmdiary/work/xmdiary-3.0.3 2>&1 > /dev/zero > patch: option requires an a

Re: ports include /etc/src.conf? i.e. graphics/libfpx

15.02.2013 19:12, Ian Lepore ???(??): > The src.conf manpage is not in error. The intent is that src.conf > applies only to the building of the freebsd world and kernel, that is, > the source that's usually located under /usr/src. If settings from > src.conf are leaking into other builds, the

Re: ports include /etc/src.conf? i.e. graphics/libfpx

14.02.2013 09:34, Peter Pentchev ???(??): However, there is then the argument of "well, if you want to use the bsd.*.mk infrastructure, then why don't you just copy it into your project and include it from there - just like many, many projects do with, say, the sys/queue.h header, or parts

Re: ports include /etc/src.conf? i.e. graphics/libfpx

14.02.2013 08:55, Tom Evans написав(ла): > On Thu, Feb 14, 2013 at 1:12 PM, Mikhail T. wrote: >> > I may sound defensive here, but I'll still repeat, that "this singular >> > port" >> > (and I do, in fact, have other ones like it) started using bsd

Re: ports include /etc/src.conf? i.e. graphics/libfpx

14.02.2013 08:02, Tom Evans написав(ла): > I think src.conf is meant only to be included when building src. For > example, bsd.port.mk sets _WITHOUT_SRCCONF before including bsd.own.mk > (which is the makefile that includes src.conf). It's done this since > src.conf was added in 2006, so evidently

Re: Re: ports include /etc/src.conf? i.e. graphics/libfpx

13.02.2013 11:22, O. Hartmann написав(ла): >> > If this is taken literally then could it be said that ports that use >> > bsd.lib.mk are broken because they are using makefile includes from >> > the source tree? >> > >> > -Kimmo For one, the particular port (its Makefile.bsd) was created in 2001,

editors/openoffice-1.1: random g++ "internal compiler error"

Stay current! Trying to build openoffice-1.1 from ports but when it comes to .cxx strange things begin In file included from /usr2/ports/editors/openoffice-1.1/work/oo_1.1_src/ solver/645/unxfbsd.pro/inc/vcl/svapp.hxx:87, from /usr2/ports/editors/openoffice-1.1/work/oo_1.1_src/

Re: lock order reversal is 5.2-BETA Nov 26

> On Thu, Nov 27, 2003 at 07:16:05PM -0500, Mikhail Teterin wrote: > > It did not crash or anything, but the following is printed on > > console now (addresses ommitted): > > > > lock order reversal > > 1st ... UMA lock (UMA lock) @ /usr/src/sys/vm/uma_co

ath driver not working...

According the the man-page, this is not supposed to happen: ath0: mem 0xe020-0xe020 irq 9 at device 11.0 on pci2 ath0: cannot map register space The machine is Sony Vaio TR2/B. The WiFi works fine from Windows (much better than the Orinoco card in another laptop). -mi __

lock order reversal is 5.2-BETA Nov 26

It did not crash or anything, but the following is printed on console now (addresses ommitted): lock order reversal 1st ... UMA lock (UMA lock) @ /usr/src/sys/vm/uma_core.c:1201 2nd ... system map (system map) @ /usr/src/sys/vm/vm_map.c:2210 Stack backtrace:

kmem_mmap_toosmall -- repeatable panic

Hello! I tried to create a cscope's database with about 6200 files listed in the cscope.files. The entire tree (including the cscope.files) is mounted over NFS from a Solaris server. The July 11th kernel would just crash, today's one is more intelligent: kmem_malloc(4096): kmem_mmap_too_

Re: gcc-3.3 issues

On Thu, 17 Jul 2003 22:18:38 +0200 Michael Nottebrock <[EMAIL PROTECTED]> wrote: => On Thursday 17 July 2003 22:11, Alexander Kabaev wrote: => => > -Werror? As doctor said: if it hurts, DON'T DO THAT. => => In the kdelibs case, it's definitely _not_ -Werror =Whatever it is, I haven't seen one

Re: ``Resource temporarily unavailable'' in vi

=>Every once in a while, a vi-session dies on me with: => => input: Resource temporarily unavailable =Are you running ksh93 per chance? I've seen this after I started an =OpenGL program such as xscreensaver-demo from ksh93 (however that =could have influenced the terminal settings or whateve

``Resource temporarily unavailable'' in vi

Every once in a while, a vi-session dies on me with: input: Resource temporarily unavailable What does it mean, why does it happen, and how can I prevent it? Thanks a lot! -mi P.S. Running recent -current. ___ [EMAIL PROTECTED] mail

problem with a file-backed md

Hello! I have a nasty problem with a file-backed md. The file is the Windows' swap file residing on a msdosfs part of the drive. First I tried to just swapon to the md: tmp=`mdconfig -a -t vnode -f /W/pagefile.sys` swapon $tmp But random big-memory programs were hanging. At that

comms/birda on -current and PalmPilot sync.

Hi! Does the combo in subject work for anyone? I have Win98 on this laptop, too, and it can sync. the palm over the IrDA port. However, with FreeBSD-current it does not work. Birda's irs is running as /opt/bin/irs -y /dev/ptypv -c -d /dev/ttyd1 -Y and I point coldsync to the correspondi

Re: continuing problems with RealPlayer

On Sunday 26 January 2003 02:28 pm, Gary Jennejohn wrote: = Mikhail Teterin writes: = > Can anyone, please, try the following URL, for example: = > = > pnm://rm.content.loudeye.com/~ttt-600111/0619060_0103_00_0002.ra = > = = Yup, kills my RealPlayer too. -stable or -current?

continuing problems with RealPlayer

Can anyone, please, try the following URL, for example: pnm://rm.content.loudeye.com/~ttt-600111/0619060_0103_00_0002.ra It causes RealPlayer8.cs2 to get SIGABRT on two of my -current systems. I must have it working on at least one machine in the house, but before changing the laptop to

keeping the Promise up

Hi! With the day-old -current I have troubles with the Promise-66 IDE add-on card. I have two identical drives connected to it. The one connected to the "IDE1" connector is now constantly reported as: ad4: READ command timeout tag=0 serv=0 - resetting ata2: resetting devices ..

Re: troubles with realplay-er

Julian Elischer wrote: me too A 5.0-RELEASE showstopper? -mi On Sat, 4 Jan 2003, Mikhail Teterin wrote: This Linux program used to work well, but now it crashes (with SIGABRT) some URLs, such as pnm://rm.content.loudeye.com/~iii-600111/0255135_0101_00_0002.ra pnm

troubles with realplay-er

This Linux program used to work well, but now it crashes (with SIGABRT) some URLs, such as pnm://rm.content.loudeye.com/~iii-600111/0255135_0101_00_0002.ra pnm://rm.content.loudeye.com/~a-600111/0631342_0103_00_0002.ra or hangs... The crashes are persistent -- the same URL will a

Re: pam_setenv() crashes rshd...

> Mikhail Teterin <[EMAIL PROTECTED]> writes: > > The following patch fixes (works around?) the problem for me > > (pam_setenv is rather inefficiently implemented by the vendor, BTW), > I am the vendor. What's wrong with pam_setenv()? I only went into the code to

pam_setenv() crashes rshd...

The rshd started to crash on my system after the recent -current upgrade. It does not dump core (why?), but with a lot of syslog() I narrowed the trouble spot down to the pam_setenv() calls -- the very first one of them, in rshd.c never returned... The libpam is: /usr/lib/libpam.so.2: $FreeBS

Re: -current unusable after a crash

On Monday 25 November 2002 12:24 pm, Kris Kennaway wrote: = On Mon, Nov 25, 2002 at 10:24:46AM -0500, Robert Watson wrote: = = > > I thought, this might be due to the priority of the background = > > fsck and have once left it alone for several hours -- with no = > > effect. The usual fsck takes a

-current unusable after a crash

The only way to get my -current system back to normal after a crash is to boot into single user and do an explicit ``fsck -p''. Otherwise the system will, seemingly, boot fine, but none of the ttyvs will accept any input, although tty-switching works fine. Remote connections (ssh, telnet) don't br

New NVidia drivers on -current

Has anyone tried them yet? After removing the #error triggered by __FreeBSD_version being over 50, I got the thing nvidia.ko to build, but: 00:50:30 aldan shutdown: reboot by root: New world, kernel. Nvidia drivers 00:56:12 aldan kernel: Preloaded elf module "/boot/kernel/nvidia.ko" at 0xc064

Re: dc and PCMCIA still panic

> Even though it doesn't make sense, can you turn on the debugging > information and run again? I use > > # Let's debug! > hw.cbb.debug=1 > hw.pccard.debug=1 > hw.pccard.cis_debug=1 > hw.cardbus.debug=1 > hw.cardbus.cis_debug=1 Actually, I lied... It is a Xircom RealPort Ethernet 10/100 + Mode

dc and PCMCIA still panic

Today's kernel (cvs update-ed 10 minutes ago) keeps panicing when the dc-card is inserted :-/ The panic always happens in Fatal trap 12 [...] db> trace pccard_scan_cis([data],0,0) at pccard_scan_cis+0x1a5 pccard_read_cis([data]) at pccard_read_cis+0xb5

Re: panic: kmem_malloc(4096): kmem_map too small

îÅĦÌÑ 06 öÏ×ÔÅÎØ 2002 03:13 am, n0g0013 ÷É ÎÁÐÉÓÁÌÉ: > On 06.10-03:06, Mikhail Teterin wrote: > > this machine has a total of 512Mb of RAM, and no swap. > > No X was running. Just ``cvs update''-ing. > > running vinum ? i am getting this consistently with v

panic: kmem_malloc(4096): kmem_map too small

... 218222592 total allocated this machine has a total of 512Mb of RAM, and no swap. No X was running. Just ``cvs update''-ing. -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: signal 6 to XFree86 (Re: cvs commit: src/tools/tools...)

[Moved to -current] > On Fri, Oct 04, 2002 at 06:30:09PM -0700, Lars Eggert wrote: > > Wesley Morgan wrote: > > >I had one today, they have decreased significantly since removing the > > >Type1 module from my server configuration. > > > > I've also found that disabling xscreensav

Re: laptop panicked [with trace]

> * De: Mikhail Teterin <[EMAIL PROTECTED]> [ Data: 2002-10-02 ] > [ Subjecte: laptop panicked [with trace] ] > > With today's -current. No X11, two ttyv0 in use -- cvs updating, the > > other -- playing hack(6): > > This is known; A temporary fix is t

laptop panicked [with trace]

With today's -current. No X11, two ttyv0 in use -- cvs updating, the other -- playing hack(6): Fatal trap 12: page fault while in kernel mode fault virtual address = 0xbc [... retyped, not copy-pasted, seemingly random numbers marked ``skipped'' ...] kernel: type 12 trap, code=0 Stopped at

hack(6) does not run in xterm!

Just noticed on my FreeBSD 5.0-CURRENT #0: Thu Sep 26 11:07:24 EDT 2002 % hack Terminal must backspace. Here is the end of the ktrace: [...] 41386 hack RET break 0 41386 hack CALL break(0x8089000) 41386 hack RET break 0

Re: troubles with recent -current

> On Wed, 25 Sep 2002, Mikhail Teterin wrote: > > FWIW, this -- introducing this sort of instability just two months > > before the scheduled release -- is a lot more damaging than the > > stupid trolls, IMO. The finger-breakers should consider leaving the > > troll a

Re: troubles with recent -current

> On Wed, 25 Sep 2002, Mikhail Teterin wrote: [...] > > Unless I set rc_ng to NO, the ypbind will not start, even though > > enable_nis_client is set and "Starting ypbind" is displayed on boot. > Locally, I discovered that the hard dependency of ypbind on rpcbind &

troubles with recent -current

Hi! I'm experiencing an increasing amount of problems here, and will try to list them below. Some of this may be well known already, but, hopefully, something will be usefull. Unless I set rc_ng to NO, the ypbind will not start, even though enable_nis_client is set and "Starting ypbind" is displa

freeze with the CardBus NIC 3CCFE575BT

Regardless of whether the xl driver is linked into the kernel or loaded as a module, the machine freezes shortly after ifconfig-ing the card. Sunday's -current. Complete freeeze -- can not go into debugger... More information available upon request... -mi To Unsubscribe: send mail to [E

troubles with the new GCC -- anyone else?

Is it just me, or do others have troubles too? I upgraded yesterday: mi@celsius:~ (101) cc -v Using built-in specs. Configured with: FreeBSD/i386 system compiler Thread model: posix gcc version 3.2.1 [FreeBSD] 20020901 (prerelease) With ``-march=pentium2 -

Re: HEADS UP: GCC 3.2.1-pre imported

On Sunday 01 September 2002 05:58 pm, Alexander Kabaev wrote: = GCC 3.2.1-pre is now in the tree. Please let me know if you see any = problems recompiling your world/kernel. = = Remember to recompile your C++ ports. GCC 3.2 is not binary compatible = with 3.1. Most excellent! Thanks! -mi

Dual AthlonMP and FreeBSD

Hi! Would FreeBSD (-current or -stable) work (in SMP mode) on a pair of Athlons, or is our SMP only for Intel chips? Thanks! -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

unkillable process :-\

KOffice's kword is stuck here... Can not be killed even with -9. Sits idle, with its window open, but not updating: UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 1042 88248 1 0 96 0 119296 28105 - WWs pm0:00,00 kword /tmp/k Machine is otherwise fin

Re: recent bsd.lib.mk changes

On Friday 21 June 2002 06:02 pm, David O'Brien wrote: = On Fri, Jun 21, 2002 at 05:46:17PM -0400, Mikhail Teterin wrote: = > Why can't we have some way to explicitly list what is and what is not = > needed? = = Feel free to send a patch adding "ONLYSHAREDLIBS". "I

Re: recent bsd.lib.mk changes

On Friday 21 June 2002 04:28 pm, David O'Brien wrote: = On Fri, Jun 21, 2002 at 02:29:33PM -0400, Mikhail Teterin wrote: = > I used to define INTERNALLIB to avoid building and installing the = > static version, but that is now almost reversed -- only the static = > will be built an

recent bsd.lib.mk changes

I guess I missed them, but now some of my ports -- which use bsd.lib.mk -- don't work on -current :-\ and I don't know how to fix them in the backward-compatible way. The ports -- such as devel/tcl-memchan, for example, only want to build and install the shared versions of the libraries. I used

IPC, npc, nwfs on -current

Any plans/updates for the subj? I did what was needed to compile the npc and nwfs modules here (proc -> thread transitions), but IPX is not even mentioned in NOTES -- any hope? -mi -- ëÁË, ÷Ù ÒÁÚ×Å ÂÅÚ ÛÐÁÇÉ ÐÒÉÛÌÉ? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscri

Re: does the order of .a files matter?

On Monday 13 May 2002 02:06 am, Terry Lambert wrote: = > If you think that providing bits on the link line in dependency = > order is a natural way of linking and the "proper" way of doing = > it, how do you explain our improper use of putting object files in = > lexical order in libraries and ho

Re: cvs commit: src/sbin/newfs newfs.8 newfs.c

On Friday 10 May 2002 03:35 pm, Giorgos Keramidas wrote: = On 2002-05-02 23:06, Makoto Matsushita wrote: = > = > Mikhail.Teterin> BTW, whatever became of the effort to make a = > Mikhail.Teterin> wrapper called mount_mfs? = > = > See mdmfs(8). It was been there since Jun/2001 (about 10 months = >

Re: does the order of .a files matter?

On Friday 10 May 2002 04:35 pm, Terry Lambert wrote: = Mikhail Teterin wrote: = > = For my information: Why didn't you take John De Bowsky's advice to: = > = = > = ld $objlist `lorder $liblist | tsort -q` = > = > I tried that before I asked on the mailing list t

Re: does the order of .a files matter?

On Friday 10 May 2002 12:51 pm, Terry Lambert wrote: = Mikhail Teterin wrote: = > > > Is there a reason for it, or this just a not-yet-implemented = > > > feature? It certainly seems like the latter -- why make the user = > > > jump through all the sorting/reordering

Re: does the order of .a files matter?

> > Is there a reason for it, or this just a not-yet-implemented > > feature? It certainly seems like the latter -- why make the user > > jump through all the sorting/reordering hoops? > Generally, this won't be necessary for properly organized code. The > code in question is organized by softwa

Re: does the order of .a files matter?

On Wednesday 08 May 2002 09:52 pm, Terry Lambert wrote: = Mikhail Teterin wrote: [...] = > The most frustrating thing is, the number of such symbols varies = > greatly with the order, in which I list the libraries on the command = > line. Is not the linker supposed to make several runs

panic: bad peter

Using ``FreeBSD 5.0-CURRENT #0: Wed Feb 27 02:00:14 EST 2002''. While cvs updating in /usr/ports: TPTE at 0xbfca0348 IS ZERO @ VA 280d2000 panic: bad peter cpuid = 0; lapic.id = 0100 Looks like there was plenty committed to src/sys in the last few hours, so I'm rebu

Re: panic: bdwrite: buffer is not busy

On 10 Feb, Bruce Evans wrote: > On Sat, 9 Feb 2002, John Baldwin wrote: > >> On 09-Feb-02 Mikhail Teterin wrote: >> > While attempting to ``fdisk fd0.1440''. Or ``fdisk fd0''. Or >> > ``newfs_msdos fd0.1440'' with or without

Re: How about gcj? (Re: Not committing WARNS settings...)

On 6 Feb, David O'Brien wrote: >> http://www.gnu.org/manual/bfd-2.9.1/ >> >> for example, seems to imply, that there was, in fact, at some point a >> release 2.9.1 of bfd... It does not quite match the bfd, > No, that document describes the BFD that was included with Binutils > 2.9.1.

Re: How about gcj? (Re: Not committing WARNS settings...)

On 6 Feb, David O'Brien wrote: > On Wed, Feb 06, 2002 at 03:46:22PM -0500, Mikhail Teterin wrote: >> > dynamically linked libiberty would be a nightmare. >> >> > libbfd and libiberty do not have version numbers, are not >> > maintained (i.e.

panic: bdwrite: buffer is not busy

While attempting to ``fdisk fd0.1440''. Or ``fdisk fd0''. Or ``newfs_msdos fd0.1440'' with or without the floppy inside :-\ With todays or Jan 3rd kernel (my previous upgrade). IdlePTD at phsyical address 0x004ed000 initial pcb at physical address 0x00411560 panicstr: bdwrite: buffer is not busy

Re: How about gcj? (Re: Not committing WARNS settings...)

On 6 Feb, David O'Brien wrote: > Yes it comes as part of binutils. Ok. > No we should not go down this path. You've already been told that > there is no official libiberty or bfd release. Well, the following URL http://www.gnu.org/manual/bfd-2.9.1/ for example, seems to imply,

Re: How about gcj? (Re: Not committing WARNS settings...)

On 6 Feb, David O'Brien wrote: > On Wed, Feb 06, 2002 at 01:05:16PM -0500, Mikhail Teterin wrote: >> > Uh, NO! It is not needed by the base system. We really do not want >> > to turn on all the support libs, etc.. that would be needed with >> > this. Ther

Re: panic: bdwrite: buffer is not busy

On 10 Feb, Bruce Evans wrote: > On Sat, 9 Feb 2002, John Baldwin wrote: > >> On 09-Feb-02 Mikhail Teterin wrote: >> > While attempting to ``fdisk fd0.1440''. Or ``fdisk fd0''. Or >> > ``newfs_msdos fd0.1440'' with or without

panic: bdwrite: buffer is not busy

While attempting to ``fdisk fd0.1440''. Or ``fdisk fd0''. Or ``newfs_msdos fd0.1440'' with or without the floppy inside :-\ With todays or Jan 3rd kernel (my previous upgrade). IdlePTD at phsyical address 0x004ed000 initial pcb at physical address 0x00411560 panicstr: bdwrite: buffer is not busy

Re: libmilter (asking for more trouble :)

On 6 Feb, Gregory Neil Shapiro wrote: > mi> FreeBSD comes with sendmail, and milter is an increasingly popular part > mi> of sendmail -- used by the authors of different spam and virii filtering > mi> software. > > mi> Shouldn't FreeBSD build and install libmilter and the relevant headers, > m

libmilter (asking for more trouble :)

FreeBSD comes with sendmail, and milter is an increasingly popular part of sendmail -- used by the authors of different spam and virii filtering software. Shouldn't FreeBSD build and install libmilter and the relevant headers, too? -mi To Unsubscribe: send mail to [EMAIL PROTECTED]

Re: How about gcj? (Re: Not committing WARNS settings...)

On 6 Feb, David O'Brien wrote: >> http://www.gnu.org/manual/bfd-2.9.1/ >> >> for example, seems to imply, that there was, in fact, at some point a >> release 2.9.1 of bfd... It does not quite match the bfd, > No, that document describes the BFD that was included with Binutils > 2.9.1.

Re: How about gcj? (Re: Not committing WARNS settings...)

On 6 Feb, David O'Brien wrote: > Yes it comes as part of binutils. Ok. > No we should not go down this path. You've already been told that > there is no official libiberty or bfd release. Well, the following URL http://www.gnu.org/manual/bfd-2.9.1/ for example, seems to imply,

Re: How about gcj? (Re: Not committing WARNS settings...)

On 6 Feb, David O'Brien wrote: > On Wed, Feb 06, 2002 at 03:46:22PM -0500, Mikhail Teterin wrote: >> > dynamically linked libiberty would be a nightmare. >> >> > libbfd and libiberty do not have version numbers, are not >> > maintained (i.e.

Re: How about gcj? (Re: Not committing WARNS settings...)

On 7 Feb, Max Khon wrote: > dynamically linked libiberty would be a nightmare. > libbfd anf libiberty do not have version numbers, are not maintained > (i.e. there is no official releases). every project includes its own > libiberty and imho an attempt to find least common denominator w

Re: How about gcj? (Re: Not committing WARNS settings...)

On 6 Feb, David O'Brien wrote: > On Wed, Feb 06, 2002 at 01:05:16PM -0500, Mikhail Teterin wrote: >> > Uh, NO! It is not needed by the base system. We really do not want >> > to turn on all the support libs, etc.. that would be needed with >> > this. Ther

Re: How about gcj? (Re: Not committing WARNS settings...)

On 6 Feb, David O'Brien wrote: > On Wed, Feb 06, 2002 at 11:19:19AM -0500, Mikhail Teterin wrote: >> BTW, how about, may be, if the stars are right, bringing in the Java >> support too? gcj is now one of the compilers, that come with the GCC >> package... > Uh

How about gcj? (Re: Not committing WARNS settings...)

On 6 Feb, Mark Murray wrote: > [...] a project as important as GCC3 [...] BTW, how about, may be, if the stars are right, bringing in the Java support too? gcj is now one of the compilers, that come with the GCC package... And it is promising -- it can compile Java into byte code or b

Re: zombie linux processes remain

On 8 Jan, Alfred Perlstein wrote: >> I'm sure, this is a bug in the program itself (graphics/mtv v. >> 1.2.5), but can't we do something about it? Notice the parent process >> id: >> >> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND >> 105 6536 1 0 9

zombie linux processes remain

Hello! I'm sure, this is a bug in the program itself (graphics/mtv v. 1.2.5), but can't we do something about it? Notice the parent process id: UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND 105 6536 1 0 96 0 00 - Z p40:00,00 (mtvp)

Re: today's current: boot/loader and console

> Are your loader and 4th files in sync? There was a change to the 4th > scripts that I thought I sent a heads up about. Anyways, do this to > get the error message: go into /sys/boot/i386/loader, edit main.c, and > change the exit() function to do a while(1); loop before callign > __ex

Re: today's current: boot/loader and console

> Are your loader and 4th files in sync? There was a change to the 4th > scripts that I thought I sent a heads up about. The hints did not change since forever: -r--r--r-- 1 root wheel2030 Feb 10 2001 device.hints Everything else seems fresh: -r--r--r-- 1 root wheel7721 Jan 3 2

Re: today's current: boot/loader and console

On 3 Jan, John Baldwin wrote: > > On 04-Jan-02 Mikhail Teterin wrote: >> After 25 days of uptime I rebuilt the world, and can no longer boot >> as usual. Both boot/loader and boot/loader.old (from Oct 30) flash >> the list of devices and immediately reset the compu

today's current: boot/loader and console

After 25 days of uptime I rebuilt the world, and can no longer boot as usual. Both boot/loader and boot/loader.old (from Oct 30) flash the list of devices and immediately reset the computer. My only way to bring it up is to press space at the right moment, get the Boot: prompt and load/boot

today's -current: pseudofs

Although pseudofs is now required for procfs to link, config(8) does not know about it -- my old kernel config file with PROCFS raised no problems until the linking time, when a bunch of pseudofs functions turned out to be absent... -mi To Unsubscribe: send mail to [EMAIL PROTECTED] wit

zombie linux processes

I just noticed a whole bunch of processes, that would not go away :-( [...] 105 55742 1 0 107 0 00 - Z p3- 0:00,00 (mtvp) 105 55744 1 5 98 0 00 - Z p3- 0:00,00 (mtvp) 105 55745 1 5 107 0 00 - Z p3- 0:00,00 (mt

panic upon manual swapon(8)

I typicly run without any swap space configured -- 320Mb of RAM is usually fine. However, after noticing a message "get swap space failed" (or similar) in the nightly report, I tried to tell my Nov 5 -current to swapon /dev/da0b I used to do this with full impunity in the past

damaged file system despite unmounts

For a while I was noticing my largest FS reported as not unmounted cleanly on boot. Today I decided to unmount it myself and check it with fsck. Here are the results. Notice, that the first fsck had to mark the FS clean. Notice that the second fsck found something else to do, and only t

Re: ouch -- the second controller on Promise-66 is not detected!

On 31 Oct, Andrey A. Chernov wrote: > On Tue, Oct 30, 2001 at 19:37:27 -0500, Mikhail Teterin wrote: >> Alright, alright, what do I do now? I did NOT wire any ata devices, > Ask Soren to fix ATA driver in the way I describe below: > >> > Giving more details: >> &

Re: ouch -- the second controller on Promise-66 is not detected!

Alright, alright, what do I do now? I did NOT wire any ata devices, and hints only list the on-motherboard ata controllers (one of them has a CD drive attached to it, that's it): hint.ata.0.at="isa" hint.ata.0.port="0x1F0" hint.ata.0.irq="14" hint.ata.1.at="isa"

lots of Linux zombies (mtvp)

(Scary title, is not it?) After watching some MPGs with the Linux binary-only mtvp (graphics/mtv port) I noticed 40 zomby processes: 68278 p1 Z 0:00,00 (mtvp) 68279 p1 Z 0:00,00 (mtvp) 68280 p1 Z 0:00,00 (mtvp) 68281 p1 Z 0:00,00 (mtvp) 68283 p1 Z 0:00,00

installing kernel is troublesome... (patch)

Due, apparently, to the several removed/renamed modules still listed in the sys/modules/Makefile Index: Makefile === RCS file: /home/ncvs/src/sys/modules/Makefile,v retrieving revision 1.201 diff -U1 -r1.201 Makefile --- Makefile

Re: proctitle progress reporting for dump(8)

On 5 Sep, Bruce Evans wrote: > snprintf, strlen, vsnprintf, sysctl, sysctlbyname > > I think all of these are safe in practice. > > It also accesses some variables that are not safe to access in > a signal handler (non-auto ones that are not of type "volatile > sig_atomic_t"

Re: proctitle progress reporting for dump(8)

On 3 Sep, Terry Lambert wrote: >> > >> > I would like it. How often does it update the proctitle? >> >> Whenever it outputs a line to the stderr -- I personally find no >> regularity in that :(. SIGINFO handling is a different thing, though. >> I'll look at that too. Thanks, > It would b

Re: proctitle progress reporting for dump(8)

Ok, attached is the patch addding a function, which sets the proctitle to the last output message and several calls to this function in places, where it looked useful to me. May be, I added too many, and/or skipped some... Note, that I intentially did not put this functionality into the msg

  1   2   3   >