from them on the subject wasn't completely
clear, but it sounded like they thought they could adjust a couple
things, move us to new hardware, and things would go on as normal. So
I'd follow up with PRGMR support before doing anything.
Gary
> So, a few questions.
>
> christos can name his software as he likes. if you don't like
> it then don't use it, but don't tell him what he can do with
> his own code.
With that point I certainly agree. I didn't mean to imply otherwise.
Gary Duzan
d a
change to prevent such hypothetical offense could reasonably be
considered gratuitous.
Gary Duzan
Can the pthread_attr fix for rust mentioned in
http://mail-index.netbsd.org/pkgsrc-users/2017/08/03/msg025409.html
be pulled up to netbsd-8? I'm getting the same thing there, and
rust is required for the latest firefox.
Thanks.
Gary Duzan
ain, but
otherwise this is netbsd-8 branch from the end of last week.
Gary Duzan
In Message <20170702022455.71f27115...@xen1.duzan.org>,
"Gary Duzan" <g...@duzan.org>wrote:
=> After upgrading from an earlier netbsd-8 snapshot, I got this on reboot:
=>
=>[...]
=>hdaudio1 at pci0 dev 20 function 2: HD Audio Controller
=>hdaudio1: in
2017-06-30 05:05 EDT, and my working tree
update from it completed at 2017-06-30 08:17 EDT. I'll do another
update/build/upgrade in case I got the tree in a weird state.
Thanks.
Gary Duzan
-pr it?
Thanks.
Gary Duzan
cy relationships are lost.
As when I encountered the problem before, I force removed packages with
files under gio/modules with older timestamps (not yet updated), which
allowed the install to continue, and restarting pkg_rolling -replace
took care of the rest.
Gary Duzan
e -f on the packages
containing the modules which had not yet been updated and doing a make
replace on gobject-introspection. The deleted packages were rebuilt by
the packages which depended on them as part of the restarted
pkg_rolling-replace. That seemed to work fine.[1] I never touched
anythin
=> => On Mon, Jun 19, 2017 at 06:49:59AM -0400, Gary Duzan wrote:
=> =>>Can anyone else recreate this?
=> =>
=> => Could be another instance of the elusive PR 51266.
=> => Thomas
=> =>
=>
=>It certainly looks like it. I'll try the workaround
=> On Mon, Jun 19, 2017 at 06:49:59AM -0400, Gary Duzan wrote:
=>>Can anyone else recreate this?
=>
=> Could be another instance of the elusive PR 51266.
=> Thomas
=>
It certainly looks like it. I'll try the workaround and see how it goes.
Thanks.
()
#3 0x70f568200669 in ?? ()
#4 0x in ?? ()
Can anyone else recreate this?
Thanks.
Gary Duzan
In Message <58fbb951.3000...@netbsd.org>,
Nick Hudson <sk...@netbsd.org>wrote:
=>On 04/22/17 20:05, Gary Duzan wrote:
=>> In Message <58fb8a80.7000...@netbsd.org>,
=>> Nick Hudson <sk...@netbsd.org>wrote:
=>>
=>> =>On 04/22/17 13:57, Ga
In Message <58fb8a80.7000...@netbsd.org>,
Nick Hudson <sk...@netbsd.org>wrote:
=>On 04/22/17 13:57, Gary Duzan wrote:
=>> Booting from the installer image, I noticed a couple of USB related
=>> issues. First, the boot menu wouldn't recognize my USB keyboard;
=>
pressed a key on the PS/2 keyboard. It
seemed like my USB devices worked after that, but I didn't do any
additional testing.
Is there anything I can do to help diagnose the problem?
Thanks.
Gary Duzan
---
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001
the installer. (Full dmesg included below.)
Is this a known issue? Is there anything I can do to help diagnose it?
I'm up for whatever code hackery may be required.
Thanks.
Gary Duzan
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005
would match scanners
=>and that libusb would fine, we could have the permissions management of
=>direct matching but the cope-with-the-rest-of-the-world benefit of
=>libusb.
Can we not build some sort of bus-like device to which both the
specialized and generic devices can attach which prevents opening
both at the same time?
Gary Duzan
by changing the tmpfs to an mfs mount. See also PR 46148.
Thanks for the pointer. I got rid of the tmpfs and at least a
few updates have gone through cleanly. If anyone has any ideas of
how to track this down, I can certainly take a whack at it. It
would be nice to know that this isn't going to be a problem for
other uses of tmpfs.
Gary Duzan
ee I updated on another box recently. After an rm -rf on the
broken tree a subsequent update succeeded, but I expect it could happen
again. In case it matters, I'm using an rsync repo clone and accessing
it over ssh.
Gary Duzan
I just did fresh checkouts from anoncvs and my own rsync clone. I see
no difference in the gcc.old directory, and while there is no gdb.old
directory, I see no difference in the gdb directory.
Gary Duzan
=> I've been rsyncing against anoncvs (and/or mirr
> tell me that?
=>
=> Maybe Linux has the right idea. The ethernet cards are always eth# no
=> matter what the actual hardware.
Note that that isn't universal across Linux. I have at least one fairly
modern Linux box at work which renames the interfaces from eth# to
something else.
Gary Duzan
ring-of-network-interfaces
As you can see from the config example, it can remember the MAC
address and assign device names accordingly. Presumably NetBSD
would need some kernel facility to rename devices, or maybe provide
interface name aliases, to support a similar capability.
Gary Duzan
n unmount of an in-use file-system. :)
=>
=>Suggestions?
If init is really its parent, check its "ps axl" output and
check its WCHAN. If it isn't "wait", maybe run "ktruss -p 1" to
get an idea of what it is doing instead of wait*() calls.
Gary Duzan
.
Gary Duzan
/.*\[\([^ ]*\) [^ ]*
filemon\].*/\1/'
202
gets you the major number, the minor number is zero, and it is a character
device.
Good luck...
Gary Duzan
more information.
Any ideas where to look for the next clue?
Thanks.
Gary Duzan
on
= the concept of ISO9660 filesystem on a umass device.
=
You can always start with the NetBSD-{ver}-amd64-install.img.gz or
NetBSD-{ver}-amd64-live-sd0root.img.gz image, which boot off USB fine.
Gary Duzan
...
Gary Duzan
/*/include/asm.h .
Gary Duzan
.
YMMV.
Gary Duzan
In Message 20131229102854.ga...@antioche.eu.org,
Manuel Bouyer bou...@antioche.eu.orgwrote:
=On Thu, Dec 26, 2013 at 10:12:00PM -0500, Gary Duzan wrote:
= In Message 52ba64e6.8020...@tastylime.net,
=Jeff Rizzo r...@tastylime.netwrote:
=
= =Yeah, this is a problem with the libxc
In Message 201312240139.rbo1dkea024...@server.cornerstoneservice.ca,
John Nemeth jnem...@cue.bc.cawrote:
=On Dec 23, 8:18pm, Gary Duzan wrote:
=}
=}For a month or so, sysctl vm on my 6.1_STABLE amd64/XEN3_DOMU
=} machine has errored out with:
=}
=} systat: nlist: can't find
at it myself if there is interest.
Gary Duzan
In Message 5280eddd.5020...@netbsd.org,
Nick Hudson sk...@netbsd.orgwrote:
=On 11/11/13 14:25, Gary Duzan wrote:
= As has been mentioned earlier, the xhci driver causes the boot
= process to hang on some machines, including mine. However, it turns
= out that a single keystroke on the PS/2
host controller in BIOS allowed it to boot, though
obviously without the xhci. xhci was just recently added to GENERIC
which is why you are seeing it now.
Gary Duzan
36 matches
Mail list logo
