Danny's Space

I've been obsessed with sharing my desktop files over the home network to all the devices connected to my home router. I finally did it once as I said here. Since then, after several reinstalls and wipes of hard drives, I lost the configuration file for the original system. In short I can't make it work. I've forgotten how I did it exactly. It turns out that samba and my samba configuration files aren't to blame. I was doing firewall configuration files with my rkhunter setup. I noticed that I don't have any entry for samba. I added my samba rule in the firewall. I checked my smartphone file manager and there it is my shares automatically appearing and ready for use. No login required. The firewall rule is: #ufw allow samba -- Donato Roque@desktop mobile:   63-9185721710 I'm on twitter and facebook . Check out my blog . Consider using my pgp ...

This is not going away soon. Will you give up this kind of power? To take life without answering for it? -- Donato Roque@desktop mobile:   63-9185721710 I'm on twitter and facebook . Check out my blog . Consider using my pgp keys for privacy.

Using Ubuntu 16.04 with RAID and Logical Volumes. I am adding Disk Encryption to my skill set. After using the Fedora 24 installer to do all of these in one night (and day) of operating system installation fiesta, I am now trying to finish the same thing using the Ubuntu installer this early morning. There's a power loss of about 30 seconds. It happens in the very early morning. Some power engineer decided to test a new hardware or to pull out an equipment for servicing in the wee hours of the morning while I'm in the middle of resyncing my RAID. I heard the sigh of the fan motors. I checked the status of the RAID - inactive, okay. Then bring it back on, right? I had to continue the resync somehow so I went back to the mdadm man pages. #mdadm -assemble --update=resync /dev/md0 /dev/sdb1... /dev/sdd1  This returns a message that my component devices are BUSY. Are they just trying to ignore me? Not at this ungodly hour, okay. So I have to stop the devices. #mdadm /dev/md0 --stop ...