On 10/31/23 14:23, Nic wrote:
> On 10/31/23 7:51 AM, Edmund wrote:
>> On 10/31/23 11:50, Nic wrote:
>>> On 10/30/23 10:45 AM, Edmund wrote:
>>>> On 10/29/23 23:31, Paul wrote:
>>>>> On 10/29/2023 12:29 PM, Handsome Jack wrote:
>>>>>> Paul <nospam@needed.invalid> wrote:
>>>>>>> On 10/29/2023 7:08 AM, Paul wrote:
>>>>>>>> On 10/29/2023 4:00 AM, Handsome Jack wrote:
>>>>>>>>> /dev/sdd         1955584 373120   1582464  20% /mnt/USB DISK
>>>>>>>>
>>>>>>>
>>>>>>> sudo nano /etc/fstab             # Don't forget to check that
>>>>>>> hard mount in the FSTAB!
>>>>>>>                                   # /mnt is not automounter
>>>>>>>                                   # /media/mint is likely to be
>>>>>>> automounter
>>>>>>>                                   # Try to find the USB DISK
>>>>>>> entry that corresponds to the /mnt thing.
>>>>>>>                                   # Comment it out with a "#" ,
>>>>>>> like the other comments use.
>>>>>>>                                   # Save your changes
>>>>>>>
>>>>>>> cat /etc/fstab                   # Quick review you really
>>>>>>> updated it.
>>>>>>>
>>>>>>> If you need more help, copy the appropriate parts of your fstab
>>>>>>> into a posting.
>>>>>>>
>>>>>>
>>>>>> I've now used the Mint formatting utility to wipe the USB drive.
>>>>>> It seems to have restored r/w ownership to me so the problem is
>>>>>> sort of solved.
>>>>>>
>>>>>
>>>>> The OS really should not be manually mounting your goods, as you
>>>>> showed
>>>>> in your results. The installer may have done it, which is why I
>>>>> recommended
>>>>> reading the /etc/fstab control file, for the details.
>>>>>
>>>>> You don't want the OS fucking with your stuff. You want your
>>>>> defacto config, to be the same as my defacto config. Then,
>>>>> when you ask a question, we're on the same page. Anything which
>>>>> has run amok on your install, the simple stuff, should be fixed
>>>>> so there are no future surprises.
>>>>>
>>>>> The automounter would normally do the mounting, with no involvement
>>>>> of the /etc/fstab control file. The automounter creates the mount
>>>>> point
>>>>> automatically, then puts the mount on top of that. Later, when the OS
>>>>> shuts down, the partition is dismounted and the mount points would be
>>>>> cleared.
>>>>>
>>>>> Manual mounts in /etc/fstab, can be entered with a text editor
>>>>> by the user, and would normally be used for captive hard drives
>>>>> inside a device.
>>>>>
>>>>> Manual mounts, also allow your /home to be stored on a separate
>>>>> partition from the rest of the OS. This allows moving your /home
>>>>> at a later date. Some of the participants in this group, handle
>>>>> various parts of their OS as separate partitions. I don't bother
>>>>> with that, as I'm a rather casual user.
>>>>>
>>>>> If you look at the custom install options for the OS, they
>>>>> support defining your /home, as a partition which mounts on
>>>>> top of / which is the root directory of the assembled file system.
>>>>>
>>>>> As part of the learning experience, you should learn what the
>>>>> moving parts under slash (the system root / ) are about.
>>>>> If your OS breaks, and you need to rescue it, that's the
>>>>> time some of this knowledge is useful. Mounts can not only
>>>>> go on /mnt, they can go just about anywhere. And it is a useful
>>>>> skill to "notice" a thing you used to have access to, is now
>>>>> owned by root. That may not be an accident! It may mean
>>>>> a mount point in a complex mount structure, has just "broken loose".
>>>>>
>>>>> /etc/fstab   <=== how the administrator controls manual mounts
>>>>>
>>>>> //etc/mtab   <=== a record, of the current set of mounts
>>>>>
>>>>> cat /etc/mtab  <=== use this command, to see what the OS has been
>>>>> up to.
>>>>>                      You might be shocked at the mess in Ubuntu,
>>>>> for example.
>>>>>
>>>>> There are also standards involved, so the structure is
>>>>> standardized with usage in Unix and Linux. There are occasional
>>>>> things which don't always follow the rules. Sometimes the packages
>>>>> you install, are in /opt. But not everything does that. Only
>>>>> some of the packages do. And /opt might be more "popular"
>>>>> on some other platform, and you're only getting things packaged
>>>>> that way for fun.
>>>>>
>>>>> On occasion, you may install a package, and then when you typed
>>>>> the command you expected to be present, it's not there! That's
>>>>> because maybe /opt is not in your $PATH. You may need to add a path
>>>>> component, into your $PATH, so the executable can be found. Maybe
>>>>> the needed path component is /opt/something/bin for example.
>>>>>
>>>>> Always expect the unexpected. If you can fix something in five
>>>>> minutes yourself, it saves wasting two days waiting for us to
>>>>> guess what broke :-)
>>>>
>>>> Yes, same for TRYING the file a bug.
>>>> For starters, it is impossible to do so.
>>>> and IF you manage to do it anyway, nobody cares.
>>>>>
>>>>>     Paul
>>>>
>>> I agree Linux Mint has its share of problems with usb at the top, but
>>> I will continue to use it instead of the m$ alternatives. It is a
>>> great system that can compete with the m$$$$$$$ way. I like to think
>>> that as computers evolve and as new knowledge is acquired eventually
>>> most of these problems will go away.
>>
>> I gave up that idea, the utter insanity and chaos in the linux society
>> make sure things will never be solved.
>>
>>
> Perhaps it is human nature or human nature dumbed down with modern day
> foods, but when it comes to innovation you never know when a new
> Beethoven will be born to the computer scene. The insanity you speak of
> is manifesting not only in the Linux society but in society in general
> as we approach greater wars and destruction's.

