Log in as the root user

  • Subscribe to RSS.
  • photoshop cs5 crack mac lion;
  • sync music mac to ipad.
  • koppla mac dator till tv!

This can be run by typing wine regedit in the terminal. Wine's regedit is virtually identical to the Windows version of regedit and also supports importing and exporting of registry files. There are two ways using which you can associate a native program with a file type. The first method is to use winebrowser and an alternative would be to write a shell script. The example below uses winebrowser to launch the default PDF handler on your system on a Unix desktop it uses xdg-open.

Save the lines below to a file pdf. Another option is to use a shell script to call a native application. Otherwise it will not work. To associate say. You can reuse this script and just edit the registry file. For example to associate. Beginning with wine Checking it enables winemenbuilder to create file associations and unchecking it disables that behavior. Users of older Wine versions and those who also want to disable the creation of menu items can accomplish this by disabling winemenubuilder.

There are several ways to do this:. Wine includes a GUI crash dialog that is turned on by default. Users of apps that work despite a background crash may find the GUI dialog annoying, and in some cases the dialog itself has been reported to prevent an app from working. The easiest way to disable the crash dialog is with winetricks :. Support for subpixel font rendering was added to Wine in version 1. Use winetricks and select one of the fontsmooth-gray, fontsmooth-rgb or fontsmooth-bgr options.

First, you should try editing with winecfg. Go to the Graphics tab, and slide the "Screen Resolution" slider accordingly. Changes will not effect the winecfg window until you restart it. If windows and fonts are so big you can't get to the controls in winecfg, see Wine's windows and fonts are extremely large. On many Linux distributions, configuring a network proxy, e.

Alternatively, you can configure a proxy in the registry. There are separate locations for wininet. For winhttp, you'll need to use the proxycfg. This utility is available in the system32 directory of a Windows installation, and MSDN describes its usage. Most of Wine's development effort is geared towards programs written for the Windows GUI, but some limited support for character mode is available with the "null" driver.

Wine automatically activates "null" whenever x11driver isn't loaded, but even then, Wine depends on the xorg libraries. Also the "null" driver will only work for pure console applications that never use any windowing functions for example, parts of OLE create purely internal windows. Wine does not currently allow sharing its configuration "prefixes" between users, due to the risk of registry corruption from running multiple wineservers simultaneously bug At present, applications must be installed separately for each user.

However, you can copy Wine prefixes; you can install everything to one prefix, then make a copy of it in each user's home directory. This saves running installers repeatedly. Wine requires your hardware to already be working on your operating system. The technical reason for this is that Wine, like most applications, runs in user mode and not kernel mode.

Just because Wine runs on a non-Windows OS doesn't mean you're protected from viruses, trojans, and other forms of malware. Wine does not sandbox in any way at all. When run under Wine, a Windows app can do anything your user can. Wine does not and cannot stop a Windows app directly making native syscalls, messing with your files, altering your startup scripts, or doing other nasty things. Note that the winetricks sandbox verb merely removes the desktop integration and Z: drive symlinks and is not a true sandbox.

It protects against errors rather than malice. It's useful for, e. The problem is that these programs conflict with Wine over the display driver. Disable these programs before using any applications with Wine especially games, or when noticing weird window problems. Recent versions of Wine will prompt you to download wine-mono on wineprefix creation.

For many. NET apps, particularly older ones, this is sufficient. You can install it by running winetricks and selecting the appropriate. NET version. Note that native. Wine itself provides a DirectX implementation that, although it has a few bugs left, should run fine. Wine supports DirectX 9. Work on DirectX 10 is underway. If you attempt to install Microsoft's DirectX, you will run into problems. It is not recommended nor supported by Wine HQ to attempt this. You can install the runtime, but it will not run. The runtime needs access to the Windows drivers, and Wine cannot access them for obvious reasons.

Additionally, versions of these DLLs are now part of the Wine tree. So, as Wine improves these DLLs will only become less relevant. That said, there are some guides out there which describe how you can install Microsoft's DirectX. We reiterate: it is not recommended nor supported by Wine HQ to attempt this. Furthermore it is considered off topic in Wine HQ support mediums such as the forums.

Wine uses the core of Firefox to implement its own Internet Explorer replacement wine-gecko. Recent versions of Wine should prompt you to install it on wineprefix creation.


  • portal 2 para mac 1 link?
  • iphone app openen op mac.
  • project my screen for mac.
  • Hint Options.
  • How to Enable the Root User in macOS!
  • macos - How to run a script as root on Mac OS X? - Stack Overflow;
  • gotham book font free mac.

