541 reputation
422
bio website down
location UK
age 39
visits member for 2 years, 5 months
seen 5 hours ago

I am a former postdoctoral research mathematician, and now a C++ software developer on Linux and Windows.


Dec
12
comment Colour is not working with ncurses on target embedded system built with buildroot
@MSumulong Actually the problem resolved itself when I upgraded my buildroot version. As soon as I configured the build to make use of bash instead of ash, I discovered that my ncurses GUI was operating in colour as intented.
Oct
1
comment Is using a read only root file system a good idea for embedded setup?
Thanks for the answer - however in the end I opted for a initramfs setup with mounting just a couple of directories with sync option on the CF drive for data persistence. This has served me pretty well for the time being.
Jan
6
comment Why is my /etc/hosts.deny file being ignored?
@Alexios Yes I use Dropbear on my system.
Jan
3
comment Why is my /etc/hosts.deny file being ignored?
@Alexios Thanks for your reply. If you post this as an answer I will accept it.
Oct
24
comment What could cause a run time remounting of my /var partition to be read only?
@Alex Yes I did a lot of reading around in books and online and the overall opinion seemed to be ext3 was best for CF. I have to have a journalled system as my logged data is of critical importance. Thanks for your suggestions anyway.
Oct
24
comment What could cause a run time remounting of my /var partition to be read only?
@JiriXichtkniha I thought I had clearly explained that the mount uses the default mount options, but anyway I have included the information you suggest.
Oct
24
comment What could cause a run time remounting of my /var partition to be read only?
@Alex Thanks for this suggestion - this gives me a place to start
Oct
24
comment What could cause a run time remounting of my /var partition to be read only?
@JiriXichtkniha And who would have thought that a site such as this was the place to ask for advice and help when people who use linux have problems. Not you clearly.
Sep
25
comment Unable to use busybox implementation of hwclock
Thanks for this. The problem was the device major minor numbers in the buildroot provided /dev/rtc file are not correct. I created a new device /dev/rtc0 as part of my initramfs with 254,0 and now it all works as I would expect.
Aug
2
comment Using ncurses for basic GUI on a process started inside an init script
Thanks what works nicely
Jul
31
comment Using ncurses for basic GUI on a process started inside an init script
OK thanks for this. I was thinking about implementing a separate application for the GUI and using IPC as you suggest but that involves a large amount of work. If all else fails I will try that
Jul
31
comment Using ncurses for basic GUI on a process started inside an init script
@goldilocks It is a busybox init system. Unfortunately there is no rc.local file. I do not need it to be portable at all. I will try the autologin approach for the time being and pray that a nicer solution is possible
Jul
31
comment What is the meaning of the errors from my cpio command?
@msw OK duly noted
Jul
31
comment What is the meaning of the errors from my cpio command?
thanks very much indeed for that comment - sudo id is root. If I call sudo find . | sudo cpio ... and omit the -c option then it works without any error. I never realised that I had to call sudo on both commands. I am still mystified why it worked without complaint in the past but I guess that is life. Thanks again for your help
Jul
31
comment What is the meaning of the errors from my cpio command?
Thanks for your answer. The second part I would agree with but I am calling this with sudo. And for the first part, why is it only starting to display these errors when it has been working without them in the past?
Jul
2
comment My process was killed but I cannot understand the kernel notice
On a run of strace I see no ioctl() calls inbetween my calls of open and ioctl using TIOCGSERIAL . It really does appear that either the open call is setting the SAK, or that the busybox implementation of setserial does not work properly. When I open /dev/ttyS0 the ASYNC_SAK bit is certainly set.
Jul
1
comment My process was killed but I cannot understand the kernel notice
I finally managed to find a code based solution and I posted it on stackoverflow. I will add this answer here but I will accept your answer as this enabled me to identify the how and why of it all. Many thanks
Jul
1
comment My process was killed but I cannot understand the kernel notice
Thankyou for your answer - it is very helpful. Unfortunately, when my application is opening the serial port, the sak that I just disabled gets re-enabled. I must be setting a particular flag combination that is re-enabling the SAK on /dev/ttyS0
Jun
27
comment My process was killed but I cannot understand the kernel notice
@MichaelKjörling Thanks for that - I will take a look.
Jun
6
comment Changed file access to read only but I can still write to the file. Why?
Thanks for this answer. I realise now that chmod is not sufficient for my requirements and I need to use chattr +i on my files. Thanks again