Well I am not disagreeing with you here but before we get philosophical,
the linux society is so extreme chaotic and unfriendly, I am not joking
when I say it is impossible to file a bug.
Even if one looks for help how it should be possible, all you find are
fragments and no way it tells you how to actually file a bug.
IF!!! one waste lots and lots of time and figure out how a bug could be
filed, what hurdles must be taken, insanity is a way too weak word for it.
I suppose there must be have been one or two persons who took all that
trouble in the past decades to file a bug about the USB.
Of course nobody cares, the bugs are here to stay.

--
-------------

The moment any organization established from pure noble intentions get
some influence, it will be corrupted from both inside and outside.
Then we have organizations established from pure evil.

Edmund

On 10/31/23 12:09 PM, Edmund wrote:
> On 10/31/23 14:23, Nic wrote:
>> On 10/31/23 7:51 AM, Edmund wrote:
>>> On 10/31/23 11:50, Nic wrote:
>>>> On 10/30/23 10:45 AM, Edmund wrote:
>>>>> On 10/29/23 23:31, Paul wrote:
>>>>>> On 10/29/2023 12:29 PM, Handsome Jack wrote:
>>>>>>> Paul <nospam@needed.invalid> wrote:
>>>>>>>> On 10/29/2023 7:08 AM, Paul wrote:
>>>>>>>>> On 10/29/2023 4:00 AM, Handsome Jack wrote:
>>>>>>>>>> /dev/sdd         1955584 373120   1582464  20% /mnt/USB DISK
>>>>>>>>>
>>>>>>>>
>>>>>>>> sudo nano /etc/fstab             # Don't forget to check that
>>>>>>>> hard mount in the FSTAB!
>>>>>>>>                                   # /mnt is not automounter
>>>>>>>>                                   # /media/mint is likely to be
>>>>>>>> automounter
>>>>>>>>                                   # Try to find the USB DISK
>>>>>>>> entry that corresponds to the /mnt thing.
>>>>>>>>                                   # Comment it out with a "#" ,
>>>>>>>> like the other comments use.
>>>>>>>>                                   # Save your changes
>>>>>>>>
>>>>>>>> cat /etc/fstab                   # Quick review you really
>>>>>>>> updated it.
>>>>>>>>
>>>>>>>> If you need more help, copy the appropriate parts of your fstab
>>>>>>>> into a posting.
>>>>>>>>
>>>>>>>
>>>>>>> I've now used the Mint formatting utility to wipe the USB drive.
>>>>>>> It seems to have restored r/w ownership to me so the problem is
>>>>>>> sort of solved.
>>>>>>>
>>>>>>
>>>>>> The OS really should not be manually mounting your goods, as you
>>>>>> showed
>>>>>> in your results. The installer may have done it, which is why I
>>>>>> recommended
>>>>>> reading the /etc/fstab control file, for the details.
>>>>>>
>>>>>> You don't want the OS fucking with your stuff. You want your
>>>>>> defacto config, to be the same as my defacto config. Then,
>>>>>> when you ask a question, we're on the same page. Anything which
>>>>>> has run amok on your install, the simple stuff, should be fixed
>>>>>> so there are no future surprises.
>>>>>>
>>>>>> The automounter would normally do the mounting, with no involvement
>>>>>> of the /etc/fstab control file. The automounter creates the mount
>>>>>> point
>>>>>> automatically, then puts the mount on top of that. Later, when
>>>>>> the OS
>>>>>> shuts down, the partition is dismounted and the mount points
>>>>>> would be
>>>>>> cleared.
>>>>>>
>>>>>> Manual mounts in /etc/fstab, can be entered with a text editor
>>>>>> by the user, and would normally be used for captive hard drives
>>>>>> inside a device.
>>>>>>
>>>>>> Manual mounts, also allow your /home to be stored on a separate
>>>>>> partition from the rest of the OS. This allows moving your /home
>>>>>> at a later date. Some of the participants in this group, handle
>>>>>> various parts of their OS as separate partitions. I don't bother
>>>>>> with that, as I'm a rather casual user.
>>>>>>
>>>>>> If you look at the custom install options for the OS, they
>>>>>> support defining your /home, as a partition which mounts on
>>>>>> top of / which is the root directory of the assembled file system.
>>>>>>
>>>>>> As part of the learning experience, you should learn what the
>>>>>> moving parts under slash (the system root / ) are about.
>>>>>> If your OS breaks, and you need to rescue it, that's the
>>>>>> time some of this knowledge is useful. Mounts can not only
>>>>>> go on /mnt, they can go just about anywhere. And it is a useful
>>>>>> skill to "notice" a thing you used to have access to, is now
>>>>>> owned by root. That may not be an accident! It may mean
>>>>>> a mount point in a complex mount structure, has just "broken loose".
>>>>>>
>>>>>> /etc/fstab   <=== how the administrator controls manual mounts
>>>>>>
>>>>>> //etc/mtab   <=== a record, of the current set of mounts
>>>>>>
>>>>>> cat /etc/mtab  <=== use this command, to see what the OS has been
>>>>>> up to.
>>>>>>                      You might be shocked at the mess in Ubuntu,
>>>>>> for example.
>>>>>>
>>>>>> There are also standards involved, so the structure is
>>>>>> standardized with usage in Unix and Linux. There are occasional
>>>>>> things which don't always follow the rules. Sometimes the packages
>>>>>> you install, are in /opt. But not everything does that. Only
>>>>>> some of the packages do. And /opt might be more "popular"
>>>>>> on some other platform, and you're only getting things packaged
>>>>>> that way for fun.
>>>>>>
>>>>>> On occasion, you may install a package, and then when you typed
>>>>>> the command you expected to be present, it's not there! That's
>>>>>> because maybe /opt is not in your $PATH. You may need to add a path
>>>>>> component, into your $PATH, so the executable can be found. Maybe
>>>>>> the needed path component is /opt/something/bin for example.
>>>>>>
>>>>>> Always expect the unexpected. If you can fix something in five
>>>>>> minutes yourself, it saves wasting two days waiting for us to
>>>>>> guess what broke :-)
>>>>>
>>>>> Yes, same for TRYING the file a bug.
>>>>> For starters, it is impossible to do so.
>>>>> and IF you manage to do it anyway, nobody cares.
>>>>>>
>>>>>>     Paul
>>>>>
>>>> I agree Linux Mint has its share of problems with usb at the top,
>>>> but I will continue to use it instead of the m$ alternatives. It is
>>>> a great system that can compete with the m$$$$$$$ way. I like to
>>>> think that as computers evolve and as new knowledge is acquired
>>>> eventually most of these problems will go away.
>>>
>>> I gave up that idea, the utter insanity and chaos in the linux society
>>> make sure things will never be solved.
>>>
>>>
>> Perhaps it is human nature or human nature dumbed down with modern
>> day foods, but when it comes to innovation you never know when a new
>> Beethoven will be born to the computer scene. The insanity you speak
>> of is manifesting not only in the Linux society but in society in
>> general as we approach greater wars and destruction's.
>
> Well I am not disagreeing with you here but before we get philosophical,
> the linux society is so extreme chaotic and unfriendly, I am not
> joking when  I say it is impossible to file a bug.
> Even if one looks for help how it should be possible, all you find are
> fragments and no way it tells you how to actually file a bug.
> IF!!! one waste lots and lots of time and figure out how a bug could
> be filed, what hurdles must be taken, insanity is a way too weak word
> for it.
> I suppose there must be have been one or two persons who took all that
> trouble in the past decades to file a bug about the USB.
> Of course nobody cares, the bugs are here to stay.
>
>
Perhaps what you are calling insanity is actually an elitist's point of
view, consider that a person, that is capable of doing the type of
coding is actually capable to code but must give up/relinquish certain
social skills, those social skills that most people take for granted.