View Issue Details

IDProjectCategoryView StatusLast Update
0008094Kali LinuxFeature Requestspublic2022-12-21 08:33
Reportervkrishn Assigned Todaniruiz  
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionreopened 
Product Versionkali-dev 
Summary0008094: Request for splitting live/filesystem.squashfs in isos
Description

Hi,

Please consider splitting live/filesystem.squashfs.
Suggestion:

  1. live/10.debian.squashfs
  2. live/20.kali.squashfs

where 10.debian.squashfs is created using pkgs from debian repos, I guess it being the base install,
and 20.kali.squashfs created using pkgs from kali.org

Thanks.

Activities

daniruiz

daniruiz

2022-12-20 10:22

manager   ~0017265

Sorry but it doesn't work that way. The squashfs is a image of the root tree of a preinstalled kali, not a container for multiple packages. Also, we are based on Debian, but that doesn't mean Kali is Debian + some tools. We do modifications in packages that come from Debian that Debian doesn't have

vkrishn

vkrishn

2022-12-21 02:40

reporter   ~0017268

Thanks for response,
Should have added more, I understand its not debian, expanding my previous note,

  1. live/10.kali.base.squashfs --> base install (without any pen testing tools).
  2. live/20.kali.penttestbase.squashfs --> all tools that comes in 4gb iso dvd.
    (1+2 == standard iso DVD)
  3. live/30.kali.penttestextended.squashfs --> all other tools that comes in 11gb full iso dvd.

I also understand build process if kernel is customized, along with other booting process and efforts involved.
I am not re-requesting/opening, but only clarifying some bits.

(considering it closed, unless otherwise)
Thanks again.

daniruiz

daniruiz

2022-12-21 08:32

manager   ~0017269

Sorry again but packages don't work that way. We can't separate them in multiple squashfs like in layers. Multiple packages do modifications (and configurations) to other files after installation. Having the packages separated that way would require an extra step for the installation process, and for that we already have the installer image

Issue History

Date Modified Username Field Change
2022-12-09 17:16 vkrishn New Issue
2022-12-20 10:22 daniruiz Note Added: 0017265
2022-12-20 10:22 daniruiz Assigned To => daniruiz
2022-12-20 10:22 daniruiz Status new => closed
2022-12-20 10:22 daniruiz Resolution open => no change required
2022-12-21 02:40 vkrishn Status closed => feedback
2022-12-21 02:40 vkrishn Resolution no change required => reopened
2022-12-21 02:40 vkrishn Note Added: 0017268
2022-12-21 08:32 daniruiz Note Added: 0017269
2022-12-21 08:33 daniruiz Status feedback => closed