On Sun, 19 Dec 2021, Greg Troxel wrote:
I didn't mean to demand human acknowledgement, merely "not
rejected by the MTA, and actually delivred to the original
poster".
I am not as close a reader as I pride myself on being, since I
lept to the impression you have just now dispersed. Good thing
On Sun, 19 Dec 2021, Greg Troxel wrote:
There's nothing wrong with a direct reply to a list message,
and it's discourteous to refuse them.
Would it be correct to claim equivalence -- more or less --
between your category "direct reply," and what I have been
accustomed to call an "off-list re
On Sat, 27 Nov 2021, Todd Gruhn wrote:
After I compile and install many libs needed by LibreOffice,
I get the message:
Harfbuzz needs to be built with Graphite support
What do I do about this?
Have you tried the build of libreoffce yet? According to this:
https://en.wikipedia.org/wiki/Harf
On Sat, 20 Nov 2021, Greg Troxel wrote:
cd /usr/pkgsrc/lang/rust
make show-options
Yes. Havard's post, between its lines, told me that there is no
repository of make options toward which curious persons
might be easily directed. The devil is still in the detail,
where he's always been.
On Sat, 20 Nov 2021, Havard Eidnes wrote:
Documentation? :)
A very helpful post; seriously. Beaucoup thank-you's.
And a sense of humor is also indispensable!
--
"The existence of God is not an experimental issue in the way it was."
John Wisdom - "Gods" (1944)
On Sat, 20 Nov 2021, Greg Troxel wrote:
Chavdar Ivanov writes:
PKG_OPTIONS.rust+= rust-llvm
RUST_TYPE=src
1.56.1 has just hit pkgsrc proper.
Regarding the kinds of options noted above, where would a
curious person go to read documentation for them? I have lines
like the above in my /etc
On Fri, 19 Nov 2021, Todd Gruhn wrote:
'uname -s' gives 'NetBSD' (is that even correct?)
Language can be so tricky. In the sense of being a "legal"
argument to 'uname,' 's' is correct (it's listed in uname's
manpage synopsis), but I meant to type 'uname -a' so that the
version number would
TYPO WARNING!
On Fri, 19 Nov 2021, Bob Bernstein wrote:
Share with us the output of 'uname -s'.
My eyes continue to go downhill.
This of course should have been 'uname -a'.
9-(
--
"The existence of God is not an experimental issue in the way it was."
On Fri, 19 Nov 2021, Todd Gruhn wrote:
I just upgraded to NETBSD-HEAD-19-November-2021 . Does anyone
have FireFox working on this version?
Your nomenclature is just a wee bit less than adequate, imho. I
think you mean that you upgraded to what is usually
(albeit informally) referred to as "c
On Sat, 30 Oct 2021, Edgar Pettijohn wrote:
A quick look at the manual for cvs looks like it
probably should have just been:
cvs tag successful-build-$DATE
where $DATE is todays date.
Here's what I see with that:
$ cd /usr/src/
$ cvs tag successful-build-20211030
cvs tag: Tagging .
cvs [ta
On Fri, 29 Oct 2021, John Nemeth wrote:
If you don't use the default shell, then it is up to you to
know how your shell functions.
You may be right.
Perhaps you can help me with this statement found in
https://www.netbsd.org/docs/current/#tagging
--snip--
Tagging a successful build
If
I'm trying to follow _The NetBSD Guide_, but I am stymied by
these instructions, at
https://netbsd.org/docs/guide/en/chap-fetch.html
$ for file in *.tgz
do
tar -xzf $file -C /
done
Entering that first line and pressing just yields
"for: Command not found."
Are those steps, as printed, dep
A couple of days ago I had my first experience with sysupgrade.
Worked like a charm, all the way through etcupdate and
postinstall.
Braced by this experience of getting something right, I decided
to look into sysbuild, and in the process came across an amazing
statement in:
http://nycdn.net
Thank you Michael, but I cannot justify taking up anymore of
your valuable time on this problem. I only purchased my first
USB stick a scant few years ago, and only then because my wife
wanted to use one on her Mac. I've never felt a need to have one
around, although I'm sure they're all kinds
On Thu, 14 Oct 2021, Michael van Elst wrote:
Are you sure you started the 'a' partition at 63 like in the example ?
I think the question is did I perform ALL the steps listed in
that section of the wiki page?
Just now, executing the last one, I ran into an error I did not
see before:
--s
On Thu, 14 Oct 2021, Michael van Elst wrote:
Are you sure you started the 'a' partition at 63 like in the example ?
I "think" I did, but I wouldn't bet my life on it!
All I can do is repeat the experiment, perhaps with a little bit
(or a lot!) more attention to the details.
Thank you.
-
On Wed, 13 Oct 2021, Michael van Elst wrote:
fn: diskn
1: NetBSD
Error 3
The message comes from the MBR bootcode and says that the PBR
bootblock has an invalid signature which usually means it
hasn't been written.
Is that a defect that is susceptible of a remedy that would not
be destruct
I put the USB stick that has been booting my NUC -- equipped
with current 9.99.88 -- into my old eMachine, hit F12 when the
eMachine logo appeared, and was presented a boot-device
selector screen that correctly identified the stick. Choosing it
I was soon at a halt with these three lines displa
On Mon, 11 Oct 2021, Thomas D. Dean wrote:
On my NUC, there is a connector between the SATA connector and
the SATA power connector.
May one ask, do you run NetBSD on your NUC?
Overnight I learned that the CMOS battery in my NUC has expired,
and that was pretty much the end of the road for me
On Sun, 10 Oct 2021, Thomas D. Dean wrote:
Is the SATA cable connection inserted firm on both
ends?
Not sure.
Does the SATA cable have 1 or 2 connectors on the
computer end?
Two. And I gave them each a push before buttoning the thing up
with new SSD inside.
I didn't look closely at the
On Sun, 10 Oct 2021, Rhialto wrote:
ahcisata0 port 0: PHY offline
This seems to be the point where things start failing.
Am I being told that the two tiny little connectors from the
SSD's "carrier" (for lack of the correct term) that plug into
what I suppose might be called the thing's ma
On Sun, 10 Oct 2021, Martin Husemann wrote:
So it should have shown up as wd0 on your sata controller (but
no drives appeared in your dmesg). Strange.
What I am finding strange is how slow this new system is, for
example, responding to keypresses, and carrying out simple tasks
such as 'mkdir
On Sun, 10 Oct 2021, Martin Husemann wrote:
Nothing obivous here. The SSD you replaced had a SATA
connector?
It matched in overall appearance things termed "SATA" in some of
the youtube videos I watched. Measures 4" x 2.75". It is labeled
"Solid State Drive."
I am brand new to these sorts
On Sun, 10 Oct 2021, Martin Husemann wrote:
It would be very helpful to see the full dmesg of the machine.
Done.
--
"The existence of God is not an experimental issue in the way it was."
John Wisdom - "Gods" (1944)
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 200
I now have a NUC that boots from a USB stick into into -current
9.99.88!
Massive props to everyone in attendance, and to David, who,
in this message:
https://mail-index.netbsd.org/netbsd-users/2021/09/28/msg027812.html
...suggested I use my bootable NetBSD CD to install a full
system on the
Said NUC is able via a CD I burned (using
NetBSD-9.99.88-amd64.iso) to boot that image,
and begin execution of the 'sysinst' resident
on it.
'sysinst' immediately interrupts with a
message; "I can not find any hard disks for use
by NetBSD."
A bit of history iydm:
Last month I discussed th
On Fri, 8 Oct 2021, Chavdar Ivanov wrote:
A sed command to replace #configdir# with ${PKG_SYSCONFDIR}
should suffice.
Yes. However, /wm/wdm seems to be without a maintainer at
present, so I think there are no further steps I can take beyond
the "head's-up" I put up on pkgsrc-users earlier to
On Fri, 8 Oct 2021, Valery Ushakov wrote:
Do you care to take a stab at what that value might be were it
to be correctly displayed?
I don't have the slightest idea. /usr/pkg/etc/wdm probably.
Yes, as was kindly pointed out to me by Martin in this post from
only a few days ago:
http://ma
On Thu, 7 Oct 2021, Valery Ushakov wrote:
Looks like a pkgsrc bug that failed to properly substitute the
actual value before installing the man page.
Do you care to take a stab at what that value might be were it
to be correctly displayed?
I'm far from certain that it even makes sense to as
If I read 'man wdm' I see this:
--snip--
-config configuration_file
Names the configuration file, which specifies
resources to control the behavior of wdm.
#configdir#/wdm-config is the default.
--snip--
Should I be seeing #configdir# thus literally, or is there --
apparently missing
On Wed, 6 Oct 2021, Martin Husemann wrote:
You should find it at /usr/pkg/share/examples/rc.d/wdm
And, of course there it is. If only I had looked in the location
you suggested, rather than one I seem to have conjured out of
pure cranial vapor lock, I would have found it. Imagine my
embaras
On Wed, 6 Oct 2021, Martin Husemann wrote:
You should find it at /usr/pkg/share/examples/rc.d/wdm
Here's what I see:
$ ls /usr/pkg/share/examples/wdm/
GiveConsole Xservers Xsetup_0
TakeConsole Xservers.fs wdm-config
Xaccess Xservers.ws wdm-config.in
Xclien
/usr/pkgsrc/x11/wdm/MESSAGE states:
--snip--
In case you don't have PKG_RCD_SCRIPTS set in your
/etc/mk.conf, copy
${PREFIX}/${RCD_SCRIPTS_EXAMPLEDIR}/wdm to /etc/rc.d/wdm and
add the following line into your /etc/rc.conf
wdm=YES
--snip--
If you'll pardon the expression, in an
As I sat pondering my response to your rather thoughtful note, I
said to myself, "But what are the odds that install CD's from
both NetBSD and OpenBSD would fail to detect the onboard disk?"
it dawned on me that I had carelessly omitted any reference in
my original post to trying an install iso
A few years ago I was given an Intel NUC
running Windows 10, and I used it for quite
awhile since it allowed me to enjoy Adobe
Acrobat and Epson's Scan Utility. I was very
familiar with both of those products.
Earlier this year the NUC went belly up
complaining that it could not find bootabl
On Fri, 24 Sep 2021, RVP wrote:
Not surprising: on NetBSD both the whole disk
device name and the `d'
name are the same device:
I knew that but thought it was important to go through the
motions of performing the experiment, given some of the ways the
universe seems to be having its little
On Fri, 24 Sep 2021, Bob Bernstein wrote:
dd if=NetBSD-7.0-amd64-install.img of=/dev/rsd0d
bs=1m
That 'rsd0d' would appear to designate a
partition.
I repeated the experiment, only using this command:
$ sudo dd if=NetBSD-9.99.88-amd64-install.img of=/dev/rsd0 bs=1m
...and had
On Thu, 23 Sep 2021, Jason Mitchell wrote:
Did you say you copied the .img file to a partition on the flash card?
You may be right. I copied this dd command from a wiki page:
dd if=NetBSD-7.0-amd64-install.img of=/dev/rsd0d bs=1m
That 'rsd0d' would appear to designate a partition.
Perhaps I
On Wed, 22 Sep 2021, Martin Husemann wrote:
Probably easiest way for now: boot the 9.1 (!) bios install
image to install...
Regrettably, results with the 9.1 install.img were unchanged
from my experiments with current-.
Right now I am going to put this project on hold. I've had to
deal wit
Last week (9/16/21) I was helped by the list to mount (for
viewing/inspection) a USB stick on which I had placed an
install.img for current 9.99.88.
Problem: the old eMachine I wish to boot from
this stick ignores its presence, and USB's
first place position in the BIOS boot order.
The boot
On Thu, 16 Sep 2021, Martin Husemann wrote:
Doesn't the image use GPT nowadays?
So it will be dkN instead of vnd0a, try
dkctl vnd0 listwedges
Bingo:
# dkctl vnd0 listwedges
/dev/rvnd0: 2 wedges:
dk0: EFI system, 262144 blocks at 2048, type: msdos
dk1: 0895dffe-fe3d-403d-b50a-91ad47f3
On Thu, 16 Sep 2021, Manuel Bouyer wrote:
Now I run aground:
$ sudo mount -t msdos /dev/vnd0a /mnt
mount: no match for `vnd0a': No such process
I am of course guessing at 'msdos' AND vnd0a! The Guide provides examples
for iso images but I don't see any for "install.img".
the install image isn
I have grabbed NetBSD-9.99.88-amd64-install.img.gz from
http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/images/ and
gunzipped it.
I thought to mount it for viewing before writing it to my USB
stick.
Shouldn't pester a busy vnode:
$ sudo vnconfig -l
vnd0: not in use
vnd1: not in use
vnd2
On Mon, 13 Sep 2021, Riza Dindir wrote:
Does a full install include the netbsd sources
Yes, pretty much, sort of.
as well as the X sources?
No, not so much, sort of.
But what are you really asking? What is it, in your view, that
either stands or falls depending upon one's definition of t
On Wed, 26 May 2021, Chavdar Ivanov wrote:
it behaves as expected - pauses when Always or "On dumb
terninals" is selected and doesn't pause when "Never" is
selected.
Turning OFF "use internal view" got the desired behaviour back
for me. I thought that perhaps mc's 'subshell' mechanism might
The option is set in mc's Configuration screen, but is
steadfastly ignored any time I "run" something in mc, even as
simple as an 'ls'.
My details:
NetBSD nebbytwo 9.99.81 NetBSD 9.99.81 (GENERIC) #0: Sat Mar 20 14:30:50 UTC
2021 mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENE
Thanks for all the encouragement.
I've decided I don't need lyx running in NetBSD. I was getting
farther into a rabbit-hole I didn't want to be in to begin with.
If you know what I mean. And I'm sure you do.
Thank you again to all.
--
RSB
On Sat, 24 Apr 2021, RVP wrote:
Correction: On NetBSD that would be:
if [ -x /usr/pkg/bin/dbus-launch -a -z
"${DBUS_SESSION_BUS_ADDRESS}" ];
In either ~/.xinitrc or ~/.xsession
dbus is launching via standard rc.conf mechanism, with a
'starting dbus' message displayed during boot. Do you
On Sat, 24 Apr 2021, Rhialto wrote:
Did you ever have LyX installed / running before?
No, not on my NetBSD machine at any rate.
It is just a wild guess, but does it help if you install that?
xdg-utils got installed along with Lyx and the qt5 packages.
Did you install from the latest sta
I have built from pkgsrc 'lyx' with the qt5 libs. Typing 'lyx'
at a command prompt yields:
$ lyx
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
'/tmp/runtime-bob'
I pecked through the qt5 pkgsrc dirs (for the qt5 packages that
were built) hoping to find a MESSAGE containing instructi
On Mon, 19 Apr 2021, Bob Bernstein wrote:
On Fri, 9 Apr 2021, Bob Bernstein wrote:
THE FIX was adding this arg to httpd_flags: '-c
/var/www/cgi-bin'
[snip]
I found that '-c' in bozohttpd's man page.
When asked why I prefer NetBSD to all the rest, my answer has
a
On Fri, 9 Apr 2021, Bob Bernstein wrote:
Since upgrading to 9.99.81, httpd doesn't launch a
cgi that has worked for years, to wit
/var/www/cgi-bin/ikiwiki.cgi.
My rc.conf looks at it always has, at least in
regard to httpd:
httpd=YES httpd_flags="-I "
httpd_w
Since upgrading to 9.99.81, httpd doesn't launch a cgi that has
worked for years, to wit /var/www/cgi-bin/ikiwiki.cgi.
My rc.conf looks at it always has, at least in regard to httpd:
httpd=YES httpd_flags="-I "
httpd_wwwdir="/var/www"
* * *
Also, I'm afraid I gave short shrift,
On Wed, 7 Apr 2021, Dan Cîrnaț wrote:
Telling pkgin: 'pkgin install gdm' led to 59 packages being
"refreshed", and 4 more installed.
Please be aware that those pkgin repos only have packages for
the main pkgsrc tree, excluding pkgsrc-wip. The gdm version
there is 2.x., an old one.
I did no
On Wed, 7 Apr 2021, Chavdar Ivanov wrote:
I don't think there are "official" pkgin repos for -current.
However, check https://pkgsrc.joyent.com/install-on-netbsd/ .
What I put in my /usr/pkg/etc/pkgin/reposiories.conf was:
https://pkgsrc.joyent.com/packages/NetBSD/trunk/x86_64/All/
Telling
I am taking a first run at pkgin. It fails trying to get a file
from:
https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/$arch/9.99.81/All
...which can be found in my
/usr/pkg/etc/pkgin/repositories.conf.
I have here:
$ uname -a
NetBSD nebbytwo 9.99.81 NetBSD 9.99.81 (GENERIC) #0: Sat Mar 20
On Mon, 5 Apr 2021, Mayuresh wrote:
What exactly do I need to do to make it bootable. I don't need
it to work with the hdd of the host or grub etc. Just need
plain simple bootable usb stick that would boot into NetBSD.
It's a small world. I just got through reading this about an
hour ago:
The meta package in question is modular-xorg. Mine is quite old.
My spidey-sense tells me that in practice one does not "update"
a meta-package per se. Or perhaps not?
What is considered Best Practices wrt this situation?
Thank you and
Happy Easter all.
--
RSB
On Fri, 2 Apr 2021, Dan Cirnat wrote:
On 31.03.21 21:34, Bob Bernstein wrote:
I am using 9.99.81 amd64 (GENERIC)
I grabbed the GIT pkgsrc tree and did 'make replace' for
/devel/glib2 and /systutils/dbus. On reboot dbus started
normally with no
complaint. Still using icewm
I am using 9.99.81 amd64 (GENERIC)
1. I built the gnome3 metapackage, and tried gedit from the
commandline. The editor launched, but not before issuing this:
"(gedit:18215): dconf-WARNING **: 14:19:18.664: failed to commit
changes to dconf: Cannot spawn a message bus without a
machine-id: Un
On https://www.netbsd.org/mirrors/#anoncvs I see this server
advertised: anoncvs3.us.NetBSD.org, but it appears to be
at least unreachable:
$ host anoncvs3.us.NetBSD.org
Host anoncvs3.us.NetBSD.org not found: 3(NXDOMAIN)
I wonder if it was not a victim of the horrible winter problems
that bef
On Sat, 20 Mar 2021, Bob Bernstein wrote:
I used the 9.1 CD I made and booted into
single-user mode. Then:
# pwd
# /
# cd lib
# ls -l libc.so.12.*
lrwxr-xr-x 1 root wheel 14 Oct 18 19:24
libc.so.12 -> libc.so.12.213
-r--r--r 1 root wheel 2079984 Oct 18 19:24
libc.so.12.213
On Sat, 20 Mar 2021, Greg Troxel wrote:
boot single user and use /rescue/sh etc. to see what's up in
terms of having libc from current and 9, and where init is
from.
I tried that, and got something I've never seen before.
I used the 9.1 CD I made and booted into single-user mode. Then:
# pw
On Sat, 20 Mar 2021, Greg Troxel wrote:
Current from may of 2020 is newer than 9.1, in terms of branch
relationships, so this was not an upgrade.
Well I'll be a monkey's uncle. Ha.
The other option is to upgrade to current current.
I think I'll give that a whirl.
Thank you!
--
RSB
The message shown is what appeared as I finished what appeared
to be an uneventful upgrade from an old 'current' netbsd (May
of last year) to amd64 9.1.
That message, about a missing libc.so.12, was interspersed on
the upgrade screen reporting almost complete success in checking
/etc. There w
I believe this is the file I want to put on my USB stick. The
ftp looked to be taking over a half an hour at ftp.netbsd.org.
Is there a better site for a simple download?
Thank you.
--
RSB
I've forgotten the cmd line for getting current pkgsrc from the
git repo.
Duh.
:(
--
RSB
On Sat, 2 Jan 2021, Bob Proulx wrote:
I apologize to the group for monopolizing the conversation
with so many mail messages here today.
To 'monopolize' the list would necessitate you invoke magical
power to reach into list subscriber's brains in order to
restrain them from posting.
Most ba
On Fri, 31 Jul 2020, Bob Bernstein wrote:
Can some Good Samaritan please point me to a
HOW-TO that would provide the needed basic
instructions?
Thank you all!
And, yes, Mike gets two extra Fig-Newtons on his plate tonight!
--
Man is essentially a dreamer, wakened sometimes for a
moment by
*** Mandatory Trigger Warning /begin ***
Brain-dead noobie post dead ahead!
*** Mandatory Trigger Warning /end ***
I have learned the hard way not to mess with the shell superuser
is supposed to use. I rarely go to su, but it would be pleasing
if, when I do, I had two features available from th
I am liable to change important system files without really
knowing what I'm doing beyond trusting one of you wonderful
NetBSD developers never far from this list.
Over the weekend, having made progress cleaning up this old
system, I asked it to build in pkgsrc Firefox68, and,
unsurprisingly,
On Fri, 17 Jul 2020, Benny Siegert wrote:
You probably need Bitstream Vera and msttcorefont.
Got 'em now. Vera brought icewm instantly to life.
Thanks guy.
--
A test of right and wrong must be the means, one would
think, of ascertaining what is right or wrong, and not a
consequence of hav
On Fri, 17 Jul 2020, Bob Bernstein wrote:
Are there some basic font configuration steps I need to take?
I believe Hegel wrote that the owl of Minerva spread its wings
only at dusk, meaning of course that enlightenment comes at the
end of the day.
Having removed all the packages from this
I progress reconstituting my NetBSD system, after removing all
packages. For example, typing 'startx' in my home dir launches
icewm, with the mouse nicely functional.
Problem: none of the wm's buttons or menus have any readable
labels, as if they don't know how to obtain needed fonts.
Are th
On Thu, 16 Jul 2020, Greg Troxel wrote:
What I would do is
export EDITOR=ed
export VISUAL=ed
Perhaps also "export TERM=cons25" would help.
I think that last one was the one that got me past having to
learn a bit of ed for the first time in probably thirty years.
vipw worked fine once i
On Thu, 16 Jul 2020, Greg Troxel wrote:
2) boot single user, by hitting space during the countdown and
"boot -s". hit return for sh. Once there, type "fsck -p" to
fix any issues. Then "mount -a". Then put back the shell with
pkg_add, or use vipw to change your shell back to /bin/sh.
vipw
There's a long back-story to this event, but it's not important.
Suffice to say that I removed all the packages from my system,
including the shell I like at /usr/pkg/bin/tcsh, and now all my
attempts to login are rejected because the shell cannot be
found.
Is there a work-around?
Thank you
est of right and wrong must be the means, one would
think, of ascertaining what is right or wrong, and not a
consequence of having already ascertained it.
J. S. Mill
On Wed, 15 Jul 2020, Greg A. Woods wrote:
At Wed, 15 Jul 2020 15:40:40 -0400 (EDT), Bob Bern
On Wed, 15 Jul 2020, Greg A. Woods wrote:
These are my relevant hacks which I make directly to
pkgsrc/mk/defaults/mk.conf:
PKGMAKECONF = /etc/mk.conf
PKGSRC_MAKE_ENV += USER=${USER:Q}
WRKOBJDIR ?=/var/package-obj/${USER}
DISTDIR ?= /var/package-distfiles
PACKAGES ?=
/var/pa
I have been working awhile now with the GIT pkgsrc, and it
occurs to me that it might be an advantage to provide different
locations for things such as distfiles, packages, and...what
else?
What is suggested, and where/how is the optimum method for
altering these values?
Thank you
--
A te
On Mon, 29 Jun 2020, Benny Siegert wrote:
I have used command lines such as
some_command | xargs pkg_admin set rebuild=YES
in the past.
Ah. That looks very promising.
My experiments with command lines such as
pkg_admin set rebuild=YES package1 package2 etc
or
pkg_admin set rebuild=YES pac
The man page for pkg_admin contains this line:
set variable=value pkg ...
Do the three final "..." indicate that if it is desired to set
that variable to that value for more than one package, then can
be named in a whitespace-separated list?
Thank you
--
A test of right and wrong must be t
In gedit's "Preferences" I have text wrapping turned on.
What is the keyboard shortcut, or menu choice, for "Wrap text"
or "Fill Paragraph?"
$ gedit --version
gedit - Version 3.22.1
$ uname -a
NetBSD nebby.localdomain 9.99.59 NetBSD 9.99.59 (GENERIC) #0:
Tue May 5 23:50:07 EDT 2020
bob@neb
On Sat, 20 Jun 2020, Greg Troxel wrote:
Perhaps it should say they are updated t.i.w.
Troublemaker.
--
"No matter how big the problem is, you can always run away from it."
Dom Irrera
For example, how to update just a branch, or even one package?
Please keep all your cards and letters coming.
Thank you
--
A test of right and wrong must be the means, one would
think, of ascertaining what is right or wrong, and not a
consequence of having already ascertained it.
My spidey sense, or "inner bofh," tells me it's time.
Other than the clone command per se (from /usr/pkgsrc/README.md)
"git clone https://github.com/NetBSD/pkgsrc.git
...are there any caveats or head's up I should heed? Any handy
"for dummies" wiki pages?
Thank You
--
A test of right and
I want to run RR on my system but prevent it from rebuilding;
1. www/ikiwiki
and
2. Any perl package on which it depends. (There are many.)
I know '-X ikiwiki' will see to #1 above, but I am at sea as to
how to enforce #2. If need be I could settle for a broader #2,
that is "Any package on w
up on my NetBSD system!
The source tarball is here:
http://alpine.x10host.com/alpine/release/
Woo-hoo!
--
Bob Bernstein
A test of right and wrong must be the means, one would
think, of ascertaining what is right or wrong, and not a
consequence of having already
On Tue, Dec 17, 2019 at 07:46:31PM +0100, Martin Husemann wrote:
> > '9.0_BETA NetBSD 9.0_BETA (GENERIC) #0: Wed Nov 20 16:50:50 UTC 2019'
>
> Since you are using 9.0_BETA the "NetBSD-current" line is not for you.
> Instead there is:
>
> Fixed:NetBSD-9 branch:October 28, 2019
>
NB. Since I don't think I should begin a thread to the Security
Officer, I am sending this to netbsd-users.
The security advisory today -- re filemon -- contains this line
under the "Affected" heading:
> Version:NetBSD-current: affected up to 9.99.17
As usual I am tardy keeping
On Fri, Nov 22, 2019 at 03:12:24PM +0100, Kamil Rytarowski wrote:
> Also looking at the error message, please upgrade your
> current snapshot to a newer version.
That did the trick: "NetBSD nebby.localdomain 9.0_BETA
NetBSD 9.0_BETA (GENERIC) #0: Wed Nov 20 16:50:50 UTC 2019
mkre...@mkrepro.ne
Again I apologize for including a long log file from the ailing
rxvt-unicode on my 'NetBSD nebby.localdomain 9.0_BETA NetBSD
9.0_BETA (GENERIC) #0: Sun Aug 18 14:36:49 UTC 2019
mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
amd64' install:
Script started on Thu Nov 21 23:41
My NetBSD install is rebooting itself on odd occasions.
This is $ uname -a
NetBSD nebby.localdomain 9.0_BETA NetBSD 9.0_BETA (GENERIC) #0: Sun Aug 18
14:36:49 UTC 2019
mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64
I have not done any tinkering with this install beyon
On Mon, 14 Oct 2019, David Brownlee wrote:
I've had good experiences running syncthing to sync data
between a set of NetBSD boxes (some directories being master
on one machine only and pushing out, others allowing changes
from multiple ends). Its cross platform. It might be overkill
for just
Request for Suggestions:
I am gathering what will ultimately be about 100G of files on my
amd64 Netbsd (an old eMachine windows box itself) system's
original HD.
That system as well as my Windows 10 (running off a NUC) are
cat-5 wired into the LAN upstairs here in the house.
The NUC now ha
On Fri, Oct 04, 2019 at 12:42:44PM +0200, Rhialto wrote:
> So something weird may be going on.
I would give assent to that speculation.
> The package that adds
> /usr/pkg/lib/perl5/vendor_perl/5.28.0/LWP.pm is
> p5-libwww-6.39.
I used this hint to solve (apparently) the problem of the
missi
A series of misadventures that began nicely enough with a
successful cvs up of my pkgsrc tree, followed by an uneventful
run of pkg_rolling-update has however left me with a new perl5, as
noted ver. 5.30.0, that appears not to have finished its build.
My attention was aroused when I tried what
A series of misadventures that began nicely enough with a
successful cvs up of my pkgsrc tree, followed by an uneventful
run of pkg_rolling-update has however left me with a new perl5, as
noted ver. 5.30.0, that appears not to have finished its build.
My attention was aroused when I tried what
On Sun, 25 Aug 2019, Edgar Pettijohn wrote:
Just install the system to the flash drive instead of the hard
drive.
Believe it or not, that possibility passed through my addled
pate more than once, and left me wondering: "H?"
Thank you
--
Poobah
Thanks for your reflections on USB sticks and booting therefrom!
I know I am going to do more experiments with them. I bought two
64 gig sticks, one of which I used to upgrade my 'current'
NetBSD machine, but the other is still in its package. Not sure
what I will do with it.
I would like to
1 - 100 of 193 matches
Mail list logo
