Search found 8 matches

by cseiler
22 May 2017, 20:53
Forum: Profound Expert Discussions
Topic: [Jessie] Separating policy from binaries
Replies: 7
Views: 14185

Re: [Jessie] Separating policy from binaries

Quick update:
cseiler wrote:I haven't yet tried the logi.RTS at all
That just works fine after the upgrade. (With the Jessie version of the package.)

Regards,
Christian
by cseiler
22 May 2017, 15:04
Forum: Profound Expert Discussions
Topic: [Jessie] Separating policy from binaries
Replies: 7
Views: 14185

Re: [Jessie] Separating policy from binaries

May I ask, how were you able to perform a dist-upgrade despite the puny 4 GB eMMC? I didn't do anything special. This was mostly the stock image as we got it from you (I think I installed the command line editor "joe" beforehand). I just checked /var/log/apt/history.log, and it did run ou...
by cseiler
22 May 2017, 13:34
Forum: Profound Expert Discussions
Topic: [Jessie] Separating policy from binaries
Replies: 7
Views: 14185

Re: [Jessie] Separating policy from binaries

Hi Lukas, Okay the former is actually a bug, other users except for the pre-configured user "pi" should always be allowed to log in. I've now replaced "exit" with "return" in that script and just pushed a rectified version of the deb-package to the apt repo. Thanks a lo...
by cseiler
22 May 2017, 10:12
Forum: Profound Expert Discussions
Topic: Kernel module + Core 3 questions
Replies: 5
Views: 13365

Re: Kernel module + Core 3 questions

Hello again, Why use a global lock piDev_g.lockPI for the process image for everything? Typically values that are read/written from/to that region are 4 bytes or smaller, where atomic operations can be used to ensure that these writes are consistent. Changing individual values could be sped up quite...
by cseiler
22 May 2017, 10:09
Forum: Profound Expert Discussions
Topic: [Jessie] Separating policy from binaries
Replies: 7
Views: 14185

Re: [Jessie] Separating policy from binaries

Hello, just to make that clear: The material you are talking about is not officially released. Yes, I was aware of that, I apologize if I didn't make that clear in my original message. I was just trying to provide some early feedback to improve the experience for everyone. Our policy to let the comm...
by cseiler
19 May 2017, 20:02
Forum: Profound Expert Discussions
Topic: [Jessie] Separating policy from binaries
Replies: 7
Views: 14185

[Jessie] Separating policy from binaries

Hello, I've already tested the Jessie packages on an existing image, and I noticed a small detail here: the piserial package contains both the binary piSerial for extracting the serial number of the device, as well as a hook into /etc/profile.d that does some automatic things (disallow any user to s...
by cseiler
19 May 2017, 19:47
Forum: Profound Expert Discussions
Topic: Kernel module + Core 3 questions
Replies: 5
Views: 13365

Re: Kernel module + Core 3 questions

Hello, thank you very much for your quick responses, very much appreciated. I'm delighted to get some hardcore questions here. :D The kernel module parses the configuration JSON file from the filesystem directly - and uses the set_fs(DS_KERNEL) trick to use the VFS API to read the file. Wouldn't it ...
by cseiler
19 May 2017, 10:22
Forum: Profound Expert Discussions
Topic: Kernel module + Core 3 questions
Replies: 5
Views: 13365

Kernel module + Core 3 questions

Hello, first of all thank you for the great product! In order to understand better how to develop applications for the RevPi, I've taken a look at the current kernel module source and have a couple of questions about it: The kernel module parses the configuration JSON file from the filesystem direct...