Dear Mr. Chmielewski,

thank you for your support request.

The Acer Aspire One 751 is only avaliable with a Microsoft Windows licence.

As a matter of principle the return of your licence is possible. The following criteria have to be met:

1.) The licence agreements, which appeared when you first started the system, MUSTN'T be accepted.

2.) The item has to be sent in to our Service Center including all accessoires and equipement. If you already created recovery discs it is utmost important that these will also be sent in with the item. No copy of the former deliverred operating system is allowed to remain in your property / hands.

3.) The ACER service is then going to remove the Windows lincence plate and will erase the whole harddisc.

4.) You then will receive a refund (by bank transfer) for the preinstalled OEM licence (about 30 Euro) .

5.) You have to pay the shipping cost to the acer service center and the shipping costs back to your address.

If you wish to return the licence we need the serial number of your notebook, your contact details including the shipping address and your bank details.

We will then provide you with a reference number with which the item can be dispatched to our Service Center.

Please follow the instructions below before dispatching the item:

- Please note the reference number clearly visible on the outer package / cardboard box.
- If possible pack the item in the original packaging or use another package that is safe for transport.
- Please note that ACER will not accept items that arrive being dispatched "freight collect".

ACER Computer GmbH
Repair Center
Kornkamp 4
22926 Ahrenburg

If you have any further questions regarding this topic please do not delete the previous correspondence.

Best regards
C. Riecken

Your ACER support team

• running memtest86+ means server downtime,
• it may not be possible to run memtest86+ on a remote server without KVM-IP, iLO or similar access.

What to do in such situations? User-space memtester to the rescue!

The obvious disadvantage is that you will not be able to test all RAM in the server, but sometimes, it’s not needed to determine if RAM is good or not.

The below command will try to allocate ~15GB RAM and make one test pass – if you see errors like below, your RAM is hosed!

Note that with the exact command line shown below you should have at least 15 GB of free, unallocated memory, otherwise, you’re likely to hang your server, or at least cause a serious downtime or OOM-killer.

# memtester 15000 1
memtester version 4.0.8 (64-bit)
Copyright (C) 2007 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 15000MB (15728640000 bytes)
got  15000MB (15728640000 bytes), trying mlock ...locked.
Loop 1/1:
  Stuck Address       : testing   0FAILURE: possible bad address line at offset 0x5d922ec8.
Skipping to next test...
  Random Value        : ok
FAILURE: 0x7f40f12dd82264da != 0x7f40f52dd82264da at offset 0x22fa2d27.
FAILURE: 0xe800dc254863429d != 0xe8005c254863429d at offset 0x22fa2de7.
FAILURE: 0x95005ca5bc351fd0 != 0x95007ca5bc351fd0 at offset 0x22fa2e47.
FAILURE: 0x16cc8129822daa5 != 0x16c4a129822daa5 at offset 0x22fa2e5f.
FAILURE: 0xce8945572424d79a != 0xce89c5572424d79a at offset 0x22fa2f1f.
FAILURE: 0x14054d669820e595 != 0x1405cd669820e595 at offset 0x22fa306f.
FAILURE: 0x8d283c130c69dc25 != 0x8d28bc130c69dc25 at offset 0x22fa309f.
FAILURE: 0x19285abae23f881 != 0x19287abae23f881 at offset 0x22fa30b7.
FAILURE: 0x55302b281ab13a51 != 0x55302f281ab13a51 at offset 0x22fa31bf.
FAILURE: 0x48b8ae1715e5084b != 0x48b8aa1715e5084b at offset 0x22fa31d7.
FAILURE: 0x28a2b64b9039074a != 0x28a2164b9039074a at offset 0x22fa5db7.
FAILURE: 0xc6080cfa18200698 != 0xc6080efa18200698 at offset 0x22fa5dcf.
FAILURE: 0x2b30fefcd69a347 != 0x2b38fefcd69a347 at offset 0x22fa5de7.
FAILURE: 0xbc27b13358294271 != 0xbc27b33358294271 at offset 0x22fa5e2f.
FAILURE: 0xc17e0d24dc21fe7e != 0xc17e0f24dc21fe7e at offset 0x22fa5e47.
FAILURE: 0x29ac181590911ae3 != 0x29ac1a1590911ae3 at offset 0x22fa5f07.
FAILURE: 0x233001ba38a53ccd != 0x233021ba38a53ccd at offset 0x22fa5f37.
FAILURE: 0x7542cd4b38a3ea9f != 0x7542c94b38a3ea9f at offset 0x22fa5f7f.
FAILURE: 0x86c89d49992151c8 != 0x86c8bd49992151c8 at offset 0x22fa5ff7.
FAILURE: 0x16208f9b584969b3 != 0x16200f9b584969b3 at offset 0x22fa609f.
FAILURE: 0x6a08171eb0a18751 != 0x6a08151eb0a18751 at offset 0x22fa60b7.
FAILURE: 0x8214f12e9a254014 != 0x8214f72e9a254014 at offset 0x22fa60cf.
FAILURE: 0x8005ab68021ad9f != 0x800dab68021ad9f at offset 0x22fa612f.
FAILURE: 0x884e76469ba12421 != 0x884e72469ba12421 at offset 0x22fa61a7.
FAILURE: 0x30509c65d890299e != 0x30509e65d890299e at offset 0x22fa62af.
  Compare XOR         : FAILURE: 0x3f81821efe3ced18 != 0x3f81861efe3ced18 at offset 0x22fa2d27.
FAILURE: 0xa8416d166e7dcadb != 0xa840ed166e7dcadb at offset 0x22fa2de7.
FAILURE: 0x5540ed96e24fa80e != 0x55410d96e24fa80e at offset 0x22fa2e47.
FAILURE: 0xc1ad5903be3d62e3 != 0xc1acdb03be3d62e3 at offset 0x22fa2e5f.
FAILURE: 0x8ec9d6484a3f5fd8 != 0x8eca56484a3f5fd8 at offset 0x22fa2f1f.
FAILURE: 0xd445de57be3b6dd3 != 0xd4465e57be3b6dd3 at offset 0x22fa306f.
FAILURE: 0x4d68cd0432846463 != 0x4d694d0432846463 at offset 0x22fa309f.
FAILURE: 0xc1d3169cd43e80bf != 0xc1d3189cd43e80bf at offset 0x22fa30b7.
FAILURE: 0x1570bc1940cbc28f != 0x1570c01940cbc28f at offset 0x22fa31bf.
FAILURE: 0x8f93f083bff9089 != 0x8f93b083bff9089 at offset 0x22fa31d7.
FAILURE: 0xe8e3473cb6538f88 != 0xe8e2a73cb6538f88 at offset 0x22fa5db7.
FAILURE: 0x86489deb3e3a8ed6 != 0x86489feb3e3a8ed6 at offset 0x22fa5dcf.
FAILURE: 0xc2f3a0e0f3842b85 != 0xc2f420e0f3842b85 at offset 0x22fa5de7.
FAILURE: 0x7c6842247e43caaf != 0x7c6844247e43caaf at offset 0x22fa5e2f.
FAILURE: 0x81be9e16023c86bc != 0x81bea016023c86bc at offset 0x22fa5e47.
FAILURE: 0xe9eca906b6aba321 != 0xe9ecab06b6aba321 at offset 0x22fa5f07.
FAILURE: 0xe37092ab5ebfc50b != 0xe370b2ab5ebfc50b at offset 0x22fa5f37.
FAILURE: 0x35835e3c5ebe72dd != 0x35835a3c5ebe72dd at offset 0x22fa5f7f.
FAILURE: 0x47092e3abf3bda06 != 0x47094e3abf3bda06 at offset 0x22fa5ff7.
FAILURE: 0xd661208c7e63f1f1 != 0xd660a08c7e63f1f1 at offset 0x22fa609f.
FAILURE: 0x2a48a80fd6bc0f8f != 0x2a48a60fd6bc0f8f at offset 0x22fa60b7.
FAILURE: 0x4255821fc03fc852 != 0x4255881fc03fc852 at offset 0x22fa60cf.
FAILURE: 0xc840eba7a63c35dd != 0xc8416ba7a63c35dd at offset 0x22fa612f.
FAILURE: 0x488f0737c1bbac5f != 0x488f0337c1bbac5f at offset 0x22fa61a7.
FAILURE: 0xf0912d56feaab1dc != 0xf0912f56feaab1dc at offset 0x22fa62af.
  Compare SUB         : FAILURE: 0x770f6d7d59b31bc0 != 0x64680d7d59b31bc0 at offset 0x22fa2d27.
