diff --git a/Custom-Packages.md b/Custom-Packages.md
index 093a42c..6132466 100644
--- a/Custom-Packages.md
+++ b/Custom-Packages.md
@@ -39,8 +39,8 @@ Building rpm-based DKMS and user packages can be done as follows:
 
 ```sh
 $ cd zfs
-$ ./configure --with-config=srpm
-$ make -j1 pkg-utils rpm-dkms
+$ ./configure
+$ make -j1 rpm-utils rpm-dkms
 $ sudo yum localinstall *.$(uname -p).rpm *.noarch.rpm
 ```
 
@@ -51,7 +51,7 @@ The key thing to know when building a kmod package is that a specific Linux kern
 ```sh
 $ cd zfs
 $ ./configure
-$ make -j1 pkg-utils pkg-kmod
+$ make -j1 rpm-utils rpm-kmod
 $ sudo yum localinstall *.$(uname -p).rpm
 ```
 
@@ -64,7 +64,7 @@ The process for building kABI-tracking kmods is almost identical to for building
 ```sh
 $ cd zfs
 $ ./configure --with-spec=redhat
-$ make -j1 pkg-utils pkg-kmod
+$ make -j1 rpm-utils rpm-kmod
 $ sudo yum localinstall *.$(uname -p).rpm
 ```
 
@@ -85,7 +85,7 @@ The key thing to know when building a kmod package is that a specific Linux kern
 ```sh
 $ cd zfs
 $ ./configure
-$ make -j1 pkg-utils deb-kmod
+$ make -j1 deb-utils deb-kmod
 $ for file in *.deb; do sudo gdebi -q --non-interactive $file; done
 ```
 
@@ -96,8 +96,8 @@ Building deb-based DKMS and user packages can be done as follows:
 ```sh
 $ sudo apt-get install dkms
 $ cd zfs
-$ ./configure --with-config=srpm
-$ make -j1 pkg-utils deb-dkms
+$ ./configure
+$ make -j1 deb-utils deb-dkms
 $ for file in *.deb; do sudo gdebi -q --non-interactive $file; done
 ```