Please do not send emails to me!
Contact me Here
|
|
| |
Find local sex contacts in your area!
Find local women on FreeHookupAffair.com! There are hot and horny single women
in your area looking for sex! Adu...
|
|
|
If my boyfriend finds your messages he will f..ck us!
I told you, please do not send emails to me, my bf can read them!
If you want to meet - contact me on that site!
___
PLUG mailing list
PLUG@pdxlinux.org
http://lists.pdxlinux.org/mailman/listinfo/plug
On Sun, 20 Oct 2019, Ben Koenig wrote:
Wow. ok. Mounting a drive isn't supposed to change the device node. You
can mount/unmount drives all day long and as along as you don't add
additional devices it should stay the same. My guess is that something is
lingering around in the driver stack. If
If you have your source and target on single host:
sudo rsync .
Should definitely work, because in that situation, it does not use ssh for
transport.
Tomas
On Sun, Oct 20, 2019, 13:20 Rich Shepard wrote:
> On Sun, 20 Oct 2019, Galen Seitz wrote:
>
> > Rather than using rsync, why not this:
On Mon, 21 Oct 2019, Rich Shepard wrote:
Got this fixed!
I wrote too quickly. It's still flipping from the initial /dev/sdc1 to
/dev/sdd1 as it sat there mounted and I responded to your message.
Any thoughts on where I should now look? It must be related to the fstab
entry:
In one of the weekend posts you learned how to obtain disk and partition
uuid - is there any technical reason to not use uuid to mount your external
drive?
Uuids definitely do not change unless you change it intentionally.
I do not want to sound weary, but this topic repeats on this list
They have free sign up here: This dating site
|
|
| |
Facebook For Hookups - Free Sex Hookups at AdultDates.com
|
|
|
,
Then find me - my nick name is Jess212.
What is your nickname there?
PS: Want to kiss you :) Jess
___
PLUG mailing
On 10/21/19 6:20 AM, Rich Shepard wrote:
On Mon, 21 Oct 2019, Rich Shepard wrote:
Got this fixed!
I wrote too quickly. It's still flipping from the initial /dev/sdc1 to
/dev/sdd1 as it sat there mounted and I responded to your message.
Any thoughts on where I should now look? It must be
Portland, baby, please contact me on This Site
Don't write to this email more,
if my husband will read it he will kill me!
On Mon, Oct 21, 2019, at 5:10 PM, Portland wrote:
>On Mon, 21 Oct 2019, Tomas Kuchta wrote:
>
> In one of the weekend posts you learned how to obtain disk and
PS: My nick there is Mary412, pleasefind it
Kisses, Mary...
On Mon, Oct 21, 2019, at 5:10 PM, Portland wrote:
>On Mon, 21 Oct 2019, Tomas Kuchta wrote:
>
> In one of the weekend posts you learned how to obtain disk and partition
> uuid - is there any technical reason to not use uuid to
Hopefully it lets me change the subject to start a new conversation. You
bring up some interesting points but it's very off topic.
On 10/21/19 6:34 AM, Tomas Kuchta wrote:
In one of the weekend posts you learned how to obtain disk and partition
uuid - is there any technical reason to not use
On Mon, 21 Oct 2019, Ben Koenig wrote:
Your fstab config is fine. Nothing in the mount process should trigger
changes in the device node. At this point you need to physically disconnect
the drive and reboot the computer.
Ben,
Here's what /var/log/messages shows (this is the most recent of
Portland hello, I live near you.I found your email on a dating site. Are you
still available?
I am Mary, I'm 29, and very pretty.
You'll find my personal pics here
On Mon, Oct 21, 2019, at 5:03 PM, Portland wrote:
>On 10/21/19 6:20 AM, Rich Shepard wrote:
> On Mon, 21 Oct 2019, Rich
I regret my misunderstanding - My assumption was - if you use "partition uuid"
to mount the partition - you do not need to care about /dev/sd* because your
drive is reliably mounted to the mount point.
Naturally - using partition uuid to mount something - implies that you remove
any other
On 10/21/19 8:10 AM, Rich Shepard wrote:
On Mon, 21 Oct 2019, Tomas Kuchta wrote:
In one of the weekend posts you learned how to obtain disk and partition
uuid - is there any technical reason to not use uuid to mount your
external
drive?
No. That's why I use it.
I'm trying to say this
On 10/21/19 8:54 AM, Rich Shepard wrote:
On Mon, 21 Oct 2019, Ben Koenig wrote:
Your fstab config is fine. Nothing in the mount process should
trigger changes in the device node. At this point you need to
physically disconnect the drive and reboot the computer.
Ben,
Here's what
On Mon, 21 Oct 2019, Ben Koenig wrote:
The device node (sdc or sdd) only changes when devices are removed and
attached by the kernel. Intermittent connections caused by a failing
cable, port, or host controller can result in the some really weird stuff
happening. If I was physically present for
On Mon, 21 Oct 2019 08:45:20 -0700
Ben Koenig dijo:
>There is a sequence of steps used to troubleshoot a given issue.
>Sometimes when running through these steps, you may appear to have
>"fixed" the problem, when all you did was poke it to do what you
>wanted. A good example is one of the Ubuntu
/media is managed by the GUI. the GUI reads the volume name when it's
connected, and mounts it on /media/[username]/[volume name]. If there is
already something there, you will end up with a second filesystem mounted
on the same mount point.
It's not a problem until it is.
-wes
On Mon, Oct
The thing about /dev/sd[a-z][0-9] and older ata /dev/hd[a-z][0-9] as well
as NVMe and USB device names is that they are controller, port and/or
plug-in order dependent.
If you have bunch of drives connected to any of these interfaces at boot
time. They are enumerated by controller/port/partition
Good point with the labels John, there are other ways to skin the cat.
You can give timeout option on your mount line to avoid excessive boot
times when your drive is not attached. Something longer than it takes to
wake up your drives.
On Mon, Oct 21, 2019, 21:02 John Jason Jordan wrote:
> On
On Mon, 21 Oct 2019 16:34:48 -0700
wes dijo:
>/media is managed by the GUI. the GUI reads the volume name when it's
>connected, and mounts it on /media/[username]/[volume name]. If there
>is already something there, you will end up with a second filesystem
>mounted on the same mount point.
A
One of the problems you were having were these ephemeral mount folders in
/media. It was causing a lot of general confusion by duplicating your
mountpoints. You should really consider moving your lines in fstab from
/media to /mnt. This would clear up issues with things not working as
expected.
23 matches
Mail list logo