FAILURE: 0x17cc5d24cac64438 != 0x6cb85d24cac64438 at offset 0x22fa2de7.
FAILURE: 0x8bda06d04720f630 != 0xf69f06d04720f630 at offset 0x22fa2e47.
FAILURE: 0x191ec89353a0b578 != 0xe4b7189353a0b578 at offset 0x22fa2e5f.
FAILURE: 0xb1bc42b59ee189c0 != 0x5cd042b59ee189c0 at offset 0x22fa2f1f.
FAILURE: 0x86575304584f0af8 != 0x316b5304584f0af8 at offset 0x22fa306f.
FAILURE: 0x4d053942f1b9f178 != 0xf8193942f1b9f178 at offset 0x22fa309f.
FAILURE: 0x206d80c97f8947d8 != 0x9719d0c97f8947d8 at offset 0x22fa30b7.
FAILURE: 0x6cf332350ca77058 != 0x5a4bd2350ca77058 at offset 0x22fa31bf.
FAILURE: 0xcae418d26b8f9b68 != 0xdd8b78d26b8f9b68 at offset 0x22fa31d7.
FAILURE: 0xdc58887f8f9e1d40 != 0xc67f887f8f9e1d40 at offset 0x22fa5db7.
FAILURE: 0x66470a0f89743570 != 0xdcf35a0f89743570 at offset 0x22fa5dcf.
FAILURE: 0x678cf2f8066c7ac8 != 0x12a0f2f8066c7ac8 at offset 0x22fa5de7.
FAILURE: 0x7e705d8189837558 != 0xf51cad8189837558 at offset 0x22fa5e2f.
FAILURE: 0x62530ceb060c3560 != 0xd8ff5ceb060c3560 at offset 0x22fa5e47.
FAILURE: 0xe1f0dc5c71b99328 != 0x589d2c5c71b99328 at offset 0x22fa5f07.
FAILURE: 0xa1a2ad6a30317bb8 != 0xc67ad6a30317bb8 at offset 0x22fa5f37.
FAILURE: 0x1d86ded3b0c73088 != 0x302e3ed3b0c73088 at offset 0x22fa5f7f.
FAILURE: 0xf1b9a3e0fcfa14f0 != 0x5c7ea3e0fcfa14f0 at offset 0x22fa5ff7.
FAILURE: 0x806d7d4232efc3a8 != 0xd5597d4232efc3a8 at offset 0x22fa609f.
FAILURE: 0x98a6f4d473117858 != 0x21faa4d473117858 at offset 0x22fa60b7.
FAILURE: 0x617c86f84528d8d0 != 0xc58176f84528d8d0 at offset 0x22fa60cf.
FAILURE: 0xbca540978cefa888 != 0x67b940978cefa888 at offset 0x22fa612f.
FAILURE: 0xe6ebd2a5a59fd8d8 != 0xf99332a5a59fd8d8 at offset 0x22fa61a7.
FAILURE: 0x1a30be8e9a1fb260 != 0x90dd0e8e9a1fb260 at offset 0x22fa62af.
  Compare MUL         : ^C^C^C^C^C
#

my $ip;
my $device = "eth0";
if ((`/sbin/ifconfig $device`) =~ /inet addr:(\d+\.\d+\.\d+\.\d+)/) {
    $ip = $1;
}

If you’d also like to get a list of all aliases the device has, you could use something like:

my $device = "eth0";
my @ipaddr_output = `ip addr show dev $device`;
my @ip_aliases;
foreach my $ip_alias (@ipaddr_output) {
    if ($ip_alias =~ m/inet (.+)\/32(.+)$device(.+)/) {
        push (@ip_aliases, $1);
    }
}

Note that if your locale is different, you may need to look for a different match (or just set locale in your perl script), i.e.:


