Warner Losh imp at bsdimp.com wrote on
Sat Jan 16 00:22:51 UTC 2021 :
> On Fri, Jan 15, 2021 at 1:03 PM Hartmann, O.
> wrote:
>
> > Running FreeBSD CURRENT on a USB only platform with a customised kernel, I
> > see this
> > message all the time I reboot or log console messages:
> >
> > [...]
> >
From: Mark Millard
Subject: Re: WARNING: Device "kbd" is Giant locked and may be deleted before
FreeBSD 13.0.
Date: Fri, 15 Jan 2021 16:54:26 -0800
> Other examples for the general type of question . . .
>
>
> For example, various aarch64, armv7, and powerpc*:
>
&g
On Fri, Jan 15, 2021 at 1:03 PM Hartmann, O.
wrote:
> Running FreeBSD CURRENT on a USB only platform with a customised kernel, I
> see this
> message all the time I reboot or log console messages:
>
> [...]
> WARNING: Device "kbd" is Giant locked and may be deleted before FreeBSD
> 13.0.
>
> Wher
On 10/26/18 10:48 AM, Dag-Erling Smørgrav wrote:
Rebecca Cran writes:
After installing 12.0-BETA1, on the first boot I noticed a warning
about $local_unbound_tls not being set properly.
Ah, I should probably have added it to /etc/defaults/rc.conf. Can you
do that (just set it to “no”) and let
Rebecca Cran writes:
> After installing 12.0-BETA1, on the first boot I noticed a warning
> about $local_unbound_tls not being set properly.
Ah, I should probably have added it to /etc/defaults/rc.conf. Can you
do that (just set it to “no”) and let me know if it helps?
DES
--
Dag-Erling Smørgr
On Mon, Sep 05, 2016 at 09:09:00AM +0200, Dimitry Andric wrote:
> On 05 Sep 2016, at 03:31, Shawn Webb wrote:
> >
> > On Tue, Aug 30, 2016 at 06:17:02PM -0700, Ngie Cooper wrote:
> >> On Tue, Aug 30, 2016 at 5:54 PM, Matthew Macy wrote:
> >>>
> >>>
> >>> I did a buildworld with llvm39. Unsurpr
On 05 Sep 2016, at 03:31, Shawn Webb wrote:
>
> On Tue, Aug 30, 2016 at 06:17:02PM -0700, Ngie Cooper wrote:
>> On Tue, Aug 30, 2016 at 5:54 PM, Matthew Macy wrote:
>>>
>>>
>>> I did a buildworld with llvm39. Unsurprisingly I had to pass NO_WERROR= as
>>> the llvm has added additional warning
On Tue, Aug 30, 2016 at 06:17:02PM -0700, Ngie Cooper wrote:
> On Tue, Aug 30, 2016 at 5:54 PM, Matthew Macy wrote:
> >
> >
> > I did a buildworld with llvm39. Unsurprisingly I had to pass NO_WERROR= as
> > the llvm has added additional warnings since 3.8.
> >
> > https://gist.github.com/mattmacy
On Tue, Aug 30, 2016 at 5:54 PM, Matthew Macy wrote:
>
>
> I did a buildworld with llvm39. Unsurprisingly I had to pass NO_WERROR= as
> the llvm has added additional warnings since 3.8.
>
> https://gist.github.com/mattmacy/5f0c994b7587a10e3f58e7fd9fc1dd01
dim's working on the issues on ^/project
On 5/9/16 10:47 PM, Glen Barber wrote:
> On Tue, May 10, 2016 at 07:15:57AM +0200, O. Hartmann wrote:
>> On a most recent buildworld with make installworld/installkernel I faced the
>> fact that all the entries in /etc/master.passwd and /etc/group were reset to
>> the initial/vanilla values. Luckil
On Tue, May 10, 2016 at 07:15:57AM +0200, O. Hartmann wrote:
> On a most recent buildworld with make installworld/installkernel I faced the
> fact that all the entries in /etc/master.passwd and /etc/group were reset to
> the initial/vanilla values. Luckily, I was able to fetch backups
> from /var/b
> On Jun 15, 2015, at 09:17, O. Hartmann wrote:
>
> Am Mon, 15 Jun 2015 17:39:58 +0200
> Baptiste Daroussin schrieb:
>
>>> On Mon, Jun 15, 2015 at 08:13:12AM -0700, Peter Wemm wrote:
>>> Beware, a recent change has moved zfs tools internal libraries to the wrong
>>> location and this can caus
Am Mon, 15 Jun 2015 17:39:58 +0200
Baptiste Daroussin schrieb:
> On Mon, Jun 15, 2015 at 08:13:12AM -0700, Peter Wemm wrote:
> > Beware, a recent change has moved zfs tools internal libraries to the wrong
> > location and this can cause machines to be unbootable. /sbin/zfs uses the
> > librari
On Mon, Jun 15, 2015 at 08:13:12AM -0700, Peter Wemm wrote:
> Beware, a recent change has moved zfs tools internal libraries to the wrong
> location and this can cause machines to be unbootable. /sbin/zfs uses the
> libraries from /lib, which are now going stale and may have undefined
> symbols
On Apr 12, 2015, at 13:18, Benjamin Kaduk wrote:
> Looking at the actual build log posted, the warning is emitted by cc, not
> ctfconvert.
This is not a compiler warning. While you can't see the ctfconvert/ctfmerge
command because it's hidden, I'm sure that the warning comes from ctf. Just
gr
On Sat, 11 Apr 2015, Rui Paulo wrote:
> On Saturday 11 April 2015 15:53:41 Oliver Pinter wrote:
> > Hi all!
> >
> > I just found the line in the subject in our jenkinsbuild log in both
> > amd64 and i386 case (we don't modified these files):
> >
> > http://nyi-01.build.hardenedbsd.org:8180/jenkin
On Saturday 11 April 2015 15:53:41 Oliver Pinter wrote:
> Hi all!
>
> I just found the line in the subject in our jenkinsbuild log in both
> amd64 and i386 case (we don't modified these files):
>
> http://nyi-01.build.hardenedbsd.org:8180/jenkins/job/HardenedBSD-master-i386
> /56/console
> http:
On 03/07/2014 11:29, Warner Losh wrote:
> On Mar 7, 2014, at 10:22 AM, Ian Lepore wrote:
>
>> On Fri, 2014-03-07 at 10:19 -0700, Warner Losh wrote:
>>> On Mar 7, 2014, at 9:47 AM, Eitan Adler wrote:
>>>
On 7 March 2014 11:41, Rui Paulo wrote:
> On 6 Mar 2014, at 23:30, David Xu wrote:
On 3/7/14 8:41 AM, Rui Paulo wrote:
On 6 Mar 2014, at 23:30, David Xu wrote:
it seems filename ended with a dot is illegal on Windows, if someone
wants to check out freebsd source code on Windows, it will be a problem.
Is this something we want to support? NetBSD made some invasive changes on
On Mar 7, 2014, at 6:30 PM, Adrian Chadd wrote:
> On 7 March 2014 15:25, Warner Losh wrote:
>>
>> On Mar 7, 2014, at 4:12 PM, Eitan Adler wrote:
>>
>>> On 7 March 2014 13:50, Rui Paulo wrote:
On 7 Mar 2014, at 10:38, David Chisnall wrote:
> On 7 Mar 2014, at 16:41, Rui Paulo
On 7 March 2014 15:25, Warner Losh wrote:
>
> On Mar 7, 2014, at 4:12 PM, Eitan Adler wrote:
>
>> On 7 March 2014 13:50, Rui Paulo wrote:
>>> On 7 Mar 2014, at 10:38, David Chisnall wrote:
>>>
On 7 Mar 2014, at 16:41, Rui Paulo wrote:
> On 6 Mar 2014, at 23:30, David Xu wrote:
>
On Mar 7, 2014, at 4:12 PM, Eitan Adler wrote:
> On 7 March 2014 13:50, Rui Paulo wrote:
>> On 7 Mar 2014, at 10:38, David Chisnall wrote:
>>
>>> On 7 Mar 2014, at 16:41, Rui Paulo wrote:
>>>
On 6 Mar 2014, at 23:30, David Xu wrote:
> it seems filename ended with a dot is illegal
On 2014-03-07 18:12, Eitan Adler wrote:
> On 7 March 2014 13:50, Rui Paulo wrote:
>> On 7 Mar 2014, at 10:38, David Chisnall wrote:
>>
>>> On 7 Mar 2014, at 16:41, Rui Paulo wrote:
>>>
On 6 Mar 2014, at 23:30, David Xu wrote:
> it seems filename ended with a dot is illegal on Windows,
On 7 March 2014 13:50, Rui Paulo wrote:
> On 7 Mar 2014, at 10:38, David Chisnall wrote:
>
>> On 7 Mar 2014, at 16:41, Rui Paulo wrote:
>>
>>> On 6 Mar 2014, at 23:30, David Xu wrote:
it seems filename ended with a dot is illegal on Windows, if someone
wants to check out freebsd sourc
On Mar 7, 2014, at 11:50 AM, Rui Paulo wrote:
> On 7 Mar 2014, at 10:38, David Chisnall wrote:
>
>> On 7 Mar 2014, at 16:41, Rui Paulo wrote:
>>
>>> On 6 Mar 2014, at 23:30, David Xu wrote:
it seems filename ended with a dot is illegal on Windows, if someone
wants to check out fre
On 7 Mar 2014, at 10:38, David Chisnall wrote:
> On 7 Mar 2014, at 16:41, Rui Paulo wrote:
>
>> On 6 Mar 2014, at 23:30, David Xu wrote:
>>> it seems filename ended with a dot is illegal on Windows, if someone
>>> wants to check out freebsd source code on Windows, it will be a problem.
>>
>>
On 7 Mar 2014, at 16:41, Rui Paulo wrote:
> On 6 Mar 2014, at 23:30, David Xu wrote:
>> it seems filename ended with a dot is illegal on Windows, if someone
>> wants to check out freebsd source code on Windows, it will be a problem.
>
> Is this something we want to support?
Yes, definitely. B
On Mar 7, 2014, at 10:22 AM, Ian Lepore wrote:
> On Fri, 2014-03-07 at 10:19 -0700, Warner Losh wrote:
>> On Mar 7, 2014, at 9:47 AM, Eitan Adler wrote:
>>
>>> On 7 March 2014 11:41, Rui Paulo wrote:
On 6 Mar 2014, at 23:30, David Xu wrote:
> it seems filename ended with a dot is il
On Fri, 2014-03-07 at 10:19 -0700, Warner Losh wrote:
> On Mar 7, 2014, at 9:47 AM, Eitan Adler wrote:
>
> > On 7 March 2014 11:41, Rui Paulo wrote:
> >> On 6 Mar 2014, at 23:30, David Xu wrote:
> >>> it seems filename ended with a dot is illegal on Windows, if someone
> >>> wants to check out
On Mar 7, 2014, at 9:47 AM, Eitan Adler wrote:
> On 7 March 2014 11:41, Rui Paulo wrote:
>> On 6 Mar 2014, at 23:30, David Xu wrote:
>>> it seems filename ended with a dot is illegal on Windows, if someone
>>> wants to check out freebsd source code on Windows, it will be a problem.
>>
>> Is t
On 7 March 2014 11:41, Rui Paulo wrote:
> On 6 Mar 2014, at 23:30, David Xu wrote:
>> it seems filename ended with a dot is illegal on Windows, if someone
>> wants to check out freebsd source code on Windows, it will be a problem.
>
> Is this something we want to support?
Yes.
> NetBSD made s
On 6 Mar 2014, at 23:30, David Xu wrote:
> it seems filename ended with a dot is illegal on Windows, if someone
> wants to check out freebsd source code on Windows, it will be a problem.
Is this something we want to support? NetBSD made some invasive changes on
their source tree to be able to s
On Mar 7, 2014, at 12:30 AM, David Xu wrote:
> When I am using mercurial to initialize a freebsd repository, it prints
> "warning: filename ends with '.', which is not allowed on Windows:
> 'tools/test/sort/bigtest/q-1.024.003.'
>
> it seems filename ended with a dot is illegal on Windows, if
On Wednesday 27 November 2013 12:59:10 Ajtim wrote:
> On Wednesday 27 November 2013 17:07:40 you wrote:
> > On Wed, Nov 27, 2013 at 4:55 PM, Ajtim wrote:
> > > OS: FreeBSD 10.0-BETA3 #0 r257580: Sun Nov 3 19:43:01 UTC 2013
> > > r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
> > >
On 26. May 2012, at 14:01 , Bjoern A. Zeeb wrote:
Hey.
> WARNING - please refrain from testing IPv6 or updating your HEAD if you do
> not have any of the above two NICs and rely on IPv6, or if you have updated
> and
> are experiencing problems. Disabling -txcsum -tso for the moment should be an
On 05/26/2012 16:36, Dag-Erling Smørgrav wrote:
> Dag-Erling Smørgrav writes:
>> probably due to an issue in the latest openpam; sudo is not affected
>
> should be fixed now.
Confirmed, thanks. :)
--
This .signature sanitized for your protection
__
Dag-Erling Smørgrav writes:
> probably due to an issue in the latest openpam; sudo is not affected
should be fixed now.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fre
On 25. May 2012, at 16:55 , Bjoern A. Zeeb wrote:
> Hey,
>
> last night I pushed in the essential offloading support changes for IPv6
> along with quite a bit of other "noise" into HEAD. There is more locking
> improvements etc. to come once I have looped things back to my working tree
> and Mic
On Thu, Jun 02, 2011, Arnaud Lacombe wrote:
> > On a related topic, do we have any mechanism to provide
> > per-subdir or per-file CFLAGS during kernel builds ?
> >
> I'd say no as the kernel per-se makes no use of , ooth,
> some modules do.
>
> > I tried to put a Makefile.inc in a subdirectory bu
A compile-with clause in the sys/conf/files configuration file may
work for what you want, e.g. picking a random example:
dev/e1000/e1000_82542.c optional em | igb \
compile-with "${NORMAL_C} -I$S/dev/e1000"
- Joshua
On Wed, Jun 1, 2011 at 9:54 AM, Luigi Rizzo wrote:
> In an at
Hi,
On Wed, Jun 1, 2011 at 12:54 PM, Luigi Rizzo wrote:
> In an attempt to build a kernel with -Wextra gives a number
> of warnings for
>
> 'inline' is not at beginning of declaration
>
> (in tcp_input.c, as an example).
>
> Is there any interest in trying to fix these ?
>
> HEAD/sy
09.07.2010 14:41, Ivan Voras пишет:
On 07/08/10 18:42, Alex Keda wrote:
When booting, I have strange message.
All work OK (processor with hyperthreading, but system seems it as 1 CPU ).
lissyara-gp# dmesg
Copyright (c) 1992-2010 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 19
On 07/08/10 18:42, Alex Keda wrote:
> When booting, I have strange message.
> All work OK (processor with hyperthreading, but system seems it as 1 CPU ).
> lissyara-gp# dmesg
> Copyright (c) 1992-2010 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>
08.07.2010 22:13, Super Biscuit ?:
--- On *Thu, 7/8/10, Alex Keda //* wrote:
From: Alex Keda
Subject: WARNING: Non-uniform processors.
To: freebsd-current@freebsd.org
Date: Thursday, July 8, 2010, 4:42 PM
When booting, I have strange message.
All work OK (process
--- On Thu, 7/8/10, Alex Keda wrote:
From: Alex Keda
Subject: WARNING: Non-uniform processors.
To: freebsd-current@freebsd.org
Date: Thursday, July 8, 2010, 4:42 PM
When booting, I have strange message.
All work OK (processor with hyperthreading, but system seems it as 1 CPU ).
lissyara-gp# d
Pau Rodriguez wrote:
> #dmesg|tail -n 2
> Warning: pid 474 used static ldt allocation.
> See the i386_set_ldt man page for more info
>
> What does it means?
>
> It was apearring for aprox. 15days.
>
> What I have to do?
>
> Maybe it was asked before... Could anybody refetch that message or answ
On Fri, Aug 08, 2003 at 11:25:49AM +1200, Andrew Turner wrote:
[...]
> I found this patch worked by removing the secound ${PROG} target if
> there was already one there.
>
> --- /usr/src/share/mk/bsd.prog.mk Mon Jun 30 06:16:26 2003
> +++ /usr/share/mk/bsd.prog.mk Mon Aug 4 17:54:22 2003
> @
Nate Lawson wrote:
I get this:
===> i386/cdboot
===> i386/kgzldr
===> i386/libi386
===> i386/loader
"/usr/share/mk/bsd.prog.mk", line 38: warning: duplicate script for target "loader"
ignored
cc -nostdlib -static -Ttext 0x0 -o loader.sym
/home/obj/home/src/sys/boot/i386/loader/../btx/lib/crt0.o ma
On Thu, Aug 07, 2003 at 02:46:23PM -0300, Daniel C. Sobral wrote:
> Nate Lawson wrote:
> >I get this:
> >===> i386/cdboot
> >===> i386/kgzldr
> >===> i386/libi386
> >===> i386/loader
> >"/usr/share/mk/bsd.prog.mk", line 38: warning: duplicate script for target
> >"loader" ignored
> >cc -nostdlib -
Nate Lawson wrote:
I get this:
===> i386/cdboot
===> i386/kgzldr
===> i386/libi386
===> i386/loader
"/usr/share/mk/bsd.prog.mk", line 38: warning: duplicate script for target "loader"
ignored
cc -nostdlib -static -Ttext 0x0 -o loader.sym
/home/obj/home/src/sys/boot/i386/loader/../btx/lib/crt0.o ma
Nate Lawson wrote:
> /home/src/sys/gnu/ext2fs/ext2_vfsops.c: In function `ext2_unmount':
> @/sys/buf.h:281: warning: inlining failed in call to `BUF_LOCK'
"Warning: compiler failed to do what the hell it was told to do".
8-).
-- Terry
___
[EMAIL PROTEC
On Fri, 18 Jul 2003, Jacques A. Vidrine wrote:
> On Fri, Jul 18, 2003 at 12:18:14PM -0700, Nate Lawson wrote:
> > Warner mentioned this was due to the gcc import. Nearly every part of the
> > kernel that uses newbus or buf.h prints out lots of warnings. Can someone
> > see about fixing this, whe
Nate Lawson <[EMAIL PROTECTED]> writes:
> Warner mentioned this was due to the gcc import. Nearly every part of the
> kernel that uses newbus or buf.h prints out lots of warnings. Can someone
> see about fixing this, whether it's by fixing our headers or build flags
> or gcc itself? I've alread
On Fri, Jul 18, 2003 at 12:18:14PM -0700, Nate Lawson wrote:
> Warner mentioned this was due to the gcc import. Nearly every part of the
> kernel that uses newbus or buf.h prints out lots of warnings. Can someone
> see about fixing this, whether it's by fixing our headers or build flags
> or gcc
Garrett Wollman wrote:
> `#if __GNUC__' wouldn't help matters; every preprocessor has to read
> and interpret every preprocessor directive (so that `#else' and
> `#endif' can be recognized).
I thought that the other discussion had concluded that:
#if 0
...
#else
Or:
Craig Rodrigues wrote:
> In , I see:
>
> #if __GNUC__
> #warning "No user-serviceable parts inside."
> #endif
>
> Does the use of #warning need to be protected by
> #if __GNUC__ in FreeBSD header files?
Yes. It is a preprocessor directive specific the GCC preprocessor.
This was discussed in gre
Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, walt writes:
Starting today I noticed this warning at bootup:
WARNING: Driver mistake: make_dev(console) called before SI_SUB_DRIVERS
Is there more info I should supply?
Ooops. No, that is plenty. I'll fix it.
Yes, fixed now. Thanks.
In message <[EMAIL PROTECTED]>, walt writes:
>Starting today I noticed this warning at bootup:
>WARNING: Driver mistake: make_dev(console) called before SI_SUB_DRIVERS
>
>Is there more info I should supply?
Ooops. No, that is plenty. I'll fix it.
--
Poul-Henning Kamp | UNIX since Zilog Z
Garance A Drosihn wrote:
> At 2:33 PM -0500 3/8/03, Garance A Drosihn wrote:
> >
> >By adding that #warning, you are going to have a compile-time error
> >on some compilers, whether or not you want it. Hiding it inside of
> >an #if/#endif will help for some compilers, but not on all of them.
>
>
At 2:33 PM -0500 3/8/03, Garance A Drosihn wrote:
By adding that #warning, you are going to have a compile-time error
on some compilers, whether or not you want it. Hiding it inside of
an #if/#endif will help for some compilers, but not on all of them.
Er, I should note that I do like the idea of
At 10:48 AM -0800 3/8/03, Marcel Moolenaar wrote:
On Sat, Mar 08, 2003 at 12:28:13PM -0500, Garrett Wollman wrote:
> `#if __GNUC__' wouldn't help matters; every preprocessor has to
> read and interpret every preprocessor directive (so that `#else'
> and `#endif' can be recognized).
I don't thin
On Sat, Mar 08, 2003 at 12:28:13PM -0500, Garrett Wollman wrote:
>
> `#if __GNUC__' wouldn't help matters; every preprocessor has to read
> and interpret every preprocessor directive (so that `#else' and
> `#endif' can be recognized).
I don't think preprocessors should interpret directives when t
On Sat, Mar 08, 2003 at 11:19:43AM -0500, Craig Rodrigues wrote:
> Hi,
>
> In , I see:
>
> #if __GNUC__
> #warning "No user-serviceable parts inside."
> #endif
>
>
> Does the use of #warning need to be protected by
> #if __GNUC__ in FreeBSD header files? I am working
> on something similar for
In the last episode (Mar 08), Garrett Wollman said:
> On Sat, 8 Mar 2003 11:19:43 -0500, Craig Rodrigues <[EMAIL PROTECTED]> said:
> > Does the use of #warning need to be protected by
> > #if __GNUC__ in FreeBSD header files?
>
> No, it needs to be replaced by the standard `#error' directive
> ins
In message: <[EMAIL PROTECTED]>
Vallo Kallaste <[EMAIL PROTECTED]> writes:
: partition c: partition extends past end of unit
: Warning, partition c doesn't start at 0!
: Warning, An incorrect partition c may cause problems for standard system utilities
: partition e: partition extends p
On Mon, 18 Nov 2002, Vallo Kallaste wrote:
> On Mon, Nov 18, 2002 at 01:00:37PM -0800, Julian Elischer
> <[EMAIL PROTECTED]> wrote:
>
> [snip]
> > In pre-geom days we had a "realhack" (TM) that would fiddle the
> > label if you read it direct from the disk. In other words
> > it "fixed" it t
On Mon, Nov 18, 2002 at 01:00:37PM -0800, Julian Elischer
<[EMAIL PROTECTED]> wrote:
[snip]
> In pre-geom days we had a "realhack" (TM) that would fiddle the
> label if you read it direct from the disk. In other words
> it "fixed" it to always look (u relative I think) even if you
> read i
On Mon, 18 Nov 2002, Vallo Kallaste wrote:
> On Mon, Nov 18, 2002 at 11:23:14AM -0800, Julian Elischer
> <[EMAIL PROTECTED]> wrote:
>
> > what are the warnings?
> > what version of disklabel.c?
>
> Here's script output:
>
> Script started on Mon Nov 18 21:46:07 2002
[...]
> sysid 165 (0xa5),(
On Mon, Nov 18, 2002 at 11:23:14AM -0800, Julian Elischer
<[EMAIL PROTECTED]> wrote:
> what are the warnings?
> what version of disklabel.c?
Here's script output:
Script started on Mon Nov 18 21:46:07 2002
bash-2.05b# dd if=/dev/zero of=/dev/da1 bs=1k count=512
512+0 records in
512+0 records out
On Mon, 18 Nov 2002, Vallo Kallaste wrote:
> Hi
>
> Just did the following:
> dd if=/dev/zero of=/dev/da1 bs=1k count=512 #remove old stuff
> fdisk -I da1#cover the entire disk with one da1s1 slice
> fdisk da1 #check what's put there
> disklabel -rw da1s1 auto#install virg
Try this then:
#!/bin/sh
#Default options
LINTCONF=LINT.CONF
LINTCONF1=LINT.CONF1
ARCH=`uname -m`
ARCH1=$ARCH
SRCDIR=/sys
START=0
END=0
NOCLEAN=0
TMPDIR=/tmp/makedepend
WD=`pwd`
#Read the command line
while [ $# -ne 0 ]
do
case "$1" in
--src-dir)
Juli Mallett wrote:
> > >find_dependcyType: application/x-java-applet
[ ... ]
> It's a bourne shell script, terry, try looking at it.
Then the MIME type is wrong. Certainly, the disposition "inline"
is wrong.
I've been bombarded with all sorts of crap like this lately
which were DDOS cl
* De: Terry Lambert <[EMAIL PROTECTED]> [ Data: 2002-10-16 ]
[ Subjecte: WARNING: Re: Kernel option dependency finding ]
> Andrew Turner wrote:
> >
> > Name: find_dependcy
> >find_dep
On Wed, Jun 12, 2002 at 04:27:19AM +0200, Cyrille Lefevre wrote:
[...]
> already done using the NetBSD way. the problem is that they use
> LC_TIME (hugh!) to pass the format string to strftime while
> LC_TIME isn't suppose to contain any format strings but a locale
> name.
Ew! That won't work for
On Wed, Jun 12, 2002 at 03:07:45AM +0200, Bjoern Fischer wrote:
> > PS : I've finished to merge diffs from OpenBSD last week, but diffs
> > w/ NetBSD are really big... so, be patient :P
>
> What about bin/35886?
already done using the NetBSD way. the problem is that they use
LC_TIME (hugh!) to p
> PS : I've finished to merge diffs from OpenBSD last week, but diffs
> w/ NetBSD are really big... so, be patient :P
What about bin/35886?
Björn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Jun 7, 2002 01:27:31 pm +0200, Cyrille Lefevre wrote:
> On Fri, Jun 07, 2002 at 02:15:09AM -0400, Trevor Johnson wrote:
> > Dan Nelson wrote:
> [snip]
> > According to Mr. Schilling's testing, GNU tar 1.13.25 has a bug:
> > ftp://ftp.fokus.gmd.de/pub/unix/star/testscripts/README.gtarfail . I gu
On Fri, Jun 07, 2002 at 02:15:09AM -0400, Trevor Johnson wrote:
> Dan Nelson wrote:
[snip]
> According to Mr. Schilling's testing, GNU tar 1.13.25 has a bug:
> ftp://ftp.fokus.gmd.de/pub/unix/star/testscripts/README.gtarfail . I guess
> it qualifies as a "non-trivial program". :-)
FYI, the curren
On Fri, Jun 07, 2002 at 02:15:09AM -0400, Trevor Johnson wrote:
> On my friend's BSD/OS system, there is no tar--or rather, it's just a hard
> link to pax:
>
> % ls -li `which tar` `which pax`
> 1819 -r-xr-xr-x 2 bin bin 58288 Jun 12 1998 /bin/pax
> 1819 -r-xr-xr-x 2 bin
Dan Nelson wrote:
> > The latest version on ftp://ftp.gnu.org/gnu/tar/ is 1.13. The ones on
> > ftp://alpha.gnu.org/gnu/tar/ (and everything else on that site) are
> > considered unstable. I suppose it's too late to suggest tar 1.13 as a
> > starting point, but maybe this could be kept in mind
>
> >
> > Hi,
> >
> > I've just noticed that something wrong with the new tar in the base
> > system (1.13.25) - when extracting some archives it creates 777 dirs,
> > while permissions in the archive itself are OK (for example GNU make
> > make-3.79.1.tar.gz - top level dir gets 777 as well as
Dan Nelson wrote:
> Tar 1.13 is 3 years old, and has many bugs (incremental backups are
> unusable, for example).
On the flip side, I hear it respects the umask when running as root...
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
In the last episode (Jun 06), Trevor Johnson said:
> > I've just noticed that something wrong with the new tar in the base
> > system (1.13.25) - when extracting some archives it creates 777 dirs,
> > while permissions in the archive itself are OK (for example GNU make
> > make-3.79.1.tar.gz - top
> I've just noticed that something wrong with the new tar in the base
> system (1.13.25) - when extracting some archives it creates 777 dirs,
> while permissions in the archive itself are OK (for example GNU make
> make-3.79.1.tar.gz - top level dir gets 777 as well as several
> other lowel level
>
> Hi,
>
> I've just noticed that something wrong with the new tar in the base
> system (1.13.25) - when extracting some archives it creates 777 dirs,
> while permissions in the archive itself are OK (for example GNU make
> make-3.79.1.tar.gz - top level dir gets 777 as well as several
> other
In message <[EMAIL PROTECTED]> Nick Hibma writes:
: Yes. I have no idea why phk has not done this.
Because the asr driver maintainer has asserted a strong lock in the
past and phk doesn't have an asr card.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current"
On Wed, Oct 31, 2001 at 12:10:14AM +, Nick Hibma wrote:
>
> Yes. I have no idea why phk has not done this.
>
> As this is a purposeful panicing of systems that worked fine before, I
> presume that someone is keeping track of the problems that are occurring
> and going to do something about i
Yes. I have no idea why phk has not done this.
As this is a purposeful panicing of systems that worked fine before, I
presume that someone is keeping track of the problems that are occurring
and going to do something about it? Or is this a bad case of 'someone
else's problem'?
Nick
On Tue, 30
On Tue, Oct 30, 2001 at 03:58:39PM -0700, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> John Baldwin writes:
> :
> : On 30-Oct-01 Poul-Henning Kamp wrote:
> : > In message <000801c1617c$9599ad00$[EMAIL PROTECTED]>, Jan
> : > Stocker
> : > writes:
> : >>Ive updated the first time my system
In message <[EMAIL PROTECTED]> John Baldwin writes:
:
: On 30-Oct-01 Poul-Henning Kamp wrote:
: > In message <000801c1617c$9599ad00$[EMAIL PROTECTED]>, Jan
: > Stocker
: > writes:
: >>Ive updated the first time my system to current (Oct-28, with cvsup). After
: >>a make
: >>buildword and install
On 30-Oct-01 Poul-Henning Kamp wrote:
> In message <000801c1617c$9599ad00$[EMAIL PROTECTED]>, Jan
> Stocker
> writes:
>>Ive updated the first time my system to current (Oct-28, with cvsup). After
>>a make
>>buildword and installworld, i made a new GENERIC kernel and copied the file
>>GENERIC.hin
In message <000801c1617c$9599ad00$[EMAIL PROTECTED]>, Jan Stocker
writes:
>Ive updated the first time my system to current (Oct-28, with cvsup). After
>a make
>buildword and installworld, i made a new GENERIC kernel and copied the file
>GENERIC.hints to /boot/device.hints and installed the new ke
[EMAIL PROTECTED] (Jan Stocker) writes:
> So whats on?
Please refer to the Handbook, section 19.2.1.4, first paragraph.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
John Baldwin wrote:
>
> I already managed to test it locally here and commit the proper fix.
> It was an order of operations bug due to the fact that ! is
> evaluated before &.
Ok, thanks!
--
Marcel Moolenaar
mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
tel: (408) 447-4222
To Unsubscribe
On 02-Nov-00 Marcel Moolenaar wrote:
> John Baldwin wrote:
>>
>> Quick question: Is this a problem for people _without_ DEVFS?
>
> That's a yes for me.
>
>> non-DEVFS case. Try this hackish patch:
>>
>> Index: bpf.c
>> ===
>> R
>
> Quick question: Is this a problem for people _without_ DEVFS? Poul
> may have accidentally broke calling make_dev for the bpf device in the
> non-DEVFS case. Try this hackish patch:
Personally, I surely get it with DEVFS and I think I also got it when running
without it. I will try the pat
John Baldwin wrote:
>
> Quick question: Is this a problem for people _without_ DEVFS?
That's a yes for me.
> non-DEVFS case. Try this hackish patch:
>
> Index: bpf.c
> ===
> RCS file: /usr/cvs/src/sys/net/bpf.c,v
> retrieving re
On 02-Nov-00 John Baldwin wrote:
>
> On 02-Nov-00 Marcel Moolenaar wrote:
>> [EMAIL PROTECTED] wrote:
>>>
>>> > I get it as well. IIRC, it simply means that the bpf pseudo device needs
>>> > to be updated, but is otherwise harmless. I forgot the details, but it's
>>> > all in the mailinglist ar
On 02-Nov-00 Marcel Moolenaar wrote:
> [EMAIL PROTECTED] wrote:
>>
>> > I get it as well. IIRC, it simply means that the bpf pseudo device needs
>> > to be updated, but is otherwise harmless. I forgot the details, but it's
>> > all in the mailinglist archives. Somewhere... :-)
>>
>> Anybody han
[EMAIL PROTECTED] wrote:
>
> > I get it as well. IIRC, it simply means that the bpf pseudo device needs
> > to be updated, but is otherwise harmless. I forgot the details, but it's
> > all in the mailinglist archives. Somewhere... :-)
>
> Anybody handling this, or anybody can give pointers as to
1 - 100 of 112 matches
Mail list logo
