Home
Name Modified Size Downloads / Week Status
Totals: 4 Items   39.3 kB 2
releases 2012-12-19 11 weekly downloads
development 2012-06-19 11 weekly downloads
readme.txt 2012-12-21 4.1 kB 11 weekly downloads
COPYING 2011-04-26 35.1 kB 11 weekly downloads
121218 Dear Users, This time there are two releases, JBD.14-0.1_isol.make.1_kit.tgz JBD.13-37.2_isol.make.1_kit.tgz These downloads enable you to burn CDs that can be used to boot Slackware Linux 14.0 and 13.37. They also serve as handy live CDs for rescue or whatever you need to do. *** About JBD.14-0.1_isol.make.1_kit.tgz: This release has everything from JBD.13-37.2_isol.make.1_kit.tgz, but it boots Slackware 14.0. This is the new default download. As usual, Download it and unpack it with "tar -xvvzf *". Look in JBD.14-0.1_isol.make.1_kit/boots/iso/JBD.14-0.1_isol.make.1/readme.txt for a HOWTO. *** About JBD.13-37.2_isol.make.1_kit.tgz: The changes this release brings may not affect you at all. They were "housekeeping" changes, and I added tools called bunch3 and part_mir3 for doing backups. I haven't written documentation bunch3 and part_mir3 yet, but go ahead and try them if you are interested. I put them on a JBD, because when they run they will also do file system checks if you want. File system checks (e2fsck) cannot be run on mounted file systems, so I thought running from a JBD would be ideal. So far, I'm not comfortable with running these tools this way. Down load and unpack in the usual way, although since this is not the default download, you'll need to "Browse All Files" to find it. Look in the folder called "releases". Find the HOWTO in the usual place JBD.13-37.2_isol.make.1_kit/boots/iso/JBD.13-37.2_isol.make.1/readme.txt *** 120629 Dear Users, I offer you a new release. I call it JBD.13-37.1_isol.make.1_kit.tgz It is now the default download. Download it and unpack it with "tar -xvvzf *". Look in JBD.13-37.1_isol.make.1_kit/boots/iso/JBD.13-37.1_isol.make.1/readme.txt for a HOWTO that tells how to make your own, custom, JBD. A few words about how to use the JBD to boot Slackware 13.37 are also given. -Joe 120619 Dear Users, Thanks for you patience as I make some changes. Since I last wrote I made some more changes to the directory structure. You will see, if you click on "Browse All Files" and take a look around, that I have organized this project into two directories: development and releases. The legacy directory that I mentioned last time is in releases. The development directory is a copy (via rsync) of my development space for this project. (I will update it from time to time.) As I mentioned before, this directory will make it easier for you to understand how to make JBDs. This is especially true if you want to make some changes. The releases directory contains releases. Please note that I copy from development to releases to make a release. So please go to releases for releases, and use development as a resource. I mentioned my use of the Isolinux boot loader. I'm also working on a kit that has tools to make custom JBDs. That should make it easy to burn a tailor-made JBD with your choice of file system, partition label, and something new-- a box parameter. The (optional) box parameter will help when you take your bootable drive and JBD to a different Linux box. You provide the box parameter on the command line when you boot to tell Linux to use different settings for different hardware. You can write your own tools to read the box parameter and change settings and/or use the rc.JBD tool that I have provided. -Joe 120601 Dear Users, I moved everything to a directory called "legacy", because I have remade the whole project in a new format. This new format is the native directory structure that I use. This will make new releases easier for me, and it will make it easier for you to understand how to make a JBD. There are also some new developments *brewing* such as use of the Isolinux boot loader and a new JBD release for Slackware 13.37. (Although I have uploaded some of the new stuff, none of it has been released and is still in work. Consider it a pre-release!) I will keep the legacy dir as some users may need it, although I plan to not use it for future development. I will make an announcement when the new stuff is released. -Joe
Source: readme.txt, updated 2012-12-21