I'm using opensuse 13.1, and I need to rename my NIC from 'em1' to 'eth0'. While I've found several other people trying to rename NICs, I haven't found anyone who seems to be doing it in Suse 13.1. One of the frequently mentioned fixes is changing parameters in the
70-persistent-net.rules file, but mine is empty. I also haven't been able to find anything in Yast that has NIC names, but that doesn't mean it isn't there.
If it helps, here's an example of someone doing in Red Hat what I'm trying to do:
http://www.sysarchitects.com/em1_to_eth0.
The problem here is that the pathways he references don't always match up with mine (for example, I don't have /etc/grub.conf, nor do I know if I have an equivalent and if I do where to find it), so I haven't been able to use this example to get mine working.
Thanks for the assistance!
openSuSE 13.1 uses grub2. You will not have an /etc/grub.conf. The change in network interface names is a result of running systemd/udev >= 197. You are in luck, you can change the device name. Look at the freedesktop.org page list below (the folks that brought you systemd/udev)
You basically have four options. The four options are detailed here Predictable Network Interface Names (I don't like this, how do I disable this?) It is toward the bottom of the page.
Related
Im using a script to automate the QtFramework installation. I was used to select all components in the ComponentSelectionPage. However nowadays with Qt5.10.0 this results in over 11 GB. So i would like to pick just the components i need. According to the documentation the ComponentSelectionPage has selectComponent(id) and deselectComponent(id) methods, id beeing the name of the component. So this should be doable.
However i can't find any documentation on the names/ids of the components. I tried several things like:
widget.selectAll()
widget.deselectComponent("MSVC 2013 64-bit")
widget.deselectComponent("MSVC*")
widget.deselectComponent("*MSVC*")
But neither of those work (i tried a bunch of differnt other combinations also). So does anybody know where to find documentation about component names of the default Qt Installer? I was already poking in their git repository but could not find anything.
so i've found out how to solve this quite a while ago, if someone is still interested:
By running strings <qt-installer-executable> | grep "qt\." i was able to extract the names of the components. (Not sure if it was strings in windows, but a similar tool exists for sure).
An example output is then something like
....
qt.qt5.5121.gcc_64
qt.qt5.5121.examples.qtpurchasing
qt.qt5.5121.doc.qtscript
qt.qt5.5121.qtdatavis3d.gcc_645
qt.qt5.5121.qtscript
qt.qt5.5121.doc.qtpurchasing
qt.qt5.5121.examples.qtscript
qt.qt5.5121.qtnetworkauth.gcc_64
...
along with a lot of other stings.
I'm fixing a few things in the current SNAPSHOT version of Putty but I'm getting slightly another putty (design) than Simon Tatham does.
Please have a look to the following Screenshot.
First my own compiled PuTTY.exe (acutally the change was the window size - I need it broader...)
Second the original one.
My version has the "old-fashioned" XP-Style 3D-Effects, while the original variant already takes care of the new "flatstlye"-Window-Style.
I was looking for any property I can set or anything I can configure in Visual Studio, but unfortunately I wasn't able to find anything.
Thanks in advance for any reply!
P.S.: Trying to run perl mkfiles.py it generates no Makefile.cyg using Windows 10 and cygwin/cygwin64 for me. Maybe using another compiler would work in the end....
It seems that you didn't add a manifest to your project.
See windows\putty.mft in PuTTY repository.
See also:
https://www.codeproject.com/Articles/4987/Using-Windows-XP-Styles-in-your-MFC-WIN32-Applicat
This is related to the question I posted here, but I hadn't gotten much visibility for that question so I wanted to ask in a more general way. I have a Qt 4.7 project that utilizes QFtp functionality. Until very recently we were using this with an FTP server that was vsftpd. Everything worked fine with it then. However, several days ago we moved the server to a new computer. All the contents are identical, but now it uses pure-ftpd instead of vsftpd. Since the move, none of my QFtp code works properly. Is there any known problems that arise when trying to use QFtp with this type of FTP server? I can't find anything helpful online, and it's rather frustrating not being able to find anything wrong with the code and yet having it not work. If anyone knows anything about this and could please share, I'd appreciate it a lot. Thanks!
So I think I just figured something out... I had it run QFtp::list to go through the ftp and retrieve directories, then use list() again on those to retrieve the files in those subdirectories. Our subdirectories to get files out of had spaces in the name, eg "My Directory". Apparently, the vsftpd we were using before could handle this with no problem, but the pure-ftpd can't handle spaces in the directory names. When I switch it to something like "MyDirectory" or "My_Directory", the pure-ftpd works fine. I couldn't find anything online about this difference, but apparently it's there, because that fixed the issue I was having.
In Windows 7 theres a possibility for getting file's previous versions like in the below image:
Is there any way to retrieve file's previous version by code? because I couldn't find any API.
Thanks advanced! =]
There are several tags listed with this question. So it is unclear if a strictly c/c++ approach is desired, or if scripting etc will work. In any case...
Here are some links that will hopefully point in the right direction:
On the MSDN site, there is documentation and example code referring
to shadow
copy
API.
Here is a Link to the
concept
of shadow copy service.
Here is a description of how you can command line, or program
script to recover
files from shadow copy.
Using the API link above with the structures found
here
will provide you with a way to get information about a particular
file, volume etc.
Finally, Here is a link talking about the Volrest utility from
Windows Server 2003 Resource Kit
tools, including
information on how you can "see a list of available previous
versions of [a] folder".
So after some searching, and thanks to #ryyker and #Ben directions I was able to find out the answer:
For example for file: C:\SomeFolder\SomeFile.exe
From cmd (run as administrator):
vssadmin list shadows for=C:\
For programmatic solution you can run it with:
CreateProcessW(NULL,L"cmd.exe /c \"vssadmin list shadows for=C:\\ > C:\\someTmpFile.txt\"",...);
Read and parse the created file.
Here above you get a list of shadow copies (kind of "Previous versions" containers).
Refer to the appropriate "Shadow Copy Volume" row (the version you want) and append the remaining file path after the volume name:
\\ Previous version path = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3\SomeFolder\SomeFile.exe"
wchar_t* prevPath = L"\\\\?\\GLOBALROOT\\Device\\HarddiskVolumeShadowCopy3\\SomeFolder\\SomeFile.exe";
Now you can read the file with the well known WIN32API functions CreateFile and ReadFile. (Create and Read file example from MSDN: EXAMPLE)
Make sure to use the UNICODE versions of that functions as the ASCII version may lack support of "\?\" paths.
Good luck! =]
I’m hoping to port an application to open vms using HP C++7.3, but at the minute just trying out a few examples to establish if it's a potential way forward but a bit stuck. Being completely new to open vms it's being a lot of fun so far.
For starters I've not got very far building boost as a whole, after some googling I found a few mentions of people having dcl scripts to build boost but no actual scripts. I don’t suppose anyone has any or can pint me to some. I ‘only’ need asio and threading.
Currently I’m just trying to compile the asio chat examples. And as I said I’m completely new to VMS and the compiler, I managed to get a few things to compile but now get a “could not open source file "sys/select.h"’, a bit of googling suggests I may need to have an HP porting library installed or maybe I’m just missing an prepocessor directive to include the correct code, can’t see anything obvious in socket_types.hpp to set?
Any pointers in the right general direction would be gratefully appreciated.
No answers since the questio is too open ended and in a realm I know little about.
Just some thoughts.
Select can be provided by the OpenVMS TCPIP services (aka UCX), or other TCP stack.
At the dcl prompt try: $ HELP TCPIP_Services Programming_Interfaces Socket_API
Async programming on OpenVMS is typically 'event driven'.
Google for SYS$QIO and AST
There is a public access OpenVMS system which holds 'NOTES FILES' (pre-cursor to web-forums)
Try TELNET to EISNER.DECUS.ORG and you'll get sign up instructions.
Once you are in find your way to the PORTING_TO_VMS conference
Once in the NOTES conference you can issue the command DIRECTORY or DIR/TIT=xxx
Unfortunately there is not topic for select, but you can find some interesting
reading using NOTES> SEARCH "select(" followed by repeated SEARCH commands)
( $ NOTES ... OPEN PORT ... SEARCH "select(" ... SEARCH [] ... SEARCH ... )
The PERL folks did an admirable job getting open stuff to work on OpenVMS.
Good luck!
boost library on OpenVMS can be used directly from headers.
I remember one thing to make sure was that BOOST logical is defined concealed, so the relative-includes work.