Sponsored Content
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News New Wall Street film shows that technology never sleeps Post 302462142 by Linux Bot on Wednesday 13th of October 2010 11:15:02 AM
Old 10-13-2010
New Wall Street film shows that technology never sleeps

Giles Nelson
10-13-2010 11:12 AM
After encountering the latest Wall Street film ‘Money Never Sleeps' earlier this week, it's apparent that it's not just the then-brick-sized mobile phones that have changed since the 1987 installmen

The movie opens with Gordon Gekko, the man who so famously stated, “greed is good” in the first film, being released from jail. It's a comical scene contrasting the technology of the '80s to the tech of today, as the guard returns Gekko's bulky mobile phone. Gekko is released into a world where the nature of how the financial world is run has completely changed. However, it was only after recently revisiting the original movie, you come to realise just how much advances in technology has fundamentally changed the way in which the trading floor environment operate

Take High frequency trading (HFT), the use of technology to monitor and submit orders to markets extremely quickly, which has been receiving a lot of bad press recently and is sometimes described as “abusive”. It is no more abusive than two traders making trades using only the telephone, as was the case in a scene from the original Wall Street fil

Yes, it can be used for rogue trading by the likes of Gekko, but so can any other technology. Technology itself is morally neutral. Similarly, algorithmic trading is also seen by some as an industry curse. Credit Suisse has been fined this year by an exchange after its algorithmic trading system went out of control and bombarded the exchange with hundreds of thousands of erroneous orders. However, this wasn't a deliberate attempt to manipulate the market. It was a mistake, albeit a careless one. There just weren't proper controls in place to protect the market from what, ultimately, was human error - the algorithms hadn't been tested sufficientl

There is no doubting that technology has generated enormous benefits for trading - greater efficiencies, more market liquidity, tighter spreads and better prices for all. To lose these benefits because of perception would be very dangerous. Having said this, technology has also made the markets faster and more complex. Therefore, all market participants need to up their game by deploying modern day monitoring capabilities to spot trading anomalies to help capture the next generation Gekkos.



Source...
 

We Also Found This Discussion For You

1. Linux

micro film scanner

epson microfilm 500 scsi: Is there any way to make this work under linux ? I'm using pclinuxos, it shows the machine in the device panel as sg2 and lists the machine , so Im guessing the kernel knows what it is, but I can't view it as a scanner or capture or input device . What catagory does... (4 Replies)
Discussion started by: tom1200
4 Replies
SYSTEMD-DETECT-VIRT(1)						systemd-detect-virt					    SYSTEMD-DETECT-VIRT(1)

NAME
systemd-detect-virt - Detect execution in a virtualized environment SYNOPSIS
systemd-detect-virt [OPTIONS...] DESCRIPTION
systemd-detect-virt detects execution in a virtualized environment. It identifies the virtualization technology and can distinguish full machine virtualization from container virtualization. systemd-detect-virt exits with a return value of 0 (success) if a virtualization technology is detected, and non-zero (error) otherwise. By default, any type of virtualization is detected, and the options --container and --vm can be used to limit what types of virtualization are detected. When executed without --quiet will print a short identifier for the detected virtualization technology. The following technologies are currently identified: Table 1. Known virtualization technologies (both VM, i.e. full hardware virtualization, and container, i.e. shared kernel virtualization) +----------+----------------+--------------------------------------+ |Type | ID | Product | +----------+----------------+--------------------------------------+ |VM | qemu | QEMU software virtualization, | | | | without KVM | | +----------------+--------------------------------------+ | | kvm | Linux KVM kernel virtual machine, | | | | with whatever software, except | | | | Oracle Virtualbox | | +----------------+--------------------------------------+ | | zvm | s390 z/VM | | +----------------+--------------------------------------+ | | vmware | VMware Workstation or Server, and | | | | related products | | +----------------+--------------------------------------+ | | microsoft | Hyper-V, also known as Viridian or | | | | Windows Server Virtualization | | +----------------+--------------------------------------+ | | oracle | Oracle VM VirtualBox (historically | | | | marketed by innotek and Sun | | | | Microsystems), | | | | for legacy and KVM | | | | hypervisor | | +----------------+--------------------------------------+ | | xen | Xen hypervisor (only domU, not dom0) | | +----------------+--------------------------------------+ | | bochs | Bochs Emulator | | +----------------+--------------------------------------+ | | uml | User-mode Linux | | +----------------+--------------------------------------+ | | parallels | Parallels Desktop, Parallels Server | | +----------------+--------------------------------------+ | | bhyve | bhyve, FreeBSD hypervisor | +----------+----------------+--------------------------------------+ |Container | openvz | OpenVZ/Virtuozzo | | +----------------+--------------------------------------+ | | lxc | Linux container implementation by | | | | LXC | | +----------------+--------------------------------------+ | | lxc-libvirt | Linux container implementation by | | | | libvirt | | +----------------+--------------------------------------+ | | systemd-nspawn | systemd's minimal container | | | | implementation, see systemd- | | | | nspawn(1) | | +----------------+--------------------------------------+ | | docker | Docker container manager | | +----------------+--------------------------------------+ | | rkt | rkt app container runtime | +----------+----------------+--------------------------------------+ If multiple virtualization solutions are used, only the "innermost" is detected and identified. That means if both machine and container virtualization are used in conjunction, only the latter will be identified (unless --vm is passed). OPTIONS
The following options are understood: -c, --container Only detects container virtualization (i.e. shared kernel virtualization). -v, --vm Only detects hardware virtualization). -r, --chroot Detect whether invoked in a chroot(2) environment. In this mode, no output is written, but the return value indicates whether the process was invoked in a chroot() environment or not. --private-users Detect whether invoked in a user namespace. In this mode, no output is written, but the return value indicates whether the process was invoked inside of a user namespace or not. See user_namespaces(7) for more information. -q, --quiet Suppress output of the virtualization technology identifier. -h, --help Print a short help text and exit. --version Print a short version string and exit. EXIT STATUS
If a virtualization technology is detected, 0 is returned, a non-zero code otherwise. SEE ALSO
systemd(1), systemd-nspawn(1), chroot(2), namespaces(7) systemd 237 SYSTEMD-DETECT-VIRT(1)
All times are GMT -4. The time now is 11:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy