Re: Newer development boards
If you are interested in helping out a project there is the PowerPC Notebook project that seems to have gotten into some jams with uboot. https://www.powerpc-notebook.org/en/ I don't think the board they are using is "newer", or exactly what you were thinking of, but it'd be great to see NetBSD on one of these things and if you're also helping a good project then that's win/win right? https://www.nxp.com/design/design-center/software/qoriq-developer-resources/qoriq-t2080-development-board:T2080RDB
Re: how to install a Fortran compiler on NetBSD?
nia wrote:
On Thu, Mar 31, 2022 at 10:12:18PM -0400, Adam Russell wrote:
There doesn't seem to be a fortran compiler available in pkgsrc? I saw
some mentions of gfortran but that must be out of date information as I
cannot find it. I understand, of course, that gfortran is part of the
gcc suite but that doesn't help me as I cannot seem to grasp how to
specify it should be installed.
How do you get a fortran compiler on NetBSD?
If you install gcc7 from pkgsrc, it will install gfortran to
${PREFIX}/gcc7/bin/gfortran. Make sure gccX/bin is in your $PATH.
Ah! Thanks for the tip. Yes, apparently /usr/pkg/gcc7/bin/ is not in the
$PATH by default. I see the gfortran binary now.
how to install a Fortran compiler on NetBSD?
There doesn't seem to be a fortran compiler available in pkgsrc? I saw some mentions of gfortran but that must be out of date information as I cannot find it. I understand, of course, that gfortran is part of the gcc suite but that doesn't help me as I cannot seem to grasp how to specify it should be installed. How do you get a fortran compiler on NetBSD?
Re: cannot start detached sessions (with -m -d) back to back
Adam Russell wrote:
RVP wrote:
On Fri, 31 Dec 2021, RVP wrote:
OP: Try this patch:
---START---
diff -u screen-4.8.0{.orig,}/screen.c --- screen-4.8.0.orig/screen.c
2020-02-05 20:09:38.0 +
+++ screen-4.8.0/screen.c 2021-12-31 01:56:30.470670972 +
@@ -1801,6 +1801,10 @@
struct win *p = windows;
windows = windows->w_next;
FreeWindow(p);
+ if (p->w_pid > 0) {
+ debug1("Hangup(%d);\n", p->w_pid);
+ killpg(p->w_pid, SIGHUP);
+ }
}
if (ServerSocket != -1) {
---END---
I goofed that (use-after-free). Try this one please:
---START---
diff -urN screen-4.8.0.orig/screen.c screen-4.8.0/screen.c
--- screen-4.8.0.orig/screen.c 2021-12-31 03:27:41.988827000 +
+++ screen-4.8.0/screen.c 2021-12-31 03:26:47.995416000 +
@@ -1801,8 +1801,13 @@
debug1("Finit(%d);\n", i);
while (windows) {
struct win *p = windows;
+ pid_t pid = p->w_pid;
windows = windows->w_next;
FreeWindow(p);
+ if (pid > 0) {
+ debug1("Hangup(%d);\n", pid);
+ killpg(pid, SIGHUP);
+ }
}
if (ServerSocket != -1) {
---END---
oh wow, great work! I will try this as soon as possible, which might not
be until tomorrow.
I can confirm that the patch given above works for me. I built this in
pkgsrc. After the existing patches ran I manually applied the patch and
then ran make.
Great work! Happy New Year!
-bash-5.1$ work/screen-4.8.0/screen -S some-session -p 0 -m -d;
work/screen-4.8.0/screen -ls; work/screen-4.8.0/screen -X quit; sleep
10; work/screen-4.8.0/screen -S some-session -p 0 -m -d;
work/screen-4.8.0/screen -ls; sleep 1; work/screen-4.8.0/screen -ls
There is a screen on:
18073.some-session (Detached)
1 Socket in /tmp/uscreens/S-adamcrussell.
There is a screen on:
20109.some-session (Detached)
1 Socket in /tmp/uscreens/S-adamcrussell.
There is a screen on:
20109.some-session (Detached)
1 Socket in /tmp/uscreens/S-adamcrussell.
Re: cannot start detached sessions (with -m -d) back to back
RVP wrote:
On Fri, 31 Dec 2021, RVP wrote:
OP: Try this patch:
---START---
diff -u screen-4.8.0{.orig,}/screen.c --- screen-4.8.0.orig/screen.c
2020-02-05 20:09:38.0 +
+++ screen-4.8.0/screen.c 2021-12-31 01:56:30.470670972 +
@@ -1801,6 +1801,10 @@
struct win *p = windows;
windows = windows->w_next;
FreeWindow(p);
+ if (p->w_pid > 0) {
+ debug1("Hangup(%d);\n", p->w_pid);
+ killpg(p->w_pid, SIGHUP);
+ }
}
if (ServerSocket != -1) {
---END---
I goofed that (use-after-free). Try this one please:
---START---
diff -urN screen-4.8.0.orig/screen.c screen-4.8.0/screen.c
--- screen-4.8.0.orig/screen.c 2021-12-31 03:27:41.988827000 +
+++ screen-4.8.0/screen.c 2021-12-31 03:26:47.995416000 +
@@ -1801,8 +1801,13 @@
debug1("Finit(%d);\n", i);
while (windows) {
struct win *p = windows;
+ pid_t pid = p->w_pid;
windows = windows->w_next;
FreeWindow(p);
+ if (pid > 0) {
+ debug1("Hangup(%d);\n", pid);
+ killpg(pid, SIGHUP);
+ }
}
if (ServerSocket != -1) {
---END---
oh wow, great work! I will try this as soon as possible, which might not
be until tomorrow.
Re: cannot start detached sessions (with -m -d) back to back
I have tried to reproduce what I believe are your findings, that some delay before starting the second session is enough to fix things. What I am finding is that works to some extent, but then that second session seems to quickly end. Here I start a session, list all sessions, quit all sessions, sleep for 10 seconds, start a new session, list all sessions, sleep one second, and then list all sessions again. As you can see the second sessions, created after the ten second sleep, does get created, but is gone a second later. -bash-5.1$ /usr/pkg/bin/screen -S some-session -p 0 -m -d; screen -ls; screen -X quit; sleep 10; /usr/pkg/bin/screen -S some-session -p 0 -m -d; screen -ls; sleep 1; screen -ls There is a screen on: 2406.some-session (Detached) 1 Socket in /tmp/screens/S-adamcrussell. There is a screen on: 1197.some-session (Detached) 1 Socket in /tmp/screens/S-adamcrussell. No Sockets found in /tmp/screens/S-adamcrussell.
cannot start detached sessions (with -m -d) back to back
I have noticed some odd behavior by Gnu Screen. This is what I see -bash-5.1$ /usr/pkg/bin/screen -S some-session -p 0 -m -d -bash-5.1$ screen -X quit -bash-5.1$ /usr/pkg/bin/screen -S some-session -p 0 -m -d -bash-5.1$ screen -X quit No screen session found. After the second invocation no screen session is actually started. For the sake of a simple example I am just running screen -X quit but other commands such as screen -ls show no screen sessions and I am not able to attach to any sessions (since truly none exist). Screen version 4.08.00 (GNU) 05-Feb-20 There seems to be no error whatsoever, any ideas of what could be happening here? I have tried the same thing on MacOS 11.6 (Big Sur) with Screen version 4.00.03 (FAU) 23-Oct-06 and do not have the same error. I have tried this on NetBSD amd 64 9.2 and NetBSD macppc 9.1 with the same result. This definitely seems to be NetBSD specific, at least with this version (4.08.0) from pkgsrc. Any ideas of what is going on?
Re: mari0 crashes
> Does LIBGL_ALWAYS_SOFTWARE=1 help? No, that did not happen to help. However when running remotely on my OS X system using XQuartz I was able to get it working by running this command defaults write org.xquartz.X11 enable_iglx -bool true Apparently, the latest version of XQuartz (X Server for OS X) do not have glx enabled by default. There was nothing wrong or misconfigured on the NetBSD system running the game.
Re: mari0 crashes
Adam Russell wrote: I installed games/mari0-1.6 from pkgsrc and everything seemed to build OK but when I try and start it it crashes quickly with this error. -bash-5.1$ mari0 [ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1) Could not set video mode: Couldn't find matching GLX visual [1] Segmentation fault /usr/pkg/love0.8/bin/love /usr/pkg/share/games... Looking around for other people reporting that error I can't seem to find anything concrete. I am on NetBSD amd64 9.2. Has anyone gotten this to work, and if so any advice? Ok, actually I can answer my own question kind of quickly on this one. I was launching the game from an xterm window with remote X. This works fine when run normally. Running it over a remote X session would be cool I guess, but already I can see that it's be a bit of a headache.
mari0 crashes
I installed games/mari0-1.6 from pkgsrc and everything seemed to build OK but when I try and start it it crashes quickly with this error. -bash-5.1$ mari0 [ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1) Could not set video mode: Couldn't find matching GLX visual [1] Segmentation fault /usr/pkg/love0.8/bin/love /usr/pkg/share/games... Looking around for other people reporting that error I can't seem to find anything concrete. I am on NetBSD amd64 9.2. Has anyone gotten this to work, and if so any advice?
Re: Recording a current audio-event
Todd Gruhn wrote: Interesting thought occurred to me: If I am listening to something on the Web, is it possible to catch the sound, and send it to an MP3 file or directly to CD/DVD? Yes, absolutely! Maybe the best general purpose software for this is ffmpeg.
RE: [External Email] parallel computing with netbsd?
Thank you ! I am familiar with MPI and I think it is the PVM information that I am most interested in for right now. From: netbsd-users-ow...@netbsd.org On Behalf Of Andrew Ball Sent: Tuesday, December 29, 2020 5:51 PM To: Netbsd-users Subject: Fwd: [External Email] parallel computing with netbsd? Package pkgsrc current URL OpenMPI 1.10.7nb5 4.1.0 https://www.open-mpi.org/ MPICH 3.2.1nb4 3.3.2 https://www.mpich.org/ PVM 3.4.6nb2 3.4.6 https://www.csm.ornl.gov/pvm/pvm_home.html -- Forwarded message - From: Andrew Ball <mailto:ab...@students.prairiestate.edu> Date: Tue, Dec 29, 2020 at 3:19 PM Subject: Re: [External Email] parallel computing with netbsd? To: Adam Russell <mailto:ac.russ...@live.com> Hello Adam, There are some related tools in pkgsrc/parallel, though I'm not sure how fresh they are. Ones that jump out at me are OpenMPI and mpich. I also see PVM in there. -Andy Ball http://cdn.netbsd.org/pub/pkgsrc/current/pkgsrc/parallel/README.html On Tue, Dec 29, 2020 at 2:31 PM Adam Russell <mailto:ac.russ...@live.com> wrote: I am looking for some instructions on how to have multiple NetBSD systems work in parallel. I recall a bunch of years ago there was at least one decent writeup on Beowulf systems using netbsd but cannot fine it anymore. Anyone have any suggested links and readings on this subject?
parallel computing with netbsd?
I am looking for some instructions on how to have multiple NetBSD systems work in parallel. I recall a bunch of years ago there was at least one decent writeup on Beowulf systems using netbsd but cannot fine it anymore. Anyone have any suggested links and readings on this subject?
RE: What are the options for netbsd on a handheld form factor PC?
>I've been using a Gemimi as my main phone for a couple of years until around 2 >weeks ago when I switched to the Cosmo which supercedes it (and I have the >Astroslide on order through crowdfunding on Indiegogo >https://www.indiegogo.com/projects/astro-slide-5g-transformer#/ ). > >I love the devices. The Cosmo clearly shows up the Gemini to be a first-gen >device. > >As I've been using them as my main phone, I've not tried anything but Android >on them. They do have multi OS boot support and the boot loader is opensource. >I >know that there's been at least one other person besides me offer a device for >a NetBSD port. > >Listed supported OSes for Gemimi are Debian Linux, Sailfish OS 3 Beta >Community Edition, Kali Linux, Standard and Rooted Android, Team Win Recovery >Project > >https://support.planetcom.co.uk/index.php/Gemini_Firmware Thanks for the report! I think I might just get one and give it a try. I am not looking for a phone as much as a device to do some work (coding, writing) during train commutes. I suppose that is somewhat optimistic that train commutes will be something I start doing again sometime in the next year! 😊 The form factor of "slightly large than a phone but smaller than a laptop" is what appeals to me.
What are the options for netbsd on a handheld form factor PC?
I have always thought that the handheld form factor was very cool, going back to the old psion days. I know netbsd will work on the older devices, like the psion, but are there any modern options? I recently heard about the Gemini https://www.www3.planetcom.co.uk/about whihc is from some opf the original psion people. I would think that netbsd would certainly be possible on these devices but have not heard of any reports of anyone trying it. In particular the Gemini PDA "wi-fi only model" which is absent of the (for me) unnecessary cellular phone features seems like it would be a good fit and the manufacturer claims it supports a variety of linux distributions. Anyone have any experience with these or any other modern handheld PCs?
What are the options for netbsd on a handheld form factor PC?
I have always thought that the handheld form factor was very cool, going back to the old psion days. I know netbsd will work on the older devices, like the psion, but are there any modern options? I recently heard about the Gemini https://www.www3.planetcom.co.uk/about whihc is from some opf the original psion people. I would think that netbsd would certainly be possible on these devices but have not heard of any reports of anyone trying it. In particular the Gemini PDA "wi-fi only model" which is absent of the (for me) unnecessary cellular phone features seems like it would be a good fit and the manufacturer claims it supports a variety of linux distributions. Anyone have any experience with these or any other modern handheld PCs?
Re: net/py-gevent build error on NetBSD in pkgsrc-2019Q1
> Hi There, > > I've tried to build py-gevent (python 3.6 version) on NetBSD 7.2 > > The process breaks with an error: > > deps/libuv/src/unix/netbsd.c: In function 'uv_exepath': > deps/libuv/src/unix/netbsd.c:81:12: error: 'KERN_PROC_PATHNAME' undeclared > (first use in this function) > mib[3] = KERN_PROC_PATHNAME; > > Formerly this macro was defined in sys/sysctl.h as: > #define KERN_PROC_PATHNAME "/proc" > > Nowadays this is missing in NetBSD 7.2 and 8.0, too. > > If the macro is set, then py-gevent builds normally. > > Any idea how to fix? I mean in NetBSD or in the py-gevent package? > > Thank you: > > FeZ py-gevent uses an embedded libuv. It would be better to link against libuv provided by devel/libuv package. A quick fix would be to add devel/libuv/patches/patch-src_unix_netbsd.c to py-gevent (with a different path, of course). I'll look into it later. Thanks for pointing this out. :) Kind regards, Adam
Re: pkgsrc python default version -> 3.7
>> The default Python version in pkgsrc is now 3.7, in preparation for >> the coming end of life date of Python 2.7 (the previous default) at >> the end of this year. > > Can we punt 3.4, 3.5 and 3.6 then? > 3.4 fails at least to build on netbsd-current due to an openssl conflict by > the looks of it. > > Roy I would like to remove Python 3.4, if there is no objection. But I would keep 3.5, and 3.6 for the time being. Kind regards, Adam
Re: NetBSD install and usage by the blind
On Fri, Apr 08, 2016 at 11:43:14PM -0400, D'Arcy J.M. Cain wrote: > On Fri, 8 Apr 2016 20:27:16 + (UTC) > mlel...@serpens.de (Michael van Elst) wrote: > > Unfortunately it doesn't inlcude an sshd, all commands are statically > > linked into a big "crunched" binary, it is limited in size and the > > default sshd build includes every feature but the kitchen sink. > > Even if you have sshd installed there is still logins, keys, etc. to > deal with. Maybe telnetd is good enough. Perhaps limit access to the > local network for a bit more security. Yeah, that could work. In my particular case my network's firewalled and I know whos using it at any given time, but for a general solution it could be risky. > In fact, how about a really simple daemon that sits on the tty > waiting for a connection which just execs the installer without > forking or running login(1)? That prevents a second installer running > and it's safe enough. If someone did manage to beat you to the > installer you would simply reboot and try again. That'd definitely work, and as you say, it'd be easy to see if someone else had already started the install. I guess this'd be a separate piece of software which was then "crunched" into the single binary in some way? Regards, Adam. signature.asc Description: PGP signature
Re: NetBSD install and usage by the blind
On Fri, Apr 08, 2016 at 07:45:05PM +, co...@sdf.org wrote: > On Fri, Apr 08, 2016 at 08:00:22PM +0100, Adam Thompson wrote: > > On Fri, Apr 08, 2016 at 10:37:26AM +, co...@sdf.org wrote: > > > Clarifying I mean to perform an install to disk using QEMU. > > > Afterwards, you can boot it. > > > > That may be possible and hadn't occured to me as an option. The trick > > would be > > to set things up such that I can install to the disk then reinstall it in > > the > > box. Not impossible, but a solution which allows automated install > > directly on > > the machine would be slightly easier I think. > > Perhaps with a liveCD containing QEMU. Yeah, that could work, perhaps with the iso on a usb drive or something. There're some accessible Linux liveCDs I could use I think. I guess I'd set it up so that it used the hdd on the box then do the install to that. I'd probably still need an image that could use a serial console though since I remember the other interfaces didn't work that well, but may be they've changed a bit. > But yes, in the case of NetBSD, it would be easier to run sshd or > do an automated install. (Unfortunately, I don't know how to do it). Agreed, if such a thing is possible. signature.asc Description: PGP signature
Re: NetBSD install and usage by the blind
On Fri, Apr 08, 2016 at 10:37:26AM +, co...@sdf.org wrote: > Clarifying I mean to perform an install to disk using QEMU. > Afterwards, you can boot it. That may be possible and hadn't occured to me as an option. The trick would be to set things up such that I can install to the disk then reinstall it in the box. Not impossible, but a solution which allows automated install directly on the machine would be slightly easier I think. Regards, Adam. signature.asc Description: PGP signature
Re: NetBSD install and usage by the blind
On Fri, Apr 08, 2016 at 10:49:12AM +, Michael van Elst wrote: > Installation usually requires access to a console, and the default PC > console is a physical keyboard and VGA display. I'm not aware of any > easy solution to make that accessible and googling for BIOS access > for blind people didn't reveal anything either. Yes, unfortunately that's the case, hence the requirement for either an automated install or some sort of accessibility (braille display support or speech) in the installer. > Some PCs have remote management support (e.g. ILO for HP servers > or Intel AMT). But these usually provide some graphical user interface > or web interface only. Nothing you could easily make accessible. Indeed, and the machine in question has no remote management in any case. > So that leaves a serial console as a possibility. For this the PC > needs a real serial port, a USB<->serial adapter is not enough. I suspected as much. > If you have a serial console you need an install CD that is configured > for serial console. Or if you have a network, you can create a PXE > boot server and configure the PXE bootloader to use a serial console. > > The installer works from a serial console. It does have a full screen > display, nothing command like. But I think that is something you > can use. I'm not sure if the box has serial, thinking about it it may well do. In which case, how does one get an appropriately configured install cd? > Saying this. It's probably not much work to create a version of the > install system that does a DHCP network configuration and starts sshd. That'd be great since I know the machine's set up for this kind of installation (it has previously been installed this way with a different os and I never altered the boot order) and I already run a dhcp server which I can set up to do this. Any idea how to go about creating that kind of installer? Regards, Adam. signature.asc Description: PGP signature
NetBSD install and usage by the blind
Hi all, As a long-time user of unix-like systems (primarily Linux, with a few others as well) I'm interested in setting up a machine with NetBSD. However I'm blind and can't find any examples of either accessibility options in the installer or an automated installation method wich isn't for Qemu or Xen. Any help is much appreciated. I currently have no access to a serial console for the machine, though I can probably get a usb to serial adapter if one will do the job. Additionally, I'm wondering about accessibility options once I have the machine installed, though I can just as easily ssh into the box as long as I can get the installer to set this up for me. Cheers, Adam. signature.asc Description: PGP signature
Re: 6.1.4-i386 Installation problem
*Problem Resolved* I found a [forum thread][1] suggesting that this issue might be the result of GUID Partition Table (GPT) on the disk. [1]: http://daemonforums.org/showthread.php?t=8186 I found [SystemRescueCd][2] and followed this [Wiping Out Old GPT Data][3] directions. [2]: http://sourceforge.net/projects/systemrescuecd/ [3]: http://www.rodsbooks.com/gdisk/wipegpt.html I used this method: # gdisk /dev/sda But it would have probably been simpler to avoid the menus and use: # sgdisk --zap-all /dev/sda After zapping the GUID partition table info from the disk, I shut down the machine, inserted the NetBSD installation disk, powered-up and the installation went as expected. On 09/06/2014 01:41 PM, Adam Jensen wrote: > I would like to tinker with NetBSD but I am having some problems getting > it to install on an old Dell Latitude CPi A366XT laptop. Both OpenBSD > and FreeBSD were successfully installed on this machine. > > [dmesg][http://pastebin.com/raw.php?i=UFHSSEsp] > > FreeBSD 10.0 is currently installed. > > NetBSD installation reaches the "newfs" step and fails with the error: > > Status: Command failed > Command: /sbin/newfs -V2 -O 2 -b 16384 -f 2048 /dev/rwd0a > Hit enter to continue > - > newfs: /dev/rwd0a: open for read: Device busy > > > I am following the directions at: > > http://www.netbsd.org/docs/guide/en/chap-exinst.html#exinst-partitions > > but there doesn't seem to be any variation of MBR partitioning and fdisk > slicing to get around this failure. > > Any advice, words of wisdom, or insight into this part of the > installation process will be greatly appreciated! > >
6.1.4-i386 Installation problem
I would like to tinker with NetBSD but I am having some problems getting it to install on an old Dell Latitude CPi A366XT laptop. Both OpenBSD and FreeBSD were successfully installed on this machine. [dmesg][http://pastebin.com/raw.php?i=UFHSSEsp] FreeBSD 10.0 is currently installed. NetBSD installation reaches the "newfs" step and fails with the error: Status: Command failed Command: /sbin/newfs -V2 -O 2 -b 16384 -f 2048 /dev/rwd0a Hit enter to continue - newfs: /dev/rwd0a: open for read: Device busy I am following the directions at: http://www.netbsd.org/docs/guide/en/chap-exinst.html#exinst-partitions but there doesn't seem to be any variation of MBR partitioning and fdisk slicing to get around this failure. Any advice, words of wisdom, or insight into this part of the installation process will be greatly appreciated!