$ ifconfig
eth0 Link encap:Ethernet Hardware Adresse 00:23:8b:eb:f2:b4
inet Adresse:192.168.111.142 Bcast:192.168.111.191 Maske:255.255.255.192



$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:23:8b:eb:f2:b4
inet addr:192.168.111.142 Bcast:192.168.111.191 Mask:255.255.255.192


• choose a location where your SVN server will keep data – for example, /srv/svn; use svnadmin create a SVN project structure there:

# mkdir /srv/svn
# cd /srv/svn
# svnadmin create yoursite.example.com

• now, import your initial version of the website:

# svn --message "Initial import" import /home/yoursite.example.com/public_html file:///srv/svn/yoursite.example.com
Adding /home/yoursite.example.com/public_html/index.html
Committed revision 1.

• add users – first, in /srv/svn/yoursite.example.com/conf/passwd:

[users]
svnadmin = secretpass

• and in /srv/svn/yoursite.example.com/conf/authz:

[groups]
full = svnadmin, someotheruser
read = readonlyuser
[/]
@full = rw
@read = r

• in /srv/svn/yoursite.example.com/conf/svnserve.conf, use setting like these:

[general]
anon-access = none
auth-access = write
password-db = passwd
authz-db = authz


• start SVN daemon:

svnserve -r /srv/svn -d

• from a separate PC, try to checkout:

svn --username svnadmin co svn://yourserver/yoursite.example.com

Here is how.

First, you need to tell qemu / kvm process to have a monitor accessible via a UNIX socket – if you use Proxmox VE, it will be created automatically, if not, just use such a command line parameter:

-monitor unix:/var/run/qemu-server/105.mon,server,nowait

Where /var/run/qemu-server/105.mon is the path to the socket.

Next, install minicom and create the /etc/minicom/minirc.105-mon file with the contents like below – this will tell minicom to connect to the serial monitor console of this qemu / kvm quest:

pu port             unix#/var/run/qemu-server/105.mon
pu minit
pu mreset

Next, minicom needs to execute a script – an example for changing a VNC password below (save it as “change-vnc-pass”; see “man runscript” for more syntax help):

send \r\r
send "change vnc password"
expect "Password:"
send some-password

The last thing would be to start minicom and execute these commands:

#!/bin/bash
minicom 105-mon -S /some/path/change-vnc-pass &
sleep 3s
kill $!

That’s it!

If you’d like to start it from crontab, you have to use screen – otherwise, minicom will complain about “No cursor motion capability (cm)” when started using cron:

50 * * * *      root    screen -d -m /some/path/change-vnc-pass.sh

# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md2 : active raid1 sda3[0] sdb3[1]
1458830400 blocks [2/2] [UU]

md1 : active raid1 sda2[0] sdb2[1]
2104448 blocks [2/2] [UU]

md0 : active (auto-read-only) raid1 sda1[0] sdb1[1]
4200896 blocks [2/2] [UU]

unused devices: <none>

It simply means nothing was yet written to that array (unless you were changing anything with –readonly option to mdadm).

I.e. if a mounted filesystem is on a given device, you are unlikely to see this. On a swap device, however, you may see it.

Assuming the device is /dev/md0 and is used for swap, do a:

swapoff /dev/md0
mkswap /dev/md0
swapon /dev/md0

and you will see “auto-read-only” is gone (careful, if you use UUIDs).

In my.cnf on both servers, add a second database:

replicate-do-db          = first_db
replicate-do-db          = second_db
binlog-do-db            = first_db
binlog-do-db            = second_db

Connect to mysql on both servers and add a new database:


# mysql -p
mysql> CREATE DATABASE second_db;


Now, restart mysql on both servers and verify that replication works (be careful when restarting if there are any writes to the database; i.e. shutdown the secondary master first, then the primary master – depending on your environment):


mysql> use second_db;
Database changed
mysql> show tables;
Empty set (0.00 sec)
mysql> CREATE TABLE example (
-> id INT,
-> data VARCHAR(100)
-> );
Query OK, 0 rows affected (0.13 sec)
mysql> drop table example;
Query OK, 0 rows affected (0.02 sec)
mysql>


After creating/dropping the example table on one server, verify it’s happening on the second server as well:


