I just migrated from Windows very recently to Slackware Linux. I played around for a couple weeks before deciding on how I wanted my semipermanent installation laid out. I have everything set up for uefi boot with my root on an encrypted lvm, and I want to rebuild my kernel so that I can utilize the efi stub loader and build drivers for my keyboard. I want to learn a lot quickly, so I'm taking every opportunity to utilize whatever obscurity my hardware will allow me.

I want to stick to the development tree, but the kernel version changes a lot. I can blacklist the kernel package and upgrade that at my convenience, but I was wondering how often I should go through the arduous process of upgrading and rebuilding it properly. If there are specific things to watch for, I haven't a clue where I can find that information. I also don't know if I'll run into problems by ignoring the kernel and upgrading my other packages.

There's so much to take in on the most basic level that I can't bring myself to touch my computer until I have it all sorted out and at least have a good system for upgrading all my software. I hope somebody can provide some insight.

Hello ymf331 - I've been using Slackware for a few years now and, as for me, I just upgrade to the next Slackware version once a year. So, I have a different set up than you do. In my experience, though, programs almost never depend on the kernel version you're running. When I do upgrade the kernel however, I usually have to recompile my video drivers and any other software that comes with their own kernel modules (like VirtualBox).

For keeping system programs up to date there is, as I'm sure you know, slackpkg (for you - syncing with slackware-current, for me - 14.1). For keeping your SlackBuilds.org packages updated, there is sbopkg. Also, there's an extension to slackpkg called slackpkg+ for staying updated with 3rd party repositories (like alienbob's): http://alien.slackbook.org/blog/intr...-repositories/

This probably wasn't too helpful for you, but it's just my two cents.

1 members found this post helpful.

I've asked help from my two friends who are professional system admins, and neither knew what I was talking about. Sorry for dp. I'll bring my machine to the more recently certified of the two, but it's scary to think that trained professionals can't solve my problems a month in.

Yes, I'm doing much of what you suggest. Any input or advice is helpful. I'm just trying to decide how often to make the -current kernel. Once a week or month will be too often for my needs. I use the same package management system. I just don't know if using the -current mirror and updating the kernel every couple months will be alright or not. I also realize that I'll need to reinstall nvidia drivers, but that's part of the process. Sbopkg has a -current mirror as well. What I'm unsure of is if and when blacklisting the kernel might break things. Also, how to tell. It seems like users of less conservative distros might know. I've tried to do as much homework as possible but I'm left with questions.

Edit: Not being happy with a basic install is only my problem. I've decided on a super-conservative distro to protect me from myself. I've searched high and low but no guide quite covers it. I'll document my transition from casual win7 to Slackware Linux as well as I can. Learning process at the front of my mind.

Edit2: Aurora on Android makes me wanna' cry.