# Systemd unit file for ApacheDS instances. [Unit] Description=Apache DS LDAP server After=syslog.target network.target [Service] Type=forking ExecStart=/opt/apacheds-2.0.0_M20/bin/apacheds start default ExecStop=/opt/apacheds-2.0.0_M20/bin/apacheds stop default SuccessExitStatus=143 User=apacheds Group=apacheds [Install] WantedBy=multi-user.targetThen execute:
systemctl enable apacheds systemctl start apacheds
netsh winhttp reset proxy
bootrec.exe /fixmbrReboot and start the update process again. Now the update should be successful.
mount /dev/sda4 /mnt mount /dev/sda3 /mnt/boot mount --bind /dev /mnt/dev mount --bind /proc /mnt/proc mount --bind /sys /mnt/sysOptionally you may mount home directory
mount /dev/sdaX /mnt/home
chroot /mntReinstall grup 2 on boot partition
grub2-install /dev/sda3You may receive following error:
grub2-install --force /dev/sda3Once the installation complets create a dump of the bootsector:
dd if=/dev/sda3 of=/tmp/linux.bootsector.bin bs=512 count=1copy the /tmp/linux.bootsector.bin to some partition accessible by Windows.
mkdir /mnt/cNow reboot and start Windows and we need to create a new BCD entry for Linux
mount /dev/sda2 /mnt/c
cp /tmp/linux.bootsector.bin /mnt/c
umount /mnt/c
bcdedit /create /d “Linux” /application BOOTSECTORThe command will return GUID e.g. {5474794d-1fe8-4008-a0ae-d10210214f2a}
bcdedit /set {5474794d-1fe8-4008-a0ae-d10210214f2a} device partition=C:
bcdedit /set {5474794d-1fe8-4008-a0ae-d10210214f2a} PATH \linux.bootsector.bin
Then configure the new entry to be shown last, and the OS selection menu timeout to be 5 seconds.bcdedit /displayorder {5474794d-1fe8-4008-a0ae-d10210214f2a} /addlast
bcdedit /timeout 5
Reboot and now you will be able to boot either Windows or Linux.Typical error is :
mount -t cifs -o username=superman,password=secret //192.168.22.14/c$ /mnt/c mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)The reason is that described in KB951916 Microsoft introduced as part of UAC a little known feature called “UAC remote restrictions”. It filters the access token for connections made with local user accounts or Microsoft accounts (the latter typically have the format MicrosoftAccount\EMailAddress). In other words it removes the SID for “Administrators”. Connections made with domain accounts remain unchanged. From KB951016:
If the user wants to administer the workstation with a Security Account Manager (SAM) account, the user must interactively log on to the computer that is to be administered with Remote Assistance or Remote Desktop, if these services are available.UAC remote restrictions can be disabled by setting the DWORD registry value LocalAccountTokenFilterPolicy to 1:
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System Value: LocalAccountTokenFilterPolicy Data: 1 (to disable, 0 enables filtering) Type: REG_DWORD (32-bit)Reboot is not required on Windows 8/10
[Unit] Description=cifs mount script Requires=network-online.service After=network-online.service Before=kodi.service [Mount] What=//192.168.0.31/MusicRock Where=/storage/music/rock Options=username=myusername,password=mypassword,rw Type=cifs [Install] WantedBy=multi-user.targetImportant: this file must be renamed to mountpoint.mount where mountpoint, is the FULL path where the share will be mounted. Slashes "/" MUST BE REPLACED with dashes "-" with .mount as extension. This means, if we want mount to "/storage/music/rock" (see above "Where=/storage/music/rock") then this file must be renamed to 'storage-music-rock.mount'. This is only for the filename! not for the What= and Where= sections!
#!/bin/bash
displayUsage() {
echo "Scans source directory and create symbolic links based on the file first two letters"
echo -e "\nUsage:\n$0 [src-dir] [links-dir]\n src-dir\tsource directory to be scanned\n links-dir\tfull path to target directory where symbolic links will be created\n\n"
echo -e "e.g.:\n $0 /storage/music/rock /storage/music/rock_links/\n\n"
echo -e "Let's have 3 files:\n /storage/music/rock/rock1\n /storage/music/rock/rock2\n /storage/music/rock/metal\n"
echo -e "then inside /storage/music/rock_links/ you will have following files:\n"
echo -e " /storage/music/rock_links/RO/rock1\n /storage/music/rock_links/RO/rock2\n /storage/music/rock_links/ME/metal\n"
}
if [[ -z $1 ]]; then
displayUsage
exit 1
fi
if [[ -z $2 ]]; then
displayUsage
exit 1
fi
dir=$1
links=$2
currdir=`pwd`
rm -Rf $links
cd $dir
mkdir -p $links
for f in *
do
prefix=`echo $f | cut -c 1,2 | tr [:lower:] [:upper:]`
mkdir -p $links/$prefix
ln -s "$dir/$f" "$links/$prefix/$f"
done
cd $currdir
[Unit] Description=Create musics catalog Requires=storage-music-rock.mount After=storage-music-rock.mount Before=kodi.service [Service] Type=oneshot ExecStartPre=/bin/bash -c 'echo "Creating music catalog ..."' ExecStart=/bin/bash -c '/storage/.config/create_symb_links.sh /storage/music/rock /storage/music/rock_links' StandardOutput=tty [Install] WantedBy=multi-user.target
systemctl enable storage-music.mount systemctl enable storage-music-rock.mount systemctl enable catalog-music-rock.service
public interface HelloEjb extends Serializable {
public String hello();
}
@Local
public interface HelloEjbLocal extends HelloEjb {
}
@Remote
public interface HelloEjbRemote extends HelloEjb {
}
//@Local(HelloEjbLocal.class) // not needed
//@Remote(HelloEjbRemote.class) // not needed
@Stateless
public class HelloEjbImpl extends HelloEjbLocal, HelloEjbRemote {
public String hello() { return "hello world!"; }
}
// Notes: POJO must be called by class from the WAR
@EJB(name="helloEjbJndi", beanInterface=HelloEjbLocal.class)
public class HelloClient {
public HelloEjb getEjb() throws NamingException {
final InitialContext ctx = new InitialContext();
return (HelloEjb)ctx.lookup("java:comp/env/helloEjbJndi");
}
}
[root@laptop ~]$ bluetoothctl [NEW] Controller AA:BB:CC:DD:EE:FF laptop [default] [bluetooth]# power on Changing power on succeeded [bluetooth]# scan on Discovery started [CHG] Controller AA:BB:CC:DD:EE:FF Discovering: yes [NEW] Device F1:F2:F3:F4:F5:F6 CHRONOS ECO XXXX [bluetooth]# info F1:F2:F3:F4:F5:F6 Device F1:F2:F3:F4:F5:F6 Name: CHRONOS ECO XXXX Alias: CHRONOS ECO XXXX Appearance: 0x1234 Paired: no Trusted: no Blocked: no Connected: no LegacyPairing: no UUID: Vendor specific (6e400001-b5a3-f393-e0a9-e50e24dcca9e) [bluetooth]# trust F1:F2:F3:F4:F5:F6 [CHG] Device F1:F2:F3:F4:F5:F6 Trusted: yes Changing F1:F2:F3:F4:F5:F6 trust succeeded [bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successful [bluetooth]# pair F1:F2:F3:F4:F5:F6 Attempting to pair with F1:F2:F3:F4:F5:F6 [CHG] Device F1:F2:F3:F4:F5:F6 Connected: yes [CHG] Device F1:F2:F3:F4:F5:F6 UUIDs: 00001800-0000-1000-8000-00805f9b34fb 00001801-0000-1000-8000-00805f9b34fb 00001805-0000-1000-8000-00805f9b34fb 0000180a-0000-1000-8000-00805f9b34fb 0000180f-0000-1000-8000-00805f9b34fb 6e400001-b5a3-f393-e0a9-e50e24dcca9e [CHG] Device F1:F2:F3:F4:F5:F6 Paired: yes Pairing successful [bluetooth]# paired-devices Device F1:F2:F3:F4:F5:F6 CHRONOS ECO XXXX [bluetooth]# info F1:F2:F3:F4:F5:F6 Device F1:F2:F3:F4:F5:F6 Name: CHRONOS ECO XXXX Alias: CHRONOS ECO XXXX Appearance: 0x1234 Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Current Time Service (00001805-0000-1000-8000-00805f9b34fb) UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb) UUID: Vendor specific (6e400001-b5a3-f393-e0a9-e50e24dcca9e) [bluetooth]# quit
[root@laptop ~]$ gatttool -t random -I -b F1:F2:F3:F4:F5:F6 [F1:F2:F3:F4:F5:F6][LE]> connect Attempting to connect to F1:F2:F3:F4:F5:F6 Connection successful [F1:F2:F3:F4:F5:F6][LE]> primary attr handle: 0x0001, end grp handle: 0x0007 uuid: 00001800-0000-1000-8000-00805f9b34fb attr handle: 0x0008, end grp handle: 0x000b uuid: 00001801-0000-1000-8000-00805f9b34fb attr handle: 0x000c, end grp handle: 0x0011 uuid: 6e400001-b5a3-f393-e0a9-e50e24dcca9e attr handle: 0x0012, end grp handle: 0x0015 uuid: 0000180f-0000-1000-8000-00805f9b34fb attr handle: 0x0016, end grp handle: 0x0020 uuid: 0000180a-0000-1000-8000-00805f9b34fb attr handle: 0x0021, end grp handle: 0xffff uuid: 00001805-0000-1000-8000-00805f9b34fbConnect to handle of "Current Time Service" (00001805-0000-1000-8000-00805f9b34fb).
[F1:F2:F3:F4:F5:F6][LE]> characteristics 0x0021 0xffff handle: 0x0022, char properties: 0x12, char value handle: 0x0023, uuid: 00002a2b-0000-1000-8000-00805f9b34fbNote the "char value handle" and use it for reading characteristics data.
[F1:F2:F3:F4:F5:F6][LE]> char-read-hnd 0x0023 Characteristic value/descriptor: df 07 04 1A 16 0e 00 00 03 00 00 00the first two bytes are the year: 07df = 2015
[F1:F2:F3:F4:F5:F6][LE]> characteristics 0x0012 0x0015 handle: 0x0013, char properties: 0x12, char value handle: 0x0014, uuid: 00002a19-0000-1000-8000-00805f9b34fb [F1:F2:F3:F4:F5:F6][LE]> char-read-hnd 0x0014 Characteristic value/descriptor: 5aThis is the battery status (in percentage): 5a = 90
user@workstation:~$ bluetoothctl [bluetooth]# power on Changing power on succeeded [bluetooth]# pairable on Changing pairable on succeededSearch for new bluetooth devices - note the btaddress of the device (00:06:66:04:9E:4A). It is needed for all bluetooth commands
[bluetooth]# scan on Discovery started [CHG] Controller aa:bb:cc:dd:ee:ff Discovering: yes [NEW] Device 00:06:66:04:9E:4A FireFly-9E4A [bluetooth]# scan off Discovery stopped [CHG] Controller aa:bb:cc:dd:ee:ff Discovering: noRetrieve some information about the device
[bluetooth]# info 00:06:66:04:9E:4A Device 00:06:66:04:9E:4A Name: FireFly-9E4A Alias: FireFly-9E4A Class: 0x001f00 Paired: no Trusted: no Blocked: no Connected: no LegacyPairing: yesOptionally configure the device to be trusted - so if it automatically accepts generated PINs. However for legacy pairing manually entered PIN is required.
[bluetooth]# trust 00:06:66:04:9E:4A [CHG] Device 00:06:66:04:9E:4A Trusted: yes Changing 00:06:66:04:9E:4A trust succeededConfigure the bluetoothctl to be default agent for dealing with PIN code.
[bluetooth]# agent on Agent registered [bluetooth]# default-agent Default agent request successfulNow pair with the device
[bluetooth]# pair 00:06:66:04:9E:4A Attempting to pair with 00:06:66:04:9E:4A [CHG] Device 00:06:66:04:9E:4A Connected: yes Request PIN code [agent] Enter PIN code: 1234 [CHG] Device 00:06:66:04:9E:4A UUIDs: 00001101-0000-1000-8000-00805f9b34fb [CHG] Device 00:06:66:04:9E:4A Paired: yes Pairing successfulDouble check the pairing and quit
[bluetooth]# paired-devices Device 00:06:66:04:9E:4A FireFly-9E4A [bluetooth]# quit
user@workstation:~$ sdptool browse XX:XX:XX:XX:XX:XX
Service Name: Object Push Profile
Service RecHandle: 0x1000f
Service Class ID List:
"OBEX Object Push" (0x1105)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 2
"OBEX" (0x0008)
Profile Descriptor List:
"OBEX Object Push" (0x1105)
Version: 0x0100
user@workstation:~$ hcitool dev
Devices
hci0 aa:bb:cc:dd:ee:ff
The adapter is called hci0
Optionally the connection could be tested with the following command
user@workstation:~$ sudo rfcomm connect hci0 00:06:66:04:9E:4A 1Creating symlink to bluetooth serial port
user@workstation:~$ sudo rfcomm bind hci0 00:06:66:04:9E:4A 1Verifying that the connection is established
user@workstation:~$ sudo rfcomm -a rfcomm0: 00:06:66:04:9E:4A channel 1 connected [tty-attached]The serial (COM) port is available as /dev/rcomm0 Any terminal program can use it. With following command will configure rootooth bluetooth device to communicate with Roomba 520 at baud rate 115200
user@workstation:~$ sudo minicom -D /dev/rfcomm0 $$$ >CMD U,115K,N >AOK --- >END
user@workstation:~$ sudo rfcomm release hci0
user@workstation:~$ bluetoothctl [bluetooth]# disconnect 00:06:66:04:9E:4A Attempting to disconnect from 00:06:66:04:9E:4A Successful disconnected [bluetooth]# remove 00:06:66:04:9E:4A [DEL] Device 00:06:66:04:9E:4A FireFly-9E4A Device has been removed [bluetooth]# power off Changing power off succeeded