SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
For those willing to follow kernel updates, it becomes a bit tricky, since kernel.org is not updated for some time. The latest version there is still 3.0.4. While 3.0.7 is already prepared.
For me it was quite new to get kernel repository from git. Perhaps other people will find it very straight forward, but for me it was tricky. For any case I decided to share my findings. Hope it would be useful for anyone.
First I got master repository:
Code:
# cd /usr/src
# git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.0.y
then I made a script in my home dir kernel-build_git.sh:
With the recent kernel.org outage, I've recently converted to using git too.
You might want to add the following to your script after the checkout just to make sure it's nice and clean and there are no stale files laying around.
It might not be necessary, but it doesn't hurt.
Code:
git clean -d -f
make mrproper
Also, given recent developments at kernel.org verifying the tag might not be a bad idea:
Code:
build@slack:/local/mirrors/linux-stable.git$ git tag -v v3.0.7
object 62bf7928bfe312ec6cf829b06893eb5649ceaec5
type commit
tag v3.0.7
tagger Greg Kroah-Hartman <gregkh@suse.de> 1318870270 -0700
This is the 3.0.7 stable release
gpg: Signature made Mon 17 Oct 2011 17:51:18 BST using RSA key ID 6092693E
gpg: Good signature from "Greg Kroah-Hartman (Linux kernel stable release signing key) <greg@kroah.com>"
build@slack:/local/mirrors/linux-stable.git$
I am aware that git is fun but if can be useful, I'm maintaining for my own use some unofficial patches/tarballs while I wait for the stuff to be back online (they are made with "git diff" and "git archive")
Run a cron that does a git pull, or git-request-pull, and notifies you of the results...?
cheers,
You may also try
Code:
git fetch --dry-run
It makes no changes whatsoever. It prints things if there is new stuff and prints nothing otherwise. This may be useful if you don't want automatic merges.
Seems like one of those cases of snatching complexity from the jaws of simplicity. You can also just download a tarball from the git repo. It's much quicker than using native git and, unless you're doing kernel devel, using git native is overkill. Plus the build process is the same as downloading a tarball from kernel.org. Plus you can do so for different branches.
Seems like one of those cases of snatching complexity from the jaws of simplicity. You can also just download a tarball from the git repo. It's much quicker than using native git and, unless you're doing kernel devel, using git native is overkill. Plus the build process is the same as downloading a tarball from kernel.org. Plus you can do so for different branches.
That might be true, but it is easier to upgrade to newer kernel versions if you use git.
That might be true, but it is easier to upgrade to newer kernel versions if you use git.
It's very easy and fast if you stay with mainline (like I do), but how does one upgrade through a major version tick of stable? When I was gitting stable, I used to reload everything, which is no better than getting tarballs. Is there a remote-related incantation that will do the trick?
If you're like me and upgrade your kernel by patching source of major version (v3.x) with minor version patches (v3.x.y), here's how to get one for v3.0.7 directly from kernel.org's gitweb:
Kernel.org is okay to use but they haven't updated anything on the main page in a while. The site is slowly returning to normal however so it might be a while till you see it up-to-date on the main pages.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.