at line 90 of the Makefile in /usr/src as the source of truth. Has that changed?Tim
they simply
> go some place else for there products. Be carefull in what you
> believe silence to be saying.
I do not see csh as root's shell as a pain point.
The #1 pain point on FreeBSD if you are used to various flavors of
linux, Solaris, UnixWare, etc.
is ps(1) not having POSIX style arguments.
--
Tim Rice
tim.r...@xinuos.com
*either* drive could fail.
>
> What am I doing wrong?
You did wait for the resilver to complete after bringing the 1st drive
back online
before the 2nd test, right?
>
> Thanks,
>
> Joe
>
>
> Joe McGuckin
> ViaNet Communications
>
> j...@vi
as been updated on the website at:
>
> https://www.freebsd.org/releases/12.0R/schedule.html
>
> Thank you in advance for your patience.
>
> Glen
> On behalf of: re@
>
--
Tim Rice
___
freebsd-current@freebsd.org mailing list
h
lly standalone DTB
file that can be edited (for example, to enable additional
serial ports) and recompiled without having the full source
tree available.
This is probably less important now that overlay DTBs are
more commonly supported.
Tim
___
free
ill use GNU tar instead of BSD tar to recreate the bootstrap and
> GNU tar doesn't seem to produce sparse file entries in the archive.
How ironic; using GNU tar in order to avoid having GNU sparse file entries. ;-)
Tim
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
never mind.
Sorry for the noise.
Silly me, using mount options that work on solaris on a freebsd system.
On 09/01/16 13:43, Tim Rice wrote:
Whatever program creates /etc/zfs/exports from a "zfs set sharenfs
" command
does not act correctly if hostnames have a - in them.
I fir
is correct.
Sorry I haven't had time to track down where the trouble is. I just ran
into this
setting up a storage server.
--
Tim Rice
t...@xinuos.com
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freeb
s otherwise not
broken --- well, at least where Coverity reported the issue.
On 21 July 2016 at 00:14, Tim Čas wrote:
> On 20 July 2016 at 22:23, Don Lewis wrote:
>> It passes a fixed-length non-NUL terminated buffer (returned by read(2))
>> to mbrtowc(). In addition to the lack
On 20 July 2016 at 22:23, Don Lewis wrote:
> It passes a fixed-length non-NUL terminated buffer (returned by read(2))
> to mbrtowc(). In addition to the lack of termination, the buffer could
> also contain a partial character at its beginning or end if the contents
> are UTF-8.
>
> The Coverity I
On 20 July 2016 at 20:33, Don Lewis wrote:
> wc(1) has problems with its multibyte support pointed out by Coverity
> as I recall.
Not sure how critical that issue is (e.g. byte counts [`-c`], line
counts [`-l`], and such should still work as intended; whether word
counts work or not depends on wh
On 20 July 2016 at 16:07, Baptiste Daroussin wrote:
> On Wed, Jul 20, 2016 at 10:47:45AM -0230, Jonathan Anderson wrote:
>> On 20 Jul 2016, at 9:13, Tim Čas wrote:
>>
>> > So, without further ado:
>> > 1) What are the reasons that UTF-8 isn't the default yet
Hello!
I've just joined this list, so I apologize if this has been discussed before.
Today in #freebsd on FreeNode, I've asked whether there was any
particular reason why UTF-8 wasn't the default in FreeBSD yet.
What followed was a small discussion regarding this, and it seems that
there's a good
On 06/07/16 01:49, Thomas Dickey wrote:
On Mon, Jun 06, 2016 at 10:12:14PM -0700, Tim Rice wrote:
Would someone please commit the attached termcap patch for Altos V
terminals.
Granted I may be the only person still using one but it'll save
continual patching.
Thanks for your consider
Would someone please commit the attached termcap patch for Altos V
terminals.
Granted I may be the only person still using one but it'll save
continual patching.
Thanks for your consideration.
--
Tim Rice
t...@xinuos.com
Index: share/termcap/te
_format_ar.o
that did not get rebuilt when archive_write_private.h got updated recently.
If you still have the /usr/obj tree around, could you check the dates on these
files:
archive_write_set_format_ar.o (in /usr/obj)
archive_write_private
quests)
How complex would it be to perform all of the fetch requests before chroot?
Tim
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> On May 22, 2016, at 1:28 PM, K. Macy wrote:
>
>
>
> On Sunday, May 22, 2016, Tim Kientzle wrote:
> Crochet has some experimental hooks to install packages onto the system being
> built, but this seems to be hitting problems due to limitations in 'pkg -c'.
a complete system environment
(which it cannot be when you're building an image for another system).
There's some further discussion on github:
https://github.com/freebsd/crochet/issues/141
Any suggestions?
Cheers,
Tim
___
freebsd
Someone just pointed out that the change also affected cpio's -p pass-through
mode. That was not intentional. I just accepted Martin's pull request to
revert the behavior for -p mode.
Cheers,
Tim
> On May 15, 2016, at 9:16 AM, Ian Lepore wrote:
>
> On Sun, 2016-0
Many people consider the traditional behavior to be a security risk, which is
why this was changed.
FreeBSD is welcome to make --insecure the default on FreeBSD, but I'm reluctant
to do that in the upstream libarchive project.
Tim
> On May 12, 2016, at 8:54 AM, Martin Matusk
A little history about this issue:
http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2304
> On May 14, 2016, at 12:17 PM, Tim Kientzle wrote:
>
> Many people consider the traditional behavior to be a security risk, which is
> why this was changed.
>
> FreeBSD
If you could please open an issue at
http://github.com/libarchive/libarchive
and include as much detail as you can, I’d appreciate it.
Cheers,
Tim
> On May 12, 2016, at 7:15 AM, Michael Butler
> wrote:
>
> It seems that today's libarchive update breaks cpio'
/etc/rc.d/pwd
root@emily:~# service pwd onestart
Starting pwd.
/
-
--
Tim Preston
graywo...@mac.com
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> On Aug 10, 2015, at 12:39 AM, Konstantin Belousov wrote:
>
> On Sun, Aug 09, 2015 at 05:24:13PM -0700, Tim Kientzle wrote:
>>
>>> On Aug 9, 2015, at 11:10 AM, Konstantin Belousov
>>> wrote:
>>>
>>> On Sun, Aug 09, 2015 at 10:53:20AM -070
> On Aug 9, 2015, at 11:10 AM, Konstantin Belousov wrote:
>
> On Sun, Aug 09, 2015 at 10:53:20AM -0700, Tim Kientzle wrote:
>>
>> I suspect the LOR is new.
>>
>> It looks like the panic is occurring when WITNESS tries to print the
>> backtrace for the
> On Aug 8, 2015, at 11:47 PM, Konstantin Belousov wrote:
>
> On Sat, Aug 08, 2015 at 05:24:37PM -0700, Tim Kientzle wrote:
>> I???m seeing the following crash quite consistently on r286438. It looks
>> like the recent work on the kernel linker locking still has so
I’m seeing the following crash quite consistently on r286438. It looks like
the recent work on the kernel linker locking still has some issues.
Any suggested workarounds?
Tim
log trace ===
...
Starting file system checks:
/dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/mmcsd0s2a
mething else. (This avoids cross-polluting the builds if you do
regular manual cross-builds on the same machine.)
If you’re having issues with /usr/obj being on NFS, that could be a factor.
Tim
___
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"
> On May 25, 2015, at 8:25 AM, Warner Losh wrote:
>
>>
>> On May 24, 2015, at 7:44 PM, Tim Kientzle wrote:
>>
>>>
>>> On May 24, 2015, at 12:55 AM, Oleksandr Tymoshenko
>>> wrote:
>>>
>>>
>>>> On May
> On May 24, 2015, at 6:44 PM, Tim Kientzle wrote:
>
>
>> On May 24, 2015, at 12:55 AM, Oleksandr Tymoshenko
>> wrote:
>>
>>
>>> On May 24, 2015, at 12:12 AM, Garrett Cooper wrote:
>>>
>>> On May 24, 2015, at 0:07, Oleksan
e/ is handled
> by dtc I believe
>
> You can take a look at how FreeBSD compiles dts files in
> sys/tools/fdt/make_dtb.sh
>
> crochet does not have cpp stage of compilation and before my TI
> code/devicetree refactoring none of the dts files referenced in
> crochet used #inclu
On Sep 3, 2014, at 7:08 AM, Tim Kientzle wrote:
>
> On Sep 3, 2014, at 6:51 AM, Tim Kientzle wrote:
>
>>
>> On Sep 2, 2014, at 1:13 PM, Garrett Cooper wrote:
>>
>>> On Tue, Sep 2, 2014 at 9:47 AM, AN wrote:
>>>> FreeBSD FBSD11 11.0-CURR
On Sep 3, 2014, at 6:51 AM, Tim Kientzle wrote:
>
> On Sep 2, 2014, at 1:13 PM, Garrett Cooper wrote:
>
>> On Tue, Sep 2, 2014 at 9:47 AM, AN wrote:
>>> FreeBSD FBSD11 11.0-CURRENT FreeBSD 11.0-CURRENT #47 r269949: Wed Aug 13
>>> 14:18:28 EDT 2014
ics at boot on BBB (armv6) with a kernel built from r270779.
Old kernel from r270339 still works.
I’ll dig out more details tonight.
Tim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsu
worked.
However, there was some work done recently to improve error reporting from the
options processor. It’s quite possible that —options xz:9 used to just be
ignored and now it’s reporting an error.
Tim
___
freebsd-current@freebsd.org mailing list
htt
I was surprised to see “portsnap fetch” download over 6,000 patches in order to
advance the April 22 snapshot to now:
# portsnap fetch
Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found.
Fetching snapshot tag from isc.portsnap.freebsd.org... done.
Fetching snapshot metadata... done.
Upda
On Fri, May 23, 2014 at 09:03:12PM -0600, Alan Somers wrote:
> On Fri, May 23, 2014 at 8:42 PM, Tim Bishop wrote:
> > On Fri, May 23, 2014 at 08:07:03PM -0600, Alan Somers wrote:
> >> On Fri, May 23, 2014 at 7:47 PM, Tim Bishop wrote:
> >> > I have a new quad CPU s
On Fri, May 23, 2014 at 08:07:03PM -0600, Alan Somers wrote:
> On Fri, May 23, 2014 at 7:47 PM, Tim Bishop wrote:
> > I have a new quad CPU system containing four of these processors:
> >
> > Intel(R) Xeon(R) CPU E7-4830 v2 @ 2.20GHz (2200.05-MHz K8-class CPU)
> >
posal ... :)
--
----
Tim Daneliuk tun...@tundraware.com
PGP Key: http://www.tundraware.com/PGP/
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to &qu
ast year
that built and streamed a Zip archive on the fly. It
worked rather well even when the archives were
multiple gigabytes with tens of thousands of entries.
Tim
___
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"
On Jan 16, 2014, at 12:36 PM, Mark Felder wrote:
> On Wed, Jan 15, 2014, at 23:11, Tim Kientzle wrote:
>>
>> On Jan 14, 2014, at 6:47 AM, Mark Felder wrote:
>>
>>> I was recently talking to someone about how one would backup / restore
>>> ACLs reliab
the same for mtree. I thought
I remembered acl_to_text having an option to use
an extended text format, so it might be a trivial change.
Tim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe,
On Jan 15, 2014, at 9:11 PM, Tim Kientzle wrote:
>
> On Jan 14, 2014, at 6:47 AM, Mark Felder wrote:
>
>> I was recently talking to someone about how one would backup / restore
>> ACLs reliably. I didn't see any mention of ACLs in the mtree man page
>> and
On Dec 14, 2013, at 3:16 PM, Darren Pilgrim
wrote:
> On 12/14/2013 12:12 PM, Tim Kientzle wrote:
>> Opened up an old VM from a month or so ago (r257910) and dhclient won’t
>> start.
>>
>> Specifically, dhclient complains (when run by root):
>> “can’t
haven’t configured it in any way.
I’ve upgraded Parallels and the Mac OS system that Parallels
is running on, so it could be related to that...
Tim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To
k I had
> suggested this previously as it would also allow us to have a tool to
> suspend/resume individual drivers at runtime apart from a full suspend/resume
> request).
Anything that made it easier to test suspend/resume
would be a huge bonus.
Tim
___
ock of “at least N bytes” and have the
allocator tell you what it *really* allocated.
This allows applications to use memory more efficiently
by taking advantage of over-allocation when it happens.
Tim
___
freebsd-current@freebsd.org mailing list
htt
ckets.
You’re trying to turn all UDP sockets with those options
into multicast sockets.
If you want a multicast socket, you should ask for one.
Tim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
ach to iterate my dev environment
(using one VM to build a new VM instead of
upgrading in place).
Tim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "free
er
or not ports or packages should install crontab files into
/usr/local/etc/cron.d/ can be richly debated after that
directory exists.)
Tim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsub
ure in the hope that I can
> convince re@ that this is a simple enough (and safe enough) change to merge
> before 10.0-RELEASE.
Please.
Tim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
T
is was about as vanilla a build as you can get:
no local code changes, no custom config, no src.conf or make.conf, no ports
installed, etc.
Tim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To un
ndency but does notice that it's installed and
goes right through.
Somehow, it appears that port dependencies are
getting built and installed properly but not always
being noticed by the main build.
Tim
___
freebsd-current@freebsd.o
nce suggests we have some badly-factored
code in our libraries. That is, some library is putting functions
into a single source file that shouldn't be combined.
Tim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/li
p;
> (flavor == F_FREEBSD9 || S_ISREG(p->fts_statp->st_mode)))
DES is right: size should just be omitted for non-regular files.
Bug-for-bug compatibility can be taken too far.
I prefer Xin's original patch.
Tim
___
freebsd-curr
ed on my own experience, I would put this rather differently:
GCC and Clang are COMPILERS.
Therefore, they have DIFFERENT BUGS.
This is why I worry about having "cc" and "gcc" be different
compilers.
Tim
___
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"
are using libarchive directly, you can ask it
to not interpret those files as metadata. Bsdtar does
request such handling from libarchive.
Tim
___
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"
On Aug 17, 2013, at 11:17 AM, O. Hartmann wrote:
> On Sat, 17 Aug 2013 10:42:07 -0700
> Tim Kientzle wrote:
>
>>
>> On Aug 17, 2013, at 10:35 AM, O. Hartmann wrote:
>>
>>> On Sat, 17 Aug 2013 21:10:49 +0400
>>> Boris Samorodov wrote:
named from
restarting after the reboot; maybe we should change the named
startup scripts to test this link and delete/recreate it if it's broken?
Tim
___
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"
ransmit
function.
I suppose this would still work with your scheme.
Tim
___
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"
ransmit
function.
I suppose this would still work with your scheme.
Tim
___
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"
ed bug, and
> induced some unnecessary code changes.
Not strictly necessary for correctness, but still good changes for the most
part.
Tim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
Thanks! I've committed all of these except the change
to contrib/bmake/ which should probably be submitted
upstream first.
Tim
On Jun 29, 2013, at 7:16 AM, d...@gmx.com wrote:
> Here's a patch to fix several compilation errors coming from -Wunsequenced
> warnings:
>
&
211458 (db_trace_thread+0x34)
>>rsp=0xde9d0514 rfp=0xc12d1b60
>> Bad frame pointer: 0xc12d1b60
>> db>
> This is completely broken. It seems that witness triggered the panic,
> and ddb is unable to obtain a backtrace from the normal panic(9) call.
Kernel backtraces are currently broken on ARM EABI kernels.
Tim
signature.asc
Description: Message signed with OpenPGP using GPGMail
stage 4.2: building libraries
stage 4.3: make dependencies
stage 4.4: building everything
> [...]
> /src/usr.bin/svn/lib/libapr/../../../../contrib/apr/include/apr_ring.h:183:34:
> note: expanded from macro 'APR_RING_PREV'
> #define APR_RING_PREV(ep, link) (ep)->link.prev
>
cross-building
bootable images, it should avoid these issues.
The only fundamental limit right now is that Crochet uses
the host system to build the UFS filesystems, so it can't
build big-endian MIPS images on i386, for example.
Tim
signature.asc
Description: Message signed with OpenPGP using GPGMail
Seems the tinderbox scripts are routinely showing too little of the actual
error these days...
On Jun 4, 2013, at 7:19 PM, FreeBSD Tinderbox wrote:
> TB --- 2013-06-05 01:10:18 - tinderbox 2.10 running on
> freebsd-current.sentex.ca
> TB --- 2013-06-05 01:10:18 - FreeBSD freebsd-current.sentex.
On Feb 13, 2013, at 2:23 AM, Baptiste Daroussin wrote:
> On Sat, Feb 02, 2013 at 09:46:41PM -0800, Tim Kientzle wrote:
>> Especially on -CURRENT, it's not going to be uncommon
>> to see things like this:
>>
>> The package management tool is not yet installed o
xup" that
I outlined earlier would work.
But this is very, very close. This is a big step forward
for non-x86 FreeBSD.
Kudos to the pkgng team!
Tim
signature.asc
Description: Message signed with OpenPGP using GPGMail
without this
setting and let us know.
Tim
___
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"
On Feb 5, 2013, at 10:55 PM, Baptiste Daroussin wrote:
> On Tue, Feb 05, 2013 at 10:34:18PM -0800, Tim Kientzle wrote:
>> I'm working on tools to build ARM system images.
>> Usually, these tools run on x86, which creates a problem
>> for packages.
>
>>
I'm working on tools to build ARM system images.
Usually, these tools run on x86, which creates a problem
for packages.
I would like to install packages onto the image as it's built.
So I've been experimenting with variations of
pkg -c add
I'm running into a few problems but I think they can
On Feb 3, 2013, at 1:08 PM, Ian Lepore wrote:
> On Sun, 2013-02-03 at 12:06 -0800, Tim Kientzle wrote:
>> I'm tinkering with a disk image that automatically
>> fills whatever media you put it onto. But I'm having
>> trouble with gpart resize failing.
>>
>
ation after step #1.
Is there some trick that will force the partition
information in memory to be updated (short of
a reboot or unmount/remount the root filesystem)?
Tim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
Especially on -CURRENT, it's not going to be uncommon
to see things like this:
The package management tool is not yet installed on your system.
Do you want to fetch and install it now? [y/N]: y
Bootstrapping pkg please wait
_http._tcp.pkg.FreeBSD.org
pkg: Error fetching
http://pkg.FreeBSD.org/fre
7;s a big performance hit
but better than crashing.
> I note we're at version 0.10.8 of this package, but upstream is at
> 1.34.2. (It requires glib 2.34.1, though, and we're only at 2.28.8).
>
> What's the best way to pro
On Jan 1, 2013, at 8:12 AM, Brett Wynkoop wrote:
> On Mon, 31 Dec 2012 15:25:15 -0800
> Tim Kientzle wrote:
>
>> I've made some progress reworking the CPSW driver for
>> BeagleBone and would appreciate any feedback:
>>
>> https://github.com/kientzle/c
loaded and unloaded while the network is
busy, etc.
The most obvious remaining issue: TX interrupts
still just stop occasionally. But the watchdog now
consistently detects and resets everything within
a few seconds, so that's much less of a headache.
I hope to commit this to FreeBSD-CURRENT within
On Dec 10, 2012, at 10:38 AM, Rick Macklem wrote:
> Adrian Chadd wrote:
>> .. what was the previous kernel version?
>>
> Hopefully Tim has it narrowed down more, but I don't see
> the hangs on a Sept. 7 kernel from head and I do see them
> on a Dec. 3 kernel fr
Mac OS 10.7 host.)
I'll try to get some more details ...
Tim
___
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"
ame/number in
the mtree file didn't both exactly match the current host. This
would be the useful behavior when using mtree files to verify
files on disk. This is likely the most appropriate default
behavior.
Tim
___
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"
need to reinstall the pkg port as well.
Tim
___
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"
particular installation.
* /rescue tools are not guaranteed to be functionally identical to the
non-rescue versions.
Better to invoke 'id' in a way that produces
"reasonable" results if 'id' is unavailable.
For example:
/bin/s
ly
> publish new package sets (incorporating the update to pkgng) from the
> repositories which will have been built using the updated DB schema.
Will new versions of pkgng support old packages?
Some folks maintain their own package repositori
On Aug 19, 2012, at 12:17 PM, Garrett Cooper wrote:
> On Sun, Aug 19, 2012 at 9:45 AM, Tim Kientzle wrote:
>>
>> On Aug 12, 2012, at 6:20 AM, Paul Schenkeveld wrote:
>>
>>> Hi,
>>>
>>> I have a wrapper script that builds packages in a chroot
ames getting fed into -T doesn't exist. (In which case
tar should report an error, but it should be a clear error.)
Can you add a printf() nearby that getvfsbyname() call,
to dump the argument that's causing problems?
Tim
___
freebsd-current@
c3fbe7b9424cea83c7555
> https://github.com/libarchive/libarchive/commit/c6d3cd3
>
>
> Dňa 29. 7. 2012 3:18 Tim Kientzle wrote / napísal(a):
>>
>> On Jul 28, 2012, at 10:21 AM, O. Hartmann wrote:
>>
>>> When updating ports (like databases/sqlite3 or graphic
r the command that's
hanging?
$ ps auxww | grep tar
Knowing the exact options that were used will help narrow
it down.
Thanks for reporting it,
Tim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-curr
t in a way that static checkers could verify. I also
agree that having static checkers interpret comments is Evil.
But I have yet to see any alternative that was as
straightforward and widely-supported as this one.
Every other viable alternative seems to require
On Jun 14, 2012, at 5:34 AM, Konstantin Belousov wrote:
> On Wed, Jun 13, 2012 at 08:32:19PM -0700, Tim Kientzle wrote:
>> On Jun 12, 2012, at 1:49 AM, Konstantin Belousov wrote:
>>>>>
>>>>> On Jun 5, 2012, at 8:09 AM, Jan Sieka wrote:
>>>>
t;>> __fixdfsi;
>>>> __fixunssfsi;
> If the symbols are used by normal programs, that I think
> we should indeed guarantee ABI stability for them, and FBSD_1.3
> namespace is the right namespace to use.
Why 1.3?
This is a common function across every ar
usage fixed.
That particular symbol is in FBSD_1.0 for amd64, i386, ia64, powerpc,
powerpc64, sparc64.
It's in FBSDPrivate_1.0 for arm.
It's not defined for mips at all.
The latter two seem to be bugs; I just committed r237039 to fix arm.
I haven't checked the situation on mips.
T
On May 24, 2012, at 1:16 AM, Damjan Marion wrote:
> On May 24, 2012, at 6:35 AM, Tim Kientzle wrote:
>
>> I think the PandaBoard ES is fully supported by U-Boot,
>> so it should be possible to use ubldr as part of the boot
>> chain for that just like I've been doi
the BeagleBone,
with DRAM starting at 0x8000 .
I think the PandaBoard ES is fully supported by U-Boot,
so it should be possible to use ubldr as part of the boot
chain for that just like I've been doing with BeagleBone.
Tim
___
freebsd-current@
}
.dynsym: { *(.dynsym) }
This seems to work pretty well for me, except for one odd point:
the make dependencies cause ubldr to get relinked on every build.
(This can be fixed in the usual way.)
If anyone sees a better way to handle this, I
On May 18, 2012, at 3:18 AM, Bjoern A. Zeeb wrote:
>
> On 13. May 2012, at 22:35 , Tim Kientzle wrote:
>
>> FYI: Saw a crash due to filesystem corruption when running SUJ.
>>
>> This is on a ARM AM335x system (BeagleBone) that is
>> still pretty experimenta
know.
Cheers,
Tim
___
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"
ility to set the system clock to
the approximately correct time (it doesn't need to be very
exact). If you have networking, you can use "ntpdate pool.ntp.org"
to set the clock from the network.
Tim
___
freebsd-current@freebsd.org mailing list
the dynamic library into memory
- fixes up references
* Calls main
The process of loading the required libraries and fixing up references
can be quite time-consuming.
Cheers,
Tim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd
1 - 100 of 423 matches
Mail list logo
