DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD Packages and Ports

OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD.

Reply
 
Thread Tools Display Modes
Old 12th October 2018
h2 h2 is offline
Port Guard
 
Join Date: Oct 2018
Posts: 10
Default

Code:
man: outdated mandoc.db lacks inxi(1) entry, run makewhatis /usr/share/man
that's an example of a small variance, in the Linux man install it updates the man db using some command, but I didn't even know about this one. I just tested and found that error, I'd missed it since it's above the man output in OpenBSD. Then there's the question of if that is an OpenBSD tool or if all the BSDs have it.

The intention is that the man db is updated post install to make sure it's up to date.

So you can see, in your single example, you have an unknown OpenBSD disk data syntax or structure variant, not corrected since I don't know what it is and can't reproduce it, you have the now fixed Memory glitch, and you have the man db update issue, and that's just from one single system that is slightly different from my test systems.
__________________
inxi system information script (install info) :: inxi git
Reply With Quote
Old 13th October 2018
ibara's Avatar
ibara ibara is offline
Future Defcon 201 speaker
 
Join Date: Jan 2014
Posts: 630
Default

Quote:
Originally Posted by h2 View Post
there's very little reason to create different ports between the various BSDs,
There are multiple huge reasons why there must be different ports between the various BSDs. A port written for FreeBSD won't work on OpenBSD and won't work on pkgsrc and all the other permutations of that.
Reply With Quote
Old 13th October 2018
h2 h2 is offline
Port Guard
 
Join Date: Oct 2018
Posts: 10
Default

Thanks for confirming, I half assumed there would be huge differences, but hoped there wouldn't be. I should in general assume that things will be different, not the same, I guess.

With that said, packaging two simple text files should not present any particular challenge to anyone familiar with the processes and tools. Once this is scripted, updating a port/package should only take a few minutes, if that long.
__________________
inxi system information script (install info) :: inxi git
Reply With Quote
Old 13th October 2018
shep shep is offline
Rc.conf Instructor
 
Join Date: May 2008
Location: Dry and Dusty
Posts: 1,171
Default

This is a little late but sysutils/dmidecode does a very verbose job of interrogating hardware.
Reply With Quote
Old 13th October 2018
GarryR's Avatar
GarryR GarryR is offline
Real Name: Garry Ricketson
Spam Deminer
 
Join Date: Jul 2015
Location: Durango, Mx.
Posts: 297
Default

RE:
Quote:
man: outdated mandoc.db lacks inxi(1) entry, run makewhatis /usr/share/man
I had not noticed that, but any way, running :
Code:
makewhatis /usr/share/man
has fixed that.

Code:
garry% man inxi
INXI(1)                           inxi manual                          INXI(1)

NAME
       inxi  - Command line system information script for console and IRC

SYNOPSIS
       inxi

       inxi [-AbBCdDfFGhiIlmMnNopPrRsSuUVwzZ]---snip----
I mentioned earlier in the this thread, about not really having time to do anything with porting, also the lack of tech knowledge/skill being a factor. Ibara has done a lot with making some tutorial videos, etc. to help on the "learning curve" part, but again how much free time I get is a factor,
any way, again I want to thank you for taking the time on this. Before, all I had was really just the inxi script, and I did not have the manual. I may have some questions later, but obviously I need to read the manual first, and see if maybe those questions are answered in the manual.

Quote:
you have an unknown OpenBSD disk data syntax or structure variant, not corrected since I don't know what it is and can't reproduce it,
I don't know if the manual will cover this or not, I am not sure how I would go about getting that information my self, it may be something I have configured poorly or wrong, any way, to me this is interesting. Thanks
==== edit =======
Quote:
h2>> With that said, packaging two simple text files should not present any particular challenge to anyone familiar with the processes and tools.
I have not yet really tried any kind of porting, all though I did start reading some of the instructions, etc. And downloaded some of what is needed. NOT making any promises here, and if someone else beats me to it, that would be fine, but any way, it seems like this might be a good 1st time project for me,.. we'll just have to see on that.
__________________
My best friends are parrots

Last edited by GarryR; 13th October 2018 at 01:16 AM. Reason: Posts while I was writing, additional comment
Reply With Quote
Old 13th October 2018
h2 h2 is offline
Port Guard
 
Join Date: Oct 2018
Posts: 10
Default

For some reason, don't ask me why, I was struck when a TinyCore guy suggested I make a tcz tce package of inxi. So eventually I got around to it, and will submit the first one as soon as I finalize inxi 3.0.27 since it has some meaningful fixes in it for tinycore. In that case, the documentation was not very good, sometimes out of date, and sometimes misleading, and the process of actually making a tinycore tce package is not that easy given what that tiny thing is technically, but I got it working eventually. I think.

