Change /etc/apt/sources.list as below:
deb http://ftp.ch.debian.org/debian/ testing main contrib non-free
deb-src http://ftp.ch.debian.org/debian/ testing main contrib non-free
#old version format of security repository
#deb http://security.debian.org/ testing/updates main contrib non-free
#deb-src http://security.debian.org/ testing/updates main contrib non-free
#new version format of security repository (after Buster)
deb http://security.debian.org testing-security main contrib non-free
deb-src http://security.debian.org testing-security main contrib non-free
# xxxx-updates, previously known as 'volatile'
deb http://ftp.ch.debian.org/debian/ testing-updates main contrib non-free
deb-src http://ftp.ch.debian.org/debian/ testing-updates main contrib non-free
From https://wiki.debian.org/Status/Testing
2016-03-17
Buffalo WBR2-G54 install Tomato Firmware by Shibby
--- Migrating from DD-WRT Firmware via Windows
- You can use the DD-WRT web interface to flash to the Tomato firmware.
- First, obtain the password for the router: In the web interface, go to Administration -> Commands. Type "nvram get http_passwd" into the text box and click "Run Commands". When the page reloads, it will show the password below. Make note of this password for later use.
- Alternatively, you can obtain the password via telnet. Assuming your router can be found at 192.168.1.1, you'd type "telnet 192.168.1.1" at a command prompt to login to the router. Once logged in, type "nvram get http_passwd" and write down the result.
- Download the Tomato firmware and extract it. In the "trx" subfolder, rename the file code.trx to code.bin. (DD-WRT does not recognize the .trx file extension as firmware.)
- Update the firmware via the DD-WRT web interface. The Tomato firmware is now installed.
- Access the Tomato web interface. Use the username "root" and the complete password provided by the "nvram get http_passwd" response above.
- Browse to Administration > Configuration > Restore Default Configuration. Then select "Erase all data in NVRAM memory (thorough)" and click OK.
- Please note that the instructions for flashing the firmware via the web interface will only work once you've installed DD-WRT (or perhaps another 3rd party firmware).
What’s that % sign after ipconfig IPv6 address?
Reference 1. What’s that % sign after ipconfig IPv6 address?
If that’s you after typing ipconfig on Windows machine with IPv6 enabled then this article is for you. Maybe at first you are looking at this ipconfig output and it seems that there is still no reason for thig %”some number” to be there. I will try to be short in this explanation and explain you crearly why is really there.
That IPv6 address with that strange % sign is called Link-Local IPv6 address. It’s by design an address that has network part same for all computers in the world. That part is called network identifier and is written fe80:0000:0000:0000 or to be short fe80::
So in you have one network card in your comuter everything is working fine and your computer can speak IPv6 to all others in the local network. But!! What if you open your computer and insert second network card NIC to it? Your computer will have two network interfaces and both of them will be with the same network identifier of course fe80:0000:0000:0000. If you go in the netowrking fundamentals you can recall that there can not be a host with two interfaces in the same subnet. Why? If you want to ping the address fe80::5c9f:bc10:bb38:63ec from your computer and your computer has two NICs with addresses fe80::1111:1111:a000:0001 and fe80::5555:5555:5555:1111. Out of what interface will the ping exit the computer? Hm, on both, only on random one? This is not going to work.
To resolve this issue there is the Zone ID. This is our misterious number after the % sign in the IPv6 Link-Local address on your network card. The number is basically an Interface ID so in the network examples below they have Interface in Zone IDs 18, 19, 20, and 21, respectively.
IPv6 Zone ID
This number it distinguishes the network segment by using a numeric zone ID following a percent sign after the IP address:
fe80:3438:7667:5c77:ce27%18
fe80::8939:7684:d84b:a5a4%19
fe80::711b:lc9:f462:7ed4%20
fe80::2112:1234:88a4:b421%21
Zone ID il localy significant. It means that if you want to ping a neighbor computer you will need to specify the neighbor’s IPv6 Link-Local address plus the Zone ID of your computer’s network adapter that is gooing to that computer.
If that’s you after typing ipconfig on Windows machine with IPv6 enabled then this article is for you. Maybe at first you are looking at this ipconfig output and it seems that there is still no reason for thig %”some number” to be there. I will try to be short in this explanation and explain you crearly why is really there.
That IPv6 address with that strange % sign is called Link-Local IPv6 address. It’s by design an address that has network part same for all computers in the world. That part is called network identifier and is written fe80:0000:0000:0000 or to be short fe80::
So in you have one network card in your comuter everything is working fine and your computer can speak IPv6 to all others in the local network. But!! What if you open your computer and insert second network card NIC to it? Your computer will have two network interfaces and both of them will be with the same network identifier of course fe80:0000:0000:0000. If you go in the netowrking fundamentals you can recall that there can not be a host with two interfaces in the same subnet. Why? If you want to ping the address fe80::5c9f:bc10:bb38:63ec from your computer and your computer has two NICs with addresses fe80::1111:1111:a000:0001 and fe80::5555:5555:5555:1111. Out of what interface will the ping exit the computer? Hm, on both, only on random one? This is not going to work.
To resolve this issue there is the Zone ID. This is our misterious number after the % sign in the IPv6 Link-Local address on your network card. The number is basically an Interface ID so in the network examples below they have Interface in Zone IDs 18, 19, 20, and 21, respectively.
IPv6 Zone ID
This number it distinguishes the network segment by using a numeric zone ID following a percent sign after the IP address:
fe80:3438:7667:5c77:ce27%18
fe80::8939:7684:d84b:a5a4%19
fe80::711b:lc9:f462:7ed4%20
fe80::2112:1234:88a4:b421%21
Zone ID il localy significant. It means that if you want to ping a neighbor computer you will need to specify the neighbor’s IPv6 Link-Local address plus the Zone ID of your computer’s network adapter that is gooing to that computer.
2016-03-04
解決Ghost出現"Encountered an NTFS Volume with a logfile that has not been flushed(536)"
Reference 1. Warning: "Encountered an NTFS volume with a logfile that has not been flushed (536)" when taking a Ghost image.
Reference 2. Win7/Win8.1升級Win10后開機慢 如何解決？
事件描述：Win8/Win10 系統，使用Ghost11.02做系統分割，執行時出現："Encountered an NTFS Volume with a logfile that has not been flushed (536)"
過程：在網上查找了各種方式，包括CHKDSK /f 等等，也有說是非正常關機造成的，重啟多遍無果。
解決：因為是Win8/Win10 系統，有個特殊的快速啟動設置，將這個設置關掉，故障提示消失了，Ghost得以正常完成。
關閉Win8/Win10 快速啟動功能：
1、打開控制面板，電源選項，單擊左側的：選擇電源按鈕的功能
2、單擊「選擇當前不可用的設置」
3、在下面的「關機設置」中，把快速啟動關掉就行了
Reference 2. Win7/Win8.1升級Win10后開機慢 如何解決？
事件描述：Win8/Win10 系統，使用Ghost11.02做系統分割，執行時出現："Encountered an NTFS Volume with a logfile that has not been flushed (536)"
過程：在網上查找了各種方式，包括CHKDSK /f 等等，也有說是非正常關機造成的，重啟多遍無果。
解決：因為是Win8/Win10 系統，有個特殊的快速啟動設置，將這個設置關掉，故障提示消失了，Ghost得以正常完成。
關閉Win8/Win10 快速啟動功能：
1、打開控制面板，電源選項，單擊左側的：選擇電源按鈕的功能
2、單擊「選擇當前不可用的設置」
3、在下面的「關機設置」中，把快速啟動關掉就行了
Subscribe to:
Posts (Atom)