Tiny Core Extensions > TCE Q&A Forum
Samsung Unified Linux driver + CLX-3185 + TC CUPS-strategy
tinypoodle:
Reading whole posted README it is not evident what is unclear to you.
Yleisajattelija:
Sorry, unambiguous question.
Reason for that sane TinyCore installation is not working is probably TC unique file system.
On that README file sane staff says that too. For every distro, default directories have to match distros file structure.
That match have to do with udev.rules files, too.
If I have understood correctly, this "PPI compatible" means that package installation matches with TC unique file structure.
I got an answer at different chain, that TC uses kernel default udev.rules, I think that README says that udev.rules mast be modified for sane-backends.
There seems to be standard makefile for compile, but those udev.rules might need some hacking.
Actually, I not sure if that udev.rules are needed only if saned -daemon is installed, if so -> can be skipped.
For compile, correct TC file structure and udev.rules handling must be known.
Yleisajattelija:
Sorry, still unambiguous question.
TC is linux is unix is coded with C -language.
That's good for me, even if I personally like most direct coding with hex editor, next to that is assembler and then C (Java is accepted occasionally, but C++ never).
One of the difficult/wonderful features with C is libraries. Commonly needed code is placed on linked C-library, and several applications can use same piece code.
Unfortunately, using libraries is not simple, for example BusyBox is "multiple call library" for some special reasons (there is problems for dynamic library loading in embedded environments).
Because several applications can use same library, there must be EXACT rules how libs are placed on directory tree.
On linux community, it is distro who decide where libs are, and debian/redhat are most common file structures.
udev.rules are mechanism for linux dynamic harware/driver/module handling. Problems are same and worse than with libs, because udev is dynamic in nature.
When scanner is connected with USB-cable, that makes udev event and triggers scanner driver modules loading to memory.
When page is scanned, that generates udev event, too. That event might need special udev.rules handling or not, depends on driver/module structure.
Yleisajattelija:
Sorry, unambiguous again, let's make third try:
a) It is distro who makes rules how handle sane-bacend libs. Of course, I can make that decision and put libs somewhere but that will cause problems, because probably on next TC update I have to manually adjust those settings. Good practice is use TC specification, if there is some.
b) Only docs I have yet found are those few diagrams for TC system.
c) FHS -spesification is something, but I think it not sufficient to describe file structure needed for lib tree.
d) Especially that udev.rules might be nightmare, and udev development on linux is going to fork .-> changes will be in near future
Yleisajattelija:
More explanations:
This lib issue is current concern with Samsung Unified Driver CUPS parts, because few files at /usr/lib/ directory must be updated (driver is not working without).
That directory seems to hold important C standard libraries and there is always risk of side effects when updating those libs.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version