A BSD port should be much easier I believe, better documentation, and far easier to work with build environment. From my perspective, I'd never take on such a thing without fully scripting it so all I had to do was run the script, then submit the built port using whatever process the BSD in question has. If that last part could be automated, I'd do that too.

inxi is looking for openbsd disk data using openbsd specific syntax, I believe the following command should give the information, unless the syntax has changed even more:

Code:
grep -E 'sector|removable' /var/run/dmesg.boot
paste the resulting lines in here verbatim and I can debug it.

I'd like to get that fixed before doing 3.0.27 since I don't like releasing a new inxi with a known failure, even if it's not my fault.

I installed OpenBSD 6.3 in vm and don't see any changes in syntax, and disk size report works as expected, but that's just one instance.

ps, I've also had some very fine parrot friends, including budgies, which act the same as, and are really just mini, parrots. But also big ones.
__________________
inxi system information script (install info) :: inxi git

Last edited by h2; 13th October 2018 at 04:44 AM.
Reply With Quote
Old 13th October 2018
GarryR's Avatar
GarryR GarryR is offline
Real Name: Garry Ricketson
Spam Deminer
 
Join Date: Jul 2015
Location: Durango, Mx.
Posts: 297
Default

Code:
garry% grep -E 'sector|removable' /var/run/dmesg.boot
sd0: 715404MB, 512 bytes/sector, 1465149168 sectors
cd0 at scsibus1 targ 1 lun 0: <HL-DT-ST, DVD+-RW GH50N, B104> ATAPI 5/cdrom removable
garry%
Thanks

I had a pair of budgies as well, but I guess best not go into that here, how ever the Parrots are what take up most of my time.
__________________
My best friends are parrots
Reply With Quote
Old 13th October 2018
ibara's Avatar
ibara ibara is offline
Future Defcon 201 speaker
 
Join Date: Jan 2014
Posts: 630
Default

Quote:
Originally Posted by h2 View Post
From my perspective, I'd never take on such a thing without fully scripting it so all I had to do was run the script, then submit the built port using whatever process the BSD in question has. If that last part could be automated, I'd do that too.
This part can be automated if inxi is available on CPAN. At least for OpenBSD.
Reply With Quote
Old 13th October 2018
h2 h2 is offline
Port Guard
 
Join Date: Oct 2018
Posts: 10
Default

GarryR, if you try pinxi (shortcut download url: smxi.org/pinxi) the disk issue should be corrected, it was a variant on the ordering of the string values for disk in dmesg.boot. This is why in general I avoid as much as possible all data structures that are not meant for machine parsing, they can and do change randomly since there is no assumption that the string values (sentences) are actually going to be used as real data.

Code:
pinxi -Ipdxxxz
This will confirm everything is working as expected.

ibara, inxi is not in cpan, nor do I expect that to ever change.

By scripting, I meant, in pseudocode:

grab latest files
read inxi file, get version, update version data
make builder with correct paths
compress file into desired format
upload port
__________________
inxi system information script (install info) :: inxi git
Reply With Quote
Old 13th October 2018
ibara's Avatar
ibara ibara is offline
Future Defcon 201 speaker
 
Join Date: Jan 2014
Posts: 630
Default

Quote:
Originally Posted by h2 View Post
ibara, inxi is not in cpan, nor do I expect that to ever change.

By scripting, I meant, in pseudocode:

grab latest files
read inxi file, get version, update version data
make builder with correct paths
compress file into desired format
upload port
Yes, and we have a script that does exactly this, but only for things in cpan.
Reply With Quote
Old 13th October 2018
h2 h2 is offline
Port Guard
 
Join Date: Oct 2018
Posts: 10
Default

Changing download urls should not present any challenges. As I said, I've never had any thought or desire re putting inxi into cpan, I don't see any upside for me there at all. It's just a piece of software, like any other, except simple files, no compiling. Plus it only became Perl recently, relatively speaking, which is actually one reason I was able to start enhancing BSD support much more, just was not practical in the legacy version of inxi.
__________________
inxi system information script (install info) :: inxi git
Reply With Quote
Old 13th October 2018
ibara's Avatar
ibara ibara is offline
Future Defcon 201 speaker
 
Join Date: Jan 2014
Posts: 630
Default

