[https://www.openbsd.org/faq] [https://begriffs.com/posts/2017-05-17-openbsd-workstation-guide.html] [https://www.unix-experience.fr/bsd/openbsd/howto_install/] [https://www.c0ffee.net/blog/openbsd-on-a-laptop]
<iframe src="https://practices.tools">
Tue Jul 18 16:36:56 CEST 2023
Init launches rc, the script
/usr/local/share/doc/pkg-readmes/firefox /usr/local/share/doc/pkg-readmes/sdl2 #tuto pour utiliser un controller ??
re:lated to core(5); can be read with $ readelf -a /file; utils core files are image file of a segfault. i think mdr.
man 5 lowdown
for syntax, quite useful!!for simple use : % xrandr –auto
list monitor xrandr -q
xrandr --auto --output DP-0 --mode 1920x1080 --right-of DP-1
--output
== targeted screen DP-smthg --mode resolution
(resoultion* is the preffered resolution believed to be optimal by Xrandr)--right-of DP-1
being mainscreen or another preffered, –left-of –above –below –same as--off
to turn off a display xrandr --output DP-1 --off
for sound mixer and audio stuff
$ rcctl set sndiod flags..
$ rcctl restart sndiod
$ rcctl reload sndiod # try first to use usb device, then internal one, if the output is not read reload would force and switch.
aucat -i to read a file.wav
aucat -o file.wav to record something
audioctl : display to sdtout, if sounds is given or receive
driver for Intel HD pci, azalia, where man azalia(8): BUGS This driver does not support codecs that are intended for HDMI or DisplayPort connectivity.
I have dug into this issue with my DP port, and dock aux output, as of now this is where I am :
dmesg
an error, drm: inteldpauxwaitdone ERROR AUX C/DDI C/PHY C: did not complete or timeout within 10ms (status 0xac20023f), so is dp for Displayport, and its aux jack output ?, or my dock output jack ? because when I plug my jack in my dock, my sound gets cut off form HP or Speaker, but no sound is displayed. Moreover audioctl writes to stdout :
`$ audioctl
active=1finnally mixerctl, doesnt display the dock jack, only the laptop one.
Other Known bug is after suspend no sound is going through after suspend, now resolved by rcctl restart sndiod
df -h
Use nsxiv, or mupdf.
disklabel # To find disks, sd0, is this pc doas mount /dev/sd2i /mnt/purse doas mount -t msdos /dev/sd2i /mnt/liseuse sd1 will be the key : otherwise go see OpenBSD FAQ disks
xcutsel, to interact with buffers and cut, maybe a solution to have clipboard history, and dispay it also xclip
After erasing my home dot files, I went back to the FAQ to repopulate, Here is what I learned, again: - xenodm is preferred by openbsd rather than startx - xenodm use .xsession script to startup, make it executable and here’s my basic one:
#!/bin/sh
export ENV=$HOME/.kshrc
xrdb -merge $HOME/.Xresources
xmodmap -e "keysym BackSpace = Delete"
xsetroot -solid black &
st -z 36 -g 87x25+0+0 &
cwm
xrdb merge .Xressources
for xsession, xmodmap keynames refer to : /usr/X11R6/include/X11/keysymdef.h man 7 globe /usr/local/share/doc/xv/manuals/xvdocs.ps this is the ps doc for xv, X Image viewer, can convert to bmp for instance to set a background with X11, using anything to bmp
fc-list
to list fonts every available fonts; more info with man
https://daemonforums.org/showthread.php?t=5371 is how I resolve vim/less UTF8 support
however I still can’t make it work with st simple terminal, nor does cat support it
The link above is using the X composing key, to compose with alt special char, i set it up as it said, however I haven’t use the .XCompose he shared, nor I have the file yet in my Home directory.
Update 5 min later, with a simple research, UTF8 OpenBSD, and in THE FAQ : https://www.openbsd.org/faq/faq10.html (ok new issue, altgr doesnt works anymore, must be compose) anyway here is the line : If logging in via xenodm(1), add export LCCTYPE="enUS.UTF-8” to your ~/.xsession before starting the window manager. See customizing X for more details. Regarding this new issue, I should try to only keep, the line in xsession, and deletes the one in zshrc and kshrc also the line in xsession with the composekey first, even though this could be very useful for special char!
in the end : the alt compose key is not a good idea for the ones with an azerty keyboard, and altgreat used to enable a bunch of char on your keyboard. Next to it I have a unused key, that is on most french keyboard ‘ImpEc’, could be use as the compose key. Im tired so here is a todo - #todo with the link above and his compose key list, use Impéc key to compose and play with it.
I havent tested it but I left the two lines to export variables enabling utf8 for GTK, and LESS in both zshrc and kshrc and left the export [z;k]shrc in xsession (startup file for xenodm). I’m pretty sure that without them it will not work, despite not testing it, I was tired of restarting X with cwm alt maj ctrl Q
Anyway I have a lot of question to marc or Arthur explaining the ENV VAR, that is often talked about in Manuel Pages, maybe set the MAN VIEWER or something, is the way to use vim as the manuel viewer instead of less.
Everything could be done with a .profile, but ive read there : (link below) that OpenBSD prefer .kshrc rather than .profile, because of conflict, it isnt clear but I trusted those guys. even in faq customising x they suggest using kshrc instead of .profile
src man 7 fonts
& i[https://twiserandom.com/unix/x11-fonts-a-tutorial/index.html]
So there is something to understand, why is there a difference between what comes out of
fc-list
xlsfonts
The later xlsfonts, looks for X11 fonts only when fc-lists looks for all the fonts, and have then a certain path
in order to know where to look for.
Then there is also two systems the Xft one, modern, anti-aliasing and scalable font, and the core one, made for bitmap font exclusively.
A lot is explained in man 7 font to set up a new font,
ok so no path tutorial ?? #todo you need to write the : export PATH=${PATH:+${PATH}/ur/path} take care avec les espaces and co, pas hésiter à tester avec une var random
+ ‘h’ on a terminal line will look in the manual for the first command
there is not, since 2014. However if needed solutions are found with Bt usb dongle. Why no bt tho ? because bt can be an easy way to come in even unwelcomed.
still not a clear understanding of the ports
tho i have that for pkglocate that can search in the pkg or the ports tree idk
get the name of your current file write into your file : :r! echo %
:. so pour executer la ligne en haut qui est une ligne vim
Deutsch4000GermanWordsbyFrequency2SED.txt summup_OpenBSD.md
list :
echo {a..z} echo {a-z} a b c d e f g h i j k l m n o p q r s t u v w x y z only zsh tho pas ksh
reprends l’arguments de la dernière commande. !$ cherche argument contenant $1 ?!$1
https://www.openbsd.org/faq/ports/ports.html everything is there
but for a reminder search the ports by : cd /usr/ports make search key=”$query”
~/colors for info xcolor to pick up any colors on screen - incredible kcolorpicker to select color in rgb - for now HS
as aliases
hey () echo “hey”