From Newsgroup: alt.os.linux.suse

I had a Win7 laptop sitting around for several years.

Dual core 1.6 ghz with 2 gigs of RAM.

Put in an SSD and loaded a full Gnome installation of SUSE.
It went smoothly and the darn thing runs great .

It will now be quite usable.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.suse

On 16/07/2024 00:17, philo wrote:

Put in an SSD and loaded a full Gnome installation of SUSE.
It went smoothly and the darn thing runs great .

It will now be quite usable.

Well, it will be once you replace GNOME with KDE Plasma ;-)
--
Rob
"I have never understood why it should be necessary to become irrational
in order to prove that you care, or, indeed, why it should be necessary
to prove it at all." - Avon, Blake's 7

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.suse

All working well.
When I did the installation I just used a default option.
Decided to examine the partitioning today and noticed the boot partition
is NTFS .
What's the reason for that ?

Also...there is very little in in. Why did the installer create a 40 gig partition by default?
That seems excessive.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.suse

On 2024-08-18 18:10, philo wrote:

All working well.
When I did the installation I just used a default option.
Decided to examine the partitioning today and noticed the boot partition
is NTFS .
What's the reason for that ?

It must be an old partition. It is not the Linux boot partition.

Also...there is very little in in. Why did the installer create a 40 gig partition by default?
That seems excessive.

--
Cheers, Carlos.

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.suse

Gparted listed it as a boot partition but it must have been from some
previous Windows installation.

Thanks
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.suse

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.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.suse

On 2024-08-23 21:00, philo wrote:

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.

There is a lot of customization possible in the installer, but you have
to know it.
--
Cheers, Carlos.

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.suse

Very easy to use.
As mentioned I was not paying attention.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.suse

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.
--
Remove numerics from my email address.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.suse

On 8/24/24 01: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.

That's why I'm using small drives to create "test" installs.

If you only had to do it twice...that's not all that bad

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.suse

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.
--
Cheers, Carlos.

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.suse

"Carlos E.R." <robin_listas@es.invalid> 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.
--- Synchronet 3.21d-Linux NewsLink 1.2