I mean, I am not offering to make any ports of inxi. At least for me, I'm also not actually talking to you, h2 (mostly); I'm trying to encourage those on these forums that appear to be users of your software to make a port.
Reply With Quote
Old 13th October 2018
h2 h2 is offline
Port Guard
 
Join Date: Oct 2018
Posts: 10
Default

Yes, I'm talking to those users too, pointing out that it's actually trivial to do it if you script it. But it's also easy to just install it and run it, so it's no big deal either way to me. Since the -U flag always works, it's basically an 'install once, run forever' tool, unless the location is overwritten in system upgrades. But if I can figure out how to make a TCE package, which is hard, weird, and convoluted, and very poorly documented, with a very strange build environment, anyone should be able to figure out how to make a simple port.

[update]Here's an almost verbatim example of how to create a package from a man page and a shell script file, which is basically the same thing as packaging inxi, except that you'd have to handle the dependencies of Perl 5 (any perl 5 >= 5.008) and recommended programs etc.

https://undeadly.org/cgi?action=arti...20080318060000

This is my tce build script: https://smxi.org/in/tcbi

I have to download it each time due to how tinycore works (runs in ram), but it give the rough logic of grab file, get version number, create build directory, squash build directory, create required files, then compress it all.

This is probably maybe 2x more steps that would be required by a normal package I'd guess. Note that because tinycore is, well, tiny, they discourage adding man pages, so i didn't. But it would just be one more file grab and move to share directory.
__________________
inxi system information script (install info) :: inxi git

Last edited by h2; 13th October 2018 at 10:12 PM.
Reply With Quote
Old 14th October 2018
GarryR's Avatar
GarryR GarryR is offline
Real Name: Garry Ricketson
Spam Deminer
 
Join Date: Jul 2015
Location: Durango, Mx.
Posts: 297
Default

Quote:
h2> GarryR, if you try pinxi (shortcut download url: smxi.org/pinxi) the disk issue should be corrected, --snip--
Ok, thanks , I will take a look at it later, I am not feeling very well right now,and it's late for me.
Kind of off topic, but I am curious , how did you stumble on to this topic ? And also welcome to the forum , I see you just joined recently.
__________________
My best friends are parrots
Reply With Quote
Old 14th October 2018
GarryR's Avatar
GarryR GarryR is offline
Real Name: Garry Ricketson
Spam Deminer
 
Join Date: Jul 2015
Location: Durango, Mx.
Posts: 297
Default

Here is the output of :
Code:
pinxi -Ipdxxxz >pinxi-output.txt
Code:
Drives:
  Local Storage: total: 682.26 GiB 
  used: 68.45 GiB (10.0%) 
  ID-1: /dev/sd0 vendor: Hitachi 
  model: HUA721075KLA330 
  size: 682.26 GiB serial: N/A 
  Optical-1: /dev/cd0 vendor: HL-DT-ST 
  model: DVD+-RW GH50N rev: B104 
  dev-links: N/A 
  Features: speed: N/A 
  multisession: N/A audio: N/A 
  dvd: yes rw: cd-rw,dvd-r state: N/A 
Partition:
  ID-1: / size: 1004.8 MiB 
  used: 91.9 MiB (9.1%) fs: local 
  dev: /dev/sd0a 
  ID-2: /home size: 496.05 GiB 
  used: 62.47 GiB (12.6%) fs: local 
  dev: /dev/sd0k 
  ID-3: /tmp size: 3.93 GiB 
  used: 848 KiB (0.0%) fs: local 
  dev: /dev/sd0d 
  ID-4: /usr size: 1.97 GiB 
  used: 749.3 MiB (37.2%) fs: local 
  dev: /dev/sd0f 
  ID-5: /usr/X11R6 size: 1004.8 MiB 
  used: 178.7 MiB (17.8%) fs: local 
  dev: /dev/sd0g 
  ID-6: /usr/local size: 9.84 GiB 
  used: 4.67 GiB (47.5%) fs: local 
  dev: /dev/sd0h 
  ID-7: /usr/obj size: 5.90 GiB 
  used: 2 KiB (0.0%) fs: local 
  dev: /dev/sd0j 
  ID-8: /usr/src size: 1.97 GiB 
  used: 2 KiB (0.0%) fs: local 
  dev: /dev/sd0i 
  ID-9: /var size: 9.73 GiB 
  used: 311.5 MiB (3.1%) fs: local 
  dev: /dev/sd0e 
  ID-10: swap-1 size: 3.20 GiB 
  used: 0 KiB (0.0%) fs: swap 
  dev: /dev/sd0b 
