Re: Encrypted partiotions - which files related?
Am Montag, 29. Januar 2024, 12:16:14 CET schrieb Arno Lehmann:
Hi Arno,
yes, I saw the option SRCDISK. For my understanding it is used, when you want
to mount a an alien system i.e. via network and make a livefile from this.
But even I will do so, still all files will be copied to the livefilesystem,
this makes no change.
You asked me, what I want. Simple: I am running KALI-Linux on one of my
notebooks· with encrypted partitions.
As my KALI got some tools, which need lots of plugins, has added some software
NOT in the KALI-repo and got several personal settings, I could not build a
livefile system of KALI by using live-build.
Thus my idea, creating a livefile from the running KALI (which I did already
successfull with a debian system on another computer) and copy it to a usb-
stick by using the dd command.
So I created an ISO with about 32GB size, than copied it to a 64GB usb-stick
and Voila, I got my own KALI running from usb-stick.
Everything is working perfectly, except this little annoying at boot.
Besides: Doing so, is a great advantage, as you might agree: I can make a
livesystem from a server, then boot it and now can dangerousless test different
configurations, can install packages, can test special settings and so on. Just
without to harm any productive system.
And after testing, I can easily change the well tested configurations to the
productive server!
Two advantages, as you see.
Does this make things a little bit clearer?
Best
Hans
> Hi Hans,
>
> Am 29.01.2024 um 11:30 schrieb Hans:
> > Hi folks,
> >
> > I created a livefile system with bootcdwrite from a system with encrypted
> > partitions.
> >
> > Everything is working fine, but ...
>
> Checking the manual for bootcdwrite.conf, I find
>
> OPTIONS
>
> SRCDISK
> The Variables SRCDISK defines the root of the files that will be copied.
>
> For example, to build an image from a remote system, export
> root-directory with nfs, mount it locally to /mnt/remote and add:
>
> SRCDISK=/mnt/remote
>
>
>
> It is added as prefix to KERNEL, INITRD, DISABLE_CRON and NOT_TO_CD, if
> this are relativ paths (without starting "/")
>
> Default:
>
> SRCDISK=/
>
>
> which I understand implies that, by default, bootcdwrite more or less
> copying the system you run it on. Thus, the expectation that it should
> keep off of your lawn, erm, partitions seems unrealistic.
>
> On the other hand, you can create a configuration that uses a different
> source system, or modifies it. In your case, it appears that you want
> some modifications.
>
> My understanding, however, is that you want modifications going so deep,
> that it may be more reasonable to *not* start with your regular system.
> Before we try to identify what you'd have to exclude, can you give us an
> idea of what your actual goal ist?
>
> Cheers,
>
> Arno
Reply to: