Skip to content

Commit

Permalink
Merge remote-tracking branch 'remotes/origin/master' into master-old
Browse files Browse the repository at this point in the history
  • Loading branch information
shipujin committed Jul 6, 2023
2 parents 9e722c1 + 3c17712 commit 884a3e7
Show file tree
Hide file tree
Showing 953 changed files with 52,776 additions and 87,856 deletions.
9,023 changes: 9,021 additions & 2 deletions ChangeLog.rss

Large diffs are not rendered by default.

7,354 changes: 7,354 additions & 0 deletions ChangeLog.txt

Large diffs are not rendered by default.

16,917 changes: 8,508 additions & 8,409 deletions FILELIST.TXT

Large diffs are not rendered by default.

16 changes: 8 additions & 8 deletions README.initrd
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@

Slackware initrd mini HOWTO
by Patrick Volkerding, [email protected]
Sat Oct 15 20:17:47 UTC 2022
Wed Jul 5 20:48:22 UTC 2023

This document describes how to create and install an initrd, which may be
required to use the 4.x kernel. Also see "man mkinitrd".
Expand Down Expand Up @@ -33,16 +33,16 @@ flexible to ship a generic kernel and a set of kernel modules for it.

The easiest way to make the initrd is to use the mkinitrd script included
in Slackware's mkinitrd package. We'll walk through the process of
upgrading to the generic 5.19.16 Linux kernel using the packages
upgrading to the generic 6.1.38 Linux kernel using the packages
found in Slackware's slackware/a/ directory.

First, make sure the kernel, kernel modules, and mkinitrd package are
installed (the current version numbers might be a little different, so
this is just an example):

installpkg kernel-generic-5.19.16-x86_64-1.txz
installpkg kernel-modules-5.19.16-x86_64-1.txz
installpkg mkinitrd-1.4.11-x86_64-30.txz
installpkg kernel-generic-6.1.38-x86_64-1.txz
installpkg kernel-modules-6.1.38-x86_64-1.txz
installpkg mkinitrd-1.4.11-x86_64-32.txz

Change into the /boot directory:

Expand All @@ -52,7 +52,7 @@ Now you'll want to run "mkinitrd". I'm using ext4 for my root filesystem,
and since the disk controller requires no special support the ext4 module
will be the only one I need to load:

mkinitrd -c -k 5.19.16 -m ext4
mkinitrd -c -k 6.1.38 -m ext4

This should do two things. First, it will create a directory
/boot/initrd-tree containing the initrd's filesystem. Then it will
Expand All @@ -61,10 +61,10 @@ you could make some additional changes in /boot/initrd-tree/ and
then run mkinitrd again without options to rebuild the image. That's
optional, though, and only advanced users will need to think about that.

Here's another example: Build an initrd image using Linux 5.19.16
Here's another example: Build an initrd image using Linux 6.1.38
kernel modules for a system with an ext4 root partition on /dev/sdb3:

mkinitrd -c -k 5.19.16 -m ext4 -f ext4 -r /dev/sdb3
mkinitrd -c -k 6.1.38 -m ext4 -f ext4 -r /dev/sdb3


4. Now that I've built an initrd, how do I use it?
Expand Down
2 changes: 1 addition & 1 deletion extra/source/brltty/brltty.SlackBuild
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ PKG=/tmp/package-brltty

PKGNAM=brltty
VERSION=${VERSION:-$(echo $PKGNAM-*.tar.?z | rev | cut -f 3- -d . | cut -f 1 -d - | rev)}
BUILD=${BUILD:-1}
BUILD=${BUILD:-2}

# Automatically determine the architecture we're building on:
if [ -z "$ARCH" ]; then
Expand Down
29 changes: 0 additions & 29 deletions extra/source/php80/doinst.sh

This file was deleted.

2 changes: 0 additions & 2 deletions extra/source/php80/fetch-php.sh

This file was deleted.

29 changes: 0 additions & 29 deletions extra/source/php80/mod_php.conf.example

This file was deleted.

19 changes: 0 additions & 19 deletions extra/source/php80/php-fpm.conf.diff

This file was deleted.

71 changes: 0 additions & 71 deletions extra/source/php80/php.imap.api.diff

This file was deleted.

62 changes: 0 additions & 62 deletions extra/source/php80/php.ini-development.diff

This file was deleted.

Loading

0 comments on commit 884a3e7

Please sign in to comment.