Jump to content

Search the Community

Showing results for tags 'slackware'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • The Highlands
    • Announcements
    • Bruno's All Things Linux
    • All Things Windows
    • All Things Mac
    • Hardware
    • Mobility
    • Security & Networking
    • Social Media
    • The Restaurant at the Edge of the Universe
    • Forum Feedback

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Skin Start Date


Skin END date


Main System Specs:


Secondary System Specs:


Other System(s) Specs:

Found 16 results

  1. http://www.tldp.org/.../slackware.html SLACKWARE (1997) I do not think it is a good idea to include qoutes when posting article links in these threads. If folks are interested in the subjects then they will click the link and read the article. Also I am not a fan of teasers and trailers, where is the mystery in that. Dive and and live the experience. however this is just too good a piece of history to not show. IF YOU FIND A DECENT RELEVANT ARTICLE PLEASE DO POST
  2. Problem SOLVED! Just did a fresh install of slackware, and find I have a lot to learn. I downloaded and burned the ISO to a USB Stick. Booted up and installed using the text install. Haven't done that since about version 6 of Victor OS. Got it installed the KDE version. Booted it up and logged in as root. Used startx and got into KDE desktop. I've tried to add a user called mel, but can't find where to do it. I've tried several different places, but no luck. Where's that Slacker Eric? Help! Guess I just have to get use to the menu system in KDE. I haven't used KDE for years probably around 2000. I will still need help I'm sure finding things such as booting to the GUI without having to use startx. I'll probably figure it out. Mel
  3. Updates Slackware 13.0Package seamonkey-1.1.17-i486-1 upgraded with new package seamonkey-1.1.18-i486-1.txz.Package seamonkey-solibs-1.1.17-i486-1 upgraded with new package seamonkey-solibs-1.1.18-i486-2.txz.Package mozilla-firefox-3.5.2-i686-1 upgraded with new package mozilla-firefox-3.5.3-i686-1.txz.Total 21051 kBB) BrunoNote: Swaret stopped working, so changed package-manager to: slackpkgCommand used: "# slackpkg update && slackpkg upgrade-all"
  4. --- Well, it's come to this... I've been using Chromium in Slackware64-14.1 for quite a few years, but last October/November a new version came out that just refuses to run on my system. It crashes about 15 seconds after startup with "segmentation fault" error. I've spent quite a bit of time troubleshooting this. I run .txz SlackBuilds from Alien Bob's (+Eric Hameleers) repos. The last version that can run on my system is chromium-52.0.2743.82-x86_64-1alien. I thought maybe that I would wait a few more versions since this problem started to try it again. Well, today I installed the newest version (54.x) and experienced the exact same issue that I had with 53.x back in Oct/Nov. I even ran it with a brand new, vanilla chromium profile. No joy. So, starting today, I guess I'll be running Firefox as my primary browser. The ol' Chromium 52.x is getting too many warnings from websites regarding its age and security issues. I have my FF set up to look and behave very similarly to my Chromium. One thing that I can say in favor of FF... the font rendering is AWESOME compared to that of Chromium. Narrow fonts in FF are sharp/dark, easily readable; not so much in Chromium. Anyway, I'll miss Chromium, but it is what it is... ---
  5. So, I haven't been able to use Google Chrome or Chromium for about 6 or so weeks in my Slackware 14.1 installation on my main system. This all started when Google Chrome and Chromium both went from the last 52.xx version to the newer 53.xx version. I use the SlackBuild script provided by Pat V. in the Slackware repos/extras directory to build a compatible .txz installer for my Slackware using a .deb Google Chrome download. I use Alien Bob's (Eric Hameleers) already built .txz from his repos for Chromium. In both cases, building/installing goes fine. The problem is that when the apps are started, they stay running for about 5-10 seconds and then crash giving me a "segmentation fault" in the command line. Somewhere between the 52.xx and 53.xx some coding changes were made that just do not like my 14.1 installation. I know it's a glibc or lib issue of some sort, but I'll be dashed if I can track it down. I figured I've spent enough time on this so far; I'll just install the newer versions of these browsers when I install Slackware 14.2 one of these days. I've been using Firefox for about a month now. I have it set up just the way my Chrome/Chromiums were set up. The only problem is that Firefox just does not render webpages as quickly as Chrome/Chromium; plus, FF has some herky-jerky scrolling issues. Myeh... oh, well. I've reinstalled the older 52.xx versions of Chrome/Chromium. I'm just going to set Google Chrome as my default browser and leave it like that for a while. Here's a screenie with them all dressed in their fall colors.
  6. http://www.phoronix.com/scan.php?page=article&item=arch_2012_linuxdistros&num=1 This shoot out is almost a year old but I thought it would be of interest. I hesitated posting as Arch is not a clear cut winner by any means. Though it does in the main kick Ubuntus butt, well it is more of a playful kick in the pants really.
  7. Gee, where's Eric been all afternoon and evening? He's probably had his head buried in that Cisco text book, I'll bet. Well, you'd be wrong, capacitor breath. He was actually attempting to recover his main and laptop installations of Slackware after they crashed and burned from an update earlier today. Weeeeeeeeee! As some of you may know, I've been running Current since upgrading from 13.37 earlier last year. Sadly, an update that came out today (numerous updates/upgrades, actually) did not play well with my main nor my laptop systems. I was somehow able to recover the lappy, but the main was UGLY. I didn't update the shop system. It survived intact, but may get wiped anyway. I had to wipe my / partition and recover from an rsync mirror. Ooopsy! Bad rsync backup. That didn't help much. You should always check your backups after you create them to make sure they are actually going to work if you should ever need them. Silly me. That bad backup was my fault. I did something stupid, but we won't go there. Anywho, I decided to just wipe the / partition clean and reinstall Slack (stable); leaving the /home partition alone, of course. That went well. It's now after 0230hrs. I'm tired. I've customized, tweaked, installed, setup, etc. for the past 6 hours. I think I've got it mostly finished. I even took a pretty picture for you to see... Yes. What you're seeing is no illusion. They are slinging snowballs down under... and I don't mean Australia. That really is KDE you're seeing there. I'm going to bed now. Didn't get much studying done tonight. Later... P.S. Wonder how the lappy would like a nice new KDE installation?
  8. OK, I'm now running GRUB from Slackware. It controls my MBR and boots all my operating systems on my main machine, with the exception of the soon-to-be plowed under borked Arch. Here's how I did it: GRUB (0.97) on Slackware - Build GRUB from SlackBuild in /Extras or download from SlackyEU (http://repository.sl...ub-legacy/0.97/ --> works on 14 current also) - Make sure to have a boot disk available (just in case) - Remove LILO if it was previously used as the bootloader on the system > #slackpkg remove lilo - Install GRUB on system > #installpkg grub-legacy* - Write to the MBR of the main drive on the system > #grub-install /dev/sd* - Copy previously used menu.lst from another source on the system or create a new menu.lst to boot the operating systems - Reboot --> JOY! YAY! I'm planning on using Clonezilla to clone my current Slackware partitions onto the old Arch partitions and use this as secondary OS on this machine. I will re-clone periodically to keep the two relatively synch'd. Of course, since they're on the same drive, a mech failure would be ugly, so I'll still regularly copy my /etc and /home to external media (DVD). This will facilitate ease of reinstall, if ever needed.
  9. I needed to torrent something earlier and I was in Arch. I didn't realize that I had not installed a bittorrent client in Arch before, so I had to snoop around a bit. I settled on Deluge. It seems to work really well and has a neat, efficient interface. I liked it so much, I'm building it for Slackware, too. Anyone here use this app? http://deluge-torrent.org/
  10. On the 28th of September, Slackware Linux Project released Slackware 14. On the 29th of September Debian released Debian 6.0.6 - Squeeze. Visit the websites of these two oldest and, in my opinion, finest GNU/Linux operating systems in existence for more information and the official release announcements. Have fun! http://www.slackware.com/ http://www.debian.org/
  11. Alien Bob (Eric Hameleers) posts an article on his blog about a possible community Slackware documentation project similar to the excellent ArchWiki: http://alien.slackbook.org/blog/slackware-documentation-project/
  12. From Nocturnal Slacker v1.0: https://noctslackv1.wordpress.com/2012/08/19/x-file-explorer-todays-featured-application/
  13. 7 More Heroes of Linux Thought you slackers might appreciate this
  14. I did not know that now Puppy Linux is based on Slackware. I have not tested it, but I'm sure it is a lot better now than before. I always preferred DSL over Puppy. Maybe that is not the case anymore. Here is where I heard the old "news" http://linuxblog.dar...t-but-same.html
  15. Here's how I did it: https://noctslackv1.wordpress.com/2012/04/26/common-mozilla-product-profiles-across-operating-systems/
×
×
  • Create New...