CygniX_ has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
CygniX_ has joined #beagle
CygniX_ has quit [Client Quit]
CygniX has quit [Remote host closed the connection]
CygniX has joined #beagle
CygniX has left #beagle [#beagle]
CygniX has joined #beagle
CygniX has left #beagle [Konversation terminated!]
CygniX has joined #beagle
renrelkha has quit [Read error: Connection reset by peer]
renrelkha has joined #beagle
vagrantc has quit [Quit: leaving]
troth has quit [Ping timeout: 256 seconds]
troth has joined #beagle
troth has quit [Ping timeout: 252 seconds]
troth has joined #beagle
ikarso has joined #beagle
troth has quit [Ping timeout: 245 seconds]
buzzmarshall has quit [Quit: Konversation terminated!]
troth has joined #beagle
rob_w has joined #beagle
otisolsen70 has joined #beagle
vd has quit [Ping timeout: 256 seconds]
Shadyman has quit [Remote host closed the connection]
florian has joined #beagle
behanw has joined #beagle
troth has quit [Ping timeout: 256 seconds]
zjason` is now known as zjason
troth has joined #beagle
otisolsen70 has quit [Quit: Leaving]
nmingotti has joined #beagle
<nmingotti>
I recently bought a BB-AI. If i plug the usb connectoer BB-AI tunrs on [ok], if i push the power button it turns off [ok], if i press again the power button just one led tuns on and after 2-3 seconds if goes down again [??]. Any idea ? Is this expected/normal ?
ikarso has quit [Quit: Connection closed for inactivity]
vd has joined #beagle
troth has quit [Ping timeout: 256 seconds]
rob_w has quit [Quit: Leaving]
thinkfat_ has joined #beagle
thinkfat has quit [Ping timeout: 256 seconds]
Siegurd has joined #beagle
<Siegurd>
Hi! Did someone has any working instructions on buildroot on newest kernel linux-5.10.30-ti-r3 for pocketbeagle?
rob_w has joined #beagle
<Siegurd>
I have an instruction no how to build buildroot but only for kernel 4.14.18
mattb0ne has joined #beagle
Siegurd has quit [Ping timeout: 256 seconds]
thinkfat_ has quit [Ping timeout: 252 seconds]
troth has joined #beagle
Siegurd has joined #beagle
rob_w has quit [Remote host closed the connection]
thinkfat_ has joined #beagle
thinkfat_ has quit [Remote host closed the connection]
thinkfat_ has joined #beagle
florian has quit [Quit: Ex-Chat]
thinkfat_ has quit [Ping timeout: 256 seconds]
Morti has quit [Ping timeout: 252 seconds]
thinkfat_ has joined #beagle
thinkfat_ has quit [Remote host closed the connection]
thinkfat_ has joined #beagle
thinkfat_ has quit [Remote host closed the connection]
thinkfat_ has joined #beagle
<rcn-ee>
zmatt, ping... our udev rules are really killing bootup speed, any ideas for something "else" or should we just limit the rules to default kernel drivers?
<zmatt>
I mean, that gist shows that if you make really awful udev rules, boot time will suffer :P
<zmatt>
you were doing a recursive chrp/chmod on the sysfs dir for every single device on the system, including the bus devices that are the parent of other devices, causing basically everything in sysfs to be chgrp'd/chmodded multiple times
ikarso has joined #beagle
set_ has joined #beagle
<rcn-ee>
zmatt, where does the %p expand from? i'd like to lock that to: /sys/bus/iio/devices/
<zmatt>
%p is the device that the rule matches
<rcn-ee>
from: /bin/chgrp -R gpio '/sys%p'
<zmatt>
the problem isn't the action, the problem is that the rule matches every device
<rcn-ee>
yeap with DRIVERS=="*" that matches everyone..
<rcn-ee>
even none iio devices..
<zmatt>
DRIVERS=="*" is a pointless criterion
<zmatt>
if you want to match IIO devices, add SUBSYSTEM=="iio"
<rcn-ee>
is it since line 4 doesn't continue to line 10.. (thus ignoring the iio setting for subystem) ?
<zmatt>
nothing continues from line to line unless joined by escaping the line-break with \
<zmatt>
each rule is evaluated separately
<rcn-ee>
thanks zmatt, someday i'll figure out udev. ;)
<zmatt>
I think udev just literally evaluates each rule one by one for each device, given that it supports flow control (GOTO)
<zmatt>
(e.g. SUBSYSTEM=="iio" is a criterion, GROUP="gpio" is an action)
<zmatt>
that's why I often put actions on the next line indented, to make the rule clearer to read, but when doing so you need to be really careful to not forget the join the lines with a backslash
<zmatt>
so in retrospect I'm not sure whether doing so is actually a good idea, people who might edit or copy rules and overlook that small but very important detail
<rcn-ee>
which i had doing, when copying them between different subsystems..
<zmatt>
get rid of DRIVER=="*" it does nothing but waste time
<zmatt>
also, the GROUP="iio" action got lost
<zmatt>
(which sets the group of the actual device in /dev)
<zmatt>
btw, there is an iio group, why not use that instead of gpio ?
<zmatt>
like the current rule actually does for /dev
<zmatt>
/dev/iio* I mean
<rcn-ee>
so both the gpio and iio "group" was something that i would add by default.. Which meant everyone started creating new groups.. i've moved to just lock everything under 'gpio"..
<zmatt>
I mean, a bit more granularity isn't a bad idea
<rcn-ee>
we'd ended up with gpio, iio, i2c, spi, rpmsg, remotproc, and more...
<zmatt>
dunno, maybe it doesn't matter I guess
<zmatt>
proper privilege minimization needs to be custom anyway, so I guess it doesn't matter
<rcn-ee>
it got messy when i added gpio support to node-red, some i/o would work, but then spi would fail, etc as the node-red user didn't have every "group" access..
<rcn-ee>
so one group to make it eaiers..
set_ has quit [Ping timeout: 256 seconds]
zjason` has joined #beagle
zjason has quit [Ping timeout: 256 seconds]
drewfustini has quit []
drewfustini has joined #beagle
<jfsimon1981>
Hi, Which is a simple way to run a program that's not a service, just a compiled executable on boot ?
<zmatt>
jfsimon1981: I mean... services *are* executables run on boot
<zmatt>
jfsimon1981: I've updated it to recommend Type=exec instead of Type=simple
<zmatt>
(Type=exec is preferred over Type=simple in almost all cases, unless you're using an ancient version of systemd that doesn't support it yet)
buzzmarshall has joined #beagle
<jfsimon1981>
ok
<zmatt>
actually lemme also add a remark on RemainAfterExit...
<zmatt>
done
<zmatt>
hmm, the manpage makes a good point about Type=simple still having benefits over Type=exec ... maybe I should rephrase things
<jfsimon1981>
ok, in fact it remains active all the time
<jfsimon1981>
(should never exit)
<zmatt>
yeah then use Type=simple or Type=exec
<zmatt>
upon further reflection, the benefits of Type=exec aren't that huge anyway... using Type=simple is fine
<zmatt>
(in situations where you'd consider Type=exec you probably actually want Type=notify and have the service report to systemd when it has successfully started)
<jfsimon1981>
all right did work
<jfsimon1981>
it's quite simple but first time with systemd took some time, thanks for help
<zmatt>
yeah, the basics are quite simple although there are lots and lots of options available for things like configuring dependencies and fine-tuning the environment
<zmatt>
some of our service files have more than 50 directives
lucascastro has quit [Ping timeout: 256 seconds]
<zmatt>
there's also a bunch of options related to failure handling, e.g. you can have systemd restart your service if it crashes, but if it crashes 3 times within 10 seconds have it reboot the system instead
bzyx has quit [Ping timeout: 256 seconds]
ikarso has quit [Quit: Connection closed for inactivity]