fbcs.over-blog.com/
20 Février 2021
Other distributions¶. Most Linux distributions have Sphinx in their package repositories. Usually the package is called python3-sphinx, python-sphinx or sphinx.Be aware that there are at least two other packages with sphinx in their name: a speech recognition toolkit (CMU Sphinx) and a full-text search database (Sphinx search). Ubuntu on Windows allows you to use Ubuntu Terminal and run Ubuntu command line utilities including bash, ssh, git, apt and many more. Please note that Windows 10 S does not support running this app. To launch, use 'ubuntu' on the command-line prompt (cmd.exe), or click on the Ubuntu tile in the Start Menu. Lollypop is a feature-packed GTK music player and manager for Linux and is a fantastic alternative to Rhythmbox, Ubuntu's stock music app. The player integrates flawlessly with the GNOME Shell desktop and has all the essential features you might need, i.e. It's easy to add music, browse music, play music, create playlists, and so on. This release is a major milestone in the 'Ultimate' series of distributions or distros for short; starting from this version forward upgrading from 1.4 to 1.5 etc. Will be a click of the mouse away and without downloading 2GB every time. Full releases will still be available for download. This version you will find to be much faster & more responsive; due to the many enhancements to the kernel and being based on Ubuntu Feisty Fawn.
How To Install Ubuntu 20.04 LTS or any other UbuntuIn this tutorial video, I show step-by-step how to install Ubuntuusing a USB drive or How To Install Ubunt.
Usually I deploy FreeBSD on my servers, but recently a collegue at workwanted to set up an Ubuntu system with software RAID1, which is mirroring.I think the Ubuntu Server Edition does this out of the box,but out of curiosity I researched how to do this for the 10.10 Desktop Edition.
Remember, mirroring is never a substitute for backup.Always keep recent backups of your data at a remote location,and restore them regularly on test systems to verify their correctness.
The system I use has two SATA disks of the same type and size.Ubuntu sees them as /dev/sda and /dev/sdb.During the installation the system needs a working Internet connection.
First, prepare a Ubuntu USB stick (or CD) and boot from it.When the desktop comes up, do not start the installler,but instead launch the Terminal.We have to prepare the disks first.
Become root. This saves you from having to type 'sudo' in front of every command.
sudo suBe sure you use clean disks (without GPT's on them). If you're unsure, wipe them first:
dd if=/dev/zero of=/dev/sda bs=1048576dd if=/dev/zero of=/dev/sdb bs=1048576Then, start 'cfdisk' with the device name of the first harddisk:
cfdisk /dev/sdaInspect the partitions:
root@ubuntu:/home/ubuntu# cfdisk -P s /dev/sdaPartition Table for /dev/sda First Last # Type Sector Sector Offset Length Filesystem Type (ID) Flag-- ------- ----------- ----------- ------ ----------- -------------------- ---- 1 Primary 0 112454 63 112455 Linux (83) None 2 Primary 112455 125033894 0 124921440 Linux raid auto (FD) Noneroot@ubuntu:/home/ubuntu# cfdisk -P s /dev/sdbPartition Table for /dev/sdb First Last # Type Sector Sector Offset Length Filesystem Type (ID) Flag-- ------- ----------- ----------- ------ ----------- -------------------- ---- 1 Primary 0 112454 63 112455 Linux (83) None 2 Primary 112455 125033894 0 124921440 Linux raid auto (FD) NoneTake note of the 'First Sector' of the second partition (112455 in this case),you'll need that later on for a dd command.
During the mdadm install a postfix configuration dialog might pop up. In that case, select the top option,'No configuration'.
apt-get install mdadmmdadm --create /dev/md0 --level=raid1 --raid-devices=2 /dev/sda2 /dev/sdb2While we're at it, let's format it too:
mkfs.ext3 /dev/md0ln /dev/md0 /dev/sdeAlso format the boot partition on both harddisks:
mkfs.ext3 /dev/sda1mkfs.ext3 /dev/sdb1Start the installer, it has an icon on the desktop.When you get to the 'Allocate drive space' dialog, choose the 'Specify partitions manually' option.Click the /dev/sda1 partition, choose 'Change..' and fill out the following options:
Use as: Ext3 journaling file systemFormat the partition: No (do not check the checkmark)Mount point: /bootClick the /dev/md0 partition, choose 'Change', and fill it out like this:
Use as: Ext3 journaling file systemFormat the partition: No (do not check the checkmarkMount point: /There's also a dropdown for 'Device for boot loader installation'. Ftp client shareware. Make sure that /dev/sda is selected there.Click the 'Install Now' button, and 'Continue' on any confirmation dialogs you might get.Fill out the rest of the install questions and sit back while Ubuntu installs itself.
When the installer is done, do not reboot the system yet (choose 'Continue testing').Go back to your terminal screen and prepare the boot partition:
mkdir /raidmount /dev/md0 /raidmount /dev/sda1 /raid/bootmount --bind /dev /raid/devmount -t devpts devpts /raid/dev/ptsmount -t proc proc /raid/procmount -t sysfs sysfs /raid/syschroot /raidapt-get install mdadmCopy the first part of the first harddisk to the second one using the 'dd' command.This ensures the MBR, GRUB boot loader, and the boot partition is also available on the second harddisk,in the case the system has to start from that disk.The count you specify should be the sector start count of the second partition (you took note of earlier), minus one.
dd if=/dev/sda of=/dev/sdb count=112454Now you can restart the system using reboot and if all is well, it should boot to the desktop.
Let's emulate a failure on the second harddisk.You can do this by just unplugging the SATA cable of the second harddisk while the system is running.Open a terminal and give the command: ll -alR /which will show a very long list of all the files on the system.While this list is running, yank the SATA cable from the second harddisk.Notice that after a few seconds, the listing suddenly stops.Ubuntu didn't crash, the mouse is still responsive, but the file system is having troubles at the moment.After two minutes Ubuntu notices that the second harddisk is permanently missing, marks it as such,and continues listing the files.The system continues to operate, albeit on only one disk.
Do a cat /proc/mdstat. You'll see output like this:
md0 : active raid1 sda2[0] 62468672 blocks [2/1] [U_]Will the PC be bootable with only one harddisk operational?Perform a sudo reboot.During the boot, which might take a little longer than usual, you might be presented by a GRUB boot selection menu; in that case, choose the first option. Next, a textual screen might appear asking you if you want to boot with the degraded RAID array. Answer 'Yes'. After this, the system comes up with the Ubuntu desktop.
More or less the same happens if you'd have disconnected the first harddisk instead of the second one.Repairing/rebuilding a broken RAID1 array is currently out of the scope of this article.An alternative would be rebuilding from scratch and restoring the data files from backup.
A useful command that will tell you the status of the RAID is cat /proc/mdstat
It's output is something like:
md0 : active raid1 sda2[0] sdb2[1] 62468672 blocks [2/2] [UU]The UU means both RAID1 components are 'Up'. If one disappears, it's 'U' will change to and underscore ('_').
Hi, Could you explain what this does? ln /dev/md0 /dev/sde Regards, Nick
æä¹æ²¡åç°æ交æ¢ååºSWAPå¢ï¼
Is this a sequential or parallel RAID1? What I'm asking is does the write to the primary drive complete BEFORE it starts writing to the mirror (high fault tolerance) OR does it perform the write in parallel (extremely low fault tolerance but high speed).
why not make the sd{a,b}1 raids as well?
I am interested in high fault tolerant storage systems. Does anyone have a link or a book reference to 'the write to the primary drive complete BEFORE it starts writing to the mirror (high fault tolerance)' mentioned by Roland? It sounds fascinating, even though as far as I know no one does that -- everyone uses 'write in parallel'. (Does a journaling file system on top of 'write in parallel' give high fault tolerance? https://en.wikipedia.org/wiki/journaling_file_system ).
Hi, all is OK till the command: mkfs.ext3 /dev/sda1 I´ve got: mke2fs 1.42.5 (29-Jul-2012) mkfs.ext4: inode_size (128) * inodes_count (0) too big for a filesystem with 0 blocks, specify higher inode_ratio (-i) or lower inode count (-N). What is wrong pls? This is fdisk -l: root@xubuntu:/home/xubuntu# fdisk -l Disk /dev/sda: 60.0 GB, 60022480896 bytes 255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 63 112454 56196 83 Linux /dev/sda2 112455 117231407 58559476+ fd Linux raid autodetect Disk /dev/sdb: 60.0 GB, 60022480896 bytes 255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 63 112454 56196 83 Linux /dev/sdb2 112455 117231407 58559476+ fd Linux raid autodetect Disk /dev/sdc: 16.0 GB, 16030597120 bytes 64 heads, 32 sectors/track, 15287 cylinders, total 31309760 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000bc84b Device Boot Start End Blocks Id System /dev/sdc1 * 32 31307775 15653872 83 Linux Disk /dev/md0: 54.0 GB, 53984755712 bytes 2 heads, 4 sectors/track, 13179872 cylinders, total 105438976 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/md0 doesn't contain a valid partition table
System admins rely on backup, cloning and encryption to keep data safe and secure. When it comes to encryption, many Linux users have relied on TrueCrypt to encrypt their data for a long, long time. Last year, without warning, the anonymous developers stopped work on the software claiming that the software was no longer secure – leaving many worried about the security of their files and searching for a new encryption solution. Here are our suggestions – and best of all, they're all free to implement.
This is the easiest way to transition from TrueCrypt for several reasons. The primary one is that much of the code was taken directly from TrueCrypt so VeraCrypt works in much the same way and looks somewhat similar (all the way down to the somewhat-messy, relatively-simple interface). VeraCrypt supports the most important encryption ciphers including AES, Serpent, and TwoFish, and allows encryption at all levels, even permitting the creation of encrypted volumes within encrypted volumes. Another important plus is that it encrypts on the fly, meaning that files remain encrypted unless and until they're actually needed. Because it's based on TrueCrypt, you might think that it could support your existing containers and files; it doesn't, but can easily convert them to the VeraCrypt format – another reason why it's the easiest option if TrueCrypt left you hanging.
For those who are just starting down the data encryption path, the simplest way to do it is with this option which comes bundled with Ubuntu and many other Linux distributions. You can choose the encryption during your initial Linux install, and it will provide an encrypted root partition and encrypted Swap via AES. The stronger and newer dm_crypt is also available on kernel versions 2.6 and later as well as in DragonFly BSD if you're comfortable working at the command line level.
GnuPG (obviously part of the German GNU project) is open-source software based on PGP (Pretty Good Privacy) – which, as you probably know, is more than pretty good. GnuPG comes as an installable package on most major Linux distributions including RedHat, Debian, and Ubuntu, although it can also be built directly from the source. It's been integrated into Evolution and KMail and there are a number of graphical front ends available. This is versatile encryption software, able to drill down to individual files, handle volumes and disk images, and even encrypt external media or drives. GnuPG uses a combination of symmetric-key and public-key encryption, using Cast5 on earlier versions and AES on the latest ones.
Originally based on and compatible with TrueCrypt, this reliable software has since been modified but resembles its predecessor in many ways including the use of AES, Twofish, Serpent and combinations of them all. It allows the user to encrypt whole drives or partitions but doesn't normally work at the file level. That makes it a worthwhile option for some users (and also makes the software extremely lightweight), but certainly isn't a full-featured choice for those who want to be able to encrypt selectively.
If you need assistance installing or configuring any of the programs listed above on your dedicated server, please feel free to contact our support department and we would be happy to assist you.
⨯Move your mouse pointer to the Activities corner at the top left of the screen to show the Activities Overview.
Click the Show Applications icon that is shown at the bottom of the bar on the left-hand side of the screen.
A list of applications is shown. Click the application you want to run, for example, Help.
Open the Activities Overview by pressing the Super key.
Start typing the name of the application you want to launch. Searching for the application begins instantly.
Once the icon of the application is shown and selected, press Enter to launch the application.
/image%2F6308649%2F20210221%2Fob_797f67_trimble-sketchup-blog.jpeg)
/image%2F6308649%2F20210221%2Fob_f477aa_excel-2016-price.png)
/image%2F6308649%2F20210221%2Fob_b865fa_jw-daily-text-2018-today.jpeg)
/image%2F6308649%2F20210221%2Fob_c4b68f_affordable-portable-ssd.jpeg)