Tag Archives: CDN

Telehop Announces Positive Fourth Quarter and Year End 2012 Results

By Business Wirevia The Motley Fool

Filed under:

Telehop Announces Positive Fourth Quarter and Year End 2012 Results


Continued positive operating income and EBITDA growth create opportunities to strengthen market efforts

TORONTO–(BUSINESS WIRE)– Telehop Communications Inc. (“Telehop” or the “Company”), (TSX-V: HOP) today announced its financial performance during the fourth quarter and year ended December 31, 2012.

Telehop has returned operations to positive EBITDA and profitability for the year due to management’s sustained focus on operations and utilization of staffing and resources. The consecutive year-over-year performance improvements create opportunities for management to strengthen its market-facing efforts and expand into new markets.

“Telehop has made significant progress on our longer-term strategic initiatives and has become a stronger, better positioned company with positive results and talented people,” said Rajiv Jagota, President CEO, Telehop.

During the fourth quarter, Telehop saw EBITDA rise to $128,493 from $(380,599) during the same period last year. Operating income grew to $85,085 from $(602,192) a year ago. EBITDA for the year is positive $191,649 compared to $(749,678) in 2011 a change of $941,327.

Company highlights during the year include:

  • Launch of the new #100 mobile dial around service on the TELUS mobility network offering all TELUS prepaid and post-paid customers an easy dial around solution from their mobile phones.
  • The Company completed a private placement for the gross proceeds of CDN $750,000 through the issuance of 7,500,000 common shares for net proceeds of $653,024.
  • The Company has gone through a rebranding strategy and developed a new logo and look and feel to the Company, with a focus on a master brand strategy versus standalone brand advertising.
  • Improved accounts receivable and collections process reducing accounts receivable and bad debts exposure.
  • Successfully completed network and switching infrastructure upgrades to enhance quality of service, product offerings, and cost efficiencies.

FINANCIAL OVERVIEW

Neverland can be build

Cranes In The Sky.

Some of you dear readers might know about Neverland. The theme “engine” that drives a lot of our current KDE websites.

It is basically a design that is based on the Bootstrap CSS Framework, for which we write themes for the nearly dozen CMS we have. That includes phpBB, Drupal, Mediawiki, WordPress and others.

And that is the pain point basically. You have to maintain a lot of different theme files, all of them written in a different way, on top of a different CMS, with a different markup as well.

So we end up with one core css file on our CDN, and nearly a dozen customized css files for each of them. Plus the theme files.

That made me wonder if the situation could be improved with a custom build system. And after some fiddling – surprise surprise – i can proudly say i found a way to automate the build of each of those themes!

It – as of now – basically consists of a simple Makefile, which builds the CSS out of the less files, and fetches skeleton files to output theme files for each CMS, done with the help of node.js . The best is, not matter of what language the theme file is based on, it can be written.

It is extendable, every CMS gets its own build file. But the important thing is, you change your markup in one place, and each CMS theme can reflect that change.

Of course it is in a very early stage, and not finished, but once done maintenance mode goes down to just a single command and the server sync

That might sound quite boring for some, especially those who are used to build systems, but for me that is an exciting step forward. So exciting that i write such a blogpost.

Learn something new every day – Done for today

…read more
Source: FULL ARTICLE at Planet KDE

Storage migration: zones and metasets

By ossupport55

Hi all,

I’m in a situation which i need to understand the best way of doing a migration of storage involved in a zone.Elements involved are solaris 10 (Generic_144488-08), metasets. I need to provision more storage to the said non-global zone and not aware of the “best practices” from the Solaris side of it.
Having said more storage, these existing volumes from the storage end needs to change. Solaris will have new LUNs, yes i can have the existing allocation preserved and kept during the migration but has to go before releasing it to the owners. This can be treated as a storage migration.
Details of the zone and the metaset are as follows.

metastat -acp
d110 m 14GB d112 d111
d112 s 14GB /dev/dsk/c4t20000011C6C7668Bd0s0
d111 s 14GB /dev/dsk/c4t500000E011351110d0s0
d120 m 20GB d122 d121
d122 s 20GB /dev/dsk/c4t20000011C6C7668Bd0s1
d121 s 20GB /dev/dsk/c4t500000E011351110d0s1
d130 m 19GB d132 d131
d132 s 19GB /dev/dsk/c4t20000011C6C7668Bd0s3
d131 s 19GB /dev/dsk/c4t500000E011351110d0s3
d150 m 82GB d152 d151
d152 s 82GB /dev/dsk/c4t20000011C6C7668Bd0s5
d151 s 82GB /dev/dsk/c4t500000E011351110d0s5

zone1set/d225 p 7.0GB zone1set/d210
zone1set/d224 p 7.0GB zone1set/d210
zone1set/d223 p 30GB zone1set/d210
zone1set/d219 p 100GB zone1set/d210
zone1set/d218 p 10GB zone1set/d210
zone1set/d217 p 145GB zone1set/d210
zone1set/d216 p 193GB zone1set/d210
zone1set/d215 p 10GB zone1set/d210
zone1set/d214 p 30GB zone1set/d210
zone1set/d213 p 10GB zone1set/d210
zone1set/d210 m 599GB zone1set/d211
zone1set/d211 s 599GB /dev/dsk/c4t60B99000486E64366134576352666A79d0s0 /dev/dsk/c4t60B99000646654724C4A6A6863464954d0s0
zone1set/d200 m 49GB zone1set/d201
zone1set/d201 s 49GB /dev/dsk/c4t60B99000486E64366134576352675A66d0s0

=================================== ZONE CONFIG ==========================================
zonepath: /export/zones/zone1set
brand: native
autoboot: false
bootargs:
pool:
limitpriv:
scheduling-class:
ip-type: shared
hostid:
fs:
dir: /db2
special: /dev/md/zone1set/dsk/d213
raw: /dev/md/zone1set/rdsk/d213
type: ufs
options: []
fs:
dir: /db2/CDN/log_archive
special: /dev/md/zone1set/dsk/d214
raw: /dev/md/zone1set/rdsk/d214
type: ufs
options: []
fs:
dir: /db2/CDN/log_dir
special: /dev/md/zone1set/dsk/d215
raw: /dev/md/zone1set/rdsk/d215
type: ufs
options: []
fs:
dir: /db2/CDN/sapdata1
special: /dev/md/zone1set/dsk/d216
raw: /dev/md/zone1set/rdsk/d216
type: ufs
options: []
fs:
dir: /db2/CDN/sapdata2
special: /dev/md/zone1set/dsk/d217
raw: /dev/md/zone1set/rdsk/d217
type: ufs
options: []
fs:
dir: /db2/CDN/saptemp
special: /dev/md/zone1set/dsk/d218
raw: /dev/md/zone1set/rdsk/d218
type: ufs
options: []
fs:
dir: /db2backups
special: /dev/md/zone1set/dsk/d219
raw: /dev/md/zone1set/rdsk/d219
type: ufs
options: []
fs:
dir: /interfaces
special: /dev/md/zone1set/dsk/d223
raw: /dev/md/zone1set/rdsk/d223
type: ufs
options: []
fs:
dir: /sapmnt
special: /dev/md/zone1set/dsk/d224
raw: /dev/md/zone1set/rdsk/d224
type: ufs
options: []
fs:
dir: /usr/sap
special: /dev/md/zone1set/dsk/d225
raw: /dev/md/zone1set/rdsk/d225
type: ufs
options: []
net:
address: 10.4.88.211
physical: ce0
defrouter not specified

Pour in all your thoughts. Thanks for your time in advance.
Cheers
TIm from Mel

Source: FULL ARTICLE at The UNIX and Linux Forums