On 12/31/2018 7:35 AM, Mike Pumford wrote:
On 30/12/2018 15:59, J. Lewis Muir wrote:
I'm trying to install NetBSD 8 on a PC Engines apu2d4
https://www.pcengines.ch/apu2d4.htm
via a USB thumb drive with a NetBSD 8 install image
https://cdn.netbsd.org/pub/NetBSD/NetBSD-8.0/images/NetBSD-8.0
On 12/19/2018 10:58 AM, Rocky Hotas wrote:
Is there a struct/XML somewhere that describes the hardware
in the machine much like parsing dmesg might? I.e., to
ensure the "current" state hasn't changed from a "desired"
state? (boards removed/added, memory complement altered,
etc.)
You almost s
What's the expected location for the "default" openssl.cnf?
I'm looking at 7.1/i386...
Man page for man.conf(5) claims "_whatdb" to be the name of the apropos db.
However, /etc/man.conf actually includes a reference to "_mandb".
ISTR _whatdb was working on 6.1 but haven't yet tested _whatdb vs. _mandb
on a 7.1 system. Can someone more knowledgeable comm
Is there a struct/XML somewhere that describes the hardware
in the machine much like parsing dmesg might? I.e., to
ensure the "current" state hasn't changed from a "desired"
state? (boards removed/added, memory complement altered,
etc.)
On 11/30/2018 1:46 PM, Brett Lymn wrote:
On Fri, Nov 30, 2018 at 12:21:46PM -0700, Don NetBSD wrote:
It is *exactly* one-to-one. I.e., it's just a 3 inch "extender cable".
Perhaps to make the tightly spaced network connectors on the rear of the
box more accessible to folks w
On 11/30/2018 4:34 AM, Julian Coleman wrote:
Hi,
I have some little (3 inch) widgets with an RJ45 plug on one end and
jack on the other. Carrying a (Sun?) part number of 422764100011. I
suspect they may have been part of the Netra T5220 I recently acquired.
First thought was perhaps a crosso
I have some little (3 inch) widgets with an RJ45 plug on one end and
jack on the other. Carrying a (Sun?) part number of 422764100011. I
suspect they may have been part of the Netra T5220 I recently acquired.
First thought was perhaps a crossover adapter? But, the Netra's inet
ports are Gbe so
I have various "not configured" (PnP?) devices attached at acpi0 showing
up on a 7.1/i386 kernel: {MCH, COPR, RMSC, OMSC, PCIE, RMEM}. How can I
sort out which devices they pertain to in order to determine if they are
being serviced by another driver attachment?
And, for those found not to be h
On 11/19/2018 2:21 PM, Brett Lymn wrote:
On Sun, Nov 18, 2018 at 03:57:53PM -0700, Don NetBSD wrote:
Think of it as having a similar function wrt the ILOM as the OBP has to
the OS in older Sun boxen.
No, this is a totally different processor, the SP is, effectively, a
separate computer that
On 11/18/2018 2:09 PM, Brett Lymn wrote:
On Sat, Nov 17, 2018 at 06:53:51PM -0700, Don NetBSD wrote:
On 11/17/2018 1:52 PM, Brett Lymn wrote:
On Fri, Nov 16, 2018 at 02:11:26PM -0700, Don NetBSD wrote:
Yes, but what's the prompt BEFORE that (u-boot>)? And, where do I
find the capa
On 11/18/2018 2:01 AM, Sad Clouds wrote:
On Sat, 17 Nov 2018 18:53:51 -0700
Don NetBSD wrote:
The earlier "u-boot" prompt is significant as it lets you tinker with
the "pre-Linux" environment. Among other things, it lets you erase
the Linux password so you CAN log into t
On 11/17/2018 1:52 PM, Brett Lymn wrote:
On Fri, Nov 16, 2018 at 02:11:26PM -0700, Don NetBSD wrote:
Yes, but what's the prompt BEFORE that (u-boot>)? And, where do I
find the capabilities, there, documented?
As someone else mentioned that is the Service Processor boot, it is a
On 11/16/2018 3:47 PM, David Young wrote:
I added a line to /etc/fstab,
swap /mfs tmpfs rw,-s8M 0 0
If memory is limited, doesn't that make creating a MFS swap just useless
overhead? I.e., if you need to page to swap, you're just consuming memory
set aside FOR swap instead of "main me
On 11/16/2018 2:53 PM, Sad Clouds wrote:
On Fri, 16 Nov 2018 13:22:19 -0700
Don NetBSD wrote:
So, it seems like there are a boat load of prompts -- "u-boot>",
"->", "ok" ... And, nothing that seems to summarize ALL of
the pertinent environments in which
On 11/16/2018 12:35 PM, Rhialto wrote:
I once made a little script to make a bootable ISO9660 live file system,
given the distribution tarballs. It has to be able to live on a
read-only medium, hence it uses a tmpfs for /var. For initializing it,
it installs a script in /etc/rc.d. I basically use
On 11/16/2018 1:56 PM, Brett Lymn wrote:
On Fri, Nov 16, 2018 at 01:22:19PM -0700, Don NetBSD wrote:
Version 3.0.10.4 r61032
Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
Warning: password is set to factory default.
-> version
SP firmware 3.0.10.4
SP firmware bu
On 11/16/2018 1:27 AM, Sad Clouds wrote:
On Fri, 16 Nov 2018 01:01:18 -0700
Don NetBSD wrote:
[probably best to take this off list?]
I am hoping to make some time to play with this over the weekend
(or, over the holiday). Right now, its just "in the way" :-/
Not sure about
On 11/16/2018 11:12 AM, Jeremy C. Reed wrote:
On Thu, 15 Nov 2018, Don NetBSD wrote:
I've a box with a DoM. I'd like to mount / as ro and create a
tmpfs for /var (and /tmp). I don't think anything else NEEDS to
be rw (the infrequent changes to /etc can be made by unlocking
On 11/16/2018 12:05 AM, Sad Clouds wrote:
On Thu, 15 Nov 2018 22:10:26 -0700
Don NetBSD wrote:
This may well be the killer. Someone appears to have flashed a
custom OFW image -- which I'll have to rid the machine of before I
can do ANYTHING with it.
If someone put the latest fir
I've a box with a DoM. I'd like to mount / as ro and create a
tmpfs for /var (and /tmp). I don't think anything else NEEDS to
be rw (the infrequent changes to /etc can be made by unlocking /
to make those changes).
I imagine I can just make a tarball of a skeletal /var and
unpack this over /var
On 11/15/2018 3:46 AM, Sad Clouds wrote:
On Wed, 14 Nov 2018 17:00:06 -0700
Don NetBSD wrote:
I've rescued a Netra T5220 (haven't attached a console, yet).
2. Solaris 11.3 is pretty good and has many features not available
in NetBSD, such as LDOMs, Zones, ZFS, good multithreading
I've rescued a Netra T5220 (haven't attached a console, yet).
I'm soliciting comments as to whether I should leave/install
Slowaris on it or NetBSD. I think the Slowaris option gives
me more "out-of-the-box" functionality (without having to
build/install the apps I might want)
On 10/16/2018 2:23 PM, Brett Lymn wrote:
On Mon, Oct 15, 2018 at 06:44:30PM -0700, Don NetBSD wrote:
You're used to dealing with "computers" where you CAN change a piece of
software AFTER release. I deal with devices/appliances where the cost of
upgrading the device far exce
On 10/14/2018 2:36 PM, Brett Lymn wrote:
I've been "manually" invoking everything that I want/need to run and
capturing any errors logged to sort out what might be missing.
Right - atf can automate this bit for you. If you are doing a
customised build then you will want to do this agin if/when
On 10/11/2018 7:26 PM, Robert Elz wrote:
| For me, I address that with additional *drives* -- typically external.
Different problem/issue. I don't care much about space any more, drives
have oddles of it, and it has become cheap (whatever connection method).
What matters is mount attributes
On 10/11/2018 4:55 PM, Robert Elz wrote:
| Mounting /Sources and symlinking /Sources/src at /usr/src, /Sources/pkgsrc
at
| /usr/pkgsrc, /Sources/xsrc at /usr/xsrc, etc. covers all the bases. Where
| would you put xsrc if you mount a partition at /usr/src? Ditto pkgsrc?
/usr/xsrc and
On 10/10/2018 7:28 PM, Robert Elz wrote:
| I've typically installed them under /usr/src,
That's the standard patrh, though they can go anywhere.
| (though usually symlinked to a separate partition mounted as /Sources).
You can certainly do it that way, but why not just mount the
partiti
On 10/8/2018 2:10 PM, Brett Lymn wrote:
On Sun, Oct 07, 2018 at 06:47:58PM -0700, Don NetBSD wrote:
I don't think so. E.g., anything that relies on (or supports) remote
clients/services would require some explicit action at a remote node to
exercise those services.
For your purposes s
What about the `Source set directories'? I didn't find it nor in the
sparc64, neither in the amd64 ISO.
In this case, the installer (obviously, when you selected some source set to
be installed in a Custom installation) looks for
There is one set of sources that are used for ALL of the va
On 10/7/2018 2:07 PM, Brett Lymn wrote:
On Thu, Oct 04, 2018 at 12:16:39PM -0700, Don NetBSD wrote:
Of course, late bindings are a potential SNAFU in this approach -- unless
I inherently know how to precipitate those events!
Why not use the automated test framework to run everything you want
A question similar, in spirit, to that of Cág ("Correct way to trim the
distribution?")
What's a "good" way to trim the exported filesystem for a diskless
system? (The goal being to eventually crunchgen a local system image
and eliminate the NFS mount entirely)
To date, I've been exporting an *
So, in a degenerate example, put 2 partitions on a disk that each represent
an entire root filesystem TO THE OS THAT IS BOOTED.
This is exactly the degenerate example I wanted to refer to. Let's consider
a BSD disklabel in the first sector of a hard disk (so, without MBR) with
the following part
On 9/27/2018 3:32 AM, Rocky Hotas wrote:
For the sake of completeness, let's consider another case, hopefully
interesting to others. If you decide to install on the same disk two or more
BSD systems, all compatible with BSD disklabel (for example, two different
versions of NetBSD, or NetBSD and F
On 9/27/2018 3:41 AM, Rocky Hotas wrote:
Sent: Tuesday, September 25, 2018 at 11:51 PM
From: "Don NetBSD"
To: netbsd-users@netbsd.org
Subject: Re: BSD disklabel partition letters in NetBSD
[...]
But it isn't placed in any of these places unless/until the system is
DIRECTED
On 9/25/2018 10:52 AM, Michael van Elst wrote:
On Tue, Sep 25, 2018 at 05:05:44PM +0200, Rocky Hotas wrote:
only if none is written to disk,
a fictious label is generated from other data like an MBR.
Sorry, I can't understand this. Maybe it's related to the following
description:
disklabel
On 9/25/2018 3:19 AM, David Brownlee wrote:
[attrs elided]
I have no idea whether this would actually map to your real
requirements, but a possible workflow could be:
Bringing up new appliance ("slot mapping")
- Assuming you have "ID" devices digitally and physically labelled 1..n.
- User is d
On 9/24/2018 6:04 PM, Michael Cheponis wrote:
I have a (linux raspberry pi) that's remotely located and NATted in such a
way that I cannot control that part of the infrastructure, although do
have complete control of the machine otherwise (e.g. access to root).
What I'd like to do is access it
On 9/24/2018 4:14 AM, David Brownlee wrote:
On Mon, 24 Sep 2018 at 11:08, Don NetBSD wrote:
On 9/18/2018 3:54 AM, David Brownlee wrote:
Just some musing about handling drive mappings:
For sd devices you could use "scsictl sdX identify" to map back from
sdX to (scsibus, target, lu
On 9/24/2018 12:30 PM, Rocky Hotas wrote:
Now, of course, this all became mood on most modern machines with the move
to GPT, and this is good. As you probably know, we use full devices for
these (dk* and rdk*), so no limiting alphabet nor reserved letters.
Despite vaguely knowing that GPT is re
On 9/24/2018 12:34 PM, Rocky Hotas wrote:
I like to mount /var on 'e', /usr on 'f', /usr/pkg on 'g' (picking up on
the g in pkG as a mnemonic), /home on 'h', /Sources on 'i', /Playpen on 'j'
and /Archive on 'k' (the hard ch as a mnemonic for the k) with /Leftovers
for 'l'.
This is a very clever
On 9/18/2018 3:54 AM, David Brownlee wrote:
Just some musing about handling drive mappings:
For sd devices you could use "scsictl sdX identify" to map back from
sdX to (scsibus, target, lun) numbers and then onto each drive's
physical location.
OK. That would help me initially identify the "s
On 9/22/2018 2:24 AM, Rocky Hotas wrote:
As regards NetBSD: this use of ‘a’ and ‘b’ is mandatory? Or is it
possible to arbitrarily change the letter assignments? (E.g. partition
/home to ‘a’ and root partition and swap to ‘e’, ‘f’, ‘g’ ...)
Any suggestion/information about this would be very use
On 9/16/2018 2:27 AM, Michael van Elst wrote:
netbsd-embed...@gmx.com (Don NetBSD) writes:
Ah! So, the sd(4) driver won't pass "non-scsi" commands and
the sd(4) devices might not accept scsi commands. (damned if you
do, damned if you don't)?
The sd driver just passe
On 9/16/2018 12:21 AM, Michael van Elst wrote:
netbsd-embed...@gmx.com (Don NetBSD) writes:
But can't I walk back up the device tree and find the number of leaves
on a particular (physical) controller?
You could find out from the config file how many disks you have wired.
Still unrelat
On 9/15/2018 11:27 PM, Michael van Elst wrote:
netbsd-embed...@gmx.com (Don NetBSD) writes:
How can I determine the number of /potential/ disk devices (sd(4))
that a system MIGHT support -- *if* the drives had been installed
prior to boot?
That would be difficult. sd(4) is used for several
How can I determine the number of /potential/ disk devices (sd(4))
that a system MIGHT support -- *if* the drives had been installed
prior to boot? E.g., if I have a 15 slot backplane but only have
a drive installed in slot 13, then *that* appears as sd0 and there
is no mention of the potential f
On 9/13/2018 11:35 PM, Michael van Elst wrote:
netbsd-embed...@gmx.com (Don NetBSD) writes:
| > SMART [...] so it is clearly possible.
|
| I think only via wd(4)?
Oh, you mean, not sd(4) - yes, possibly. Sorry, I have no idea how
one would access that kind of data over s
On 9/11/2018 11:16 AM, Mike Pumford wrote:
[attrs elided]
I've done a lot of work with SAS disk enclosures that support SES. They
often have an SES command that can turn off the drive in a bay prior to
removal (but support is optional).
Aren't standards *wonderful*? What value to "optional"
On 9/11/2018 6:28 AM, Robert Elz wrote:
Date:Tue, 11 Sep 2018 00:19:57 -0700
From:Don NetBSD
Message-ID: <3cedac34-90d8-78ff-b320-de2c5ac8c...@gmx.com>
| [should I be "reply all" or just the list? I guess a matter of personal
| preferenc
On 9/10/2018 11:03 PM, Michael van Elst wrote:
On Mon, Sep 10, 2018 at 05:37:53PM -0700, Don NetBSD wrote:
So, I can use the 'd' partition to access the medium (after unlocking the label
portion). But, I can't count on anything else "displayed" by disklabel. And,
[should I be "reply all" or just the list? I guess a matter of personal
preferences?]
On 9/10/2018 10:08 PM, Robert Elz wrote:
| So, I can use the 'd' partition to access the medium (after unlocking the
label
| portion). But, I can't count on anything else "displayed" by disklabel.
A
On 9/9/2018 10:26 PM, Michael van Elst wrote:
On Sun, Sep 09, 2018 at 05:49:15PM -0700, Don NetBSD wrote:
On 9/9/2018 1:52 PM, Michael van Elst wrote:
On Sun, Sep 09, 2018 at 12:08:14PM -0700, Don NetBSD wrote:
Said another way, are these "in-kernel" values (which no longer r
On 9/10/2018 11:33 AM, Mike Pumford wrote:
On 10/09/2018 01:49, Don NetBSD wrote:
I'm not concerned with automatically detecting insertion/removal; that's
the job that the operator performs (above) -- along with the tagging of
the media, etc.
I've done a lot of work with SAS
On 9/9/2018 1:52 PM, Michael van Elst wrote:
On Sun, Sep 09, 2018 at 12:08:14PM -0700, Don NetBSD wrote:
Said another way, are these "in-kernel" values (which no longer reflect
the physical medium) ever reported in other system calls/ioctls/etc.
INSTEAD of the "real" val
On 9/8/2018 11:55 PM, Michael van Elst wrote:
netbsd-embed...@gmx.com ("Don NetBSD") writes:
My understanding is that the 'd' partition is intended to reference the
entire medium. But, a simple test (disklabel -e) indicates that I can
create an arbitrary (start,size) for
I have to design an appliance to accept "foreign" disks (sd(4) and wd(4)) and
massage them into a form/content suitable for deployment (in yet another
appliance).
My understanding is that the 'd' partition is intended to reference the entire
medium. But, a simple test (disklabel -e) indicates
57 matches
Mail list logo