A critical vulnerability has been reported in the GNU Bourne-Again Shell (also known as Bash), the common command-line shell used in many Linux/UNIX operating systems and Apple’s Mac OS X. This flaw could allow an attacker to remotely execute shell commands by attaching malicious code in environment variables used by the operating system.
<br>
Are Exacq products affected?
Exacq does not believe that any current exacqVision software packages have direct vulnerability associated with Bash. However, several Ubuntu/Linux core operating system components and other software used within the operating system are affected. Also, exacqVision Web Service versions released before December 2013 are vulnerable (versions 3.2.1 and later are not affected).
<br>
How do I protect my systems?
NOTE: As the Linux community improves its solutions to patch the vulnerable code, this article will be updated with new information. Please revisit this article periodically to check for any changes. (Permalink: https://exacq.com/kb/?crc=13518)
<br>
Currently, there are several things you can do to limit the situations that could make your system vulnerable:
Use static IP addresses to reduce vulnerability, as DHCP is affected
<br>
Update Bash to the latest version using one of the following options:
a.) Browse to https://exacq.com/files and click the Shellshock folder. Download the .deb file and copy it to the Ubuntu Desktop. Double-click the file and wait for the patch to install.
b.) Open a command prompt and run the following commands:
sudo apt-get update sudo apt-get install bash
<br>
NOTE: All exacqVision systems shipped after October 6, 2014 will have the latest Bash version installed at the time of manufacture.
NOTE: If you are running 8.04Ubuntu, these patches will not work. You must either upgrade your server to 10.04 Ubuntu or higher, or apply a third-party patch. Exacq has tested the patch at the following location and has not found any issues with the DEB file near the bottom of the page: http://uwekamper.de/how-i-patched-the-gnu-bash-shellshock-bug-on-ubuntu-804-hardy-heron.html
In April 2014 a Security Advisory was issued by the OpenSSL project notifying the public of a serious vulnerability in the encryption software used by a large number of companies. (For detailed information, visit http://heartbleed.com/.) Exacq Technologies took immediate action to assess how its products might be affected by this vulnerability.
<br>
The exacqVision S-Series uses Ubuntu 12.04 with the version of OpenSSL that could be affected. However, the vulnerability exists only if you have installed the exacqVision Web Service on your S-Series system and you are using SSL connections on the exacqVision web server, which is not the default configuration. If you have manually set up that configuration, complete the following procedure to ensure you do not have any issues. (If you are not using SSL in the web server, this procedure is optional.
<br>
Affected Versions
All exacqVision S-Series Servers manufactured before Apr 10, 2014 (including S-Series Version A, S-Series Version B-1 B-2)
Click on the Heartbleed folder and download the two files to the Desktop. Alternately, you can download them to a portable drive and save them to the server.
Double-click each file to install.
If you see a message stating that a newer repository is available, click OK to continue the installation.
After the installations are complete, delete the files from the Desktop.
If you have configured SSH connections to the computer, the next time you connect you will get a Security Warning message. This is expected, and the script will update the server’s SSH keys.
NOTE: This document only applies to exacqVision Web Service 2.4.0 to 8.8. Web Service 9.0.0 replaced Apache with proprietary WFE service.
If your exacqVision Web Service is connected to the Internet, the server could be located using certain search parameters in a search engine. To hide the server from an Internet search engine, complete the following procedure:
<br>
Note: Depending on the operating system, you might need to log in as an administrator to complete this process.
Browse to C:\Program Files\exacqVision\WebService\Apache2.2\htdocs.
Use Notepad to create a text file named robots.txt.
Add the following lines to disallow all indexing on the entire Web Service:
Restart the Web Service to ensure all changes are published.
If you see motion images from a Bosch camera that appear to be out of order, the issue can often be resolved by selecting a different setting for the camera’s GOP Structure. To change the setting, complete the following steps:
<br>
Open the camera’s web configuration page by entering it’s IP address in an Internet browser.
Open the Settings page and select Advanced Mode in the menu on the left.
Select the Cameras entry and then Encoder Profile.
Click the Expert Settings button to reveal additional options, including GOP Structure.
Make sure IP (which stands for I Frames, B Frames, and P Frames) is selected in the GOP Structure drop-down list.
Follow the instructions in Article 1002 to configure HTTPS support in the Web Service.
<br>
Version 8.2 and Lower
SSL, a security system combining authentication and encryption, is used to protect communication between a web server and client. Enabling SSL on a web server allow all clients connecting to that server two key protections:
The client is able to identify the server. There is no way for a fake server to misrepresent itself to a client.
The communication between the client and server is encrypted, preventing a third-party from seeing what data is sent. This ensures the safety of private communication such as usernames and passwords, video data, and more.
NOTES:
This article assumes that exacqVision Web Service version 3.10 or later has been installed with default settings. If you are running version 3.0 to 3.8, see the attached legacy PDF.
A self-signed certificate allows you to use a web browser, but it does not work with mobile devices. Only trusted third-party certificates work with mobile devices.
To use SSL with exacqVision Web Server in Linux, complete the following steps:
Stop exacqVision Web Server by typing sudo /usr/local/exacq/webservice/service.sh stop in a Terminal window.
Open the Web Server Apache Configuration file by typing sudo gedit /etc/evapache/httpd.conf in a Terminal window. Find the following lines:
Delete the pound signs (#) at the beginning of each line.
Save and close the file.
It is recommended, but not required, that you disable the access log for SSL, as this file can grow very large. To do this, open the Apache SSL Configuration file by typing sudo gedit /etc/evapache/extra/httpd-ssl.conf in a Terminal window. Find the line with the following text:
TransferLog “${SRVROOT}/logs/access.log” Change it to:#TransferLog “${SRVROOT}/logs/access.log”When finished, save and close the file.
Open the Web Service configuration file by typing sudo gedit /etc/webservice.conf Add the following lines to the end of the document:
If you were issued certificates, rename them to server.crt and server.key and save them to the /etc/evapache directory and then skip to Step 10. Otherwise, continue with the following steps.
Run cd /etc/evapache in a Terminal window.
To create a self-signed certificate, type sudo openssl req -new -x509 -sha256 -days 365 -nodes -out /etc/evapache/server.crt -keyout /etc/evapache/server.key and answer the questions. NOTE: COMMON NAME should be the IP address or FQDN that you use for access to your exacqVision Web Service.
Re-start exacqVision Web Server by typing sudo /usr/local/exacq/webservice/service.sh restart.
NOTE:Â To connect to exacqVision Web Server using SSL, you must use HTTPS instead of HTTP.
Troubleshooting
If exacqVision Web Service does not start after configuring it for SSL, complete the following steps:
Open the Apache error logs, found by default at /user/local/exacq/webservice/evapache/logs/error_log.
Look for an entry similar to the following:
[Wed Mar 04 09:08:54.512004 2015] [ssl:emerg] [pid 19116] AH02565: Certificate and private key www.example.com:443:0 from CERTIFCATE_FILE_NAME.crt and KEYFILE_NAME.key do not match AH00016: Configuration Failed
If you see this entry, complete the following steps:
a.) Run the following commands, replacing the values in all caps with your values:
b.) Compare the result values from all of the calls. Each resulting string should be identical. If the values do not match, confer with the certificate authority that issued the certificate.
NOTE: Web Sockets communication will not work using SSL encryption for Web Service versions 7.2.0 – 7.2.6.
Workaround
Disable web sockets in the client configuration page of the browser Client.
Resolution
Update to exacqVision Web Service version 8.4 or later.
These instructions only apply to web services 9.4 and earlier.Â
The changes described only affect the default image quality in “simple” mode and this process is not upgrade safe. You must perform this process again each time you upgrade Web Server.
<br>
For Windows: Browse to C:\Program Files\exacqVision\WebService\bin\templates.
For Linux: Browse to /usr/local/exacq/webservice/bin/templates.
Change the values to match your preferred settings for the following parameters:
NOTE: Starting in Web Server 2.1, the following values are stored in a cookie generated from the Web Server. However, you can add these values to the config.html.mako file to override the cookie.
w = width h = height q = quality r = refresh interval
Save the file.
Open or refresh the Web Server page in your web browser.
The codec used to transmit video will depending on the plugin used. In many cases the exacqVision Web Service performs transcoding and transmits a compressed JPEG stream of images to the Web Client or Exacq Mobile 3 app. Some plugins are capable of forwarding the H.264 stream without the need to transcode.
exacqVision software can be thought of as a suite of applications that work together to provide different services.
The primary application is the exacqVision Server, which records video, audio, and event data. The exacqVision Client provides an interface to view live and recorded video as well as to configure the server application. A single site may have the exacqVision Client installed on many workstations. The exacqVision Web Service connects to the server application as well to provide the ability to view live and recorded video via web browser or mobile app.
These may be updated using the user interface, or by downloading and manually running installers for the newer version.
When opting to update one of these applications it is not uncommon for users to forget to update the others. This guide will explain how to update each of these applications on both Windows and Linux machines. Use the Contents menu to skip to sections relevant to your installation.<br><br>
exacqVision Client
‘Check for Updates’ using the Client
The exacqVision Desktop Client software for Windows, Linux, and Mac operating systems provides an easy way to update the software using the ‘Check for Updates’ button.
Open the exacqVision Client software.<br><br>
Click the exacqVision logo in the upper corner. <br><br>
Click the ‘Check for Updates’ button. NOTE: This requires the client workstation to have internet access.<br><br>
Allow the update to download. <br><br>
When ready, click the ‘Install’ button. <br><br>
The Client installer requires the Client software to be closed during update. Click ‘Yes’ to automatically close the Client application and continue with the update. <br><br>
The Client installer will complete and you may reopen the Client application to continue use.
NOTE: This only updates the Client software on the machine it was performed on. Each client workstation should be updated.<br><br>
Download the exacqVision Client installer beneath the section for your operating system (Windows, Linux, or MacOS).<br> Avoid using the ‘exacqVision Server Bundle’ to update client workstations. You may unintentionally install additional instances of the exacqVision Server and/or Web Service on your network which could lead to user problems.<br> NOTE: Only 64-bit installers are provided for current versions here. Refer to Legacy Software Downloads for 32-bit software.<br><br>
Install the new version.
Windows:
Run the downloaded .EXE executable by double-clicking it. Unless you’ve changed the download location, it will likely be located in your Downloads directory.
Linux (Ubuntu/Debian):
Run the downloaded .DEB installer by double-clicking it. Unless you’ve changed the download location, it will likely be located in your Downloads directory.
MacOS:
Double-click the downloaded .DMG file to open it.
Drag the ‘edvrclient’ and ‘ePlayerPro’ icons into the ‘Applications’ folder.<br><br>
On Windows and Linux, follow the prompts to complete the Client software update. NOTE: This only updates the Client software on the machine it was performed on. Each client workstation should be updated.<br><br>
Client software deployment
Windows .MSI installers are also provided on the Software Downloads page for those users that need to provide software deployments.<br><br>
exacqVision Server
Before Server Update – Best Practice
Prior to making changes to your server installation, it is best practice to export a copy of your server’s settings.
Open the exacqVision Client application and change to the Configuration screen by clicking the gear icon from the upper-left of the toolbar.<br><br>
You will need to be connected to the exacqVision Server with administrator privileges. Logged in user accounts can be changed by navigating to the ‘Add Systems’ page and highlighting the server of your choice then changing the ‘Username’ and ‘Password’ used to connect.<br><br>
While logged in with administrator privileges, use the navigation panel on the left-hand side to expand the tree under the name of your server by clicking the + symbol beside the server name.<br><br>
Click on the ‘Configure System’ node beneath it. <br><br>
Select the ‘System’ tab and locate the ‘Settings’ section. Click the ‘Export’ button to save your server’s settings for safe keeping. If keeping several backups, it may be helpful to name the exported files with the date the export was performed. <br><br>
‘Check for Updates’ on Server
Open the exacqVision Client application and change to the Configuration screen by clicking the gear icon from the upper-left of the toolbar.<br><br>
You will need to be connected to the exacqVision Server with administrator privileges. Logged in user accounts can be changed by navigating to the ‘Add Systems’ page and highlighting the server of your choice then changing the ‘Username’ and ‘Password’ used to connect.<br><br>
While logged in with administrator privileges, use the navigation panel on the left-hand side to expand the tree under the name of your server by clicking the + symbol beside the server name.<br><br>
Click on the ‘Configure System’ node beneath it. <br><br>
Select the ‘Update’ tab from the list of tabs across the top of the ‘Configure System’ page. The tab displays the current exacqVision Server version and provides a ‘Check for Updates’ button. <br><br>
Click the ‘Check for Updates’ button. NOTE: This requires the system running the exacqVision Server application to have internet access.<br><br>
The Version drop-down menu will populate with all available versions, automatically choosing the latest version that your system is licensed to use. NOTE: If your server license is expired, only versions released prior to your license expiration date will be available to you.<br><br>
After making the version selection, click the ‘Update’ button. NOTE: The server will go offline during this process and pause recording during that time. This could take several minutes depending on your system. Click ‘Continue’ to accept.<br><br>
The server will begin the process of downloading the update and installing the new version. The Client software will reconnect to the Server once the update has completed and the service returns.<br><br>
Download the exacqVision Server installer beneath the section for your operating system (Windows, Linux).<br> NOTE: Only 64-bit installers are provided for current versions here. Refer to Legacy Software Downloads for 32-bit software.<br><br>
Install the new version.
Windows:
Run the downloaded .EXE executable by double-clicking it. Unless you’ve changed the download location, it will likely be located in your Downloads directory.
Linux (Ubuntu/Debian):
Run the downloaded .DEB installer by double-clicking it. Unless you’ve changed the download location, it will likely be located in your Downloads directory.
Follow the prompts to complete the Server software update. NOTE: This only updates the Server software on the machine it was performed on. Client software is unaffected. See Client updates section for more.<br><br>
exacqVision Web Service
‘Check for Updates’ in Web Service
Open a web browser and navigate to the Web Service landing page. By default the Web Service uses port 80, so using the browser on the system running the exacqVision Web Service, it can be reached at http://127.0.0.1<br><br>
On the landing page, a link for ‘Web Service Configuration’ can be found in the lower corner. Click this link. NOTE: If you cannot see this, you may not be using the browser on the system running the Web Service, and/or the configuration settings to display this link may have been changed.<br><br>
Log into the Web Service Configuration using the administrator account configured for the web service.<br><br>
From the left-hand side, expand the ‘Configuration’ menu, then select ‘Updates’. <br><br>
Click the ‘Check For Updates’ button. You will be notified if an update to your existing version exists. Click to ‘Install’ the update. <br><br>
Confirm the install. NOTE: The web service will be unreachable by your site’s web and mobile users during the software update, which could take several minutes.<br><br>
The Web Service will restart when the update has finished. <br><br>
Download the exacqVision Web Service installer beneath the section for your operating system (Windows, Linux).<br> NOTE: Only 64-bit installers are provided for current versions here. Refer to Legacy Software Downloads for 32-bit software.<br><br>
Install the new version.
Windows:
Run the downloaded .EXE executable by double-clicking it. Unless you’ve changed the download location, it will likely be located in your Downloads directory.
Linux (Ubuntu/Debian):
Run the downloaded .DEB installer by double-clicking it. Unless you’ve changed the download location, it will likely be located in your Downloads directory.
Follow the prompts to complete the Web Service software update. NOTE: This only updates the Web Service software on the machine it was performed on.<br><br>
Yes, ExacqVision Server has been tested on the following:
Ubuntu 22.04 (64-bit)
Ubuntu 20.04 (64-bit)
Ubuntu 18.04 (64-bit)
Ubuntu 16.04 (64-bit)
Ubuntu 14.04 (64-bit or 32-bit with PAE1)
Ubuntu 12.04 (32-bit with PAE1)2
Ubuntu 10.04 (32-bit with PAE1)2
Version numbers are listed as YY.MM.
ExacqVision supports Ubuntu LTS releases only. Canonical provides LTS releases every two years. Long Term Support (LTS) lasts for a period of 10 years after release. ExacqVision will provide support for future LTS releases of Ubuntu as they become available.<br>
PAE stands for Physical Address Extension, which allows 32-bit systems to use more than 4GB of memory.
These versions are no longer receiving security updates from Canonical. At the end of long term support, future Exacq software releases will not be tested on these versions.
The settings for the storage device iqn.2001-04.com.example:storage.lun1 on 192.168.0.101:3260,1 are stored in the file /etc/iscsi/nodes/iqn.2001-04.com.example:storage.lun1/192.168.0.101,3260,1/default.
<br>
We need to set the username and password for the target in that file; instead of editing that file manually, we can use the iscsiadm command to do this for us:
server1:~# iscsiadm -m node --targetname "iqn.2001-04.com.example:storage.lun1" --portal "192.168.0.101:3260" --login Logging in to [iface: default, target: iqn.2001-04.com.example:storage.lun1, portal: 192.168.0.101,3260] Login to [iface: default, target: iqn.2001-04.com.example:storage.lun1, portal: 192.168.0.101,3260]: successful server1:~#
<br>
… or by restarting the initiator:
sudo /etc/init.d/open-iscsi restart
<br>
(If you want to log out, you can run iscsiadm -m node --targetname "iqn.2001-04.com.example:storage.lun1" --portal "192.168.0.101:3260" --logout)
<br>
If your iSCSI device has already been formated, and contains data, please skip to Mounting your drive.
<br>
Continue on ONLY if your device is being set up for the first time, or you instructed to do so by tech support.
<br>
In the output of
<br>
sudo fdisk -l
<br>
you should now find a new hard drive (/dev/sdb in this example); that’s our iSCSI storage device:
<br>
server1:~# fdisk -l
Disk /dev/sda: 32.2 GB, 32212254720 bytes 255 heads, 63 sectors/track, 3916 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00031334
Device Boot Start End Blocks Id System /dev/sda1 * 1 3749 30113811 83 Linux /dev/sda2 3750 3916 1341427+ 5 Extended /dev/sda5 3750 3916 1341396 82 Linux swap / Solaris
Disk /dev/sdb: 21.4 GB, 21474836480 bytes 64 heads, 32 sectors/track, 20480 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Disk identifier: 0x00000000
Disk /dev/sdb doesn't contain a valid partition table server1:~#
<br>
To use that device, we must format it (replace /dev/sdX with the value obtained from the last command):
<br>
sudo fdisk /dev/sdX
<br>
server1:~# fdisk /dev/sdb Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel Building a new DOS disklabel with disk identifier 0x882944df. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won’t be recoverable.
<br>
The number of cylinders for this disk is set to 20480. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
<br>
Command (m for help): <– m Command action a toggle a bootable flag b edit bsd disklabel c toggle the dos compatibility flag d delete a partition l list known partition types m print this menu n add a new partition o create a new empty DOS partition table p print the partition table q quit without saving changes s create a new empty Sun disklabel t change a partition’s system id u change display/entry units v verify the partition table w write table to disk and exit x extra functionality (experts only)
<br>
Command (m for help): <– n Command action e extended p primary partition (1-4) <– p Partition number (1-4): <– 1 First cylinder (1-20480, default 1): <– ENTER Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-20480, default 20480): <– ENTER Using default value 20480
<br>
Command (m for help): <– t Selected partition 1 Hex code (type L to list codes): <– L
<br>
0 Empty 1e Hidden W95 FAT1 80 Old Minix be Solaris boot 1 FAT12 24 NEC DOS 81 Minix / old Lin bf Solaris 2 XENIX root 39 Plan 9 82 Linux swap / So c1 DRDOS/sec (FAT- 3 XENIX usr 3c PartitionMagic 83 Linux c4 DRDOS/sec (FAT- 4 FAT16 <32M 40 Venix 80286 84 OS/2 hidden C: c6 DRDOS/sec (FAT- 5 Extended 41 PPC PReP Boot 85 Linux extended c7 Syrinx 6 FAT16 42 SFS 86 NTFS volume set da Non-FS data 7 HPFS/NTFS 4d QNX4.x 87 NTFS volume set db CP/M / CTOS / . 8 AIX 4e QNX4.x 2nd part 88 Linux plaintext de Dell Utility 9 AIX bootable 4f QNX4.x 3rd part 8e Linux LVM df BootIt a OS/2 Boot Manag 50 OnTrack DM 93 Amoeba e1 DOS access b W95 FAT32 51 OnTrack DM6 Aux 94 Amoeba BBT e3 DOS R/O c W95 FAT32 (LBA) 52 CP/M 9f BSD/OS e4 SpeedStor e W95 FAT16 (LBA) 53 OnTrack DM6 Aux a0 IBM Thinkpad hi eb BeOS fs f W95 Ext'd (LBA) 54 OnTrackDM6 a5 FreeBSD ee EFI GPT 10 OPUS 55 EZ-Drive a6 OpenBSD ef EFI (FAT-12/16/ 11 Hidden FAT12 56 Golden Bow a7 NeXTSTEP f0 Linux/PA-RISC b 12 Compaq diagnost 5c Priam Edisk a8 Darwin UFS f1 SpeedStor 14 Hidden FAT16 <3 61 SpeedStor a9 NetBSD f4 SpeedStor 16 Hidden FAT16 63 GNU HURD or Sys ab Darwin boot f2 DOS secondary 17 Hidden HPFS/NTF 64 Novell Netware b7 BSDI fs fd Linux raid auto 18 AST SmartSleep 65 Novell Netware b8 BSDI swap fe LANstep 1b Hidden W95 FAT3 70 DiskSecure Mult bb Boot Wizard hid ff BBT 1c Hidden W95 FAT3 75 PC/IX Hex code (type L to list codes): <-- 83
<br>
Command (m for help): <– w The partition table has been altered!
<br>
Calling ioctl() to re-read partition table. Syncing disks. server1:~#
<br>
Afterwards, the output of
<br>
sudo fdisk -l
<br>
should look as follows:
<br>
server1:~# fdisk -l
<br>
Disk /dev/sda: 32.2 GB, 32212254720 bytes 255 heads, 63 sectors/track, 3916 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00031334
<br>
Device Boot Start End Blocks Id System /dev/sda1 * 1 3749 30113811 83 Linux /dev/sda2 3750 3916 1341427+ 5 Extended /dev/sda5 3750 3916 1341396 82 Linux swap / Solaris
<br>
Disk /dev/sdb: 21.4 GB, 21474836480 bytes 64 heads, 32 sectors/track, 20480 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Disk identifier: 0x882944df
<br>
Device Boot Start End Blocks Id System /dev/sdb1 1 20480 20971504 83 Linux server1:~#
<br>
Now we create a filesystem on /dev/sdb1…
<br>
sudo mkfs.ext3 /dev/sdX1
<br>
Issue the following command, and make note of the largest number listed< /p>
<br>
ls /mnt/edvr/
<br>
server1:~# ls /mnt/edvr 0 1 server1:~#
<br>
Mount the drive with the command below, substituting Y with the the largest number returned from the previous command + 1 (2 in our example)
<br>
sudo mount /dev/sdX1 /mnt/edvr/2
<br>
You should now see the new device in the outputs of…
sudo mount
<br>
server1:~# mount /dev/sda1 on / type ext3 (rw,errors=remount-ro) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) /dev/sdX1 on /mnt/edvr/2 type ext3 (rw) server1:~#
To have the device mounted automatically at boot time, e.g. in the directory /storage, we create that directory…
<br>
mkdir /storage
<br>
… and add the following line to /etc/fstab:
<br>
sudo nano /etc/fstab
<br>
For test purposes, you can now reboot the system:
<br>
sudo reboot
<br>
After the reboot, the device should be mounted:
<br>
sudo mount
<br>
server1:~# mount /dev/sda1 on / type ext3 (rw,errors=remount-ro) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) /dev/sdX1 on /mnt/edvr/Y type ext3 (rw,_netdev) server1:~#
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