Info:
  Processes: 60 Uptime: 34m 
  Memory: 2.95 GiB 
  used: 685.0 MiB (22.7%) 
  Init: init (BSD) v: N/A Compilers: 
  gcc: 4.2.1 clang: 5.0.1 Shell: csh 
  pinxi: 3.0.26-26
Does the Inxi manual also apply to Pinxi ? this is reduntant, but
Code:
pinixi -F
Code:
garry% pinxi -F
System:    Host: garry.garry.org Kernel: OpenBSD 6.3 amd64 bits: 64 Desktop: Openbox 3.6.1 
           OS: OpenBSD 6.3 
Machine:   Type: N/A Mobo: Dell model: OptiPlex 780 serial: BSN8BP1 BIOS: Dell v: A06 rev: 2.5 
           date: 11/03/2010 
Battery:   Permissions: Unable to run dmidecode. Are you root? 
CPU:       Topology: Dual Core model: Intel Core2 Duo E8400 bits: 64 type: MCP L2 cache: N/A 
           Speed: 3000 MHz min/max: N/A Core speeds (MHz): No speed data found for 2 cores. 
Graphics:  Message: Device data requires root. 
           Display: server: X.Org 1.19.6 driver: modesetting resolution: 1440x900~60Hz 
           OpenGL: renderer: Mesa DRI Intel Q45/Q43 v: 2.1 Mesa 13.0.6 
Audio:     Message: Device data requires root. 
Network:   Message: Device data requires root. 
           IF-ID-1: em0 state: active speed: 1000baseT duplex: full-duplex,master mac: f0:4d:a2:27:86:49 
Drives:    Local Storage: total: 682.26 GiB used: 68.45 GiB (10.0%) 
           ID-1: /dev/sd0 vendor: Hitachi model: HUA721075KLA330 size: 682.26 GiB 
Partition: ID-1: / size: 1004.8 MiB used: 91.9 MiB (9.1%) fs: local dev: /dev/sd0a 
           ID-2: /home size: 496.05 GiB used: 62.47 GiB (12.6%) fs: local dev: /dev/sd0k 
           ID-3: /tmp size: 3.93 GiB used: 482 KiB (0.0%) fs: local dev: /dev/sd0d 
           ID-4: /usr size: 1.97 GiB used: 749.3 MiB (37.2%) fs: local dev: /dev/sd0f 
           ID-5: /var size: 9.73 GiB used: 311.5 MiB (3.1%) fs: local dev: /dev/sd0e 
           ID-6: swap-1 size: 3.20 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sd0b 
Sensors:   Platform: No Openbsd support. Is a comparable sensors tool available? 
Info:      Processes: 63 Uptime: 42m Memory: 2.95 GiB used: 471.0 MiB (15.6%) Shell: csh pinxi: 3.0.26-26 
garry%
__________________
My best friends are parrots
Reply With Quote
Old 14th October 2018
h2 h2 is offline
Port Guard
 
Join Date: Oct 2018
Posts: 10
Default

pinxi is the development branch of inxi, so the only difference re man page it that the man page might be slightly ahead of the inxi man page re new features or edits. Plus it's man pinxi, not man inxi, of course.

I found this thread searching for inxi things, and then noticed the bug in memory output, then the bug in the disk total size, and wanted to get those resolved. Searching for inxi things is a decent way to proactively fix bugs I notice that never get reported, as in this case, or to see if it's working as expected in various systems and configurations.

inxi has built in error output that can tell me that certain types of internal errors happened, plus the Perl errors I saw show me that something that should have been tested as valid data had not been tested since it's never empty in normal use. So sometimes when I am lucky I can work out the error based on either the Perl error or the value of the field that should be present but isn't without having to get more information, or a debugger dataset, or waiting for a github issue that will probably never get filed.

The question of ports was also interesting, since I don't tend to see a lot of feedback from BSD users, so I don't really have much idea of BSD use of inxi.

The disk total size is fixed, good, so I can do 3.0.27 now, thanks.
__________________
inxi system information script (install info) :: inxi git

Last edited by h2; 14th October 2018 at 05:47 PM.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Generate a tone or "beep" GarryR OpenBSD General 9 3rd November 2017 09:08 PM
Generate passwords from the commandline Carpetsmoker Guides 18 24th February 2014 01:43 AM
Hardware recommendation: what hardware to buy for my new FreeBSD desktop? Broodjegehaktmetmayo General Hardware 92 11th February 2009 10:43 PM
Generate xorg.conf.new and black screen aleunix OpenBSD Packages and Ports 2 4th June 2008 10:49 AM


All times are GMT. The time now is 03:42 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick