Hi everybody !
Please can anybody explain how to work with Zdrv-cutter .......step by step ..?
Thanks in advance ..
How to use Zdrv-cutter?
Zdrive
Hi !
Found the answer ..
O.K . let me explain what is meant . In my constant research to cut down my O.S. making a remaster of Dpupexprimo ...threw out a lot of programms and or substituted a lot of build in programms with sfs versions of programms i use .I just load sfs programms on on demand ,
In short ... during remaster process one can choose to exclude all driver-files as a zdrv-sfs file . I did choose that option ..optained a remasterd iso with the drivers as a separat zdrv-sfs file .Later when using my new remasterd Dpup i used "zdrv-cutter " pet .(downloaded it )
which cuts down unnessesary driver libs .This programm makes a sfs file smaller than the original zdrv-sfs this is just for your special machine you are using .It removes unneeded drivers .
The trick was naming the newer smaller zdrv-sfs file same as the original one .use this new one instead of the older,bigger one ... ... put the old one beside .
Cuts down my new remasterd Os 20 megabytes .
Found the answer ..
O.K . let me explain what is meant . In my constant research to cut down my O.S. making a remaster of Dpupexprimo ...threw out a lot of programms and or substituted a lot of build in programms with sfs versions of programms i use .I just load sfs programms on on demand ,
In short ... during remaster process one can choose to exclude all driver-files as a zdrv-sfs file . I did choose that option ..optained a remasterd iso with the drivers as a separat zdrv-sfs file .Later when using my new remasterd Dpup i used "zdrv-cutter " pet .(downloaded it )
which cuts down unnessesary driver libs .This programm makes a sfs file smaller than the original zdrv-sfs this is just for your special machine you are using .It removes unneeded drivers .
The trick was naming the newer smaller zdrv-sfs file same as the original one .use this new one instead of the older,bigger one ... ... put the old one beside .
Cuts down my new remasterd Os 20 megabytes .
I have the same request as Backi - don't know how to use zdrv-cutter and honestly didn't find the answer even in the suggested link. I want to cut down the zdrv.sfs in TahrPup. I install the .pet, it makes another zl15.05420.sfs with many folders but neither a GUI nor a menu entry. What am I supposed to do then?
Hello backi, riedzig and all.
I wouldn't touch the zdrv*.sfs file of any Puppy if I were you. It contains the
modules for various hardware on your machine. Messing with this file if you don't
know what you're doing is asking for trouble, IMO. To remove anything in it, you
have to know what specific hardware your machine uses and what exact modules
match it. And NOT remove the ones your machine needs.
Believe me, it's for specialists, very experienced Puppy and/or Linux devs, not for
the casual user.
Remove the wrong module and something on your machine will stop working:
ethernet card, sound card, mouse or mousepad, the drive bus, you name it. The
zdrv sfs file is simply an "extraction" into a separate file of what there is at
/lib/modules in the Puppies that do not have the zdrv sfs file.
Why cut any of it? Is PuppyLinux so big? Come on...
if you have a limited amount of RAM, you may however de-activate some of
the services and unneeded modules in Puppy without messing with the modules
zdrv file. Simply open your menu and go to
Config -> System -> Boot Manager.
In this Boot Manager, what you are looking for is at the 3rd and 4th tabs.
Study this and be sure of yourself before you do anything drastic. Although in the
BootManager, you can -- usually -- re-activate the stuff you de-activated.
Yes, I said "usually"... Because to err is all too human...
You've been warned!
For your own safety -- and for your carefree enjoyment of Puppy.
Bye for now.
I wouldn't touch the zdrv*.sfs file of any Puppy if I were you. It contains the
modules for various hardware on your machine. Messing with this file if you don't
know what you're doing is asking for trouble, IMO. To remove anything in it, you
have to know what specific hardware your machine uses and what exact modules
match it. And NOT remove the ones your machine needs.
Believe me, it's for specialists, very experienced Puppy and/or Linux devs, not for
the casual user.
Remove the wrong module and something on your machine will stop working:
ethernet card, sound card, mouse or mousepad, the drive bus, you name it. The
zdrv sfs file is simply an "extraction" into a separate file of what there is at
/lib/modules in the Puppies that do not have the zdrv sfs file.
Why cut any of it? Is PuppyLinux so big? Come on...
if you have a limited amount of RAM, you may however de-activate some of
the services and unneeded modules in Puppy without messing with the modules
zdrv file. Simply open your menu and go to
Config -> System -> Boot Manager.
In this Boot Manager, what you are looking for is at the 3rd and 4th tabs.
Study this and be sure of yourself before you do anything drastic. Although in the
BootManager, you can -- usually -- re-activate the stuff you de-activated.
Yes, I said "usually"... Because to err is all too human...
You've been warned!
For your own safety -- and for your carefree enjoyment of Puppy.
Bye for now.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Thanks musher0 for your quick reply,
I agree that reducing zdrv can be a tricky thing, but that's just why one expects this zdrv cutter was made to do it correctly. On the other hand, an error cannot have fatal results, in frugal installs you can make backups and easily replace any broken folder.
I would still appreciate a help for zdrv_cutter...
I agree that reducing zdrv can be a tricky thing, but that's just why one expects this zdrv cutter was made to do it correctly. On the other hand, an error cannot have fatal results, in frugal installs you can make backups and easily replace any broken folder.
I would still appreciate a help for zdrv_cutter...
Hi riedzig !
" I install the .pet, it makes another zl15.05420.sfs "
This zl15.05420.sfs is your cutdown new zdrive.sfs .
This zl15.05420.sfs must be renamed to the name of the old (in my case using tahrpup 6.0.5 to zdrv_tahr_6.0.5.sfs ) -zdrv.sfs .
You can do it savely by backing up your old Zdrive.sfs ( better your savefile-folder too........ Did it with tahrpup 6.0.5 .
You then can delete the old zdrive.sfs while running your puppy and replace it with the new zdrive.sfs (in my case renamed to zdrv_tahr_6.0.5.sfs ).....important ...it must be renamed to the same name as the old Zdrive.sfs .
Shut down and boot with your new cutdown zdrive again .
The whole procedure step by step :
You must extract your new zdrive.sfs from your running programm .
1. Load zdrivecutter pet.
2. I could not find a menue entry , but started it from usr/bin/zdrvcutr .
3. Zdrv Cutter appears........"Show files......Continue "........ do both
4. after continuing a little later... it appears ....." Show files...or Exit "
5. continue....wait a while.... look at root ..you will find a new xxxxx.sfs and a checksum.txt .
6. copy your old Zdrive.sfs to a save place .Put this new zdrive.sfs to a save place ...... rename it with the name of the old zdrive.sfs .
7. you have to rename the new smaller zdrive.sfs to the name of the older one to replace the older bigger one .
You can delete the old zdrive modules while running your puppy and replace it with the new zdrive.sfs.....important ...it must have the same name as the old Zdrive.sfs
This new zdrive module can only be used on your running machine .
In case something went wrong ....just use your old zdrive.sfs again .
But ...there is no urgent need to cut it down because of maybe 20 mega bytes
saving .
Any further questions ......here to help !
" I install the .pet, it makes another zl15.05420.sfs "
This zl15.05420.sfs is your cutdown new zdrive.sfs .
This zl15.05420.sfs must be renamed to the name of the old (in my case using tahrpup 6.0.5 to zdrv_tahr_6.0.5.sfs ) -zdrv.sfs .
You can do it savely by backing up your old Zdrive.sfs ( better your savefile-folder too........ Did it with tahrpup 6.0.5 .
You then can delete the old zdrive.sfs while running your puppy and replace it with the new zdrive.sfs (in my case renamed to zdrv_tahr_6.0.5.sfs ).....important ...it must be renamed to the same name as the old Zdrive.sfs .
Shut down and boot with your new cutdown zdrive again .
The whole procedure step by step :
You must extract your new zdrive.sfs from your running programm .
1. Load zdrivecutter pet.
2. I could not find a menue entry , but started it from usr/bin/zdrvcutr .
3. Zdrv Cutter appears........"Show files......Continue "........ do both
4. after continuing a little later... it appears ....." Show files...or Exit "
5. continue....wait a while.... look at root ..you will find a new xxxxx.sfs and a checksum.txt .
6. copy your old Zdrive.sfs to a save place .Put this new zdrive.sfs to a save place ...... rename it with the name of the old zdrive.sfs .
7. you have to rename the new smaller zdrive.sfs to the name of the older one to replace the older bigger one .
You can delete the old zdrive modules while running your puppy and replace it with the new zdrive.sfs.....important ...it must have the same name as the old Zdrive.sfs
This new zdrive module can only be used on your running machine .
In case something went wrong ....just use your old zdrive.sfs again .
But ...there is no urgent need to cut it down because of maybe 20 mega bytes
saving .
Any further questions ......here to help !
-
gcmartin
Correct me if I am wrong.
In a remaster, you gain much of what your running system needs for booting in the ZDRV produced. And, by most every account since the PUP "industry" shifted to using ZDRV, we have few accounts of problems in what it contains.
ZDRV is only used at system boot, for most instances. On any PC manufactured in the last 2 decades, a 20MB savings in a boot process suggest 2 thing:
But, this thread does help in one aspect: ZDRV without touching is a reasonably complete, safe, and rapid feature of the boot process. With touching your mileage will vary but not significantly and ONLY at system boot.
Hope this is helpful only as an informational. Others may have knowledge that show additional benefits in Live or Frugal booting not currently mentioned.
In a remaster, you gain much of what your running system needs for booting in the ZDRV produced. And, by most every account since the PUP "industry" shifted to using ZDRV, we have few accounts of problems in what it contains.
ZDRV is only used at system boot, for most instances. On any PC manufactured in the last 2 decades, a 20MB savings in a boot process suggest 2 thing:
- The original ZDRV is reasonably complete and sparce for a given remaster
- A 20MB savings over all the modules included in ZDRV seems to have little to no impact on boot times.
But, this thread does help in one aspect: ZDRV without touching is a reasonably complete, safe, and rapid feature of the boot process. With touching your mileage will vary but not significantly and ONLY at system boot.
Hope this is helpful only as an informational. Others may have knowledge that show additional benefits in Live or Frugal booting not currently mentioned.