I don't need fancy environments and tick boxes, I just don't want to put an unbelievable and unjustifiable amount of effort in order to even try something, paste the dam thing. Then you open the terminal and you try to copy and paste. Is the mint installer a shell script? If so, you could try removing the '-force' from the grub-install command.1) Create a new empty document in the desktop of Debian.Ģ) Copy and paste commands from browser or wherever you find them on your empty document.ģ) highlight the text you want on the document (just select it and do nothing)Ĥ) put the mouse point on the xterm and click the middle button (roller)įirst attempt to use Linux and you find a guy willing to help you ''You have problem with Linux? no problem just put this command on the terminal: ''. We removed that from refractainstaller, but I don't remember the reason. I don't know enough about "scripts" to say if it's a shell script or not. I did see something in the file that referred to schell. Made a really stripped down and bare-bones LXDE system this time just to save time. I just built some Python text based menus. Plus, it's just for testing all of this out. I built a sktop file and put it in /usr/share/applications. chow's it to pi:pi, chmod'd it to 755 and it works except that it unststs on runnig UXTerm as it terminal emulator instead of LDTerminal whic, I want. I have scoured the web and there seems no way to force the. I've built 4 snapshots this evening and tested each one. However, if I execute 'x-terminal-emulator' from the terminal i just opened I get another instance of lxterminal, with window title lxterminal. Ran a snapshot before editing the file, and ended up with the same situation as before. If I execute lxterm I get an instance of 'uxterm' which looks like the 'raw' xterminal. Same failure message about the bootloader and no username/password copy over. I'm not sure if I was in the right configuration file or not. TERMINAL VS UXTERM VS XTERM WINDOWSI then edited /usr/lib/live-installer/installer.py hey folks, from my experience it is safe to use any of the 2 following commands for launching a terminal windows and executing a command at startup: Code: Select all. usr/bin/xterm -e sudo path/to/executable lxterminal -e sudo path/to/executable. Stupid me didn't make a copy of it before I edited it. I found -force in a line having to do with grub, and removed it. TERMINAL VS UXTERM VS XTERM INSTALLRan a snapshot, burned it to a USB, and tried to install it on a partition. It stayed hung up when the installer first started trying to format the partition, and it never went any further. Went back, put -allow where (I thought) -force was. It did the exact same thing when I tried to install it. Same thing happened when I tried to install it. Like I said, I don't even know if that was the correct file to edit. HOWEVER, I'm going to take a day or two away from this. Best by far, I feel is using a DebianDog installer that simplifies and even hides as many technical details as possible without losing too much flexibility.Īfter this evening's turmoil, I've had enough for now.Reading some of the details you have been discussing recently I can't help thinking that though dd can be used to create a bootable usb from hybrid iso, as you discuss, I personally think that is far too technical a procedure for many users. Doesn't matter if everyone using DD is technically skilled in using Linux, which may be the majority case (I don't know) but its nice to build in as much user-friendliness as feasible. Not that it is difficult to cut and paste an appropriate dd commandline, but it comes across as a bit rough in terms of elegance don't you think? To be honest, I haven't even tried creating a bootable usb with the new distribution since I always just extract the live folder onto my hard drive and boot via my grub4dos installation, so maybe I'm missing something.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |