FreeBSD Package Installation Part 2

The original Japanese version is available here.

It’s Sunday today. It is not too dark outside but we see a lot of cloud everywhere in the sky. I have to go to Nissan today for 12-month inspection for my new car. I woke up a bit late and did preperation to visit Nissan. Then my younger sister came to my house with her husband and handed me a box of strawberries. It doesn’t look good but taste is good. These strawberies are used for strawbery jam. So they were ripe and very sweet.

They go to Mie Prefecture to pick up clams every year. The taste is very good as this is used to make strawberry jam.

We just installed the packages last time. We will need to make them work with some configuration. We normally start watching the message file when we install them.

At first, messages from trousers package.

We need to load fusefs kernel modules in fusefs package.

We need to use kldload command to load kernel modules.

If we restart the system, all changes will be lost. So we need to edit loader.conf file and set some variables.

Then configure dbus daemon next.

We need to set variables as we can see in the startup file.

dbus should be started during boot up process.

The samba next.

Set the variables as we see in the startup scripts. Then reboot the system to make sure all required services are up and running automatically.

We see messages at the end of /var/log/messages file. The first error message is from tcsd daemon. It complains that the configuration file is not owned by root/_tss .

We need to change the owner and group as they like. Then we run the startup script manually. The installer prepared special group for this application. So file owner group should have read access at least and the file mode shuld be 750 at least. But there was errors and file owner/group/mode were reset as they were before. This could be a bug. Checking it up in the internet.

We can see this description in FreeBSD bug information.

This part in the startup script need to be changed.

Then we don’t see the error message again.

The next error is from Samba. Samba processes can’t read the configuration file.

We found we don’t have any configuration file. So minimum configuration is written in the configuration file. All other configuration is just the default. Then samba started.

We see dangerous tcp ports related to M$ opened.

M$ service without configuration sounds like dangerous. We don’t know what the default configuration is yet. So we only need to run NetBIOS over tcp/ip service for now.

Restart the system for testing. Then we found that tcsd and tpmd services are not running.

We need to check /var/log/messages file again. Then tpmd complains that it can’t create socket file in /var/run/tpm directory.

We see useful information in messages file.

If we see the startup script, then we found we can set startup user.

new bug caused by fixes for another bug ?

we changed the startup user from _tss to root based on the changes in tcsd. Just reboot the system for sure.

Now everything started as expected.

If we see the console, then we see messages and they say the samba on pokemon is now the master browser in this network segment.

The default messages will be out to the console.

The master browser is used by Windows client. We can use hostnames instad of IP addresses.

We haven’t setup any other name reslution services such as DNS yet. Windows client can use this master browser to resolve IP address from host name. The samba file share can be configured in other articles later.

Advertisement below