Try these commands: sudo dpkg --configure -a sudo apt install -f If you continue to have issues, please copy and paste the command you are executing along with any error messages. ------------------ For your convenience I've included the complete instructions. This procedure requires a fresh Linux install on a Chromebook, which installs a base Debian container which we transform into Kali. 1. Base Install: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-4bKeaVw_eqc.html 2. Install Kali: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-CpGeCU4eG2o.html&lc=Ugwo_ICwIfUItHYJiet4AaABAg Here are the complete instructions: Install nano from a terminal: sudo apt install nano -y Delete everything in the repository source file and add the following line: sudo nano /etc/apt/sources.list deb http.kali.org/kali kali-rolling main contrib non-free Download Kali software key: sudo wget archive.kali.org/archive-key.asc -O /etc/apt/trusted.gpg.d/kali-archive-keyring.asc Update system: sudo apt update -y sudo apt full-upgrade -y Install software: sudo apt install kali-defaults -y sudo apt install kali-desktop-xfce -y sudo apt install synaptic -y sudo apt install xserver-xephyr -y Create gox script: sudo nano /usr/bin/gox Xephyr -br -fullscreen -resizeable :20 & sleep 5 sudo -u <user-id> DISPLAY=:20 startxfce4 &> /dev/null & Ctrl-O, Enter, Ctrl-X to save the file and exit nano. Make gox script executable: sudo chmod +x /usr/bin/gox Create gosyn script (may no longer be necessary, use only if needed): sudo nano /usr/bin/gosyn xhost + && sudo synaptic && xhost - Ctrl-O, Enter, Ctrl-X to save the file and exit nano. Make gosyn executable: sudo chmod +x /usr/bin/gosyn Shut down Linux, shut down Chromebook, and then restart Chromebook and start up Linux. Then execute gox script: gox Change launch command for Synaptic Package Manager to: gosyn
Are you using sudo in front of the command? sudo apt install kali-defaults -y sudo apt install kali-desktop-xfce -y sudo apt install synaptic -y sudo apt install xserver-xephyr -y If you are using sudo, please run the following command to list the holding process: sudo lsof /var/lib/dpkg/lock-frontend If there are no processes listed, try these fix commands: sudo dpkg --configure -a sudo apt install -f If you continue to have issues, please copy and paste the command you are executing along with any error messages.
Due to current limitations of UserLAnd's VNC, sound and OpenGL graphics are not available: ru-vid.comdsQDYFv97F4 Kali is a fork of Debian. Most things that work on Debian will work with Kali. While PulseAudio will not produce any sound. It may be necessary for certain apps to run. Here are two examples: For LMMS, you'll need to make a script to make it work (script can be any name). From a terminal (Linux On Android - Install LMMS video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-HJBec7xNrjI.html ): cd /usr/bin nano golmms pulseaudio --start & sleep 2 lmms && pulseaudio -k Ctrl-O, Enter, Ctrl-X to save chmod +x /usr/bin/golmms For clarity, it's pulseaudio space dash dash start space & and pulseaudio space dash k. Change the LMMS launch command to golmms. Remember there will be NO SOUND, but the file can be moved to and played on the Android side. Using the file manager you can copy the music file from the Linux side to the Android side. I recommend copying the file to the /Downloads folder. The same technique can be used for many other programs such as games. For example, to run Flight of The Amazon Queen: cd /usr/bin nano goaq pulseaudio --start & sleep 2 scummvm -f -p /usr/share/scummvm/flight-of-the-amazon-queen queen && pulseaudio -k Ctrl-O, Enter, Ctrl-X to save chmod +x /usr/bin/goaq
It appears that Linux is not connecting to the internet. We have also updated the gox script so that it restarts the network on the Linux side (I will be updating this video soon). Here's the updated gox script: Xephyr -br -fullscreen -resizeable :20 & sleep 3 sudo systemctl restart networking &> /dev/null & sleep 3 sudo -u <user-id> DISPLAY=:20 startxfce4 &> /dev/null & To see if the Linux side is connected to internet from a terminal (Ctrl+C to stop the ping): ping google.com If there is no output, restart the network: sudo systemctl restart networking If restarting the network fails, create a new resolv.conf file (it's resolve without an e on the end). After creating the file, reboot Linux. Linux may recreate the file after rebooting, that's normal. This should restore internet on the Linux side: cd /etc mv resolv.conf resolv.bak nano resolv.conf nameserver 8.8.8.8 nameserver 8.8.4.4 Ctrl-O, Enter, Ctrl-X to save the file and exit nano Reboot Linux --------------------------- Due to recent changes, it may not be necessary to use the gosyn script for Synaptic to run. From a terminal try launching Synaptic: synaptic-pkexec --------------------------- Neofetch can also be installed from a terminal: sudo apt install neofetch -y
I would recommend shutting down Linux, shutting down the Chromebook, restart the Chromebook, put the Chromebook online, start up Linux again, and try executing the gol script (6:52). For your convenience I've included the complete install instructions. If you continue to have an issue, please copy and paste your go script (4:38): From Terminal app: sudo apt update -y sudo apt dist-upgrade -y sudo apt install task-lxde-desktop -y sudo apt install xserver-xephyr -y sudo apt install nano -y sudo systemctl disable lightdm sudo nano /usr/bin/gol Xephyr -br -fullscreen -resizeable :20 & sleep 5 DISPLAY=:20 startlxde & Ctrl-O, Enter, Ctrl-X sudo chmod +x /usr/bin/gol gol
Due to current limitations of UserLAnd's VNC, sound and OpenGL graphics are not available. Google is in the process of merging Android and ChromeOS VMs and hardware. This may provide better solutions in the future. www.androidauthority.com/chrome-os-running-on-pixel-3442496/
It doesnt work for me... After i did all correctly i open the terminal Linux and It keeps loading until It says that i have to restart the program... What should i do?
I recommend shutting down Linux, shutting down the Chromebook, restart the Chromebook, put the Chromebook online, start up Linux again, and try executing the gox script. If that fails, please let me know.
It may be an issue with the go script. Please copy and paste your go script (4:30). Here's the go script script I am currently testing for quick reference with the example user id being ruth. The original script is in the instructions below: Xephyr -br -fullscreen -resizeable :20 & sleep 3 sudo systemctl restart networking & sleep 3 sudo -u ruth DISPLAY=:20 startxfce4 & If retrying the install instructions and the script above fails, please copy and paste any error messages from the terminal here. -------------------- For your convenience I've included the complete instructions. This procedure requires a fresh Linux install on a Chromebook, which installs a base Debian container which we transform into Kali. 1. Base Install: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-4bKeaVw_eqc.html 2. Install Kali: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-CpGeCU4eG2o.html&lc=Ugwo_ICwIfUItHYJiet4AaABAg Here are the complete instructions: Install nano from a terminal: sudo apt install nano -y Delete everything in the repository source file and add the following line: sudo nano /etc/apt/sources.list deb http.kali.org/kali kali-rolling main contrib non-free Download Kali software key: sudo wget archive.kali.org/archive-key.asc -O /etc/apt/trusted.gpg.d/kali-archive-keyring.asc Update system: sudo apt update -y sudo apt full-upgrade -y Install software: sudo apt install kali-defaults -y sudo apt install kali-desktop-xfce -y sudo apt install synaptic -y sudo apt install xserver-xephyr -y Create gox script: sudo nano /usr/bin/gox Xephyr -br -fullscreen -resizeable :20 & sleep 5 sudo -u <user-id> DISPLAY=:20 startxfce4 &> /dev/null & Ctrl-O, Enter, Ctrl-X to save the file and exit nano. Make gox script executable: sudo chmod +x /usr/bin/gox Create gosyn script (may no longer be necessary, use only if needed): sudo nano /usr/bin/gosyn xhost + && sudo synaptic && xhost - Ctrl-O, Enter, Ctrl-X to save the file and exit nano. Make gosyn executable: sudo chmod +x /usr/bin/gosyn Shut down Linux, shut down Chromebook, and then restart Chromebook and start up Linux. Then execute gox script: gox Change launch command for Synaptic Package Manager to: gosyn
edit: fixed the issue. Please help. I am unable to install the desktop. This is what I have so far: @penguin:~$ sudo apt install kali-desktop-xfce -y Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: Unsatisfied dependencies: kali-desktop-xfce : Depends: libspa-0.2-bluetooth but it is not installable Recommends: blueman but it is not going to be installed Recommends: catfish but it is not going to be installed Recommends: gvfs-backends but it is not going to be installed Recommends: gvfs-fuse but it is not going to be installed Recommends: gnome-disk-utility but it is not going to be installed Recommends: gnome-system-tools but it is not going to be installed Recommends: kali-hidpi-mode but it is not going to be installed Recommends: kali-undercover but it is not going to be installed Recommends: lightdm-gtk-greeter-settings but it is not going to be installed Recommends: network-manager-fortisslvpn-gnome but it is not installable Recommends: network-manager-l2tp-gnome but it is not going to be installed Recommends: network-manager-openconnect-gnome but it is not going to be installed Recommends: network-manager-openvpn-gnome but it is not going to be installed Recommends: network-manager-pptp-gnome but it is not going to be installed Recommends: network-manager-vpnc-gnome but it is not going to be installed Recommends: xfce4-panel-profiles but it is not going to be installed Recommends: onboard but it is not going to be installed Recommends: xfce4-battery-plugin but it is not going to be installed Recommends: xfce4-clipman-plugin but it is not going to be installed Recommends: xfce4-cpufreq-plugin but it is not going to be installed Recommends: xfce4-datetime-plugin but it is not going to be installed Recommends: xfce4-diskperf-plugin but it is not going to be installed Recommends: xfce4-fsguard-plugin but it is not going to be installed Recommends: xfce4-netload-plugin but it is not going to be installed Recommends: xfce4-places-plugin but it is not going to be installed Recommends: xfce4-sensors-plugin but it is not going to be installed Recommends: xfce4-systemload-plugin but it is not going to be installed Recommends: xfce4-timer-plugin but it is not going to be installed Recommends: xfce4-verve-plugin but it is not going to be installed Recommends: xfce4-wavelan-plugin but it is not going to be installed Recommends: xfce4-xkb-plugin but it is not going to be installed Error: Unable to correct problems, you have held broken packages. I referenced another comment asking about the desktop and tried: apt list kali-desktop-xfce. Reply was: kali-desktop-xfce/kali-rolling 2024.4.6 all I am assuming that means I am not working with 2024.1 like you had spoken about, but I am unsure where to go from here.
I also continued with the rest of the video in the hopes that the error messages wouldn’t make a difference, and when I launch gox, the screen is black
Hi, Ruth, Great video, easy to follow and the install actually works! ;) One thing, my Lenovo P12 Pro has Android 14, and for whatever reason, I am unable to import or directly read files from external media (sdcard or USB flash drive). I tried the UserLand documentation on github, and other documentation, but still can't get data off the sdcard. I CAN read the data using Files and other Android utilities, but can't then copy that data to Linux. Do you have any advice on how to read files off an sdcard once you've installed Linux. I've tried both Debian and Kali on Userland, neither gives me access to sdcard or flash drive. Thanks!
Inserting an SD card or USB stick into an Android will autogenerate the Android file structure on the storage device. To move files in and out from an external SD card or USB stick: Find the storage id from a terminal (For example the output should include: .../mnt/media_rw/426B-9A39 so the storage id is 426B-9A39. 426B-9A39 is an example, your id will be different): cat /proc/mounts | grep vold File path to external storage example: /host-rootfs/storage/426B-9A39 /host-rootfs/storage/426B-9A39/Android/tech.ula/files In the files directory, you can read and write files. ---------------------- Here are some other directories you may wish to explore. To access both UserLAnd's internal and external storage locations from UserLAnd (All of these may not work on all Android devices depending on the model and the version): / /storage/internal /storage/sdcard /host-rootfs/storage/emulated/0 /host-rootfs/storage/emulated/0/Download /sdcard /sdcard/Download /Downloads For internal storage: /host-rootfs/storage/emulated/0 To read/write to internal or external storage, add /Android/data/Tech.ula/files to the end of the file path (Access will vary with model and version): /host-rootfs/storage/emulated/0/Android/data/Tech.ula/files /host-rootfs/storage/426B-9A39/Android/data/Tech.ula/files
Perfect just what I needed. Thank You! Another topic "Anyway to map keyboard shortcuts "? I think the chromebook blocks them, or the chromebook has weird key mapping.
The ChromeOS keyboard shortcuts can be edited and deactivated from the "Key Shortcuts" app on the ChromeOS side (can be opened with Ctrl+Search+S). ------------------------ To enable function keys: Go to chrome://flags in the Chrome browser from the ChromeOS side. Select Disabled in the drop-down next to "Enable improved keyboard shortcuts" flag. Restart Chromebook. Search+1 to Search+= are now the F1 to F12 keys. Another flag you may be interested in from ChromeOS Settings: Device > Keyboard and inputs > enable Treat top-row keys as function keys ------------------------ From the LXDE desktop, keyboard shortcuts can be created from Menu > Preferences > Setup Hot Keys Set up a shortcut to launch an application. For example, to set Ctrl+Alt+T to launch LXTerminal: 1. Go to the Programs tab 2. Click Create new action button (white box with star in it) 3. Click box under Hotkey 1 and do Ctrl+Alt+T 4. Under Command line: enter in lxterminal 5. Click Accept changes button (green check mark) 6. Click save button to apply changes (red arrow) 7. Now pressing Ctrl+Alt+T will open LXTerminal Set up a shortcut to perform an action. For example, to move a window with Alt+F7: 1. Go to the Actions tab 2. Click Create new action button (white box with star in it) 3. Click box under Hotkey 1 and do Alt+F7 4. Click Add an action button (white box with star in it) 5. From Name dropdown, select Move 6. Click Apply button 7. Click Accept changes button (green check mark) 8. Click save button to apply changes (red arrow) 9. Now pressing Alt+F7 will allow the mouse to move the window ------------------------ Some commands you may also be interested in: xmodmap xev sudo showkey -a xbindkeys (install xbindkeys)
There should be a key with a ~ on it near the top left of the keyboard under the esc key. You'll need to hold Shift in order to type the ~. Alternatively, you can do Ctrl+Shift+U on the keyboard and then type the Unicode for ~ which is 007e and press Enter. If this doesn't work in a specific app, then you can copy the tilde from a terminal and paste it into the app. ------------------ The character map from Menu > Accessories > Character Map shows the Unicode for any character. To search for a specific character, Search menu > select Find.
It sounds like the desktop may not have fully installed. Try repeating the install instructions: From the terminal: sudo apt update -y sudo apt dist-upgrade -y sudo apt install dialog -y sudo apt install kali-defaults -y sudo apt install kali-desktop-xfce -y sudo apt install synaptic -y sudo apt install nano -y Disconnect from the session, Stop Session, and close UserLAnd. Restart UserLAnd, and click on Kali in the Sessions menu and wait a few moments for the XFCE desktop to start up on it's own. For any Plugin Restart windows that come up, click on the Remove button. For the Synaptic Package Manager, create the gosyn script from a terminal: sudo nano /usr/bin/gosyn xhost + && sudo synaptic && xhost - Ctrl-O, Enter, and Ctrl-X to save the file and exit nano. Change launch command for Synaptic Package Manager to: gosyn Firefox Fix: Open Firefox and go to the URL about:config. Click Accept the Risk and Continue button. Enter sandbox into the search bar. For security.sandbox.content.tempDirSuffix, click the far right arrow to clear the value. Set any values with a number to 0 Set any true/false values to false. May require a reboot. ----------------------- If the internet is not working from the Linux side, then try the following fix for the internet: If resolv.conf doesn't exist, create it (it's resolve without an e on the end). If it does, it should have the two Google DNS nameservers listed below. Then reboot Linux. This should restore internet on the Linux side. cd /etc nano resolv.conf nameserver 8.8.8.8 nameserver 8.8.4.4 Ctrl-O, Enter, Ctrl-X to save the file and exit nano ----------------------- If the session has a connection failed, there is a known app killer issue starting with Android 12, also known as the Phantom Process Killer. As of Android 14, there is a new option in Android Settings for disabling the Phantom Process Killer (Android Settings > System > Developer options > in the Apps section enable the Disable child process restrictions option). Here's a video that explains the issue: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-N5Q5J36wIkc.html ----------------------- As a last resort: 1. There are a few options you can try. First, I recommend closing the UserLAnd app, power the device off and on, put the device online, open the UserLAnd app, if the Linux session is not already trying to start, try starting it again and wait a few minutes (20 minutes max). 2. If that fails, close UserLAnd, power the device off and on, put the device online, open UserLAnd, and click on the 3 dot menu in the top right corner from the UserLAnd main menu and select Clear All Support Files. After that, don't start the Kali session, start a different session from the Apps menu, such as Ubuntu. If Ubuntu successfully loads, disconnect and stop the Ubuntu session, and then try starting the Kali session (Try this process as many as 3 times). 3. If that fails, close UserLAnd, power the device off and on, put the device online, open UserLAnd, and from the Apps screen, click on the Refresh button in the top bar. Then try the 2nd process again. Starting a session should never take more than 20 minutes. If it does, then try the above procedures. ----------------------- You can also post a question on the UserLAnd GitHub site: github.com/CypherpunkArmory/UserLAnd/issues
To manually edit the Synaptic launch command from a terminal: cd /usr/share/applications ls cp synaptic.desktop ~/.local/share/applications/ cd ~/.local/share/applications ls nano synaptic.desktop This file may look scary. Scroll down until you see the line that starts with Exec (this may be close to the bottom) Change the launch command from this: Exec=synaptic-pkexec To this: Exec=gosyn Ctrl+O, Enter, and Ctrl+X to save the file and exit nano. Now Synaptic should open from Menu > Preferences > Synaptic Package Manager ------------------- NEVER edit: /usr/share/applications OK to edit: ~/.local/share/applications
ruth when i am using kali there is a problem that is unable to acquire dpkg frontend lock (:13 permission denied) can you please tell me how to resolve it
I have been playing around with Linux for years. This is an excellent video. You are a very good communicator, before anything else. This is a novel way to boot into Linux and which you methodically explain. One can *also* learn plenty of other things Linux as you show the main objective. And, let's face it, there aren't many ladies showing Linux on UTube. It's a welcome change to see variety. Well done. Thanks for sharing.
I've been working on scripts to allow the scale to be set when the desktop is started. Once the PC/Laptop install videos are done, I'll be making a video on scaling the desktop on a Chromebook with scripts. I've tested these scripts with Debian. The script below uses sommelier to set the desktop screen size with a set scale: To adjust the desktop size with this script, change the scale value. .5 is double the size, and 2 is half the size. If I wanted to make my screen 20% bigger, I would add 20 to 100 and then divide 100 by 120 which equals .83 which is 83%. What this means is my current screen is 83% as big as I would like it to be. sudo killall Xephyr &> /dev/null sudo rm /tmp/.X20-lock &> /dev/null sleep 3 sommelier -X --scale=.83 --glamor \ Xephyr -br -fullscreen -resizeable :20 \ &> /dev/null & sleep 3 sudo -u <user-id> env XDG_RUNTIME_DIR=/run/user/1000 \ GDK_BACKEND=x11 \ PATH=/usr/local/bin:/usr/bin:\ /usr/local/games:/usr/games \ DISPLAY=:20 startlxde &> /dev/null & This may adversely affect any programs that use previously used prefixes such as "env GDK_BACKEND=x11". Removing the prefix for the program should fix this. For more info on sommelier from a terminal (it's dash dash help): sommelier --help More advanced scaling scripts are in the pinned comment of my Linux On A Chromebook Without Rooting! RU-vid short: ru-vid.comqOAY9Yw1Enk For additional scaling options, you may be interested in: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-7fqpNJl3aDc.html
Debian moved the webpages used to navigate to the current live .iso file. My concern was for newbies getting lost before they reached the download. As a content creator, it'd be easier if all the downloads were on the Debian homepage.
@@ruthake I'm not a newbie and I still get lost in Debian's labyrinthine website. With all their computer fantastic knowledge and spectacular work in providing an damn fine version of Linux, it's an enigma as to why they are utterly rubbish they are have making an easily navigable website.
This comment has 2 parts, read the 2nd comment for the rest of the instructions. =================================== LINUX INSTALL OVERVIEW =================================== Whatever system you do have will NOT be affected during this install process. In other words, you will always have a working system during this whole procedure. 1. Download live ISO image 2. Create Debian Live USB Stick with the ISO file and a USB stick 3. Change boot order to boot from USB 1st 4. Use Debian Live USB Stick to install Debian on an SD card 5. Fixes and configurations ----------------------------------- Hardware Required: - USB stick (minimum of 8 GB) - SD or microSD card (I recommend 128 GB, but it can be smaller or larger) - USB to SD or USB to microSD card adapter ----------------------------------- Linux can be run from an SD card indefinitely, and you never have to run Linux on a hard drive/SSD if you don't want to. Installing Linux onto an SD card first is a good practice because it allows us to try/test Debian Linux before committing to it, work out any fixes, and also ensures that you always have a working system during the whole install process. This also makes installing Linux on a hard drive/SSD easier. Later on I will show how to use the Debian Live USB Stick as a portable system as well as a backup/recovery system! =================================== 1. DOWNLOAD ISO IMAGE =================================== If EtchDroid app IS available for your device from the Play Store (play.google.com/store/apps/details?id=eu.depau.etchdroid ): Install the ISO Image from the Android side. If EtchDroid app is NOT available from the Play Store: Install the ISO image from the UserLAnd Linux side. If you're not familiar with UserLAnd Linux, then watch my Linux on Android Without Rooting Playlist: ru-vid.com/group/PLuCbba_UxUz4ipj-EzXKzZPNGZWwi0rXk ----------------------------------- Current Debian Live ISO (if current version fails to install Linux, try a previous version. Ex. debian-live-12.2.0-amd64-lxde.iso): Scroll down to the list of live images and click the debian-live file ending in lxde.iso (the download is about 3 GB). Other desktops are available from this list. My videos will focus on the LXDE desktop: cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/ The live ISO allows us to try Debian Linux before installing, and it also gives us a more streamlined install procedure. ----------------------------------- Version Debian 12.2.0: cdimage.debian.org/mirror/cdimage/archive/12.2.0-live/amd64/iso-hybrid/ Scroll down to the list of live images and click debian-live-12.2.0-amd64-lxde.iso (the download is about 3 GB). Background: The version Debian 12.6.0 (debian-live-12.6.0-amd64-lxde.iso), will fail to install Linux. The error message is: "Command <i>/usr/sbin/bootloader-config</i> failed to finish in 600 seconds. There was no output from the command." Bug report (Same issue, different desktop, different day): lists.debian.org/debian-boot/2023/06/msg00074.html How does this make it through Debian/Calamares quality assurance and into publication? Only Debian knows for sure. Good news! Debian uses a best practice of archiving earlier versions which are readily available from their website: cdimage.debian.org/mirror/cdimage/archive/ =================================== 2. CREATE DEBIAN LIVE USB STICK =================================== EtchDroid Method: Install EtchDroid App: play.google.com/store/apps/details?id=eu.depau.etchdroid Enable EtchDroid app notifications if not already enabled: Android Settings > Apps > See all apps > EtchDroid > Notifications > enable All EtchDroid notifications Plug USB stick into Android device. From the EtchDroid App: Select Write raw image or ISO. Select .iso file. Select USB stick. Click OK button to allow EtchDroid to access USB stick. Click circle button in the bottom right. Click FLASH IMAGE button. Monitor progress through notifications. ----------------------------------- Generic Method: Plug USB stick into Android device Format USB Stick as FAT32: Android Settings > Storage > click the This device pull-down and select the USB stick Click 3 dot menu button from the top right and select Format. Click Format button, and click the Format button again to confirm. Click Done button when done. Folders autogenerated on USB stick can be ignored. From Linux inside the UserLAnd app, open a terminal and extract the files from the .iso file and place them in the Downloads folder (watch Linux on Android Without Rooting! Playlist if you are unfamiliar with the UserLAnd app: ru-vid.com/group/PLuCbba_UxUz4ipj-EzXKzZPNGZWwi0rXk ): 7z x <.iso file name> -o/Downloads/HOLD From Files app on the Android side, copy ALL the extracted files to the USB Stick: Internal storage > Download > HOLD Copy everything inside HOLD folder to the USB stick (Copy folders individually if an error occurs). Fix file '/boot/grub/splash.png not found' From the USB files, copy splash images from /isolinux to the /boot/grub =================================== 3. CHANGE BOOT ORDER =================================== When booting, "Boot Menu" allows us to temporarily change the boot order for the current boot, to boot from USB first. "Setup" allows us to permanently change the boot order to boot from USB first (I STRONGLY recommend taking a picture with a phone before permanently changing the boot order). To choose what to boot from or access the boot order, key(s) need to be pressed before the computer completely starts up. The key(s) and screens for choosing what to boot from and changing the boot order will vary for every system. Common places the key(s) can be found are: - Screen that pops up before the computer completely boots up - Written somewhere on the computer - Search online for "<manufacture> <model> boot order" At the GRUB menu, press Enter to start Debian Linux, the first item should already be selected (Live system (amd64)). Live versions will not start as fast, be patient. =================================== 4. INSTALL DEBIAN ONTO AN SD CARD =================================== Disable Screensaver (prevents install interference): Menu > Preferences > XScreenSaver Settings Mode pull-down > select Disable Screen Saver Plug in the SD Card, click OK button for any window that pops up and close any file manager windows. Install Linux onto the SD card: Double click Install Debian icon on the Desktop. Select language > click Next button Location: Select Region & Zone > click Next button Keyboard: Select Keyboard layout > click Next button Partitions: Click the Select storage device pull-down and select the SD card. Make sure the SD card is selected or else the install will wipe out your main system! Select Manual partitioning > click Next button Click New Partition Table button > select GUID Partition Table (GPT) > click OK button Select Free Space > click Create button > set the following: Size: 500 MiB File System: fat32 Mount Point: /boot/efi FS Label: boot Flags: check the boot flag Click the OK button. Select Free Space > click Create button > set the following: Size: No change (leave the rest of the space to this partition) File System: ext4 Mount Point: / FS Label: main Flags: don't check any flags Click the OK button Click the Next button. Users: Set desired names and password. Check the box to Log in automatically without asking for the password. Click the Next button. Summary: Last chance to check that Linux is being installed on the SD card and NOT the main system. When ready, click the Install button. When the install is done, uncheck the Restart now box and click the Done button. =================================== 5. FIXES & CONFIGURATIONS =================================== Prevent SD card wear and tear: - No swap partition (already done during install setup) - Send tmp & log files to RAM - Disable journaling ----------------------------------- Send tmp and log files to RAM (prevents SD card wear and tear): Unplug the SD card from the computer. Plug the SD card back into the computer. Click the OK button for the window that pops up and close any file manager windows. Menu > select Run > execute sudo pcmanfm to open the file manager with root. From the file manager window, go to /media/user/main/etc Right click fstab file and open it with Mousepad. File menu > select Save As > save the copy as fstab.bak Close Mousepad. Open original fstab file with Mousepad again, and add the following lines: tmpfs /var/log tmpfs defaults,noatime 0 0 tmpfs /var/tmp tmpfs defaults,noatime 0 0 tmpfs /tmp tmpfs defaults,noatime 0 0 File menu > select Save > close Mousepad ----------------------------------- Further instructions are in the 2nd comment.
Disable journaling (prevents SD card wear and tear): Open a terminal from Menu > System Tools > LXTerminal (Ctrl+Shift++, Ctrl+Shift+- to temporarily adjust text size). Switch to root user: sudo su List mounted file systems: df -h /dev/sdb2 is an example. The SD card will be the last device plugged in so the Filesystem will be /dev/sd<highest letter>2 and it will be Mounted on /media/user/main umount /dev/sdb2 List file system features: debugfs -R features /dev/sdb2 Disable journaling (no ^ would enable journaling): tune2fs -O ^has_journal /dev/sdb2 ----------------------------------- Fix SD Card Not Booting Up: Connect to the internet (Menu > Preferences > Connman Settings > click the icon that pops up in the bottom right of the taskbar): - Wired (Ethernet or USB Tethering from an Android device. See video for USB Tethering 30:41) - Wireless if available (WiFi or WiFi Dongle) Open a terminal from Menu > System Tools > LXTerminal (Ctrl+Shift++, Ctrl+Shift+- to temporarily adjust text size): sudo apt update -y sudo apt install gparted -y Open GParted from Menu > System Tools > GParted: Click pull-down from top right and select the SD Card. SD card will have fat32 and ext4 partitions we made when we installed Linux earlier. Right click fat32 partition > select Manage Flags Uncheck boot flag (msftdata flag will be automatically checked) Click Close button and close GParted. Unplug SD card. Plug SD card back in. Click OK button for any window that pops up. From the window that only has the EFI folder (/media/user/BOOT/EFI): Copy ALL files from /EFI/Debian to /EFI/boot Rename /EFI/boot/grubx64.efi to /EFI/boot/BOOTx64.efi From /EFI/Debian copy grubx64.efi to /EFI/boot Close out of the file manager. Open GParted from Menu > System Tools > GParted: Click pull-down from top right and select the SD card. Right click fat32 partition > select Manage Flags Check boot flag (esp flag will also automatically be checked) Click Close button and close GParted. Shut down Linux from Menu > Logout > Shutdown Unplug Debian Live USB Stick, leave the SD card plugged in, and turn the computer back on to start up Linux from the SD card! ----------------------------------- Update (This fixes issues with things not working such as there being no Wireless option): Connect to the internet (Menu > Preferences > Connman Settings > click the icon that pops up in the bottom right of the taskbar): Wired (Ethernet or USB Tethering from an Android device. See video for USB Tethering 30:41) Wireless if available (WiFi or WiFi Dongle) Open a terminal from Menu > System Tools > LXTerminal (Ctrl+Shift++, Ctrl+Shift+- to temporarily adjust text size): Update software index list (Enter in the password that was set during the install. The password will not be visible while typing. After typing in the password, press Enter to execute the command. For forgotten password, see below.): sudo apt update -y Upgrade already installed packages: sudo apt dist-upgrade -y Reboot Linux from Menu > Logout > Reboot Check to see if everything is working properly. If something is still not working properly, try updating the kernel: Connect to the internet. Open a terminal from Menu > System Tools > LXTerminal: Check current kernel version in use: uname -r List available kernel updates: apt-cache search linux-image | grep "PCs (signed)" Update to latest kernel version, for example: sudo apt install linux-image-6.9.7+bpo-amd64 Reboot Linux from Menu > Logout > Reboot Check to see if everything is working properly. ----------------------------------- Configure Resolution: Generally, it is best to adjust app resolution as opposed to the display resolution which can also be changed from: Menu > Preferences > Monitor Settings ----------------------------------- Configure Audio (this also fixes no sound or loss of sound when switching an app to fullscreen): Menu > Sound & Video > PulseAudio Volume Control Go to the Configuration tab. Click the Profile pull-down and select a Profile. You can try out each option until one works. If switching an app to fullscreen results in a loss of audio: Take the app out of fullscreen. Close the app. Open a terminal from Menu > System Tools > LXTerminal Reset PulseAudio: systemctl --user restart pulseaudio Select a different sound Profile from Menu > Sound & Video > PulseAudio Volume Control: Go to the Configuration tab. Click the Profile pull-down and select a Profile. To quickly test sound, open a terminal from Menu > System Tools > LXTerminal: sudo apt install alsa-utils -y speaker-test =================================== PASSWORD WORKAROUND =================================== At the GRUB menu, press the Down arrow key and then the Up arrow key to prevent the system from booting up. Press E to edit the startup configuration. At the end of the line that starts with linux, add the following: init=/bin/bash Ctrl+X From the terminal: Press Enter mount -o remount,rw / passwd <user-id> Enter in the new password. umount / Alt+Ctrl+Del
The Live install is more streamlined. It can be used as a portable system for those on the go. Additionally, it can be used to create a full backup system on a USB stick. Video coming soon!
ruth i have done everything done but after giving usr which is gox for you iam getting a tab opened but display is not happening its only black screen iam not getting kali display what might be the problem
It may be an issue with the go script. Please copy and paste your go script (4:30). Here's the go script script I am currently using for quick reference with the example user id being ruth. The original script is in the instructions below: Xephyr -br -fullscreen -resizeable :20 & sleep 3 sudo systemctl restart networking &> /dev/null & sleep 3 sudo -u ruth DISPLAY=:20 startxfce4 &> /dev/null & -------------------- For your convenience I've included the complete instructions. This procedure requires a fresh Linux install on a Chromebook, which installs a base Debian container which we transform into Kali. 1. Base Install: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-4bKeaVw_eqc.html 2. Install Kali: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-CpGeCU4eG2o.html&lc=Ugwo_ICwIfUItHYJiet4AaABAg Here are the complete instructions: Install nano from a terminal: sudo apt install nano -y Delete everything in the repository source file and add the following line: sudo nano /etc/apt/sources.list deb http.kali.org/kali kali-rolling main contrib non-free Download Kali software key: sudo wget archive.kali.org/archive-key.asc -O /etc/apt/trusted.gpg.d/kali-archive-keyring.asc Update system: sudo apt update -y sudo apt full-upgrade -y Install software: sudo apt install kali-defaults -y sudo apt install kali-desktop-xfce -y sudo apt install synaptic -y sudo apt install xserver-xephyr -y Create gox script: sudo nano /usr/bin/gox Xephyr -br -fullscreen -resizeable :20 & sleep 5 sudo -u <user-id> DISPLAY=:20 startxfce4 &> /dev/null & Ctrl-O, Enter, Ctrl-X to save the file and exit nano. Make gox script executable: sudo chmod +x /usr/bin/gox Create gosyn script (may no longer be necessary, use only if needed): sudo nano /usr/bin/gosyn xhost + && sudo synaptic && xhost - Ctrl-O, Enter, Ctrl-X to save the file and exit nano. Make gosyn executable: sudo chmod +x /usr/bin/gosyn Shut down Linux, shut down Chromebook, and then restart Chromebook and start up Linux. Then execute gox script: gox Change launch command for Synaptic Package Manager to: gosyn
To install third party software from a terminal: sudo apt install ./<file-name>.deb Here's a video example with VS Code: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-5gfFBlYUMyA.html
poswalraghu@penguin:~$ gox /usr/bin/gox: line 1: xephyr: command not found access control disabled, clients can connect from any host sudo: synaptic: command not found poswalraghu@penguin:~$ please help to fix my problem 😥😥
I have never purchased a used/refurbished Chromebook. This is the list of ChromeOS systems supporting Linux on ChromeOS: www.chromium.org/chromium-os/chrome-os-systems-supporting-linux/ If that option is not available, there are more aggressive methods of installing Linux. The Chrome Unboxed Team covers alternative methods for installing Linux on Chromebooks. Chrome Unboxed Links: www.youtube.com/@chromeunboxed chromeunboxed.com/
To access a USB stick from Linux: Open the ChromeOS Files app and plug in the USB stick. Right click the USB stick and select Share with Linux. From the Linux side, the USB stick will be available at: /mnt/chromeos/removable To unshare any shared storage with Linux: Open ChromeOS Settings. Go to About ChromeOS > Linux development environment > Manage shared folders Click the x next to the name of the storage to unshare it. ChromeOS does not currently support CDs and DVDs.
This comment has 2 parts, read the 2nd comment for the rest of the instructions. =================================== LINUX INSTALL OVERVIEW =================================== Whatever system you do have will NOT be affected during this install process. In other words, you will always have a working system during this whole procedure. 1. Download live ISO image 2. Create Debian Live USB Stick with the ISO file and a USB stick 3. Change boot order to boot from USB 1st 4. Use Debian Live USB Stick to install Debian on an SD card 5. Fixes and configurations ----------------------------------- Hardware Required: - USB stick (minimum of 8 GB) - SD or microSD card (I recommend 128 GB, but it can be smaller or larger) - USB to SD or USB to microSD card adapter ----------------------------------- Linux can be run from an SD card indefinitely, and you never have to run Linux on a hard drive/SSD if you don't want to. Installing Linux onto an SD card first is a good practice because it allows us to try/test Debian Linux before committing to it, work out any fixes, and also ensures that you always have a working system during the whole install process. This also makes installing Linux on a hard drive/SSD easier. Later on I will also show how to use the Debian Live USB Stick as a portable, backup/recovery system! =================================== 1. DOWNLOAD ISO IMAGE =================================== If you want to use the Chromebook Recovery Utility Method (a Chrome browser extension) to create the Debian Live USB Stick (chromewebstore.google.com/detail/chromebook-recovery-utili/pocpnlppkickgojjlmhdmidojbmbodfm ): Download the ISO Image using the Chrome browser on the ChromeOS side. If you want to use the Generic Method to create the Debian Live USB Stick: Download the ISO image from the Linux side. If you're not familiar with Linux on a Chromebook, then watch my Linux On A Chromebook Without Rooting! Playlist: ru-vid.com/group/PLuCbba_UxUz6_2D5fWnDzLgxfW3Q6J3yJ ----------------------------------- Current Debian Live ISO (if current version fails to install Linux, try a previous version. Ex. debian-live-12.2.0-amd64-lxde.iso): Scroll down to the list of live images and click the debian-live file ending in lxde.iso (the download is about 3 GB). Other desktops are available from this list. My videos will focus on the LXDE desktop: cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/ The live ISO allows us to try Debian Linux before installing, and it also gives us a more streamlined install procedure. ----------------------------------- Version Debian 12.2.0: cdimage.debian.org/mirror/cdimage/archive/12.2.0-live/amd64/iso-hybrid/ Scroll down to the list of live images and click debian-live-12.2.0-amd64-lxde.iso (the download is about 3 GB). Background: The version Debian 12.6.0 (debian-live-12.6.0-amd64-lxde.iso), will fail to install Linux. The error message is: "Command <i>/usr/sbin/bootloader-config</i> failed to finish in 600 seconds. There was no output from the command." Bug report (Same issue, different desktop, different day): lists.debian.org/debian-boot/2023/06/msg00074.html How does this make it through Debian/Calamares quality assurance and into publication? Only Debian knows for sure. Good news! Debian uses a best practice of archiving earlier versions which are readily available from their website: cdimage.debian.org/mirror/cdimage/archive/ =================================== 2. CREATE DEBIAN LIVE USB STICK =================================== Chromebook Recovery Utility Method: From the Chrome browser, in the Chrome Web Store, add the Chromebook Recovery Utility browser extension: chromewebstore.google.com/detail/chromebook-recovery-utili/pocpnlppkickgojjlmhdmidojbmbodfm Click the Extensions button (puzzle piece icon at the top right of the Chrome browser). Select Chromebook Recovery Utility. Click the gear icon at the top right of the window > select Use local image Select the .iso file (if .iso file isn't visible, zip it, and try selecting it again) > Click Open button Plug the USB stick into the Chromebook. Click the Select pull-down and select the USB Stick. Click the Continue button from the bottom right > click the Create now button Click the Done button when finished. Open the Files app: If the USB stick is mounted, click the eject button. Unplug the USB stick from the Chromebook. ----------------------------------- Generic Method: Plug the USB stick into the Chromebook. Format USB Stick as FAT32: Open Files app from Chrome side > right click USB stick > select Format device Name the USB Drive (can be anything) and select FAT32 for the Format. Click Erase and Format button. From Linux, open a terminal and extract the files from the .iso file and place them in the home directory, inside a folder called hold. Then copy the splash images so they are in the correct folder (Watch Linux On A Chromebook Without Rooting! Playlist if you are unfamiliar with Linux on a Chromebook: ru-vid.com/group/PLuCbba_UxUz6_2D5fWnDzLgxfW3Q6J3yJ ): 7z x <.iso file name> -o$HOME/hold cp ~/hold/isolinux/splash* ~/hold/boot/grub Open Files app from the ChromeOS side: Linux files > hold Click 3 dot menu button from top right > select Show hidden files Ctrl+A to select all files, Ctrl+C to copy all files. Select the USB Stick > Ctrl+V to paste everything When everything is copied, click the eject button next to the USB stick. =================================== 3. CHANGE BOOT ORDER =================================== When booting, "Boot Menu" allows us to temporarily change the boot order for the current boot, to boot from USB first. "Setup" allows us to permanently change the boot order to boot from USB first (I STRONGLY recommend taking a picture with a phone before permanently changing the boot order). To choose what to boot from or access the boot order, key(s) need to be pressed before the computer completely starts up. The key(s) and screens for choosing what to boot from and changing the boot order will vary for every system. Common places the key(s) can be found are: - Screen that pops up before the computer completely boots up - Written somewhere on the computer - Search online for "<manufacture> <model> boot order" At the GRUB menu, press Enter to start Debian Linux, the first item should already be selected (Live system (amd64)). Live versions will not start as fast, be patient. =================================== 4. INSTALL DEBIAN ONTO AN SD CARD =================================== Disable Screensaver (prevents install interference): Menu > Preferences > XScreenSaver Settings Mode pull-down > select Disable Screen Saver Plug in the SD Card, click OK button for any window that pops up and close any file manager windows. Install Linux onto the SD card: Double click Install Debian icon on the Desktop. Select language > click Next button Location: Select Region & Zone > click Next button Keyboard: Select Keyboard layout > click Next button Partitions: Click the Select storage device pull-down and select the SD card. Make sure the SD card is selected or else the install will wipe out your main system! Select Manual partitioning > click Next button Click New Partition Table button > select GUID Partition Table (GPT) > click OK button Select Free Space > click Create button > set the following: Size: 500 MiB File System: fat32 Mount Point: /boot/efi FS Label: boot Flags: check the boot flag Click the OK button. Select Free Space > click Create button > set the following: Size: No change (leave the rest of the space to this partition) File System: ext4 Mount Point: / FS Label: main Flags: don't check any flags Click the OK button Click the Next button. Users: Set desired names and password. Check the box to Log in automatically without asking for the password. Click the Next button. Summary: Last chance to check that Linux is being installed on the SD card and NOT the main system. When ready, click the Install button. When the install is done, uncheck the Restart now box and click the Done button. =================================== 5. FIXES & CONFIGURATIONS =================================== Prevent SD card wear and tear: - No swap partition (already done during install setup) - Send tmp & log files to RAM - Disable journaling ----------------------------------- Send tmp and log files to RAM (prevents SD card wear and tear): Unplug the SD card from the computer. Plug the SD card back into the computer. Click the OK button for the window that pops up and close any file manager windows. Menu > select Run > execute sudo pcmanfm to open the file manager with root. From the file manager window, go to /media/user/main/etc Right click fstab file and open it with Mousepad. File menu > select Save As > save the copy as fstab.bak Close Mousepad. Open original fstab file with Mousepad again, and add the following lines: tmpfs /var/log tmpfs defaults,noatime 0 0 tmpfs /var/tmp tmpfs defaults,noatime 0 0 tmpfs /tmp tmpfs defaults,noatime 0 0 File menu > select Save > close Mousepad ----------------------------------- Further instructions are in the 2nd comment.
Disable journaling (prevents SD card wear and tear): Open a terminal from Menu > System Tools > LXTerminal (Ctrl+Shift++, Ctrl+Shift+- to temporarily adjust text size). Switch to root user: sudo su List mounted file systems: df -h /dev/sdb2 is an example. The SD card will be the last device plugged in so the Filesystem will be /dev/sd<highest letter>2 and it will be Mounted on /media/user/main umount /dev/sdb2 List file system features: debugfs -R features /dev/sdb2 Disable journaling (no ^ would enable journaling): tune2fs -O ^has_journal /dev/sdb2 ----------------------------------- Fix SD Card Not Booting Up: Connect to the internet (Menu > Preferences > Connman Settings > click the icon that pops up in the bottom right of the taskbar): - Wired (Ethernet or USB Tethering from an Android device. See video for USB Tethering 30:12) - Wireless if available (WiFi or WiFi Dongle) Open a terminal from Menu > System Tools > LXTerminal (Ctrl+Shift++, Ctrl+Shift+- to temporarily adjust text size): sudo apt update -y sudo apt install gparted -y Open GParted from Menu > System Tools > GParted: Click pull-down from top right and select the SD Card. SD card will have fat32 and ext4 partitions we made when we installed Linux earlier. Right click fat32 partition > select Manage Flags Uncheck boot flag (msftdata flag will be automatically checked) Click Close button and close GParted. Unplug SD card. Plug SD card back in. Click OK button for any window that pops up. From the window that only has the EFI folder (/media/user/BOOT/EFI): Copy ALL files from /EFI/Debian to /EFI/boot Rename /EFI/boot/grubx64.efi to /EFI/boot/BOOTx64.efi From /EFI/Debian copy grubx64.efi to /EFI/boot Close out of the file manager. Open GParted from Menu > System Tools > GParted: Click pull-down from top right and select the SD card. Right click fat32 partition > select Manage Flags Check boot flag (esp flag will also automatically be checked) Click Close button and close GParted. Shut down Linux from Menu > Logout > Shutdown Unplug Debian Live USB Stick, leave the SD card plugged in, and turn the computer back on to start up Linux from the SD card! ----------------------------------- Update (This fixes issues with things not working such as there being no Wireless option): Connect to the internet (Menu > Preferences > Connman Settings > click the icon that pops up in the bottom right of the taskbar): Wired (Ethernet or USB Tethering from an Android device. See video for USB Tethering 30:12) Wireless if available (WiFi or WiFi Dongle) Open a terminal from Menu > System Tools > LXTerminal (Ctrl+Shift++, Ctrl+Shift+- to temporarily adjust text size): Update software index list (Enter in the password that was set during the install. The password will not be visible while typing. After typing in the password, press Enter to execute the command. For forgotten password, see below.): sudo apt update -y Upgrade already installed packages: sudo apt dist-upgrade -y Reboot Linux from Menu > Logout > Reboot Check to see if everything is working properly. If something is still not working properly, try updating the kernel: Connect to the internet. Open a terminal from Menu > System Tools > LXTerminal: Check current kernel version in use: uname -r List available kernel updates: apt-cache search linux-image | grep "PCs (signed)" Update to latest kernel version, for example: sudo apt install linux-image-6.9.7+bpo-amd64 Reboot Linux from Menu > Logout > Reboot Check to see if everything is working properly. ----------------------------------- Configure Resolution: Generally, it is best to adjust app resolution as opposed to the display resolution which can also be changed from: Menu > Preferences > Monitor Settings ----------------------------------- Configure Audio (this also fixes no sound or loss of sound when switching an app to fullscreen): Menu > Sound & Video > PulseAudio Volume Control Go to the Configuration tab. Click the Profile pull-down and select a Profile. You can try out each option until one works. If switching an app to fullscreen results in a loss of audio: Take the app out of fullscreen. Close the app. Open a terminal from Menu > System Tools > LXTerminal Reset PulseAudio: systemctl --user restart pulseaudio Select a different sound Profile from Menu > Sound & Video > PulseAudio Volume Control: Go to the Configuration tab. Click the Profile pull-down and select a Profile. To quickly test sound, open a terminal from Menu > System Tools > LXTerminal: sudo apt install alsa-utils -y speaker-test =================================== PASSWORD WORKAROUND =================================== At the GRUB menu, press the Down arrow key and then the Up arrow key to prevent the system from booting up. Press E to edit the startup configuration. At the end of the line that starts with linux, add the following: init=/bin/bash Ctrl+X From the terminal: Press Enter mount -o remount,rw / passwd <user-id> Enter in the new password. umount / Alt+Ctrl+Del
I usually don't comment on any vedio but this time this vedio helped me a lot and much thankful to you again thank you so much for such a beautiful Vedio... almost trying from 5 months to setup Kali in Chromebook but always i failed to do that but this time your vedio helped me and this done I'm done with Kali set-up thanks again...❤
So I followed all the steps but when I restart the Chromebook and start the terminal, the Linux container times out before opening the terminal. What do I do ?
Google is merging the hardware, AI, Chromebook, and Android divisions. ChromeOS is also being separated from the Chrome browser. You may have received an update that I haven't received yet. We have very recently experienced several issues when starting the Kali desktop. Here are a few potential solutions: First, I recommend shutting down Linux, shutting down the Chromebook, restart the Chromebook, put the Chromebook online, start up Linux again, and try executing the gox script. --------------------- If that fails, I recommend trying to start Kali from a crosh terminal: Termina is a virtual machine (NOT the terminal) and takes a moment to start up. As an alternative to logging into the container with the <user-id> you can log in with root (lxc exec penguin -- bash (it's dash dash space bash)). If echo $DISPLAY is not blank, then it doesn't need to be set with DISPLAY=:0 . Shut down Linux normally. Reboot the Chromebook. Ctrl+Alt+T to open a Crosh terminal: vmc list vmc start termina lxc list lxc start penguin lxc list lxc exec penguin su - <user-id> echo $DISPLAY DISPLAY=:0 export DISPLAY echo $DISPLAY sudo mv /etc/environment /etc/environment.bak gox If a window asking for a password pops up, you can close it. --------------------- The mergers involving ChromeOS and Kali rolling updates, make running Kali Linux more challenging. The below script is a work in progress which I am currently using: sudo rm /tmp/.X20-lock &> /dev/null Xephyr -br -fullscreen -resizeable :20 & sleep 3 sudo systemctl restart networking &> /dev/null & sleep 3 sudo -u <user-id> DISPLAY=:20 startxfce4 &> /dev/null & --------------------- Crosh and Terminal are also available through the ChromeOS Chrome Browser with the following URLs: chrome-untrusted://crosh chrome-untrusted://terminal
I'm trying to do this with my Chromebook and every time I get to the command where you says sudo space nano space sources.list it says no command is found. Any solutions?
Nano may not be installed. To verify if nano is installed from a terminal (if apt doesn't show [installed] and which doesn't give an output, then nano is not installed): apt list nano which nano To install nano: sudo apt install nano -y
