I saw this article on the blackberry site https://blogs.blackberry.com/en/2023/02/this-is-the-kind-of-rust-the-automotive-industry-needs Do anyone know if this is available yet? Even as a preview package or similar? I would very much like to try it out. So if it is possible to download and install in a QNX 7.x or CAR3 environment, I would be very happy if someone could give me some pointers how to do that.

I’m interested in testing some QNX Web Browser 2.0 development (https://www.qnx.com/developers/docs/7.0.0/#com.qnx.doc.blink.browser/topic/browser_about.html) . But the Web Browser package is not available for neither SDP 7.1 or 8.0, which is the only versions I have license for. Is it possible to get the Web Browser package separately in some way? Or do I have to get a 7.0 license and install that locally first?

I am trying to install QNX 6 from CD. I formatted the entire hard drive using cfdisk as "QNX 6 filesystem", but I still get the error message "No QNX 6.1 filesystem or greater available to mount". Any idea how I can fix this error?

I’m trying to figure out if I’m able to port a webassembly based webapplication to QNX. But it is hard to find any information about what versions of browsers and web engine libraries that are shipped with what version of QNX and what features they support. SDP 7.x (which I believe is used with QNX 7 and CAR 3?) seems to be shipped together with a modernized browser based on the Blink engine (instead of the webkit lib used in QNX 6). [It uses uses the V8 JavaScript engine](https://blackberry.qnx.com/content/dam/qnx/products/qnxcar/QNX_WebBrowser_ProductBrief_FINAL.pdf) [which supports webassembly](https://v8.dev/) So the browser in it self should support webassembly, right? I guess the webassembly code created with Emscriptens should be able to be compiled on any platform and transferred to the QNX system. Cause I believe Emscriptens wont run correctly on QNX? Or can I compile Emscripten with q++ on QNX and create the webassemby directly on the QNX system? I'm not sure I understood it correctly. But it seems like Emscripten should be able to compile and run on any system that can use LLVM, which QNX does. Can anyone with a bit more QNX knowledge confirm if this might be possible or not?

I am using QNX (ARM Cortex A53 with FOUR cores) and when I do ***top***, I have the below. According to the below idle percentages for each of the core, I'd like to confirm CPU/Core 0 is the most idle, that is, being used only ~7%, thus being the most candidate available for usage? CPU 1 is maxed out with zero percentage of idling. The one process uses most of one of the core is my_app, which has four thread. Based idle CPU idle percentage info below, it looks like my_app is tied to Core 2. But why is Core 1 has 0% of idling, that is, maxed out of percentage of usage. Thanks for any explanation.

PID         TID PRI STATE    HH:MM:SS    CPU     COMMAND
1335344     9   254 Run      0:32:31     25.00%  my_app
1335344     5   253 Run      0:06:58     5.60%   my_app
1335344     7   253 Rdy      0:00:38     0.51%   my_app
1335344     6   253 Rdy      0:00:32     0.43%   my_app

              Min        Max       Average 
CPU 0 idle:   93%        93%        93% 
CPU 1 idle:    0%         0%         0% 
CPU 2 idle:   72%        73%        72% 
CPU 3 idle:   93%        94%        93%
 
Mem Avail:   1396MB      1396MB      1396MB  
Processes:    55         55         55    
Threads:     142        142        142

I am using a resource manager to read the data from the communication channel and send it to the application. I have doubt, is the QNX resource manager half duplex or full duplex? Can simultaneous read/write work with QNX resource manager?

I've done a lot of digging but haven't found an answer to my problem. Currently, I have the following command: netstat | grep telnet | grep ESTABLISHED | awk 'NR==1{ print $5}' Which returns something like this: 192.168.15.73.64759 From this, I want to get just the IP without the port. So, 192.168.15.73 The system I'm doing this on runs an embedded Unix variant (QNX) and does not support -o as an option to grep. The system supports sed which is likely the best route, but I'm unfamiliar with that application. Can anyone tell me what I could add to get the output I'm looking for?

I'm using QNX. I have the following output of ls -l: drwxr-xr-x 2 root root 4096 Jul 26 2021 bin From this, I would want to use sed to extract the user and group, and put these strings into shell variables. I do not have access to a stat command.

I'm building QNX OS (BSP 7.0 x86_64) and I have a working image. I'm running it over a qemu emulated enviroment. Qemu virtual machine runs in a Windows host and is invoked as follows: ./qemu-system-x86_64.exe -m 1G -smp 4 -hda QNX.img -realtime mlock=off -vga std -sdl -nic tap,id=mynet0,ifname=tap0,model=e1000,script=no,downscript=no Once started I run: export GRAPHICS_ROOT=/usr/lib/graphics/intel-drm export LD_LIBRARY_PATH=$(getconf _CS_LIBPATH):$GRAPHICS_ROOT With valid environment variables, I launch intel-drm. No logs are generated so seems it is working properly. pidin | grep drm-intel 430102 1 _64/sbin/drm-intel 10r SIGWAITINFO 430102 2 _64/sbin/drm-intel 10r CONDVAR (0x8452bb0) 430102 3 _64/sbin/drm-intel 10r CONDVAR (0x824cefc) 430102 4 _64/sbin/drm-intel 10r RECEIVE 1 430102 5 _64/sbin/drm-intel 10r RECEIVE 1 430102 6 _64/sbin/drm-intel 10r RECEIVE 1 462873 1 _64/sbin/drm-intel 10r SIGWAITINFO 462873 2 _64/sbin/drm-intel 10r CONDVAR (0x8452bb0) 462873 3 _64/sbin/drm-intel 10r CONDVAR (0x824cefc) 462873 4 _64/sbin/drm-intel 10r RECEIVE 1 462873 5 _64/sbin/drm-intel 10r RECEIVE 1 462873 6 _64/sbin/drm-intel 10r RECEIVE 1 The problem comes when trying to launch drm-probe-displays. Just after execution it crashes and makes intel-drm crash. Process 577558 (drm-intel) terminated SIGSEGV code=1 fltno=11 ip=000000000809057f(/x86_64/sbin/drm-intel@main+0x000000000003181f) mapaddr=000000000004857f. ref=0000000000000028 Please run drm server first! # Jun 16 10:07:54.049 dumper.4 slog 0 run fault pid 577558 tid 4 signal 11 code 1 ip 0x809057f x86_64/sbin/drm-intel Jun 16 10:07:54.050 dumper.4 slog 0 pid 577558 core file created at /tmp/drm-intel.core There isn't more information about the crash. By checking pci-tool, I'm able to see that the device vendorID/deviceID are not intel specifics. **Could be the error produced by this device?** **If it is the case, does anyone knows how can I emulate intel graphics on qemu?** B000:D02:F00 @ idx 4 vid/did: 1234/1111 Technical Corp, class/subclass/reg: 03/00/00 PC Compatible VGA Display Controller **Any clue about what could be the root cause?**

I'm doing a university project on QNX RTOS (using an academic license). I'm following [Building a BSP](http://www.qnx.com/developers/docs/7.0.0/#com.qnx.doc.neutrino.building/topic/bsp/bsp_build.html) . So far I've managed to build (using bios_mkusbimage script in the BSP archive) .img file for x86_64 target. Then I converted .img to .vdi file (VBoxManage convertdd input.img output.vdi) and finally loaded it. The result is: Or, as text:

Loading IFS...decompressing...done 
System page at phys:000000000010c000 user:ffff808000003000 kern 808000006000 

Starting next program at vffff80000007388b MFLAGS=1 .11 ClockCycles offsets within tolerance elcome to Q. Neutrino SDP 7.0 on x8664 system 
Starting slogger2 server ...
Starting PCI server ... 
Set PCI device list ... 
Starting EIDE block driver ... 
unable to access /dev/hd0t179 'ot3Tt11:7.n:nele7i7la:TensleieCted 
Starting USD host ... 
Starting devb-umass o audio device has been detected 
Starting input services ... 
Starting serial driver ... 
Starting consoles ... 
Starting shells ... 
#

The OS seems to boot successfully, but I'm unable to type anything. I'm looking either for a way to fix the keyboard input, or get a SSH/telnet/... connection to the QNX shell.

We have tried to configure using ./configure command. An error is like no c++11 compiler support. We are following the steps ie mentioned in some blog. We want to know like is there any other specific steps for this?

I have a server with qnx 6.5 I want to use dd comand to take full os backup What is right to dd /dev/hd0 or dd /dev/hd07t my aim is to have an image to be applied for other hardware Other concern is if i take dd /dev/hd0 will this produce a file with the same hdd size or the final size will be the data size only

I have Ubuntu 16.04 where I have QNX7 as a virtual machine running in Vmware player 15. My problem is that the font is so small in the virtual machine. I have tried different display resolution in the virtual machine settings. But no matter what resolution I set, the QNX7 display size remains constant. I have saw one solution to the similar situation with Windows 10 as a host machine : https://unix.stackexchange.com/questions/297569/guest-os-resolution-text-too-small-in-vmware-workstation-12-player But I could not figure out how to do the options "override high DPI scaling behavior" and select the System Enhanced for Scaling performed by:. and so on as in the above post. Any suggestion is very appreciated. Thank you so much.

What I want to do ----------------- I just want to extract a backup version of a file for analysis, /etc/net.cfg, which is in a tar. What happens when I try ----------------------- It fails, like so... # tar -tf mytar.tar | grep net.cfg /etc/net.cfg # tar -xf mytar.tar /etc/net.cfg tar: Removing leading `/' from absolute path names in the archive # tar -xf mytar.tar etc/net.cfg tar: etc/net.cfg: Not found in archive tar: Error exit delayed from previous errors Troubleshooting I've tried -------------------------- I made a separate test.tar which contains only a "test1.txt" and "test2.txt", and if I do tar xf test.tar test1.txt it correctly extracts just the 1 file I want. So extracting the single file is working in this other case. Question -------- Am I doing something wrong? **How do I extract from an *absolute path* like /etc/net.cfg out of the given tar file into the working directory?** Details ------- Operating system: QNX Shell: /bin/ksh

I have 3 computers, A, B, and C, and I perform identical operating system and software installations on them. For any specific file on A, can I expect that same file on B and C to have the same inode number for its instance of that file? Our intrusion detection system is set up by acquiring an initial file system image from A and then using that same file system image to do future comparisons against A, B, and C. I am new to the program, but it seems that this has worked in the past. I don't know how the inode number sequencing works, so I'm guessing it just starts at 1 and counts up for each file, or something similar. If that's the case, that's probably why file inode numbers have been consistent even across computers for us in the past - the same files were created in the same order. Though I'm not sure if we can always count on that. However, now I am getting notifications of a few files changed, and for the first file I am looking into it is only the file inode number which has changed. I think someone reinstalled the operating system and software on the computer with the notifications. **Can file inode numbers be counted on to be the same across identical OS/software installs on different computers (or sequential re-installs on the same computer)?** If I were to acquire a new file system image from either A, B, or C, can I expect that to fix my "problem" (not even sure if it's a problem)? I generally have access to only 1 or 2 of the computers at a time, so I cannot inspect A or C right now, and I do not know what their report would look like. I only know that the inode number of at least 1 file on computer B is not what was expected. In this case, the operating system is QNX 6. For file system type, mount tells me that the /dev/hd file's are "on / type qnx4"... so file system type qnx4? I guess qnx has its own file system type? I didn't realize that. Or maybe that's no accurate. Other commands for checking file system type do not seem to exist on the computer. **Update**: Apparently I was mistaken about something. Although our reference data on the original state of the file system does include files' inode numbers and I have the option to include that in the test, I was not supposed to include the inode data in this check that I described in the question, and "It worked in the past" is because of this. So I do not actually need what I have asked for here after all, sorry about that. I will leave this question open though since I still find it interesting and a partial answer has been started in the comments.

**TL;DR**: What does mount -e do? Overview -------- Over ssh, mount commands are being sent by software that I need to maintain. Twice, the mount commands use an -e option. I don't know what -e is for and can't find a good enough answer. Details ------- In my case, the procedure that is doing this is named "Verify Backup OS" and the command being sent over ssh is the following: mount -e /dev/hd0; umount -f /dev/hd0t177.1; mount -e /dev/hd0; mount -tqnx6 /dev/hd0t177.1 /BackupPartition After doing that, the software then appears to do a search in /BackupPartition so I think that's where the "verify" part of the procedure name comes into play. Man output ---------- If I do man mount, the text for the command and for -e is: Usage: mount [-abwruv] -t type [-o options] [special] mntpoint mount [-abwruv] -T type [-o options] special [mntpoint] mount [-abwruv] -e [-t|T type] [-o options] special [mntpoint] mount … -e Enumerate the device given by special Product Documentation --------------------- On the QNX page for mount , it has -e Enumerate the children of the special device. By the description it would appear that the mount -e somehow enumerates the device in some capacity. I was expecting that to mean "prints out some data to stdout", but that doesn't make much sense in this case since the output is not visible to the software user and is not piped or redirected anywhere, and I tried the command manually on the command line where it produced no output and no sign that anything happened. **What does mount -e do?**

I have 5 diferent serial devices that are connected to physical serial ports on debian stretch computer and internally should be forwarded to QEMU machine. Inside qemu is QNX 6.5.0 system, so i am not sure if i can use virtio-seral drivers or similar solutions. Linux standard limitation of 4 serial ports is solved with: /etc/default/grub: 8250.nr_uarts=8 So the only problem now I have with QEMU max serial ports = 4. Can this be solved by recompiling qemu, and is there some other solution?

I am facing an issue where I have to write a shell script to read a file only if it is not used or under write by any other program. I cannot use lsof as this script is going to run on the embedded hardware running QNX with very basic shell functionalities hence no third party-tools and libraries.

I have Ubuntu 17.10 on USB Flash drive and in VM VirtualBox. I have a QNX4 image file on an external hard drive that I can mount on the computer running from the Ubuntu 17.10 USB flash drive. I have another computer with Ubuntu 17.10 running in VM VirtualBox Version 5.2.2 r119230 (Qt5.6.2) that gives me an error when trying to mount the QNX4.img file. The error I get is "/mnt/QNX4_Drive: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error." I have the external hard drive shared from host to virtual machine. I perform on system running Ubuntu from USB modprobe qnx4 mount -t qnx4 QNX4.img /mnt/QNX4_Drive -o loop which works fine and I can access the files. on Windows 7 pro system running VM VirtualBox running Ubuntu modprobe qnx4 mount -t qnx4 /media/sf_C_DRIVE/QNX4.img /mnt/QNX4_Drive -o loop Produces the error message listed above Is there something else I need to do on the VM VirtualBox to be able to mount image files on the host machine?

QNX4 operating system using Korn Shell. This is in a .profile file. export VARDIR=//1/usr/pvcs What does the //1/ represent?