Tiny core server

[Mr Green]

Are there any guides on making a tiny core server? want to set up a basic file server at the moment

MrG

[curaga]

1. Install MC
2. Install a server
3. Configure the server, have it start on boot



If you need specific advice, you'll need more specific questions.

[Mr Green]

Thinking along the lines of openssh to start, I can figure out how to get it running ....

How do I go about installing mc? can do tci install no problem

Thanks

MrG

[Juanito]

You can obviously run your server from either microcore or tinycore. If you used the gui installer, just choose microcore.gz instead of tinycore.gz

[Mr Green]

Have installed tiny core without too many problems but wanted just a basic server [no gui] I will run tci and look for mc

Thanks

[Mr Green]

Found an old 256mb usb stick in the bottom of a box of spare parts, ran tiny core (tci)  [under Virtualbox] installed MicroCore good to go.

It is about time I learnt how to run Linux from command line 

MrG

[curaga]

Starting a server is usually mentioned in the info file, you'd add it to bootlocal.sh. For openssh:

/usr/local/etc/init.d/openssh start

[Mr Green]

Managed to get openssh running [well localhost anyway!] put config files in .filelist in /opt but they are not kept over reboot. Is there a way to backup settings keys etc ?

[Rich]

Hi Mr Green
If you are looking for something that Windows based machines can easily access then Samba is a
good choice. Using the forum's search function enter  samba  for the subject and  Rich  for user.
Included in the posts returned you will find my  config  file with a brief explanation of what each line
does and how to mount a Samba share on a client. You will also find information about backing up
your settings.
Among the other possibilities there is NFS which is primarily used for sharing between Linux machines
and FTP.

[Mr Green]

No windows machines here I am afraid, would like to keep system small and light eventually hook it up to a hard drive for more storage.

Thanks for the heads up, enjoying messing around in a terminal at last

MrG

[beerstein]

HI:
Does somebody know how to configure cups as a server for
linux machines? I have cups running and printing via lpt0
but I can not see the printer from another linux machine.

I assume that, if I want to see the printer from a windows machine,
cups server is not enough - I think I need samba in this case.

Thank you for helping out here

[Juanito]

Does somebody know how to configure cups as a server for
linux machines? I have cups running and printing via lpt0
but I can not see the printer from another linux machine.

It's a question of setting up cups to share printers and making them browseable - in this case when you start cups on the remote linux machine, it will display the shared printer automatically - I'm not at a linux machine at the moment, but google should turn up something on this.

I assume that, if I want to see the printer from a windows machine,
cups server is not enough - I think I need samba in this case.

I believe this is correct - I recently posted a method to be allow windows machines to use a local printer driver rather than the cups one here:

http://forum.tinycorelinux.net/index.php?topic=9633.0

Edit: see also:

http://forum.tinycorelinux.net/index.php?topic=818.0

[SamK]

I assume that, if I want to see the printer from a windows machine,
cups server is not enough - I think I need samba in this case.

In a multi-user LAN consisting of Linux and Windows workstations, Samba is the usual means of providing shared directories.  It controls who has access to the shared resource.  In such circumstances, Samba is also often used to provide controlled access to printing resources.  If uncontrolled access is acceptable, Samba is not required to share printing resources.  This can be achieved for both Linux and Windows workstations via CUPS alone.

A summary of the what is required to set up uncontrolled access might look like:

• CUPS sets up a print server
• The print server is made available via Share printers connected to this system
• A print queue for the physical printer is set up within CUPS
• The print queue is published via Share this printer

At this point, providing each LAN workstation is set-up appropriately, both Linux and Windows have uncontrolled access to the printer.
   

[ldak]

Hello

Just did this  for a friend using a thin client with external usb drive.  Used Putty in Windows for ssh access using public/private keys (couldn't get acpid to work at first) and share level samba.  Managed to get the power button to shutdown also.  All using info mostly available here in the forums.  Will write a guide if time available soon as a give back.  How far have you got so far?

[ldak]

In the meantime, here is a nice guide...

http://www.parkytowers.me.uk/thin/Igel2110/IgelLinux.shtml