By default, the Kali Linux CuBox image does not contains the kali-linux-default metapackage which is often found in Kali platforms. If you wish to install extra tools please refer to our metapackages page.
Cubietruck – Kali Linux
By default, the Kali Linux CubieTruck image contains the kali-linux-default metapackage similar to most other platforms. If you wish to install extra tools please refer to our metapackages page.
There are two revisions of the A20. Since Feb 2014 it is RevB. The Rev state is not printed on the board and is not retrievable from the SoC. There is also no information regarding the differences of these revisions. There is evidence of different behavior and boot problems with older kernel on RevB cubietrucks.
The cubietruck is prepared to power directly a 3.5" HDD with Cubietech's optional 3.5 inch HDD addon package. Unlike other sunxi boards that feature an onboard SATA-power-connector suitable for powering 2.5" disks the Cubie solution is able to feed 3.5 disks that need both 5V/12V from a single 12V power source (using a 5.5/2.1 power barrel). The Addon board contains a step-down converter supplying 5V on 2 USB type A ports (from where you can feed the board using an USB-to-4/1.7mm-cable) and provides 12V on a JST XH 0.1"/2.5mm header. An identical header on the Cubietruck routes the 12V to the SATA connector on the board's edge (see gallery below).
Check the Source.list file to contain the repository entries. You can find them at - -use/kali-linux-sources-list-repositories.After editing the file, save it and run "apt-get update && apt-get upgrade". Now run "apt-get install linux-headers-$(uname -r)"
I have noted that Fedora does not have build in support for the SUNXI GPIO pins provided in the cubietruck but in this project I will be using the Raspberry pi for this and using the Cubietruck for Application development, training and documentation along with general studies such as Shell scripting and Assembley/Gforth and C++ language training.
i3 has steadily gained popularity as a Windows tiling manager of choice for a couple of reasons. Here are some of the salient reasons why i3 is one of the most popular tiling window managers.if(typeof ez_ad_units != 'undefined')ez_ad_units.push([[250,250],'linuxopsys_com-medrectangle-4','ezslot_5',103,'0','0']);__ez_fad_position('div-gpt-ad-linuxopsys_com-medrectangle-4-0');
When it asks which packages to install, showing the possible options, only hit enter and it will install all the necessary ones.if(typeof ez_ad_units != 'undefined')ez_ad_units.push([[336,280],'linuxopsys_com-box-4','ezslot_3',104,'0','0']);__ez_fad_position('div-gpt-ad-linuxopsys_com-box-4-0');
On Debian and Ubuntu distributions, run the following commands to install the i3 window manager. These commands were tried on Debian 11 and Ubuntu 22.04if(typeof ez_ad_units != 'undefined')ez_ad_units.push([[336,280],'linuxopsys_com-banner-1','ezslot_6',105,'0','0']);__ez_fad_position('div-gpt-ad-linuxopsys_com-banner-1-0');
Once you are logged into your system, a blank screen will be displayed. To the right hand side, a window pane will prompt you to either generate a configuration file which will be saved in your home directory ( in this case /home/linuxopsys/.config/i3/config) or use the default configuration which will be placed in the /etc/i3 directory.
Next, you will be required to specify the modifier key. also referred to as the $mod key. This can either be the Windows logo key or the Alt Key. Here we will opt to go with the Windows key as the $mod key.if(typeof ez_ad_units != 'undefined')ez_ad_units.push([[336,280],'linuxopsys_com-large-leaderboard-2','ezslot_7',106,'0','0']);__ez_fad_position('div-gpt-ad-linuxopsys_com-large-leaderboard-2-0');
Sample i3 config file for reference:if(typeof ez_ad_units != 'undefined')ez_ad_units.push([[250,250],'linuxopsys_com-leader-1','ezslot_13',107,'0','0']);__ez_fad_position('div-gpt-ad-linuxopsys_com-leader-1-0');
If you press $mod + ENTER again, the new terminal will be opened adjacent to the existing terminal splitting the screen into half. From what you can see, the workspace is split into two halves ( horizontally be default ).if(typeof ez_ad_units != 'undefined')ez_ad_units.push([[250,250],'linuxopsys_com-large-mobile-banner-1','ezslot_14',108,'0','0']);__ez_fad_position('div-gpt-ad-linuxopsys_com-large-mobile-banner-1-0');
Here the windows are such that every window gets an equal amount of space in the container. splith arranges the windows horizontally ( windows are arranged one beside each other) while splitv arranges them vertically ( windows are arranges one on top of each other )if(typeof ez_ad_units != 'undefined')ez_ad_units.push([[300,250],'linuxopsys_com-large-mobile-banner-2','ezslot_15',110,'0','0']);__ez_fad_position('div-gpt-ad-linuxopsys_com-large-mobile-banner-2-0');
This is just the same as stacking, however, the list of windows at the top is made up of a vertically split single line.if(typeof ez_ad_units != 'undefined')ez_ad_units.push([[300,250],'linuxopsys_com-leader-4','ezslot_18',111,'0','0']);__ez_fad_position('div-gpt-ad-linuxopsys_com-leader-4-0');
If two or more application windows are present, they are tiled vertically as shown. Obviously, the workspaces seem too congested.if(typeof ez_ad_units != 'undefined')ez_ad_units.push([[250,250],'linuxopsys_com-leader-2','ezslot_16',112,'0','0']);__ez_fad_position('div-gpt-ad-linuxopsys_com-leader-2-0');
Other basic command shortcuts include:if(typeof ez_ad_units != 'undefined')ez_ad_units.push([[250,250],'linuxopsys_com-mobile-leaderboard-1','ezslot_19',113,'0','0']);__ez_fad_position('div-gpt-ad-linuxopsys_com-mobile-leaderboard-1-0');
Close an application window: $mod + shift + qif(typeof ez_ad_units != 'undefined')ez_ad_units.push([[336,280],'linuxopsys_com-narrow-sky-1','ezslot_22',114,'0','0']);__ez_fad_position('div-gpt-ad-linuxopsys_com-narrow-sky-1-0');
Exit i3 windows manager: $mod + Shift + eif(typeof ez_ad_units != 'undefined')ez_ad_units.push([[300,250],'linuxopsys_com-mobile-leaderboard-2','ezslot_21',115,'0','0']);__ez_fad_position('div-gpt-ad-linuxopsys_com-mobile-leaderboard-2-0');
I got a strange problem concerning dovecot.My dovecot was working flawlessly on my cubietruck until yesterday, when I upgraded from debian/jessie to debian/stretch (armhf)./var is symlinked to another mounted drive (mountpoint /extended): /var -> /extended/hostname/var 2ff7e9595c
Comments