05-19-2014, 02:30 AM
Back again after re-burning LL onto DVD media. Sad to say, no change.
Fearlessly, I purged rsyslog + ubuntu-minimal. The 'find' command used earlier now shows only
/var/log/upstart/rsyslog.log
/etc/rsyslog.d
/run/rsyslogd.pid
I suppose I should reboot, but am not sure whether that is even possible, with ubuntu-minimal gone...
My request to "sudo apt-get install rsyslog" was met with the following reply:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package rsyslog is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'rsyslog' has no installation candidate
Thinking I may need to reinstall ubuntu-minimal first, I tried that...However:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package ubuntu-minimal
Then, when I tried Synaptic, I realized I had not updated the package lists. Once that was done, I tried installing rsyslog. Interestingly, that was possible to do WITHOUT bringing ubuntu-minimal along with it.
Also interesting is this notice shown at the end of the installation:
Creating config file /etc/rsyslog.d/50-default.conf with new version
The user `syslog' is already a member of `adm'.
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
rsyslog start/running, process 3252
Processing triggers for ureadahead (0.100.0-16) ...
Okay: /etc/apparmor.d/disable/usr.sbin.rsyslogd is a file containing configurations telling which rsyslog files will be read and followed, or skipped. If this 'profile' is being ignored, THAT could be the reason that the instructions in the file aren't being followed. But that is where the trail grows cold for me: I don't know where the instruction to ignore the profile are coming from.
I've taken this as far as I can. If anyone knows where I should go from here, I'd love to hear your ideas. If any of you like playing detective, get a copy of the 2.0-beta version and see if you can track this down. Or maybe one of LL's programmers already knows what to do?
In the meantime, I'll have to go back to my old OS. I really hope the inability to record system activities and warnings is soon resolved, though, because LL is exactly what I've been looking for, trying out one distro after another for the past year! Finding such a beautifully-designed OS without an ounce of bloat seemed like a miracle: I found LL on the same day that I gave up trying to create my own version of "lightweight and beautiful" from Ubuntu 14.04 Core. Naturally, I'm disappointed over having to set LL aside. I hope it won't be for long!
Fearlessly, I purged rsyslog + ubuntu-minimal. The 'find' command used earlier now shows only
/var/log/upstart/rsyslog.log
/etc/rsyslog.d
/run/rsyslogd.pid
I suppose I should reboot, but am not sure whether that is even possible, with ubuntu-minimal gone...
My request to "sudo apt-get install rsyslog" was met with the following reply:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package rsyslog is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'rsyslog' has no installation candidate
Thinking I may need to reinstall ubuntu-minimal first, I tried that...However:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package ubuntu-minimal
Then, when I tried Synaptic, I realized I had not updated the package lists. Once that was done, I tried installing rsyslog. Interestingly, that was possible to do WITHOUT bringing ubuntu-minimal along with it.
Also interesting is this notice shown at the end of the installation:
Creating config file /etc/rsyslog.d/50-default.conf with new version
The user `syslog' is already a member of `adm'.
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
rsyslog start/running, process 3252
Processing triggers for ureadahead (0.100.0-16) ...
Okay: /etc/apparmor.d/disable/usr.sbin.rsyslogd is a file containing configurations telling which rsyslog files will be read and followed, or skipped. If this 'profile' is being ignored, THAT could be the reason that the instructions in the file aren't being followed. But that is where the trail grows cold for me: I don't know where the instruction to ignore the profile are coming from.
I've taken this as far as I can. If anyone knows where I should go from here, I'd love to hear your ideas. If any of you like playing detective, get a copy of the 2.0-beta version and see if you can track this down. Or maybe one of LL's programmers already knows what to do?
In the meantime, I'll have to go back to my old OS. I really hope the inability to record system activities and warnings is soon resolved, though, because LL is exactly what I've been looking for, trying out one distro after another for the past year! Finding such a beautifully-designed OS without an ounce of bloat seemed like a miracle: I found LL on the same day that I gave up trying to create my own version of "lightweight and beautiful" from Ubuntu 14.04 Core. Naturally, I'm disappointed over having to set LL aside. I hope it won't be for long!