Linux web-conference.aiou.edu.pk 5.4.0-204-generic #224-Ubuntu SMP Thu Dec 5 13:38:28 UTC 2024 x86_64
Apache/2.4.41 (Ubuntu)
: 172.16.50.247 | : 52.14.6.24
Cant Read [ /etc/named.conf ]
7.4.3-4ubuntu2.28
appadmin
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
bcache-tools /
[ HOME SHELL ]
Name
Size
Permission
Action
README.Debian
1.28
KB
-rw-r--r--
changelog.Debian.gz
1.04
KB
-rw-r--r--
copyright
3.2
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : README.Debian
bcache-tools for Debian ======================= Notes: * Always back important data up first! * Don't put /boot onto a bcache device (grub doesn't understand the disk format), but it does work fine for the root device if you use a separate (uncached) /boot partition. * A separate /boot may not be necessary on UEFI systems (untested) * You can use lvm for the backing and the caching devices, but currently the initrd will not automatically activate the vg. This is an issue if you plan on caching your root device. A basic setup guide: -------------------- Create a backing device: This formats the partition HDD1 and creates /dev/bcache0. $ make-bcache -B /dev/HDD1 Create a caching device, copy the `Set UUID' for later. $ make-bcache -C /dev/SSD1 Connect the two; this only needs to be done once: $ echo "Set UUID" > /sys/block/bcache0/bcache/attach You probably want write-back caching, otherwise only reads will be sped up. Note that this means a dead SSD could result in data loss. $ echo writeback > /sys/block/bcache0/bcache/cache_mode Find the UUID of the device: $ ls /dev/disk/by-uuid -l | grep bcache0 Use this UUID in /etc/fstab since the /dev/bcacheX number may change when a second bcache device is created. -- David Mohr <david@mcbf.net> Wed, 26 Mar 2014 00:09:49 -0600
Close