Editing Introduction to a Self Managed Life: a 13 hour & 28 minute presentation by FUTO software (section)

=== Step 6: Boot into the LibreELEC system &amp; set it up ===

After installing LibreELEC, it will boot into the operating system &amp; start KODI. The rest of the setup is a breeze.

'''Networking Configuration''':

* Use the default internet connection settings.
* There is no need to configure a static IP address for a ''client.'' Static IP addresses are for servers.
* If you are using this to watch stuff stored on your server’s ZFS pool, disabling samba server &amp; disabling ssh is the smart way to go. No need to run unnecessary services if you don’t have to.

'''Audio Configuration:'''

By default, it will output audio via the HDMI cable.

* If your HDMI cable connects to an '''audio/video receiver that is hooked up to your speakers''', you’re fine.
* If your HDMI cable connects to your '''television''', you may hear the audio through your '''TV speakers''', which is horrible; we will need to change where Kodi outputs to.

To change the audio output:

# '''Access System Settings''': Navigate to the gear icon for settings, then '''Audio'''.
# '''Select the Audio Output Device''': Choose <code>ALSA: HDA Intel PCH, ALC888-VD Digital S/PDIF</code>. Yours may look mildly different - we want whatever looks closest to S/PDIF digital optical/toslink output. Experiment to find which one works for you.
# '''Check Display Settings''': Make sure it is set to what your television is capable of. in my case, it is set at ***3840 by 2160 and 60 fps.

<blockquote>'''Why not a static IP? Didn’t we make a static IP for everything else?'''

Static IPs aren’t important for a computer that doesn’t provide services. When we’re running a server, like our machine with the ZFS pool that stores our media files, we are running something where clients(aka our home theater PC) are going to want to know where to access it.

Think of your server like your favorite store. We are going to tell our home theater PC to always go to the store to get movies(….) at <code>192.168.5.2</code> - so our server always NEEDS to be at <code>192.168.5.2</code>.

The home theater PC we are setting up right now is the ''“customer”'' - it doesn’t have to have a static IP, nor does it always have to be at the same address every day.

A customer can visit a store from a different address every day; it makes no difference to the shopowner selling goods to the customer. However, if the '''''store’s''''' address changed ''every single day'' without notice, the customer would have a very hard time finding the store. They may stop going to that store altogether.

We can use the default setup where the server grabs an IP address via DHCP''(aka, it grabs whatever’s available from the router)'' without concern here.
</blockquote>
<span id="step-7-adding-media-content-to-kodi"></span>