mysql> show tables;
+---------------------+
| Tables_in_second_db |
+---------------------+
| example |
+---------------------+
1 row in set (0.00 sec)
mysql> show tables;
Empty set (0.01 sec)


Don’t forget to add a user with proper privileges, i.e.:


mysql> CREATE USER someuser IDENTIFIED BY 'password';
Query OK, 0 rows affected (0.23 sec)
mysql> GRANT ALL ON second_db.* TO 'someuser'@'%';
Query OK, 0 rows affected (0.00 sec)


Here is a quickie on how to update it using CentOS development / testing repository.

• First, create a /etc/yum.repos.d/CentOS-dev.repo file and add this content to it:

[c5-dev]
name=CentOS-5 Testing
baseurl=http://dev.centos.org/centos/5/testing/$basearch/
enabled=1
gpgcheck=1
gpgkey=http://dev.centos.org/centos/RPM-GPG-KEY-CentOS-testing

• As you just want to update PHP (but not all software on the server), see what PHP packages you have on the server:

# rpm -qa|grep php
php-gd-5.1.6-24.el5_4.5
php-common-5.1.6-24.el5_4.5
php-pdo-5.1.6-24.el5_4.5
php-cli-5.1.6-24.el5_4.5
php-mysql-5.1.6-24.el5_4.5
php-ldap-5.1.6-24.el5_4.5
php-5.1.6-24.el5_4.5

• Now, time to upgrade PHP to 5.2 on your CentOS 5.x server (to PHP 5.2.10, as of writing this blog entry):

# yum install php-gd php-common php-pdo php-cli php-mysql php-ldap php

Packet manager (yum) will ask if you want to install CentOS-testing GPG key – if you confirm, it will upgrade PHP to the latest version from the development repository.

• After the upgrade, make sure that your existing websites still function properly. If they do, you may want to remove /etc/yum.repos.d/CentOS-dev.repo file (or comment out its content, or disable it per yum configuration) – to prevent accidental updating of all software to development versions.

Currently, Exim does not support signing mails with both DomainKeys and DKIM. You have to pick one of them, unless you do some tricks with patching Exim or connecting back to itself.

Still though, such setup is not perfect: Exim does not wrap its DomainKeys signature, which may result in SpamAssassin installations tagging your mail with HEAD_LONG rule (“Message headers are very long”) and assigning it 2.5 spam points.

So how to sign mail with DKIM and DomainKeys without negative consequences of being tagged by SpamAssassin for very long headers? DKIMproxy to the rescue!

Exim configuration

Exim should listen on an additional port – make sure you have something similar in your exim.conf file:

local_interfaces = 0.0.0.0 : 127.0.0.1.10025

Exim should speak TLS only on port 25, otherwise, it won’t be able to communicate with DKIMproxy:

tls_advertise_hosts = 0.0.0.0.25

at the beginning of the routers section in exim.conf:

dkimproxy:
driver = manualroute
condition = "${if eq {$interface_port}{10025} {0}{1}}"
transport = dkimproxy_smtp
route_list = "* localhost byname"
self = send

transports section in exim.conf (does not matter where):

dkimproxy_smtp:
driver = smtp
port = 10027
allow_localhost

DKIMproxy configuration

Download and install DKIMproxy (“./configure; make; make install” after you downloaded and extracted dkim-proxy package, unless your distribution provides it packaged).

Create a /etc/dkimproxy/dkimproxy_out.conf file with similar content:

# specify what address/port DKIMproxy should listen on
listen 127.0.0.1:10027

# specify what address/port DKIMproxy forwards mail to
relay 127.0.0.1:10025

# specify what domains DKIMproxy can sign for (comma-separated, no spaces)
domain host.example.com,example.com

# specify what signatures to add
signature dkim(c=relaxed)
signature domainkeys(c=nofws)

# specify location of the private key
keyfile /etc/dkimproxy/dkim.key.private

# specify the selector (i.e. the name of the key record put in DNS)
selector default

Make sure DKIMproxy is started when your server boots (add it to your startup scripts):

/usr/local/bin/dkimproxy.out --conf_file=/etc/dkimproxy/dkimproxy_out.conf --daemonize

