View Single Post
  #3   (View Single Post)  
Old 30th July 2019
Sensucht94's Avatar
Sensucht94 Sensucht94 is offline
Real Name: Paolo Vincenzo Olivo
Fdisk Soldier
 
Join Date: Oct 2017
Location: Rome
Posts: 69
Default

Hello, and welcome

Quote:
Originally Posted by Luarini View Post
There is a video explaining how to install NetBSD 8.0
Hope you installed 8.1 though, since that's the latest formal release version, and 8.1 includes some important security fixes which haven't been backported to 8.0
Quote:
Installing Bash and using pkgin inside it enables to install packages
As you can confirm here under no circumstances should bash be a dependency for pkgin
Quote:
that in other way can't be installed
The simplest way of installing binaries is using pkg_add(1) from the native pkg_install framework, which is written in C and isvery fast, though it doesn't handle dependencies very well.
pkgin represents no more than a wrapper and an abstraction layer around the pkg_install suite, providing more features and a a modern UI, but also a higher degree of complexity. Another nice pkg_install wrapper is nih, which follows a totally different approach .

That said, pkgsrc is pretty much oriented towards compiling from source (I'm under the impression this sort of usage is implicitely encouraged and recommended in most scenarios), either natively using make, by cross-compiling through build.sh, or by relying on pkg_comp, which is a suite to automate package builds in a sandboxed env....as you can see, there's plenty of choice
Quote:
In turn, when I tried to install xf86-input-vmware, xf86-input-keyboard and xf86-video-vmware... these packages are not in the repository at all.
As shep already told rather exhaustively, a monolithic X version is already included by default in NetBSD's base, and all the related files should be located at /usr/X11R7/*, providing you chose 'Full Installation' as opposed to 'Installation without X' when prompted by sysinstall; the latter doesn't extract the x*.tgz binary sets, but doing it manually after installation requires literally no more than 2 commands.

Again, stressing shep's words, while pkgsrc also provides a modular (=split in the classical separate packages) version of Xorg, that is only meant for users who intend to tweak configure options, need the latest libraries and drivers available, or seek a very minimal X installation for embedded use; to sum up, modular Xorg is likely not what you're looking for.

xf86-input-keyboard and xf86-video-vmware can be both found in the monolithic X included in base, check out official sources at xsrc/external/mit
Quote:
Looking for the net I found theses packages in an ftp site of SmartOS, that uses NetBSD packages
Joyent's SmartOS repos provide pkgsrc binary packages for illumos, macOS and Linux only (at some point QNX), not NetBSD: most likely you downloaded a Linux or Solaris ELF which is never going to run on NetBSD! (...well, unless you enable Linux/SunOS binary emulation )
Quote:
The package xf86-input-keyboard gives an error that "keyring" not found, and can't be installed.

The question is, why, if the video shows how install those packages directly by using pkgin install program_name, those packages don't exist anymore in NetBSD repositories.
The answer is that the pkgsrc_2019Q2 quarterly branch has just been released and it usually takes some time for all binaries to be populate the latest repo (let's say it: they're really slow at carrying out this task and don't seem to care about it this much); on the plus side, they've had troubled getting rust-1.35 building on stable 8.x, which resulted in 300+ being broken (fortunately issue was fixed today by moving to 1.36): this may account for additional delay
Quote:
Using pkgsrc and make install clean gives an unrecoverable error about randrproto>1.6.0 is needed.
That's because whenever you decide to use modular Xorg, you need at least to specify it inside /etc/mk.conf, so that make(1) will know it has to pull all the required library dependencies from pkgsrc (rather than linking against base X11R7) in order to avoid incompatible versions, mismatches, unmet requirements, ultimately resulting in a dependency hell. This is all reasonably well explained in the official docs, see also this recent thread on the forum.
Quote:
hope NetBSD will update repositories, because it is very difficult to work this OS with.
On one hand I won't deny NetBSD is all but the prototype of the neophyte-friendly OS and can result quite irksome at times (add here the absolute lack of easily accesible tutorials)...nonetheless it's also true that NetBSD is just different, it thinks differently and has a different approach, philosophy, goals, target userbase... than Linux, Solaris or the other BSDs: you shouldn't expect it to work like something it isn't. Once understood this and grasped the basics, it becomes a very fun Unix system to work with, a pleasant never-ending discovery in its unique design
__________________
Be the change you want to see in the World

Last edited by Sensucht94; 30th July 2019 at 02:13 AM.
Reply With Quote