Menu

Home partition fun

2023-07-15
2023-07-20
  • packing4mars

    packing4mars - 2023-07-15

    Many thanks to the team for all their work on the Distro...and on this forum!!

    Been using Peppermint for about 18 months, and this is my first installation problem - quite possibly self-induced.

    I have just completed a fresh installation of the new Pep Debian, but did something I now realise was a bit daft: I didn't mount my home partition during the installation process - I chose the manual option, but only set up the boot and root partitions (not even swap!). My idea was to boot in, change the /etc/fstab file, remove the newly installed home directories, set up symlinks and then reboot. Well doing this reinstated the personalisations from my old installation and broke the pep hub - nothing happens when I attempt to go into it. I now know the .config file sits in /home.

    My intention is to reinstall, unless advised otherwise. My questions are:
    1) Is there anything I should do in preparation for reinstalling? I've backed up my data, but would prefer not to wipe my /home partition!
    2) By mounting my /home partition, does the installer overwrite or archive the configuration files from the old installation?
    3) I'm guessing that having these configuration files in my /home partition would make it difficult to dual boot distros while sharing a /home partition? I was considering doing this to access some KDE tools without needing to use snaps/flatpaks.

    Here is my inxi -Fxz

    System:
    Kernel: 6.1.0-9-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    Desktop: Xfce v: 4.18.1 Distro: PeppermintOS bookworm
    Machine:
    Type: Laptop System: LENOVO product: 80X4 v: Lenovo ideapad 320S-14IKB
    serial: <superuser required="">
    Mobo: LENOVO model: LNVNB161216 v: SDK0J40700 WIN
    serial: <superuser required=""> UEFI: LENOVO v: 4QCN51WW(V2.15)
    date: 11/19/2019
    Battery:
    ID-1: BAT1 charge: 24.4 Wh (100.0%) condition: 24.4/30.0 Wh (81.4%)
    volts: 8.1 min: 7.4 model: SIMPLO PABAS0241231 status: full
    Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard
    charge: 55% (should be ignored) status: discharging
    CPU:
    Info: dual core model: Intel Core i3-7100U bits: 64 type: MT MCP
    arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB L2: 512 KiB
    L3: 3 MiB
    Speed (MHz): avg: 2023 high: 2400 min/max: 400/2400 cores: 1: 2400 2: 2400
    3: 2400 4: 894 bogomips: 19200
    Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
    Graphics:
    Device-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel
    arch: Gen-9.5 bus-ID: 00:02.0
    Device-2: Chicony EasyCamera type: USB driver: uvcvideo bus-ID: 1-5:3
    Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1: 1920x1080~60Hz
    2: 1366x768~60Hz
    API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 620 (KBL
    GT2) direct-render: Yes
    Audio:
    Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
    API: ALSA v: k6.1.0-9-amd64 status: kernel-api
    Server-1: PulseAudio v: 16.1 status: active
    Network:
    Device-1: Intel Dual Band Wireless-AC 3165 Plus Bluetooth driver: iwlwifi
    v: kernel bus-ID: 02:00.0
    IF: wlp2s0 state: up mac: <filter>
    Bluetooth:
    Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-7:4
    Report: hciconfig ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 2.1
    lmp-v: 4.2
    Drives:
    Local Storage: total: 119.24 GiB used: 19.36 GiB (16.2%)
    ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLW128HEGR-000L2
    size: 119.24 GiB temp: 27.9 C
    Partition:
    ID-1: / size: 33.35 GiB used: 5.61 GiB (16.8%) fs: ext4 dev: /dev/nvme0n1p2
    ID-2: /boot/efi size: 300.4 MiB used: 9.8 MiB (3.3%) fs: vfat
    dev: /dev/nvme0n1p1
    Swap:
    Alert: No swap data was found.
    Sensors:
    System Temperatures: cpu: 39.0 C pch: 36.5 C mobo: N/A
    Fan Speeds (RPM): N/A
    Info:
    Processes: 177 Uptime: 2h 24m Memory: 7.62 GiB used: 1.86 GiB (24.4%)
    Init: systemd target: graphical (5) Compilers: gcc: 12.2.0 Packages: 1579
    Shell: Bash v: 5.2.15 inxi: 3.3.26</filter></filter></superuser></superuser>

     
  • alynur

    alynur - 2023-07-16

    It looks like by what you want to do, you will have to experiment and accept the worse should it happen. So List your current Home partition as your mount point for your new Home partition and don't reformat it. But if you're going to dual boot, make another partition for the second OS and format it as ext4. Before any of this, I would recommend reading up on making DATA partitions and using symlinks.

     
  • packing4mars

    packing4mars - 2023-07-20

    Thanks @alynur and I sorry I didn't report back earlier. I found that as soon as I unmounted my data partition the conflict was resolved and access to the Pep Hub restored. So I am now keeping symlinks/mounting of my data file completely clear of home!! I'll clear out the old configuration files when I get around to it.

     

Log in to post a comment.