However, again, to be fair, these issues would be faced only if you go deep, but if you just run virtual OS for fun, or for simple usage, you'd have nothing to worry about. If you use the virtual OS you're running as a main drive or you rely on it for professional purposes, this could be a total disaster as you'd face countless network issues that'd hold you back. Changing the size of disk storage could be an issue, but such issued were paid attention to with newer versions (5.2). It takes a while to come up and if your computer isn't good on the specs side, you might have a laggy and slow experience. Some features aren't supported without installing add-ons. Some computers do not allow the installation of a Virtual Machine software without changing the BIOS, and this, of course, isn't something everyone can do. However, if you'd like to use it more in-depth, you'd find a few issues. If you just want to test operating systems and not go in-depth, VM VirtualBox would be okay. 21 hours ago Search: Sudo Startx Login Loop. It's not exclusive to only one operating system. OSX users can get around this limitation by using Vagrant, VirtualBox and the VirtualBox Extension Pack. Fawn Creek Township is in Montgomery County. It helps you test any OS in a few steps and switch between the operating systems you're running easily and swiftly. Fawn Creek Township is located in Kansas with a population of 1,618. VirtualBox is open-source, easy and super fast to install and start, and it's free as well. On the personal side, I'd say almost flawless, but on the professional side, it's not what I'd rely on, but again, you get what you pay for! PROS Whether that will be Antix 17 or Debian Stretch with or without systemd stuff or something else entirely remains to be seen.My personal experience with it could be both satisfactory and disappointing, honestly. My Wheezy system is headed for End Of Life May 2018, and I want to get a replacement system installed and ready to go by that time. True, I don't boot to a terminal, but I'm just testing and evaluating now. But for now I installed lightdm, and X and Openbox load and work fine after logging in. I've had similar"problems" happen before. I mentioned in another reply that this startx problem could be a VirtualBox glitch. pkg-message: Code: Xorg-server has been installed. It's likely that the problem boils down to some of those files having the wrong ownership or permissions. Code: > Backend to use for input device configuration: you can only select none or one of them DEVDoff: Use devd for autoconfiguration of input devices UDEVon: Use udev via libudev-devd for autoconfiguration of input devices. It generates a copious list of all system calls which will show all the files that are being accessed. Another approach is to run Xorg with the strace command. Having similar systems that work may make debugging easier. My hope is that maybe most of this can be fixed with a well-placed chown -R or chmod -R command. I personally use startx instead of a display manager and what you want is in accord with the antiX"lean and mean" motto. And to be as"light' and fast as possible. I don't want to install a display manager as I want the system to boot to a standard terminal and not X as many times I only need a terminal. Traditional Desktops which I abandoned about 6 years ago are such leviathans and CPU gluttons, and no more useful than a good window manager and a single panel. I've tested Stretch in VirtualBox under numerous configurations - systemd init, sysv and runit inits with and without systemd components - installed the same way as I did Antix and never experienced any startx problems. My thinking now is this startx failure is an Antix 17 Beta glitch and not an upstream Debian Stretch or xorg problem. Although, I don't think the bug report applies (and it's a year old), but I'll read it more thoroughly later. Thanks for your quick response, advice and the bug link. Update to VirtualBox version 6.1. You can probably explore this further but it might be faster/easier to install slim or lightdm or some other display manager that you can start as an init.d service. I think the problem is upstream with Debian and/or X.org and/or. Code: Select all sudo chmod u+x /usr/bin/Xorgīut that didn't change anything.
0 Comments
Leave a Reply. |