On Thu, Jan 23, 2025 at 04:16:29PM +0100, Hans wrote:
Fourth: exfat (needed or big files) does not have a journal like ext3 or ext4,
so data may be going corrupt on the harddrive and could not be restored.
That's not what a journal is for, and if the copy completes and the disk
is unmounted th
Hi folks,
in the last weks there were several issues with data transfer from ext4 to
exfat. Most cases wanted to be done, to transfer seceral terrabyte of date to
a MS-Windows system.
Thinking of it, IMO this is a bad choice. Olease let me explain:
Besides to host tzerrabyte of important data
On 1/24/24 11:27 PM, Greg Wooledge wrote:
On Wed, Jan 24, 2024 at 10:43:51PM +0100, Miroslav Skoric wrote:
I do not have root account.
Sure you do. You might not have a root *password* set.
(I use sudo from my user account.) I think I
already tried rescue mode in the past but was not prompt
BTW, instead of rescue mode, you can use the initramfs to do such things
(I like to do that when I don't have a LiveUSB at hand because it lets
you manipulate *all* partitions, including /).
I.e. do something like:
- Reboot
- In Grub, edit your boot script (with `e`) to add `break=mount` t
On Wed, Jan 24, 2024 at 10:43:51PM +0100, Miroslav Skoric wrote:
> I do not have root account.
Sure you do. You might not have a root *password* set.
> (I use sudo from my user account.) I think I
> already tried rescue mode in the past but was not prompted for root
> password.
You can set a ro
Hello,
On Wed, Jan 24, 2024 at 09:20:47AM +0700, Max Nikulin wrote:
> Notice that separate /usr is not supported by latest systemd that should be
> a part of the next Debian release.
I don't think this is the case. What I think is not supported is a
separate /usr that is not mounted by initramfs.
On 1/24/24 3:20 AM, Max Nikulin wrote:
On 24/01/2024 06:29, Miroslav Skoric wrote:
# df -h
/dev/mapper/localhost-root 6.2G 4.7G 1.2G 81% /
Taking into account size of kernel packages, I would allocate a few G
more for the root partition.
dpkg -s linux-image-6.1.0-17-amd64 | grep -i
On 1/24/24 12:42 AM, Greg Wooledge wrote:
You'll have to unmount it, which generally means you will have to reboot
in single-user mode, or from rescue media, whichever is easier.
If you aren't opposed to setting a root password (some people have *weird*
self-imposed restrictions, seriously), si
Hi,
On Wed, Jan 24, 2024 at 12:29:18AM +0100, Miroslav Skoric wrote:
> Dunno ... in any case, for some reason the rescue mode I went to by booting
> from an old installation CD (dated back to Debian 6.0.1A Squeeze!) did not
> see partitions in form of e.g. /dev/mapper/localhost-home, b
On Wed, Jan 24, 2024 at 06:45:12AM +0100, to...@tuxteam.de wrote:
> On Tue, Jan 23, 2024 at 06:42:43PM -0500, Greg Wooledge wrote:
> > You'll have to unmount it, which generally means you will have to reboot
> > in single-user mode, or from rescue media, whichever is easier.
>
> If you log in as r
On Tue, Jan 23, 2024 at 06:42:43PM -0500, Greg Wooledge wrote:
> On Wed, Jan 24, 2024 at 12:29:18AM +0100, Miroslav Skoric wrote:
> > Total PE 76249
> > Alloc PE / Size 75146 / <293.54 GiB
> > Free PE / Size 1103 / <4.31 GiB
> > VG UUID fbCaw1-u3SN-2H
On 24/01/2024 06:29, Miroslav Skoric wrote:
# df -h
/dev/mapper/localhost-root 6.2G 4.7G 1.2G 81% /
Taking into account size of kernel packages, I would allocate a few G
more for the root partition.
dpkg -s linux-image-6.1.0-17-amd64 | grep -i size
Installed-Size: 398452
Notice that
On Wed, Jan 24, 2024 at 12:29:18AM +0100, Miroslav Skoric wrote:
> Total PE 76249
> Alloc PE / Size 75146 / <293.54 GiB
> Free PE / Size 1103 / <4.31 GiB
> VG UUID fbCaw1-u3SN-2HCy-w6y8-v0nK-QsFE-FETNZM
>
> ... seems that I still have some 4 GB of un
ome of the things in / out into it where possible, to free up some
more space on /.
Dunno ... in any case, for some reason the rescue mode I went to by
booting from an old installation CD (dated back to Debian 6.0.1A
Squeeze!) did not see partitions in form of e.g.
/dev/mapper/localhost-h
On 1/22/24 11:21 PM, Greg Wooledge wrote:
On Mon, Jan 22, 2024 at 10:41:57PM +0100, Miroslav Skoric wrote:
As I need to extend & resize more than one LV in the file system (/, /usr,
and /var), should they all need to be unmounted before the operation? As I
remember, it is ext3 system on that com
On 1/22/24 7:01 PM, to...@tuxteam.de wrote:
Ah, forgot to say: "pvdisplay -m" will give you a "physical" map of
your physical volume. So you get an idea what is where and where
you find gaps.
"pvdisplay -m" provided some idea that there was some free space but (if
I am not wrong) not how mu
On 1/22/24 5:02 PM, Greg Wooledge wrote:
On Mon, Jan 22, 2024 at 03:17:36PM +, Alain D D Williams wrote:
The shrinking of /home is the hard part. You MUST first unmount /home, then
resize the file system, then resize the logical volume.
Before doing any of that, one should check the volume
Hi,
On Mon, Jan 22, 2024 at 10:59:55PM +0100, Miroslav Skoric wrote:
> On 1/22/24 6:59 PM, to...@tuxteam.de wrote:
> > On Mon, Jan 22, 2024 at 03:40:06PM +, Alain D D Williams wrote:
> > > On Mon, Jan 22, 2024 at 10:29:55AM -0500, Stefan Monnier wrote:
> > > > lvreduce --size -50G --resizefs /
On Mon, Jan 22, 2024 at 10:59:55PM +0100, Miroslav Skoric wrote:
[...]
> That last resize2fs (without params) would not work here, or at least it
> would not work for my three file systems that need to be extended: / , /usr
> , and /var . Maybe to extend each of them separately like this:
>
> lv
On Mon, Jan 22, 2024 at 10:41:57PM +0100, Miroslav Skoric wrote:
> As I need to extend & resize more than one LV in the file system (/, /usr,
> and /var), should they all need to be unmounted before the operation? As I
> remember, it is ext3 system on that comp.
What?? I don't think these wor
On 1/22/24 6:59 PM, to...@tuxteam.de wrote:
On Mon, Jan 22, 2024 at 03:40:06PM +, Alain D D Williams wrote:
On Mon, Jan 22, 2024 at 10:29:55AM -0500, Stefan Monnier wrote:
lvextend --size +1G --resizefs /dev/mapper/localhost-home
Ie get lvextend to do the maths & work it out for me.
Those
On 1/22/24 4:40 PM, Alain D D Williams wrote:
On Mon, Jan 22, 2024 at 10:29:55AM -0500, Stefan Monnier wrote:
lvextend --size +1G --resizefs /dev/mapper/localhost-home
Ie get lvextend to do the maths & work it out for me.
Those who are cleverer than me might be able to tell you how to get it r
98% /var
/dev/mapper/localhost-home 257G 73G 172G 30% /home
tmpfs 297M 40K 297M 1% /run/user/1000
As my system has encrypted LVM, I suppose that I shall reduce some space
used for /home, and then use it to extend /, /usr, and /var logical
partitions. I think I did (or tr
On Mon, Jan 22, 2024 at 07:01:13PM +0100, to...@tuxteam.de wrote:
> On Mon, Jan 22, 2024 at 11:02:06AM -0500, Greg Wooledge wrote:
> > On Mon, Jan 22, 2024 at 03:17:36PM +, Alain D D Williams wrote:
> > > The shrinking of /home is the hard part. You MUST first unmount /home,
> > > then
> > > r
On Mon, Jan 22, 2024 at 01:06:16PM -0500, Gremlin wrote:
> I use to use LVM and RAID but I quit using that after finding out that
> partition the drive and using gparted was way more easier
If you allocate all the space during installation and don't leave any
to make adjustments, or to make snapsh
dev/mapper/localhost-home 257G 73G 172G 30% /home
tmpfs 297M 40K 297M 1% /run/user/1000
As my system has encrypted LVM, I suppose that I shall reduce some space
used for /home, and then use it to extend /, /usr, and /var logical
partitions. I think I did (or tr
On Mon, Jan 22, 2024 at 11:02:06AM -0500, Greg Wooledge wrote:
> On Mon, Jan 22, 2024 at 03:17:36PM +, Alain D D Williams wrote:
> > The shrinking of /home is the hard part. You MUST first unmount /home, then
> > resize the file system, then resize the logical volume.
>
> Before doing any of t
On Mon, Jan 22, 2024 at 03:40:06PM +, Alain D D Williams wrote:
> On Mon, Jan 22, 2024 at 10:29:55AM -0500, Stefan Monnier wrote:
> > > lvextend --size +1G --resizefs /dev/mapper/localhost-home
> > >
> > > Ie get lvextend to do the maths & work it out for me.
> > >
> > > Those who are cleverer
On Mon, Jan 22, 2024 at 03:17:36PM +, Alain D D Williams wrote:
> The shrinking of /home is the hard part. You MUST first unmount /home, then
> resize the file system, then resize the logical volume.
Before doing any of that, one should check the volume group and see
if there are unallocated h
On Mon, Jan 22, 2024 at 10:29:55AM -0500, Stefan Monnier wrote:
> > lvextend --size +1G --resizefs /dev/mapper/localhost-home
> >
> > Ie get lvextend to do the maths & work it out for me.
> >
> > Those who are cleverer than me might be able to tell you how to get it right
> > first time!
>
> lvred
> lvextend --size +1G --resizefs /dev/mapper/localhost-home
>
> Ie get lvextend to do the maths & work it out for me.
>
> Those who are cleverer than me might be able to tell you how to get it right
> first time!
lvreduce --size -50G --resizefs /dev/mapper/localhost-home
?
Stefan
ost-var 2.7G 2.5G 55M 98% /var
> /dev/mapper/localhost-home 257G 73G 172G 30% /home
> tmpfs 297M 40K 297M 1% /run/user/1000
>
> As my system has encrypted LVM, I suppose that I shall reduce some space
> used for /home, and then use it to extend /,
r/1000
As my system has encrypted LVM, I suppose that I shall reduce some space
used for /home, and then use it to extend /, /usr, and /var logical
partitions. I think I did (or tried to do) something similar several years
ago, but forgot the proper procedure. Any link for a good tutorial is
welcomed. Thanks.
Misko
Hi.
On Wed, Nov 15, 2023 at 10:11:16AM +, Drone Ah wrote:
> I found
> https://unix.stackexchange.com/questions/709184/fakeraid-partition-missing-not-mapped-as-a-device-on-boot-after-upgrade-to-ubu/760998#760998
>
> Using kpartx as suggested in the above post does solve the problem. Ge
Hi,
I installed debian on an SSD, but the motherboard has a softraid
controller, which I used to create a couple of RAID5 volumes - for when I
use(d) windows.
In linux, I have dmraid installed and it correctly detects the disks. I can
also (c)fdisk the disks to see the partitions. It, however
Windows-10-Jorge.xml
Description: XML document
Hi! After I upgraded to bookworm, my QEMU-KVM VM fails to boot the
guest OS; instead it drops to the EFI shell. If I boot the physical
host into bullseye's kernel (Linux 5.10) then the VM boots normally.
This VM has two virtual disks, each backed
On Thu, 2022-11-10 at 10:59 +0100, DdB wrote:
> Am 10.11.2022 um 04:46 schrieb hw:
> > On Wed, 2022-11-09 at 18:26 +0100, Christoph Brinkhaus wrote:
> > > Am Wed, Nov 09, 2022 at 06:11:34PM +0100 schrieb hw:
> > > [...]
> [...]
> > >
> > Why would part
On Thu 09 Dec 2021 at 08:28:37 (-0800), Peter Ehlert wrote:
> the full error message at the end of update-grub:
>
> Warning: os-prober will not be executed to detect other bootable partitions.
> Systems on them will not be added to the GRUB boot configuration.
> Check GRUB_DI
the full error message at the end of update-grub:
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Question: why would this desirable?
it's totall
On 10/1/21 05:40, fran...@libero.it wrote:
About the questions sent:
Thank you for the information.
Fujitsu Esprimo P2560 MI4W-D2041
https://support.ts.fujitsu.com/IndexDownload.asp?lng=en&OpenTab=
FTS_ESPRIMOP15xxP2440P2540P2550P2560P2760__1079164.PDF
FTS_MainboardD3041ShortDescription_
Hi,
for me the easiest way to clone a drive is using clonezilla-live-cd.
The only thing, one has to pay attention to, that the target is not smaller
than the source, so if you need to clone a 300GB drive, the target must be
300GB or greater.
If it is greater, and you want bigger partitions
About the questions sent:
Fujitsu Esprimo P2560 MI4W-D2041
Intel® Pentium® processor E5700 (2 Cores / 2 Threads, 3.0 GHz, 2 MB, 800 MHz)
RAM 2+4 GB.
Video card included in the motherboard
internal HD 300 GB
I think there would be added a second HD of 80 GB or maybe another of 300 GB
because
On Fri, Oct 01, 2021 at 07:40:42AM +0200, fran...@libero.it wrote:
> Taking a cue from the Thread "About user and password on Debian 10" I would
> like to transfer the partitions related to Debian 10 to a larger HD, but with
> the possibility of having the / partition larger t
On 9/30/21 22:40, fran...@libero.it wrote:
Taking a cue from the Thread "About user and password on Debian 10" I would
like to transfer the partitions related to Debian 10 to a larger HD, but with the
possibility of having the / partition larger than the current one. It's p
Taking a cue from the Thread "About user and password on Debian 10" I would
like to transfer the partitions related to Debian 10 to a larger HD, but with
the possibility of having the / partition larger than the current one. It's
possible?
I was thinking of using Filezilla, but
On Jo, 26 nov 20, 01:29:13, Kanito 73 wrote:
> to...@tuxteam.de Wrote:
>
> > This is a pattern which I like to call "emergent evil". Most likely
> > nobody does it on purpose, yet it happens often enough to annoy
> > competing ecosystems. Magic!
>
> HAHAHAHAHA (with capital letters)... As far as
On Mi, 25 nov 20, 21:56:06, Charlie Gibbs wrote:
>
> In situations like this, I think not of Occam's, but of Hanlon's Razor:
>
> Never attribute to malice that which can
> be adequately explained by stupidity.
+1
> At this point, though, a little voice in the back of my mind says,
> "Bu
On Thu, Nov 26, 2020 at 09:06:49AM +, Joe wrote:
> On Thu, 26 Nov 2020 01:29:13 +
> Kanito 73 wrote:
>
> >
> > I hate Windoze as an operating system but some programs and games are
> > cool... [...]
> > environments (when computers had simple text terminals) and further
> > graphical op
On Thu, 26 Nov 2020 01:29:13 +
Kanito 73 wrote:
>
> I hate Windoze as an operating system but some programs and games are
> cool... And there is a fact: THE ONE WHO HITS FIRST, HITS TWICE
> (translated from spanish). Bill Gates was pioneer of the graphical
> environments (when computers had
On Wed, Nov 25, 2020 at 09:56:06PM -0800, Charlie Gibbs wrote:
> On Wed, 25 Nov 2020 22:30:02 +0100 Joe wrote:
[...]
> >> This is a pattern which I like to call "emergent evil". Most likely
> >> nobody does it on purpose, yet it happens often enough to annoy
> >> competing ecosystems. Magic!
> >
On Wed, 25 Nov 2020 22:30:02 +0100 Joe wrote:
> On Wed, 25 Nov 2020 22:11:47 +0100 wrote:
>
>> On Wed, Nov 25, 2020 at 03:47:12PM -0500, Stefan Monnier wrote:
>>
Microsoft changes the system required to kill the fast-boot every
so often, almost surely to make it difficult for users of
> Microsoft has a bad habit of changing things under the hood without
> bumping the version number. They could very well have changed NTFS
> enough to bollix Linux NTFS libraries and not bothered to tell anyone.
Except that `ntfs-3g` can read and write NTFS and hasn't seen the need
for updates to
o annoy Linux users since long time ago... Installing Windoze disables
Linux to boot... NTFS was cryptic for years with no tech specifications of the
filesystem, a mystery so for many years Linux developers were unable to create
a driver to access such partitions, in fact I remember that in th
On Wed, 25 Nov 2020 21:22:30 +
Joe wrote:
> NTFS has been NTFS since the 90s, while Linux has had ext2, ext3,
> ext4, Reiser among other filesystems. Is it not likely that 'NTFS'
> has really been a similar parade of different filesystems with each
> version of Windows retaining the code to r
On Wed, 25 Nov 2020 22:11:47 +0100
wrote:
> On Wed, Nov 25, 2020 at 03:47:12PM -0500, Stefan Monnier wrote:
> > > Microsoft changes the system required to kill the fast-boot every
> > > so often, almost surely to make it difficult for users of Linux
> > > to access Windows from the Linux system.
On Wed, Nov 25, 2020 at 03:47:12PM -0500, Stefan Monnier wrote:
> > Microsoft changes the system required to kill the fast-boot every so often,
> > almost surely to make it difficult for users of Linux to access Windows from
> > the Linux system.
>
> That seems highly unlikely: it's a tiny number
> Microsoft changes the system required to kill the fast-boot every so often,
> almost surely to make it difficult for users of Linux to access Windows from
> the Linux system.
That seems highly unlikely: it's a tiny number of users, and not only
they're not a threat but annoying them won't bring
disk (HDD) and the
whole secondary disk (SDD) also as a unique NTFS partition.
Well, I installed Windows, then Installed Linux and tested the NTFS
partitions from Linux (Debian) mounting and copying some files
successfully.
[...]
So I think that Windows 10 locks the partitions or something weird
t a
>> large NTFS partition for data on the primary disk (HDD) and the
>> whole secondary disk (SDD) also as a unique NTFS partition.
>> Well, I installed Windows, then Installed Linux and tested the NTFS
>> partitions from Linux (Debian) mounting and copying some
vailable when I need them).
Thanks all of you (and the other people who helped me along the installation
and configuration) for your help and comments. My Windows 10 / Debian 10 box
is up and running. Once everything was working and tuned up I made a
Clonezilla backup of all partitions, so
mmonly used but they are
available when I need them).
Thanks all of you (and the other people who helped me along the installation
and configuration) for your help and comments. My Windows 10 / Debian 10 box is
up and running. Once everything was working and tuned up I made a Clonezilla
back
partition.
Which parts went onto the SSD and which onto the HDD in the end?
Which of the two systems do you intend to use more often?
Which of the two systems will run computation-intensive (CPU, RAM, GPU)
applications?
Well, I installed Windows, then Installed Linux and tested the NTFS
partitions
P.S. Debian is working 100% perfectly, it is up and running, the
unique problem is the access to the NTFS partitions
You are running into Windows "hibernation" that leaves the disks in an
"unclean" state when shut down in that manner (sadly, a
default..."fastboot&
d the whole secondary
> disk (SDD) also as a unique NTFS partition.
>
> Well, I installed Windows, then Installed Linux and tested the NTFS
> partitions from Linux (Debian) mounting and copying some files
> successfully. After rebooting with Windows those partitions were not
> ac
isk (HDD) and the whole secondary
> disk (SDD) also as a unique NTFS partition.
>
> Well, I installed Windows, then Installed Linux and tested the NTFS
> partitions from Linux (Debian) mounting and copying some files
> successfully. After rebooting with Windows those partitions were
NTFS partition.
Well, I installed Windows, then Installed Linux and tested the NTFS partitions from Linux (Debian) mounting and copying
some files successfully. After rebooting with Windows those partitions were not accessible from Linux anymore. If they
are mounted at boot time via /etc/fstab it
, then Installed Linux and tested the NTFS partitions
from Linux (Debian) mounting and copying some files successfully. After
rebooting with Windows those partitions were not accessible from Linux anymore.
If they are mounted at boot time via /etc/fstab it silently mounts them as "ro"
On Sun 27 Sep 2020 at 16:47:43 (-0500), Charles Zeitler wrote:
> so, is displaying partitions of all drives normal behavior for
> parted --list /dev/sdb ?
>
> On Sat, Sep 26, 2020 at 12:02 AM Charles Zeitler wrote:
> > i'm working on a thumb drive to use it as install m
hanks, all.
On Sat, Sep 26, 2020 at 12:02 AM Charles Zeitler wrote:
>
> i'm working on a thumb drive to use it as install media.
> su -c 'parted --list /dev/sdb' (/dev/sdb is thumb drive}
> lists partitions from /dev/sda 9system drive)
> even when /dev/sdb doesn&
On 2020-09-27 at 17:47, Charles Zeitler wrote:
> so, is displaying partitions of all drives normal behavior for
> parted --list /dev/sdb ?
It's normal behavior for 'parted --list'.
The '--list' option to parted doesn't take an argument. The '/dev/sdb&#
so, is displaying partitions of all drives normal behavior for
parted --list /dev/sdb ?
On Sat, Sep 26, 2020 at 12:02 AM Charles Zeitler wrote:
>
> i'm working on a thumb drive to use it as install media.
> su -c 'parted --list /dev/sdb' (/dev/sdb is thumb drive}
> lis
On Sb, 26 sep 20, 00:02:57, Charles Zeitler wrote:
> i'm working on a thumb drive to use it as install media.
> su -c 'parted --list /dev/sdb' (/dev/sdb is thumb drive}
How did you determine that /dev/sdb is the thumb drive?
> lists partitions from /dev/sda 9system dri
i'm working on a thumb drive to use it as install media.
su -c 'parted --list /dev/sdb' (/dev/sdb is thumb drive}
lists partitions from /dev/sda 9system drive)
even when /dev/sdb doesn't exist!
fdisk -l /dev/sdb properly reports it as missing,
and gparted seems to be unconf
On 1/5/20, to...@tuxteam.de wrote:
> On Sun, Jan 05, 2020 at 10:47:52AM +0100, Pascal Hambourg wrote:
>> Le 04/01/2020 à 20:47, Sven Joachim a écrit :
>
> [FAT, hard links]
>
>> >a feature that is crucial for dpkg.
>>
>> I vaguely remember this, but not when and why dpkg needs to create
>> additio
Le 05/01/2020 à 11:00, to...@tuxteam.de a écrit :
On Sun, Jan 05, 2020 at 10:47:52AM +0100, Pascal Hambourg wrote:
Le 04/01/2020 à 20:47, Sven Joachim a écrit :
[FAT, hard links]
a feature that is crucial for dpkg.
I vaguely remember this, but not when and why dpkg needs to create
addition
On Sun, Jan 05, 2020 at 10:47:52AM +0100, Pascal Hambourg wrote:
> Le 04/01/2020 à 20:47, Sven Joachim a écrit :
[FAT, hard links]
> >a feature that is crucial for dpkg.
>
> I vaguely remember this, but not when and why dpkg needs to create
> additional hard links. Can you refresh my memories ?
org/wiki/Specifications/BootLoaderSpec/>
now <https://systemd.io/BOOT_LOADER_SPECIFICATION/>
Also mentionned in the Discoverable Partitions Specification.
<https://www.freedesktop.org/wiki/Specifications/DiscoverablePartitionsSpec/>
<https://www.freedesktop.org/software/sy
On 2020-01-04 13:38 +0100, Pascal Hambourg wrote:
> Le 04/01/2020 à 11:25, Bonno Bloksma a écrit :
>
>> If I had not created that /boot partition would those files be in
>> /boot folder on the / (root) partition or would /boot then be on the
>> EFI partition?
>
> On the root partition. Some new bo
Bonno Bloksma writes:
> Hi,
>
>
>
> I have been creating a small (300MB) primary /boot partition at the
> beginning of the disk for as long as I can remember... That is after
> disks got to be too big for the BIOS to reach all of the disk to be
> able to boot from a file anywhere on the disk.
>
>
Le 04/01/2020 à 11:25, Bonno Bloksma a écrit :
I have been creating a small (300MB) primary /boot partition at the beginning
of the disk for as long as I can remember... That is after disks got to be too
big for the BIOS to reach all of the disk to be able to boot from a file
anywhere on the
Hi,
I have been creating a small (300MB) primary /boot partition at the beginning
of the disk for as long as I can remember... That is after disks got to be too
big for the BIOS to reach all of the disk to be able to boot from a file
anywhere on the disk.
So far so good, that still works but
McGarrett wrote:
> > I bought a new computer last summer, and it came with Windows 10 on
> > FOUR partitions! I shrank the Windows partition 4 to 100 GiB to
> > allow a minimum Windows system for anything that won't run on
> > OpenSUSE TW, and made
On Sun, Dec 29, 2019 at 10:30 AM Joe wrote:
> On Sun, 29 Dec 2019 07:55:22 -0500
> rhkra...@gmail.com wrote:
>
> > On Saturday, December 28, 2019 03:46:53 PM Doug McGarrett wrote:
> > > I bought a new computer last summer, and it came with Windows 10 on
> > &
On Sun, 29 Dec 2019 07:55:22 -0500
rhkra...@gmail.com wrote:
> On Saturday, December 28, 2019 03:46:53 PM Doug McGarrett wrote:
> > I bought a new computer last summer, and it came with Windows 10 on
> > FOUR partitions! I shrank the Windows partition 4 to 100 GiB to
> > al
?
Probably:
HP
Dell
Toshiba
Lenovo
and others
> What is on /dev/sda3 and /dev/sda4?
ESP MSR WinOS Recovery
<https://en.wikipedia.org/wiki/Microsoft_Reserved_Partition>
<https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/images/dep-win10-partitions-u
On Saturday, December 28, 2019 03:46:53 PM Doug McGarrett wrote:
> I bought a new computer last summer, and it came with Windows 10 on FOUR
> partitions! I shrank the Windows partition 4 to 100 GiB to allow a
> minimum Windows system for anything that won't run on OpenSUSE TW, an
On Lu, 20 mai 19, 09:31:05, Greg Wooledge wrote:
> On Sun, May 19, 2019 at 02:20:19PM +0300, Andrei POPESCU wrote:
> > for $dir in /media/removable/*
> > do
> > mount /dev/disk/by-label/$dir /media/removable/$dir
> > done
>
> for dir in /media/removable/*
> do
> mount /dev/
On Sun, May 19, 2019 at 02:20:19PM +0300, Andrei POPESCU wrote:
> for $dir in /media/removable/*
> do
> mount /dev/disk/by-label/$dir /media/removable/$dir
> done
for dir in /media/removable/*
do
mount /dev/disk/by-label/"$dir" /media/removable/"$dir"
done
Note the lack of
t; > > Assuming there are entries in fstab for each partition, [...]
> > > > > > for i in /dev/sd*; do mount $i; done
> > > >
> > > > Rchard Owlett wrote:
> > > > > There are not.
> > > >
> > > > In the most
On Thu, Apr 11, 2019 at 14:34 Felix Miata wrote:
> Tom Browder composed on 2019-04-11 08:42 (UTC-0500):
>
...
> > Does GPT partitioning on Windows 10 allow a user-friendly label along
> with
> > its UUID for a partition?
>
> > If so, is that label visible with Debian system administration progra
Tom Browder composed on 2019-04-11 08:42 (UTC-0500):
> I run dual boot Deb/Win 10 on several systems, only one of which has UEFI
> capability (the latest, new as of last fall). Unfortunately, I failed to
> use the GPT on the new one, and the Win 10 disk management program doesn't
> show much info
On Thu, Apr 11, 2019 at 12:44 PM Pascal Hambourg wrote:
>
> Le 11/04/2019 à 15:42, Tom Browder a écrit :
> >
> > Does GPT partitioning on Windows 10 allow a user-friendly label along with
> > its UUID for a partition?
>
> Why do you care ? You can manage it in Debian.
I care because my main Win b
Le 11/04/2019 à 15:42, Tom Browder a écrit :
Does GPT partitioning on Windows 10 allow a user-friendly label along with
its UUID for a partition?
Why do you care ? You can manage it in Debian.
I run dual boot Deb/Win 10 on several systems, only one of which has UEFI
capability (the latest, new as of last fall). Unfortunately, I failed to
use the GPT on the new one, and the Win 10 disk management program doesn't
show much info on the non-NTFS disks.
Does GPT partitioning on Windows 10 al
r i in /dev/sd*; do mount $i; done
> > > > > >
> > > > > > Rchard Owlett wrote:
> > > > > > > There are not.
> > > > > >
> > > > > > In the most general case i would have a where-to-mount directory
>
:
Assuming there are entries in fstab for each partition, [...]
for i in /dev/sd*; do mount $i; done
Rchard Owlett wrote:
There are not.
In the most general case i would have a where-to-mount directory with
lots of directories for the various partitions (here 10 drives with
20 partitions each).
But
; > > > > Assuming there are entries in fstab for each partition, [...]
> > > > > > for i in /dev/sd*; do mount $i; done
> > > >
> > > > Rchard Owlett wrote:
> > > > > There are not.
> > > >
> > > > I
Owlett wrote:
There are not.
In the most general case i would have a where-to-mount directory with
lots of directories for the various partitions (here 10 drives with
20 partitions each).
But thankfully I don't have to deal with the most general case as I am
as compulsive about givin
mount $i; done
> >
> > Rchard Owlett wrote:
> > > There are not.
> >
> > In the most general case i would have a where-to-mount directory with
> > lots of directories for the various partitions (here 10 drives with
> > 20 partitions each).
>
&
done
> >
> > Rchard Owlett wrote:
> > > There are not.
> >
> > In the most general case i would have a where-to-mount directory with
> > lots of directories for the various partitions (here 10 drives with
> > 20 partitions each).
>
> But thankfully I do
1 - 100 of 1496 matches
Mail list logo
