From: dave@dave123royal.com   
      
   "Carlos E.R."  Wrote in message:   
      
   > On 2024-08-24 08:39, Dave Royal wrote:   
   >> philo@novabbs.com (philo) Wrote in message:   
   >>   
   >>> I ran a few more tests.   
   >>> If the drive is NTFS to begin with, the default installer will evidently   
   >>> assume one has Windows installed and shrink the partition...so that is   
   >>> why I ended up with NTFS.   
   >>>   
   >>> What I should have done was the custom installation.   
   >>>   
   >>> My fault for not paying attention.   
   >>> Still ,for a newbie wanting to dual boot...a nice safe way to do things.   
   >>>   
   >>   
   >> I did a new installation of Tumbleweed yesterday. The box has   
   >>   Win11 on an NVMe. I added an old SATA SSD (which had DOS   
   >>   partitions) which I cleared by writing a GPT partition table to   
   >>   it using gparted.   
   >>   
   >> I intended to let the TW installer suggest partitions and then   
   >>   modify them. But its only suggestion was to shrink the NTFS   
   >>   partition so I had to build SDA myself by adding the partitions   
   >>   one by one. At the end it wasn't happy with my /boot/efi   
   >>   partition size so I had to do the whole thing twice.   
   >>   
   >> Maybe I should have added a partition - swap say - onto the disk   
   >>   with gparted and it would then have offered to install into the   
   >>   unallocated space.   
   >>   
   >> I wonder if - had that been a new SSD - it would have offered to   
   >>   use it?   
   >>   
   >> Anyway, the install (from DVD) was trouble-free. I've used Leap   
   >>   and its antecedents for years. I'm testing whether I can get on   
   >>   with TW.   
   >   
   > At least on Leap the partitioner has an expert option to tell it what   
   > disk to use for the proposal.   
      
   I was surprised. The install process was very familiar from Leap.   
    I would have expected the partitioner to be the same. It might   
    have been a quirk of the bios: I subsequently had to relax secure   
    boot restrictions to get it to boot from SDA.   
      
   The TW installer created  the user 'david' in group 'david'   
    instead of group 'users' as I have in Leap (thought that account   
    was created years ago so Leap may do that too).  I've left it   
    like that for now.   
      
   When installing the zoom rpm yast managed to create ~/.config/ibus   
    owned by root! Easily fixed. That's the only problem I've had so   
    far.   
      
   I might try Suse Aeon. That needs it's own volume though.   
   --   
   Remove numerics from my email address.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)