Mkdist
Mkdist
multifunction file converter useful in making/tuning puplets up.
mkdist-1.3.tar.gz
http://shino.pos.to/party/bridge.cgi?puppy/opt/
USAGE:
Open the archive in a working directory in a partition with Linux filesystem.
Drop the source file/directory on the script mkdist.
Difference with the remastering tools:
Mkdist cannot handle additional packages, PET/SFS.
Add the packages, and use the remastering tools in such a case.
See RemasterX:
http://www.murga-linux.com/puppy/viewtopic.php?t=94033
Mkdist can be used small tuning of the remastered ones.
Mkdist can be done on any Puppy, whereas the remastering tool must be run on the Puppy which you are want to modify.
mkdist-1.3.tar.gz
http://shino.pos.to/party/bridge.cgi?puppy/opt/
USAGE:
Open the archive in a working directory in a partition with Linux filesystem.
Drop the source file/directory on the script mkdist.
Difference with the remastering tools:
Mkdist cannot handle additional packages, PET/SFS.
Add the packages, and use the remastering tools in such a case.
See RemasterX:
http://www.murga-linux.com/puppy/viewtopic.php?t=94033
Mkdist can be used small tuning of the remastered ones.
Mkdist can be done on any Puppy, whereas the remastering tool must be run on the Puppy which you are want to modify.
Last edited by shinobar on Sat 12 Nov 2016, 13:47, edited 2 times in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Adding a Graphical Boot Menu to the Puppy Live CD
HOW TO USE Mkdist (1):
Adding a Graphical Boot Menu to the Puppy Live CD
1. Drag and drop the source .iso file on mkdist.
The content files are expanded in the directory inside_iso.
2. Get the files for the graphical menu:
http://www.murga-linux.com/puppy/viewtopic.php?t=61132
You need not dir2iso because mkdist can do it.
3. Arrange (replace and edit) the files in inside_iso.
4. Drag and drop the directory inside_iso on mkdist.
Customized .iso file is created.
Adding a Graphical Boot Menu to the Puppy Live CD
1. Drag and drop the source .iso file on mkdist.
The content files are expanded in the directory inside_iso.
2. Get the files for the graphical menu:
http://www.murga-linux.com/puppy/viewtopic.php?t=61132
You need not dir2iso because mkdist can do it.
3. Arrange (replace and edit) the files in inside_iso.
4. Drag and drop the directory inside_iso on mkdist.
Customized .iso file is created.
- Attachments
-
- graphical_menu_inside.png
- inside_iso
- (8.6 KiB) Downloaded 1504 times
Last edited by shinobar on Thu 26 Jun 2014, 19:06, edited 3 times in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Replacing init script in initrd.gz
HOW TO USE Mkdist (2):
Replacing init script in initrd.gz
1. Drag and drop the source .iso file on mkdist.
The content files are expanded in the directory inside_iso.
2. Drag and drop inside_iso/initrd.gz on mkdist.
initrd.gz is expanded in a directory initrd-tree.
3. Replace the script initrd-tree/init.
4. Drag and drop initrd-tree on mkdist.
inside_iso/initrd.gz is updated.
5. Edit the files(menu.lst, README.HTM and etc.) in inside_iso, if needed.
6. Drag and drop inside_iso on mkdist.
Customized .iso is created.
See an example:
http://www.murga-linux.com/puppy/viewto ... 277#780277
Replacing init script in initrd.gz
1. Drag and drop the source .iso file on mkdist.
The content files are expanded in the directory inside_iso.
2. Drag and drop inside_iso/initrd.gz on mkdist.
initrd.gz is expanded in a directory initrd-tree.
3. Replace the script initrd-tree/init.
4. Drag and drop initrd-tree on mkdist.
inside_iso/initrd.gz is updated.
5. Edit the files(menu.lst, README.HTM and etc.) in inside_iso, if needed.
6. Drag and drop inside_iso on mkdist.
Customized .iso is created.
See an example:
http://www.murga-linux.com/puppy/viewto ... 277#780277
- Attachments
-
- mkdist_work.png
- Working directory
- (32.31 KiB) Downloaded 1358 times
Last edited by shinobar on Thu 26 Jun 2014, 19:08, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Kernel panic - not syncing: No init found
Mkdist looks like a great utility. Having a problem though.
Steps I followed:
1) Dragged the ISO file into source component field and clicked OK
2) It created 2 folders from the ISO. 'inside_iso' & 'Puppy_Precise_5.7.1'.
3) I made changes to some files inside the new 'Puppy_Precise_5.7.1' folder it created and wanted to make the new ISO.
4) I dragged the now modified 'Puppy_Precise_5.7.1' into the source component field and clicked ok. (Maybe i'm doing it wrong)
5) New mkdist window opens up and it's pre-filled in. I just click OK and it made new ISO. (Was I supposed to make changes to the 'inside_iso' folder also?)
Then I try to boot this new version and I see the 'Kernel panic - not syncing: No init found' and it fails to boot up.
I thought it was simple but I think I'm missing a step. Any ideas?
Thanks
Steps I followed:
1) Dragged the ISO file into source component field and clicked OK
2) It created 2 folders from the ISO. 'inside_iso' & 'Puppy_Precise_5.7.1'.
3) I made changes to some files inside the new 'Puppy_Precise_5.7.1' folder it created and wanted to make the new ISO.
4) I dragged the now modified 'Puppy_Precise_5.7.1' into the source component field and clicked ok. (Maybe i'm doing it wrong)
5) New mkdist window opens up and it's pre-filled in. I just click OK and it made new ISO. (Was I supposed to make changes to the 'inside_iso' folder also?)
Then I try to boot this new version and I see the 'Kernel panic - not syncing: No init found' and it fails to boot up.
I thought it was simple but I think I'm missing a step. Any ideas?
Thanks
Mosifying PuppySFS
HOW TO USE Mkdist (3):
Modifying PuppySFS
nassausky already showed the step:
1) Dragged the ISO file into source component field and clicked OK
2) It created 2 folders from the ISO. 'inside_iso' & 'Puppy_Precise_5.7.1'.
3) I made changes to some files inside the new 'Puppy_Precise_5.7.1' folder it created and wanted to make the new ISO.
4) I dragged the now modified 'Puppy_Precise_5.7.1' into the source component field and clicked ok. (Maybe i'm doing it wrong)
5) New mkdist window opens up and it's pre-filled in. I just click OK and it made new ISO.
You can add suffix to show the iso is modified. Anyway, new components are automatically add new ID string to identify distinct one with the original.
Modifying PuppySFS
nassausky already showed the step:
1) Dragged the ISO file into source component field and clicked OK
2) It created 2 folders from the ISO. 'inside_iso' & 'Puppy_Precise_5.7.1'.
3) I made changes to some files inside the new 'Puppy_Precise_5.7.1' folder it created and wanted to make the new ISO.
4) I dragged the now modified 'Puppy_Precise_5.7.1' into the source component field and clicked ok. (Maybe i'm doing it wrong)
5) New mkdist window opens up and it's pre-filled in. I just click OK and it made new ISO.
You can add suffix to show the iso is modified. Anyway, new components are automatically add new ID string to identify distinct one with the original.
- Attachments
-
- suffix.png
- You can add suffix before cliking OK
- (5.38 KiB) Downloaded 1145 times
Last edited by shinobar on Fri 04 Nov 2016, 06:46, edited 1 time in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
Test avec Pupjibaro (Puppy-es Precise 5.7.1)
Test avec Pupjibaro (Puppy-es Precise 5.7.1)
Si working fine, je traduirai en français et espagnol
IF OK, how-to translated UK US >>>> FR ES
Si working fine, je traduirai en français et espagnol
IF OK, how-to translated UK US >>>> FR ES
it's really not clear for me (cause of english)
it's really not clear for me (cause of english); the only way to modify the iso is to modify the Puppy.sfs (with edit sfs among others).
and then to close the iso again
and then to close the iso again
mkdist-1.3
Updated: mkdist-1.3.tar.gz
http://shino.pos.to/party/bridge.cgi?puppy/opt/
#2016-11-11 v1.3: no '-b 1024k' compression, improbed GUI, read from live CD, NLS
http://shino.pos.to/party/bridge.cgi?puppy/opt/
#2016-11-11 v1.3: no '-b 1024k' compression, improbed GUI, read from live CD, NLS
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
http://shinobar.server-on.net/puppy/opt/ indicates a 57KB download for mkdist-1.3.tar.gz, but the download is 975 KB.
It would appear that there are 3 xpm files in ./misc ~310KB each.
Is this how it should be?
It would appear that there are 3 xpm files in ./misc ~310KB each.
Is this how it should be?
== [url=http://www.catb.org/esr/faqs/smart-questions.html]Here is how to solve your[/url] [url=https://www.chiark.greenend.org.uk/~sgtatham/bugs.html]Linux problems fast[/url] ==