Hi Porteus members,
(3.1)
For folders in /mnt/sda1/porteus/rootcopy/root/.config, I use make links, Mousepad@, xfce4@ etc, these actual folders are stored inside /mnt/sda1/portable
So whenever some adjustments to desktop settings or application preferences, they all get stored exactly like I wish and loaded up with /root/.config/ folders are links to /mnt/sda1/portable
in (3.2rc5)
I did the same setting like above, but links folders didn't perform like in 3.1.
Any ideas how to make such setting works? Thank you very much.
3.2rc5 rootcopy behaviour different from 3.1
-
- Full of knowledge
- Posts: 2564
- Joined: 25 Jun 2014, 15:21
- Distribution: 3.2.2 Cinnamon & KDE5
- Location: London
Re: 3.2rc5 rootcopy behaviour different from 3.1
^ Please furnish example of what you did for one of these folders in detail. Please use code blocks, where it will be of advantage to do so.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB
-
- Contributor
- Posts: 676
- Joined: 26 Jun 2013, 14:03
- Distribution: x64 Openbox
- Location: Russia is causing the immense damage to humanity
- Contact:
Re: 3.2rc5 rootcopy behaviour different from 3.1
If mentioned folders already exist in your folders tree they could not be overwritten by symlinks, then symlinks must be in module (loaded as last) or changes layer. The easiest way is to make module from your rootcopy. Or maybe your /mnt/sda1 is changed to another mount point. I use Porteus in similar way.
You have mind and feelings. Be wise and clever.
Re: 3.2rc5 rootcopy behaviour different from 3.1
Thank you tome for this information.