In most cases Wine's IE replacement wine-gecko is sufficient. If you really need the real IE for a specific application to work, use winetricks to install ie6, ie7 or ie8. You should put IE in a separate wineprefix , with whatever app really needs it. Note that the Wine project does not support installing the real Internet Explorer, as it requires a huge number of native DLLs, which is hard to configure.

Please do not ask the Wine project for help if you run into problems. Copy protection uses several "dirty" methods to detect if discs are "real" or not. Some of these methods work in Wine but many do not, such as the extremely invasive StarForce system. Wine would need to be altered to allow for almost rootkit-like functionality of programs to get some of these copy protection schemes to work, so support is likely to be a long time off if ever some people use illegally modified or "cracked" games with the copy protection removed, but the Wine project cannot advocate that.

There are many unofficial howtos for various apps posted on blogs and forums. They are rarely maintained by their authors, and because of Wine's rapid rate of development, even ones that were correct at the time they were posted can quickly become outdated. Applying tweaks that are no longer needed in current Wine can actually prevent an app that now runs fine without tweaks from working at all Office is a prime example. The only howtos supported here are the ones on this site. If you insist on following an outside one, ask its author for help.

If in doubt, start again installing the app in a fresh wineprefix and ask for help on the user forum. Consult the support channels for whatever third party application you used. Links to some of these outside applications are provided as a convenience on the Third Party Applications page, but they are not supported here.

This is called a regression. Please perform a regression test to identify which patch caused it, then file a bug report and add the "regression" keyword: we'll pay special attention to it, since regressions are a lot easier to fix when caught early. Briefly, you can improve Wine yourself, convince someone else to do it for you, or try some complicated hacks involving native Windows DLLs rather than Wine's unfinished ones. This is a bad idea. See the Developer FAQ. See 3D Driver Issues for more information. Actually, Wine is sometimes faster.

The speed of an application depends on a lot of factors: the available hardware and their drivers, the quality of the code in the APIs the application uses, and the quality of the code in the underlying operating system. Driver code matters a lot. If you're running a graphics-heavy application using a video card with very poor drivers such as an ATI card under Linux, performance will degrade substantially.

On the other hand, Linux has superior memory management, and comes out ahead of Windows in many CPU-related tasks. Sometimes, bugs in Wine can make applications excessively slow. That said, Wine works on correctness first, performance second. Ignore them. Generally speaking, a fixme message will not make much sense to someone unfamiliar with Wine development. They are for Wine developers. Also, it's important to understand that fixme messages often do not indicate a serious problem. Many applications will work fine even though Wine prints a few fixme messages.

That said, they can still sometimes provide insight into how a particular application works or doesn't work. If there are a very large number of these messages scrolling repeatedly, you can sometimes speed Wine up a little by turning them off altogether. For example, your command line could look something like:. More advanced users and programmers interested in debugging Wine should see Debug Channels and the Developers wiki pages.

Enable or disable the root user

Here's an example to selectively turn off fixme messages from dsound and part of D3D only:. You can then copy the log from the screen and paste it into a file if it's short; otherwise redirect the output of wine to a file using a Unix shell redirection , e. Important : Unless you have been asked specifically to provide a debug trace then do not do so.

Simply follow the instructions above. Important : If you get a crash dialog while doing this, please click Close. Otherwise your log will be incomplete. Important : If the resulting text file doesn't have names of C source files in it, your copy of wine probably lacks debugging symbols. Please either build wine from source, or install the debug symbols package. Note : Please only use this procedure when instructed. In most cases a regular terminal output is enough see above. To retrieve a trace, run:. If the resulting file is larger than 1 MB, compress it with bzip2 or rzip before attaching.

Please mention that in the bug report. For a list of debug channels that are available in Wine, see Debug Channels. If you ran the program from a terminal window by typing wine program. If you ran the application some other way, such as from a launcher shortcut, then you can open up a terminal and forcibly kill the process:.

How to Enable the Root User on Your Mac

You can also open up a Wine version of the Windows task manager by running wine taskmgr in a terminal. This will allow you to kill individual Wine processes. If you are getting a complete deadlock and are unable to even use your mouse after running Wine, it's probably not a specific problem with the Wine software. Wine is a user-level process, and shouldn't be able to completely hang the operating system under any circumstances. Instead, Wine is likely exposing a deeper problem with the system, such as a defective hardware driver, a bad memory stick, or overclocking flakiness.

It's often a graphics driver problem, in which case non-Wine apps might also be affected. If running glxgears also crashes, it's definitely a graphics driver problem. The most common cause is upgrading to a new kernel without also updating the graphics drivers to match. Try reinstalling your graphics drivers. If the computer is a laptop and shutting itself off entirely, a likely cause is overheating.

Tutoriel Mac Os Terminal en root Activer le compte root

Log in as the root user When the root user is enabled, you have the privileges of the root user only while logged in as the root user. If the login window is a list of users, click Other, then log in. Remember to disable the root user after completing your task. Yes No. Character limit: Maximum character limit is The purpose of xhosts on Xwindows systems is to allow other hosts to connect to and bring up windows on your display.

On an Xwindows system, typing 'xhost -' disables anyone else from sending a window to your display. The short answer is, no. Under Mac OS X, you can't launch an application as another user other than root. Pardon my ignorance as I am very new to all this, but is there a way to change a user like this, and then perform tasks as that user in the Finder? Let's say, for instance, I wanted to make a slight change in a file within the System Library, but can't unless I'm root or I change the permissions for said file Nope: you'll be root in the terminal if you execute a command such as sudo -s this will be indicated with the " " prompt , but changing your terminal identity this way doesn't affect the GUI: the critical windowing processes that are doing all the heavy lifting were started by the user who logged in via the GUI, and that's not going to change without a logout or a change in the way that apple implements this stuff so that there can be multiple, swappable sessions on the go at the same time, with only one "visible".

Cheers, Paul. I've used sudo and su a lot, and there are reasons for using one or the other. By what you're saying, you want to edit a file you don't own, which you can do by using 'sudo command', where command is the command you want to do with any required parameters. Additional sudo commands done within the next 5 minutes don't need a password and the timer resets with each call, so if you edit a bunch of files within 5 minutes of each other you can potentially chain hours or days together , so as long as you keep doing sudos, you won't need to authenticate yourself each time.

How to Run GUI Apps as root in Mac OS X

The 5 minute limit is to ensure you don't walk away from your keyboard and give someone else temporary root. I almost never use sudo -s, unless I need to do a ton of actions as root debugging an install, for instance. With sudo -s you're leaving a door open in your system. For the most part, it's not that dangerous if you're just doing it at home, but you never know when the feds are going to wiretap your home for all those napster downloads This has implications if you're running programs that have the sticky bit set that do a setuid or setgid - er, in English, that's programs that run as a different user than the owner of them and the program itself runs some part of itself as a different user.

The ONLY place I've ever used anything like this is in a Web perl-CGI that needed to be executed with root priveleges, but run as a specific user specifically because I was remote logging into machines where I didn't have a root password. This is handy if you want to figure out problems with another user's shell variables. I've used this FAR too much usually because of slow logins due to stale remote mounts or someone putting Xwindows display settings in their.

The su I'm describing above is always 'su username' though - you really never need 'su -' unless you need your effective user ID set. You can actually use GUI programs as root without logging out—it just involves restarting the program you want to use as root. When you're done, you can quit the same way, and start the Finder as yourself as above without the sudo, or by clicking in the Dock. My slight guesswork explanation as to why this works is that root, having access to everything, has access to your display interlocks whatever those are , and so can use your display.

I imagine that with the appropriate tweaking of groups and permissions that you could set up your computer to allow you to use your display as other users, too. Lost your password? Powered by the Parse. In order to execute a command via another user, without knowing their password, you can use the "su" command to log into root and then their account. Any comments from the UNIX experts? Execute commands as another user 23 comments Create New Account. The following comments are owned by whoever posted them. This site is not responsible for what they say. Execute commands as another user Authored by: escowles on Feb 20, '03 AM.

You should really use sudo for this. Just type: sudo -u username command Not only is it easier, but it's also very customizable -- you can control which users can execute which programs as what users. Execute commands as another user Authored by: morgion on Feb 20, '03 AM. This next command is helpful if you want to run a series of commands as another user after you are root, naturally : su username This method is much safer than logging in as root; you don't even have to enalbe the root password.

Execute commands as another user Authored by: tobyc on Feb 20, '03 AM. Authored by: Garin on Feb 20, '03 PM.