New answers tagged opensuse
Choose and add the Packman mirrors from here: To find out if already have Packman , open the terminal and type : zypper lr -d e,g : Open-suse Leap 42.1 Add pacman mirrors using the following command: zypper ar -f -n packman http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_42.1/ packman To install the Broadcom Drivers, you need 2 packages:...
Installed filezilla from repo -- This solved the filezilla errors.
Umount it, and make the mountpoint more permissive. Sometimes this is relevant... maybe it is in your case because using a different mountpoint has different results. Compare the permissions on those 2 directories for more info. Check man ntfs-3g for options, and use them, for example: mount -o fmask=664,dmask=775,uid=1000,gid=1000 /dev/sde1 /home/craig/...
From your explanations and details, assuming the errors are relevant for the actual problem, I am fairly confident that the issue is an inconsistency between FZ and SSH server. Apparently the group for the key exchange that the server is supposed to reply with was not received by FZ. It is more secure to allow the SFTP server to manage this but in your case,...
Ok, all, thanks for taking a look, unfortunatly no possible answer from the comunity so far, BUT good new for others who read this. I found a solution. added the following line to the /etc/rc.d/rc3.d/S05network start script: ifenslave bond0 eth0 eth1 sleep 2 and changed the following in the config files: /etc/sysconfig/network/ifcfg-bond0 DEVICE=bond0 ...
Did it! You were right: I needed to change file permissions, for the directories and the qcow2 file, the correct user was qemu and the group wheel. Thank you!
commands which you have to fire are : 1. Check your NIC ifconfig Choose one and set it with ip which you want to give ifconfig enp0s8 192.168.1.34 go to cd /etc/sysconfig/network-scripts/ edit NIC file vim ifcfg-enp0s8 do --> 'IPADDR' = 192.168.1.34 'NETMASK'= 255.255.255.0 'ONBOOT' = yes 'BOOTPROTO'= 'static' 5. done
I installed: ca-certificates-cacert ca-certficates-mozilla and it solved the issue.
If the root= parameter is correct and the issue is just that the necessary device isn't available (for example because the initramfs failed to assemble an md RAID), then it's enough to make the device available manually, for example: mdadm --assemble ... Then check that the device is there and if everything looks good, hit ctrl + d or type exit to quit ...
Top 50 recent answers are included