Re: [opensuse] copying .exe to Win 10?
On 15/09/2019 23.43, Doug McGarrett wrote:
On 09/15/2019 05:11 PM, Carlos E. R. wrote:
On 15/09/2019 23.05, Doug McGarrett wrote:
2. From a root terminal, mount -v /dev/sda4 comes back with message "Not found in fstab", which is true, and mount -v all produces the same thing. I looked at the fstab file and it's complicated! Now what?
I did not say "mount -v /dev/sda4". I said "mount -v". Please pay attention.
You said mount -v and "paste here a line for the windows partition or all if I don't know what it is." I know it's /dev/sda4. I just entered (this time) mount -v and I got a many-line output. Then linux-4qnb:~ # /dev/sda4 -bash: /dev/sda4: Permission denied The all command gets rejected altogether.
Please, just do exactly what I asked. Type into a terminal just this exact line: mount -v and paste all of it here here. Nothing more, nothing less. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 09/15/2019 06:09 PM, Carlos E. R. wrote:
On 15/09/2019 23.43, Doug McGarrett wrote:
On 09/15/2019 05:11 PM, Carlos E. R. wrote:
On 15/09/2019 23.05, Doug McGarrett wrote:
2. From a root terminal, mount -v /dev/sda4 comes back with message "Not found in fstab", which is true, and mount -v all produces the same thing. I looked at the fstab file and it's complicated! Now what?
I did not say "mount -v /dev/sda4". I said "mount -v". Please pay attention.
You said mount -v and "paste here a line for the windows partition or all if I don't know what it is." I know it's /dev/sda4. I just entered (this time) mount -v and I got a many-line output. Then linux-4qnb:~ # /dev/sda4 -bash: /dev/sda4: Permission denied The all command gets rejected altogether.
Please, just do exactly what I asked. Type into a terminal just this exact line:
mount -v
and paste all of it here here. Nothing more, nothing less.
linux-4qnb:~ # mount -v sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) devtmpfs on /dev type devtmpfs (rw,nosuid,size=8128596k,nr_inodes=2032149,mode=755) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) /dev/sda9 on / type btrfs (rw,relatime,ssd,space_cache,subvolid=268,subvol=/@/.snapshots/1/snapshot) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=14782) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) /dev/sda9 on /var type btrfs (rw,relatime,ssd,space_cache,subvolid=258,subvol=/@/var) /dev/sda9 on /srv type btrfs (rw,relatime,ssd,space_cache,subvolid=261,subvol=/@/srv) /dev/sda9 on /opt type btrfs (rw,relatime,ssd,space_cache,subvolid=263,subvol=/@/opt) /dev/sda9 on /boot/grub2/i386-pc type btrfs (rw,relatime,ssd,space_cache,subvolid=266,subvol=/@/boot/grub2/i386-pc) /dev/sda9 on /.snapshots type btrfs (rw,relatime,ssd,space_cache,subvolid=267,subvol=/@/.snapshots) /dev/sda9 on /home type btrfs (rw,relatime,ssd,space_cache,subvolid=264,subvol=/@/home) /dev/sda9 on /usr/local type btrfs (rw,relatime,ssd,space_cache,subvolid=259,subvol=/@/usr/local) /dev/sda9 on /boot/grub2/x86_64-efi type btrfs (rw,relatime,ssd,space_cache,subvolid=265,subvol=/@/boot/grub2/x86_64-efi) /dev/sda9 on /tmp type btrfs (rw,relatime,ssd,space_cache,subvolid=260,subvol=/@/tmp) /dev/sda9 on /root type btrfs (rw,relatime,ssd,space_cache,subvolid=262,subvol=/@/root) /dev/sda7 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1627740k,mode=700,uid=1000,gid=100) fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100) /dev/sda4 on /run/media/root/B66C5BE86C5BA1C3 type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2) /dev/sdb1 on /run/media/root/USB20FD type vfat (rw,nosuid,nodev,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) tracefs on /sys/kernel/debug/tracing type tracefs (rw,nosuid,nodev,noexec,relatime) linux-4qnb:~ # -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16/09/2019 20.57, Doug McGarrett wrote:
On 09/15/2019 06:09 PM, Carlos E. R. wrote:
On 15/09/2019 23.43, Doug McGarrett wrote:
...
Please, just do exactly what I asked. Type into a terminal just this exact line:
mount -v
and paste all of it here here. Nothing more, nothing less.
linux-4qnb:~ # mount -v sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
...
/dev/sda7 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) ... fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) ... /dev/sda4 on /run/media/root/B66C5BE86C5BA1C3 type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2) /dev/sdb1 on /run/media/root/USB20FD type vfat (rw,nosuid,nodev,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) ... linux-4qnb:~ #
Thank you! Well, as you see, sda4 id mounted ro, which means, read only, so it is impossible you can write anything to it. You can compare to sdb1 which is mounted rw. Now, there is another problem. They are mounted by *root*, and this is not good. It means you are running the desktop as *root*. This is anathema! You must never do that. Run the desktop as plain user. Now, as to the reason why it is mounted ro, it usually means that it is not clean, and probably the advice you got about what to do in Windows are correct. We can make certain, though. Do: # umount -v /dev/sda # mkdir /run/media/root/BBB # mount -v /dev/sda4 /run/media/root/BBB # journalctl | tail -20 And post here the entire sequence with the results, in a single mouse swipe operation. Just one paste. This is quick to do, I'll wait for it. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 09/16/2019 02:35 PM, Carlos E. R. wrote:
Now, as to the reason why it is mounted ro, it usually means that it is not clean, and probably the advice you got about what to do in Windows are correct. We can make certain, though. Do:
# umount -v /dev/sda # mkdir /run/media/root/BBB # mount -v /dev/sda4 /run/media/root/BBB # journalctl | tail -20
And post here the entire sequence with the results, in a single mouse swipe operation. Just one paste. This is quick to do, I'll wait for it.
Be careful remounting /dev/sda4 if /dev/sda4 is a windows drive for the reasons explained in my other post on this thread. It will depend on whether Win10 is really completely shutdown, or just in its semi-"Shutdown" state. -- David C. Rankin, J.D.,P.E.
On 17/09/2019 00.56, David C. Rankin wrote:
On 09/16/2019 02:35 PM, Carlos E. R. wrote:
Now, as to the reason why it is mounted ro, it usually means that it is not clean, and probably the advice you got about what to do in Windows are correct. We can make certain, though. Do:
# umount -v /dev/sda # mkdir /run/media/root/BBB # mount -v /dev/sda4 /run/media/root/BBB # journalctl | tail -20
And post here the entire sequence with the results, in a single mouse swipe operation. Just one paste. This is quick to do, I'll wait for it.
Be careful remounting /dev/sda4 if /dev/sda4 is a windows drive for the reasons explained in my other post on this thread. It will depend on whether Win10 is really completely shutdown, or just in its semi-"Shutdown" state.
No need to be careful :-) Linux knows that and will do what is correct, and tell us about the situation in the messages it prints to the console (that's the reason for the -v parameter). It will probably say that there is more info in the log, which is why I asked for the end of the journal. What is dangerous, and the manual says it is, is telling mount to force mount in read-write mode. But that is not included in the command line I supplied, so _that_ line above is not dangerous. However, if the OP is adventurous and issues some other different command, like he did previously... -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Mon, 16 Sep 2019 21:35:16 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 16/09/2019 20.57, Doug McGarrett wrote:
On 09/15/2019 06:09 PM, Carlos E. R. wrote:
On 15/09/2019 23.43, Doug McGarrett wrote:
...
Please, just do exactly what I asked. Type into a terminal just this exact line:
mount -v
and paste all of it here here. Nothing more, nothing less.
linux-4qnb:~ # mount -v sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
...
/dev/sda7 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) ... fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) ... /dev/sda4 on /run/media/root/B66C5BE86C5BA1C3 type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2) /dev/sdb1 on /run/media/root/USB20FD type vfat (rw,nosuid,nodev,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) ... linux-4qnb:~ #
Thank you!
Well, as you see, sda4 id mounted ro, which means, read only, so it is impossible you can write anything to it. You can compare to sdb1 which is mounted rw.
Now, there is another problem. They are mounted by *root*, and this is not good. It means you are running the desktop as *root*. This is anathema! You must never do that. Run the desktop as plain user.
Now, as to the reason why it is mounted ro, it usually means that it is not clean, and probably the advice you got about what to do in Windows are correct. We can make certain, though. Do:
# umount -v /dev/sda # mkdir /run/media/root/BBB # mount -v /dev/sda4 /run/media/root/BBB # journalctl | tail -20
And post here the entire sequence with the results, in a single mouse swipe operation. Just one paste. This is quick to do, I'll wait for it.
Did you really mean: # umount -v /dev/sda ?? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 17/09/2019 12.30, Dave Howorth wrote:
On Mon, 16 Sep 2019 21:35:16 +0200 "Carlos E. R." <> wrote:
linux-4qnb:~ # mount -v ... /dev/sda7 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) ... /dev/sda4 on /run/media/root/B66C5BE86C5BA1C3 type fuseblk (ro,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2) /dev/sdb1 on /run/media/root/USB20FD type vfat (rw,nosuid,nodev,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2) ...>>> linux-4qnb:~ #
Thank you!
Well, as you see, sda4 id mounted ro, which means, read only, so it is impossible you can write anything to it. You can compare to sdb1 which is mounted rw.
Now, there is another problem. They are mounted by *root*, and this is not good. It means you are running the desktop as *root*. This is anathema! You must never do that. Run the desktop as plain user.
Now, as to the reason why it is mounted ro, it usually means that it is not clean, and probably the advice you got about what to do in Windows are correct. We can make certain, though. Do:
# umount -v /dev/sda # mkdir /run/media/root/BBB # mount -v /dev/sda4 /run/media/root/BBB # journalctl | tail -20
And post here the entire sequence with the results, in a single mouse swipe operation. Just one paste. This is quick to do, I'll wait for it.
Did you really mean: # umount -v /dev/sda
??
No. Oops. Actually, it should be: #umount -v /dev/sda4 -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
participants (4)
-
Carlos E. R. -
Dave Howorth -
David C. Rankin -
Doug McGarrett