Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I've been keeping most of my blogging with blogger.com, and for awhile I was using iWeb (for my Mac and motorcycling blogs and web pages). Well, I'm beginning to hate iWeb, since I can only use my Macs with it. I don't like being that tied to my Macs.
So, I think I'll give this blog a shot again...I'll just straight up start adding ANYTHING technological to this blog and try to take advantage of this site's publicity.
I'm going to try to make my Dell Mini's desktop look more like the OS X desktop. I'd rather not install OS X to do this...
I've installed Avant Window Navigator, and it is running but there is also already a taskbar on the bottom of Ubuntu's Gnome. I'd kill it but I don't know if I can get it back later. I'd also like to add more widgets to it (for every widget showing on my Ubuntu install, I'd like a comparable and functional AWN widget).
Yeah, I thought I'd nailed this, but there is still an issue with my Slackware machine's Snort startup/shutdown script. For some reason, it'll start fine, will not shut down cleanly and will error out. The script will not start on its own and requires manual intervention (dunno why). I'll have to add some debugging code to it so that I can track the issue. It must be some flag that I'm using when implementing 'ps', because that's the only difference between the two scripts (the OpenBSD and Slackware)....
IP 18.104.22.168, an IP that belongs to Vrtservers.net, has been very active lately. The machine has been compromised twice in 30 days and does a multitude of scans. Last month I reported this IP to isc.sans.org and the machine was eventually taken offline (after waiting over two weeks). I reported it again this weekend when I noticed the IP was scanning against port 80 on my public server.
I've attempted to do some digging via Google but have found nothing solid, other than finding...