Place the private key you want to use with DKIMproxy in /etc/dkimproxy/dkim.key.private. If you use cPanel, you may symlink it to a key in /var/cpanel/domain_keys/private/.

DNS configuration

Similar entries will be needed in your DNS zone configuration:

default._domainkey 14400 IN TXT "k=rsa; p=MH.........;"
_asp._domainkey.example.com. IN TXT "dkim=unknown"
_adsp._domainkey.example.com. IN TXT "dkim=unknown"
_domainkey.example.com. IN TXT "t=y; o=~;"

Key generation

# openssl genrsa -out private.key 1024
# openssl rsa -in private.key -pubout -out public.key

Testing

You can test if DKIM and DomainKeys signing works properly on these websites:

• http://www.myiptest.com/staticpages/index.php/DomainKeys-DKIM-SPF-Validator-test

• http://www.brandonchecketts.com/emailtest.php

You can also test it by sending an email to:

• check-auth@verifier.port25.com

Troubleshooting

If you use cPanel, you will see such entries in your /var/log/exim_mainlog:

socket bind() to port 10025 for address 127.0.0.1 failed: Address already in use: waiting 30s before trying again

This is because /etc/init.d/exim script shipped with cPanel starts two instances of Exim, one of them is listening on port 465 – SMTP over SSL (TLS), but reading the same config file. This conflicts with “local_interfaces = 0.0.0.0 : 127.0.0.1.10025“. Second instance of Exim will try to bind to port 10025 as well, but will give up after 10 tries.

To fix it, add this to your Exim config file:

daemon_smtp_ports = 25 : 465
tls_on_connect_ports = 465

And comment out these lines from /etc/init.d/exim:

echo -n "Starting exim-smtps: "
# TMPDIR=/tmp $DAEMONIZE /usr/sbin/exim -tls-on-connect -bd -oX 465
# echo $RESULT

If yes, you may have problems downloading photos from it – depending on your kernel and udev settings, or more generally, on Linux distribution used.

The tips from below may help you.

Every USB device connected to your Linux system will make the kernel print some messages. You can print them with dmesg command, started in the console, i.e.:


# dmesg -c
scsi 4:0:0:0: Direct-Access MATSHITA DMC-TZ5 0100 PQ: 0 ANSI: 2
usb-storage: device scan complete
Driver 'sd' needs updating - please use bus_type methods
sd 4:0:0:0: [sda] 7954431 512-byte hardware sectors (4073 MB)
sd 4:0:0:0: [sda] Write Protect is off
sd 4:0:0:0: [sda] Mode Sense: 04 00 00 00
sd 4:0:0:0: [sda] Assuming drive cache: write through
sd 4:0:0:0: [sda] 7954431 512-byte hardware sectors (4073 MB)
sd 4:0:0:0: [sda] Write Protect is off
sd 4:0:0:0: [sda] Mode Sense: 04 00 00 00
sd 4:0:0:0: [sda] Assuming drive cache: write through

The above output meant that the connected camera was recognized as /dev/sda block device – good, your distro supports it out of the box. If you never see a block device like sda or sdb, but only output like below – it means you need to complain to your distribution vendor:


# dmesg -c
usb 1-2: new high speed USB device using ehci_hcd and address 3
usb 1-2: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
usb 1-2: New USB device found, idVendor=04da, idProduct=2372
usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2: Product: DMC-TZ5
usb 1-2: Manufacturer: Panasonic
usb 1-2: SerialNumber: 0000000000000000005F0208220775
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
scsi 3:0:0:0: Direct-Access MATSHITA DMC-TZ5 0100 PQ: 0 ANSI: 2
usb-storage: device scan complete

There is a simple workaround to that. In /etc/udev, search for such a line:

SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device", NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0644"

You can do it with grep command:

# grep -r "bus/usb" /etc/udev

When you localize it, comment it out, restart udevd, i.e. use killall command to stop it, and start it in verbose mode to see more information on what it does:

# killall udevd
# udevd --verbose

For me, I had problems getting photos from DMZ-FZ20 and DMC-TZ5 Lumix models on Mandriva and OpenSuse. On Ubuntu though, everything worked from scratch and I didn’t have to do any udev changes.