Tiny Core Linux
Tiny Core Base => TCB Q&A Forum => Topic started by: hal9king on April 14, 2015, 08:36:30 PM
-
I've found several references to this subject but I'm not finding all I need.
First when I used Apps to attempt to get inetutils-servers.tcz all I ended up with was the dep file nothing else
I then tried tce-fetch.sh and retrieved the tcz -- no dep provided (I guess this is normal?)
From the discussions on the forum there are at least more dependency??.
So how do I find out what they all are and how to get them?
Do I manually create the inetd.conf???
Is there a howto somewhere?
-
Start by reading the book. http://tinycorelinux.net/book.html
Then read the info pages for any extensions you want to install.
The Apps utility will show you the files included, the deps, and the info file.
-
the word 'inetd' is not mentioned anywhere in the 'book'
-
I have found iana-etc.tcz as a dependency -- but all my attempts to retrieve fail.
assuming I eventually find it -- do i manually create inetd.conf -- in /etc??
Will it be found??
-
How to use the Apps program is.
If you are running in text mode, use tce-ab or tce-load.
-
I have tried I'm telling you that while the Apps browser finds inetutils-servers.tcz it fails when downloading -- several mirrors.
When I perform tce-fetch.sh it will download. iana-etc.tcz is never found I have downloaded it from a google search
Note, I find there already is a 'inetd' located in /usr/sbin -- a new inetd along with ftpd, telnetd, etc. will be in /usr/local/sbin
iana-etc installs its stuff in /usr/local as well -- if this includes an inetd.conf I haven't locate it yet.
Also am I required to reboot for this to run? rebooting now ...
-
Answewr to last is apparently not -- Apps Local extension takes care of it ...
But the connection is still refused ... more checking in progress.
-
I also noticed that Xvesa was set in .xsession to be -nolisten on tcp -- I thought I fixed this by making .xsession read only --
not sure if that worked (comes up without the setting in ths running Xvesa but still connection refused).
Note, inetd does not come up running, nor are inetutils-servers activated -- i.e. I still have to use local extension in Apps to manually install after a reboot, and to run manually inetd as root.
This is not working well.
-
Core is not a load and run distribution. It is a toolkit.
You need to edit the /opt/bootlocal.sh script to start any services you want running at boot.
You also need to add any modified config files to /opt/.filetool.lst and do a backup.
Please read the book as you do not understand the fundamental design philosophy of Core.
-
I'm well aware of that. I'm not trying to set this up just for me but for a group of people on a project. Each will have their own base copy. Most will not need the server function, but some will. I was hoping to have a common hand out version to all. What I'm finding is that will be impossible.
While what you say about TC is true, the problem is most people do NOT want to spend that kind of effort on these kind of issues. They are wanting to address their real projects first. So the base utilities need to be robust and the repositories need to be complete without such issues.
Frankly, the biggest problem has been the unreliable nature of the Apps browser. Manual hack arounds need to be the exception not the rule.
At a minimum there needs to be generated a 'howto' once issues of these types are solved -- and the howto's need to be easily found by the appropriate search/query.
This shouldn't be an 'ego-game' of someone knowing more than another. (far too common in Linux land). That is one of the main failings of a 'free' product -- it really isn't free if you have to spend too much time on it.
-
Feel free to write those howtos.
I have been using the Apps browser for years, and have not found it unreliable.
Core is not designed for "most people", and those that do not wish to invest the necessary time to learn it can find many
install and run distros that may be more to their liking.
-
Frankly, the biggest problem has been the unreliable nature of the Apps browser. Manual hack arounds need to be the exception not the rule.
Please explain what do you mean 'unrealible nature'.
-
iana-etc was indeed missing from 6.x, added, thanks for reporting.
-
Thanks curaga inetutils-servers now downloads and installs clean (and includes iana-etc).
I'm still getting connection refused on both ftpd and telnetd. 'inetd' is running /etc/protocols and /etc/inetd.conf in place.
HOWEVER, when I manually run 'ftpd' or 'telnetd' both die with a '1' in $? -- I assume that is also occurring when 'inetd'
attempts to start them.
So obviously something is still missing. Out of ideas at the moment.
-
Either use busybox inetd or install ipv6-KERNEL.tcz.
---- edit ----
Or specify tcp4 in inetd.conf.
-
Hi hal9king
Try:
sudo ftpd -D
-
Thanks the busybox inetd worked! (tcp4 had no effect).
Never thought to try it since the telnetd and ftpd servers came in the same package as the inetd that didn't work.
Should have considered it -- thanks again.
-
tcp4 definitely works.
Contents of /etc/inietd.conf:
telnet stream tcp4 nowait root /usr/local/sbin/telnetd telnetd
inetd invoked by:
/usr/local/sbin/inetd /etc/inetd.conf
-
Yes, the busybox inetd worked (but tcp4 did not).
I tried to post earlier -- thought I had -- but when I looked again I didn't find it.
Thanks to all for the help -- project is a go.
Closed on success!
-
tcp4 works with the inetd from inetutils-servers , not from busybox inetd