filetool.lst

[alan52]

Have installed my printer but I need to add a line to /opt/.filetool.lst but i can't find it, using tinycore 3.2!

[gerald_clark]

Files starting with '.' are hidden. to see them you need the -a option to ls.
ls -a /opt

This is very basic Linux/Unix.  I suggest you get a good beginner's Linux book.

[Tahoe]

Copies of both core and findutils, along with a quick hands on couldn't hurt.

[tinypoodle]

Copies of both core and findutils, along with a quick hands on couldn't hurt.

What do you exactly mean by that, and how is it related to the topic?

[aus9]

hi

if you install a graphical text editor you can run

Code: [Select]

sudo (nameofeditor)

eg sudo leafpad
and then navigate to your /opt/.filetool.lst

2) if you prefer terminal stuff I higly recommend

sudo mc (you will need to install mc)

navigate to /opt

then press F4 when you are on the filetool entry

press enter at end of file and add the file

press F2 to save

press F10 to exit that file

press F10 to quit mc

(the F numbers show up at bottom of screen)

[maro]

I'm sorry, but if one just needs to add an entry to a text file I find using an editor to be a bit "overkill". In particular suggesting to install a GUI editor or using a file manager (like 'mc') for such a "trivial" task is IMHO "over the top" (and I'm saying this as a very long time user of 'mc').

What I'd suggest is to use echo path/to/file >> /opt/.filetool.lst As always for entrys to '/opt/.filetool.lst': please ensure to not use an absolute path (i.e. don't use '/path/to/file').

I dont' want to start a flamewar about which editor is to be preferred, but I think that using the "bigger guns" to solve a trivial task is not always appropriate.

BTW my suggestion for the task of the deletion of a entry would be sed -i '/path\/to\/file/d' /opt/.filetool.lst Now this time what appears to be a leading forward slash in the 'path/to/file' is actually required syntax for the "delete" command of 'sed' (i.e. '/RegularExpression/d'), and therefore the forward slashes "inside" of the regular expression will have to be "escaped" (with a back-slash for each of them).

Well, that's all pretty standard UNIX/Linux stuff, but if anyone still insist to install a couple of extenions to achieve the same I'm certainly not in a position to stop you ...

[aus9]

I don't want to start a flamewar either so will not expand any further

good bye

[Terminator3000]

Well 'vi' is already there, so a quick 'vi /opt/.filetool.lst'  (W/O quotes) will bring up the file ready to amend without any of the above mentioned drama ! Just basic tools needed.
         Maro's way is fine for users who have more experience but not everyone has the necessary number of manhours to study(and practice) the thousands of commands and variants in a Linux handbook (yes I have one) especially if they are also learning other stuff for which they are actually hoping to put to use the said operating system!

The Microcore forum is an excellent medium to learn from and I for one have found
that I learned more in 2-3 weeks here than in 2 years messing about elsewhere thanks to the very high standard of posters and staff members.

[tinypoodle]

Well 'vi' is already there, so a quick 'vi /opt/.filetool.lst'  (W/O quotes) will bring up the file ready to amend without any of the above mentioned drama ! Just basic tools needed.
         Maro's way is fine for users who have more experience

I beg to differ.
Being a vi-idiot myself (believe me I have spent a lot of time trying...), Maro's instructions look much more simple to me than attempting to aquire enough experience to ever be able to do

a quick 'vi /opt/.filetool.lst'  (W/O quotes) will bring up the file ready to amend without any of the above mentioned drama !

and therefore could be useful to me, as only tools contained in base are required (as is the case with busybox applet vi).

[roberts]

There will always be the CLI vs the GUI. I have spent considerable time to create tiny GUIs for Tiny Core. If CLI only I would not have started this project.

Micro Core users primarily have CLI only. Tiny Core GUI. Many posts do not specify if the user is running Tiny or Micro. I suspect largely Tiny Core.

CLI always is an option for both. But note that some users are coming from GUI environments. I usually answer posts by specifying a GUI solution.

After watching this topic and recently others, perhaps I need to go further in providing more GUIs. Note that my GUIs are mainly front ends to CLI. That way I support both Tiny and Micro. I am off to ponder.

[roberts]

I am back from my pondering! The result of which will become apparent in v3.3.

Advanced power users will likely scoff. "vi or die", say aye! CLI forever.
 
New users may find it is just what is needed to help get past the vi or cli dilemma.

And those who, like myself, truly appreciate what can be achieved in tiny software may be pleasantly surprised.

Data centric view is coming to Tiny Core.

[tinypoodle]

Wondering why the menu options "Add to Filetool" & "Add to Xfiletool" were not mentioned at all in this thread...

However, for me only the latter one of the both works, and I suspect some permissions might have been messed up somewhen for "Add to Filetool" not to work...  

Code: [Select]

tc@box:~$ ls -l /opt/.*file*
-rw-rw-r--    1 root     root          641 Oct 29 17:46 /opt/.filetool.lst
-rw-rw-r--    1 tc       staff         913 Oct 25 00:34 /opt/.xfiletool.lst

[roberts]

You must be running a non-recent version as both of those are long gone and were of very limited value. However, they once existence, demonstrated my concern for such matters.

[tinypoodle]

True, 2.10, and my bad I hadn't considered they might have been gone. (Which of course explains why I wondered why it was not mentioned)