text:
Row as Benefits show hits Stockton
A council leader has said the makers of the controversial reality TV show Benefits Street have ignored pleas to stay away from his town.
Filming for the second series of the Channel 4 show has begun in Kingston Road, Stockton, Teesside, despite opposition from local MPs, residents' groups and the local authority.
The first series of Benefits Street made a star of Deirdre Kelly, better known as White Dee, who is currently appearing in Celebrity Big Brother.
The first series of Benefits Street was made in James Turner Street in Birmingham
Filmed in James Turner Street, Winson Green, Birmingham, it set out to depict a close-knit community where many of the residents received benefits.
Critics of the show claimed it exploited the participants and branded it "poverty porn".
Ofcom received 900 complaints about the shows, first broadcast in January, but it cleared the broadcaster of breaching any rules.
Stockton Council leader Bob Cook is concerned the show will damage his town.
He said: "I am deeply disappointed to learn that the programme-makers have chosen Stockton despite the local residents' associations, residents, MP and council all making it clear that they aren't welcome.
"They have ignored us in pursuit of their own needs and I am extremely concerned about the way in which the fantastic people who live and work in Stockton Borough will be portrayed by this programme.
"The vast majority of people know that the programme plays to negative stereotypes and I'm certain it won't reflect the amazing sense of community we have here in Stockton.
"We understand the difficulties many of our residents are facing given the current economic situation but that's why we are focusing our efforts on protecting our most vulnerable residents, attracting investment and jobs as well as improving facilities.
"It's a shame that the programme won't be showing any of the recent brilliant examples of great community spirit such as the 1,245 Sunflower Project, Stockton's Community Carnival or our residents' involvement in Sky TV's Big Town Dance.
"Let's not forget, the borough has had a whole host of accolades in the last few weeks which highlight what a fantastic place Stockton is and that the economy is performing strongly.
"No doubt this programme won't highlight the excellent work that is on-going to make our town an even better place to live and work."
James Wharton, Tory MP for Stockton South - the neighbouring constituency to where filming is happening - said: "Lots of great things are happening in Stockton and I worry this programme will ignore that and reflect badly on the town.
"I don't want them here making a programme which will show people in the worst possible light and potentially do such huge damage.
"For the producers it's easy ratings for a few weeks, but the damage they do can last much longer.
"They should think again, not just about coming here but the whole nature of the programmes they make."
Alex Cunningham, Labour MP for Stockton North, where the show is being filmed, was "deeply disappointed".
He said: "There is no doubt this is about exploiting vulnerable people in order to make money.
"I know they will say it is about trying to give people a voice, but all they will do is expose them to the full glare of the national media."
Mr Cunningham was on holiday but said he will visit the street when he returns.
"I would hope we can still get people to pull out," he said.
Kingtson Road is a terraced street north of Stockton town centre where a three-bedroom house would sell for around £50,000, according to the Zoopla property website.
Sorry we are not currently accepting comments on this article.


text:
The following pages link to GeometryMANIFEST:
"We're mortal -- which is to say, we're ignorant, stupid, and sinful --
but those are only handicaps. Our pride is that nevertheless, now and then, we do our best.
A few times we succeed. What more dare we ask for?" - Ensign Flandry
All trademarks referenced herein are the properties of their respective owners. This site is not sponsored, endorsed, or run by the U.S. Government.

subset: commoncrawl


text:
Difference between revisions of "Install The 2007 PPC Gentoo"
Mindbender (Talk | contribs)
m (→Install EM mode utilities)
Mindbender (Talk | contribs)
m (→Install EM mode utilities)
|Line 35:
|Line 35:
After it boots to EM mode, use any FTP client to upload EM_mode_binaries.tar.gz to /tmp on the Kuro (hint: Windows may change the extension of the file when you download it from the internet).
After it boots to EM mode, use any FTP client to upload EM_mode_binaries.tar.gz to /tmp on the Kuro (hint: Windows may change the extension of the file when you download it from the internet).
Revision as of 14:12, 6 November 2007
Current Gentoo Image Date: 2007/11/04
Using this method, you can install an entire Gentoo image complete with portage and overlay in about 15 minutes (actually with downloading and unpacking I think it might be more like 30 - 45 minutes).
These instructions are admittedly kurobox centric, however PPC linkstations should work with the image as well. Please add to or correct these instructions to make them work for both platforms if you find anything missing or confusing.
The image was created immediately following a deep world update. There is only one version of the gentoo image (previous image had two versions). The only requirement is that your box must have uboot that boots a 2.6 kernel. The 1.2 uboot that supports a dtb is preferred, and in fact the image includes a 2.6.22 kernel and dtb file, generated from gentoo-sources.
- 1 Origins of the Gentoo Image
- 2 Preparing for Install
- 3 Install Gentoo Image
- 4 Configure Network
- 5 You may want to get a kernel now
- 6 Clean up and Reboot
- 7 Post Installation Tasks
- 8 Notes on initial configuration
- 9 Troubleshooting
- 10 Submitting Bugs and Issues
Origins of the Gentoo Image
A Little History
(please fill in missing info, I don't mean to leave anyone out) This gentoo image has its roots in the kurobox.com forums, probably dating back to 2005 or so. jgmdean kicked off the project and TGL and others in the forums made valuable contributions. With the advent of uboot for the kurobox and linkstation from linuxnotincluded, the submission of the linkstation patches to kernel.org by lyakh, and the firmimg.bin for EM mode by mindbender, the gentoo image is now thriving again with support for both PPC linkstations and kuroboxes.
Preparing for Install
It is recommended that you have uboot installed prior to installing the gentoo image. linuxnotincluded, the author of the uboot port to PPC linkstations and kuroboxes, has documented the steps for building uboot on his website here: uboot for the linkstation. This gentoo image is not very useful for testing the RAM build and flashing the ROM build unfortunately because the binaries in the image are linked with glibc 2.6 (and therefore will not run under a 2.4 kernel). Additionally, the kernel provided in this image requires dtb support, a feature provided in uboot 1.2. The instructions for installing 1.2 UBoot are here on the wiki. You don't have to build the kernel as it shows in the instructions if you don't want to since there is a kernel supplied in the gentoo image. Also, you may be able to find a 1.2 uboot pre-built and ready to flash in the downloads section (for the HG: here, and the HD: here).
Please be careful.
The rest of these instructions assume you have a working 1.2 uboot.
Download needed files
You will need to download the gentoo image, the EM mode utilities, and the latest portage tree.
- For the EM mode utilities, download from here: EM_mode_binaries.tar.gz
- For the gentoo 15-minute image, download from here: gentoo-20071104-uboot.tar.bz2
- For the latest portage snapshot, use a gentoo mirror near you (see Gentoo Mirror), and navigate to the portage "snapshots", I use ibiblio for example portage-latest.tar.bz2.
Install EM mode utilities
Switch the box to EM mode (see the Frequently Asked Questions for details on how to do this). Note, uboot 1.2 , if connected to the uboot shell via netcat, typically is set up to boot to EM mode by hitting "s <return>", and then entering "run emboot" at the prompt. you can also use the so called "minimal-console" to boot to EM mode. Watch this video tutorial describing this:
2.4.17/2.4.20 linkstations (Stock firmimg.bin)
If you already have installed uboot then you need to install the firmimg.bin which features telnet/ftp like the kurobox one does. Look [[1]] for installation instructions.
220.127.116.11 firmimg.bin (Kurobox/KuroboxHG/LS1/HG/HS)
The binaries from EM_mode_binaries.tar.gz should be included. it was reported that bzip2 was missing, so install the EM_mode_binaries and set the date as described below.
2.4.17/2.4.20 Kurobox / Kurobox HG (Stock firmimg.bin)
After it boots to EM mode, use any FTP client to upload EM_mode_binaries.tar.gz to /tmp on the Kuro (hint: Windows may change the extension of the file when you download it from the internet).
then login to kuro using a telnet client.
Kroutoshikou KURO-BOX (IETSUNA) kernel 2.4.17-kuro-box on ppc KURO-BOX-EM login: root Password: kuro (kuroadmin on HG)
Change to the root and untar the binaries.
# cd / # tar xvzf /tmp/EM_mode_binaries.tar.gz bin/ bin/sfdisk bin/fdisk bin/bzip2 bin/date bin/chroot #
Check and set the date.
# date Fri Feb 1 12:37:03 JST 2006 # date 02032238 Thu Feb 3 22:38:00 JST 2006
Partitioning & Formating the HDD
Note: The /etc/fstab file that comes with the Gentoo image is configured to work with a simple hard drive partitioning scheme. If you want to use a different partitioning scheme you must edit /etc/fstab accordingly. The flash contains the standard visual editor, vi. Instructions for using vi are available at http://www.cs.colostate.edu/helpdocs/vi.html.
Note: the image is prepared for use with an instream 2.6 kernel, which uses the PATA driver, or /dev/sda, for the hard drive. When running under a 2.4 kernel or a legacy 2.6 kernel with out-of-stream patches, the drive is /dev/hda. Keep that in mind when creating the partitions and editing the fstab file.
Run fdisk and create partitions. The image uses three partitions: sda1 for /, sda2 for the swap space, sda3 for /datafiles. This section from the Gentoo Handbook explains how to prepare your hard disk (create partitions). For most users, 10gb for / on sda1 and is adequate (the image consumes around 1.4G when freshly installed). 512mb is good for a swap space on sda2 and use the remainder for /datafiles on sda3. However, you can decide which way you want to break up your hard disk. Remember you need to mount all of the drives (except the swap and /datafiles) before you untar the image (More on that later).
# fdisk /dev/hda (to match the fstab supplied in the image, you will need to create 3 partitions, 1=~10G, 2=~512M, 3=rest-of-drive)
Once the partitions are created we format the partitions. Here we format the first partition on /dev/hda (the hard drive is /dev/hda).
# mke2fs -j /dev/hda1 mke2fs 1.22, 22-Jun-2001 for EXT2 FS 0.5b, 95/08/09 Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 1251712 inodes, 2502115 blocks 125105 blocks (5.00%) reserved for the super user First data block=0 77 block groups 32768 blocks per group, 32768 fragments per group 16256 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 Writing inode tables: done Creating journal (8192 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 29 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. #
We do this for all of the partitions we plan to use.
# mke2fs -j /dev/hda3
# mkswap /dev/hda2 Setting up swapspace version 1, size = 518184960 bytes #
Install Gentoo Image
Mount new partitions
This will allow us to create the gentoo system on the hard drive instead of in the flash ram disk. We will create the directoy /gentoo and mount /dev/hda1 there.
# mkdir /gentoo # mount -t ext3 /dev/hda1 /gentoo (if you created any other partitions to be mounted under /, you should mkdir and mount them now)
Extracting the Image
Use your FTP client to upload the gentoo image (gentoo-20071104-uboot.tar.bz2) to the /gentoo directory on the kuro/LS.
Then, back at the EM-mode prompt, change directories to /gentoo and untar the image in what will be our root directory
# cd /gentoo # tar xvjf gentoo-20071104-uboot.tar.bz2
Once the image is untarred, we can delete the image from /gentoo
# rm gentoo-20071104-uboot.tar.bz2
Extracting the portage snapshot
Again, use your ftp client to upload the portage snapshot (portage-latest.tar.bz2) to the /gentoo directory on the kuro/LS
Then, back at the EM-mode prompt, untar the snapshot into the usr directory
# cd /gentoo/usr # tar xvjf /gentoo/portage-latest.tar.bz2
Once the snapshot is untarred, we can delete it from /gentoo
# cd /gentoo # rm portage-latest.tar.bz2
Configure Network
Next we configure the network.
If you want to change the hostname now, edit this file
# vi /gentoo/etc/conf.d/hostname
If you want to use DHCP, you can skip this step as the image is configured for DHCP. Note, that if DHCP fails, the box will fallback to the well-known IP address of 192.168.11.150.
# vi /gentoo/etc/conf.d/net
The Gentoo Handbook Section 4 explains how to configure the settings for various options. The /etc/conf.d/net file supplied in the image looks like this:
# This configuration will use DHCP for eth0 but fallback to the # well-known 192.168.11.150 if DHCP fails config_eth0=( "dhcp" ) fallback_eth0=( "192.168.11.150/24" )
You may have to configure your DNS servers in resolv.conf file according to your network. If you stick to DHCP, you generally don't have to edit the file, as it will be generated by dhcpcd upon bootup.
# vi /gentoo/etc/resolv.conf
The file supplied in the image looks like this:
nameserver 127.0.0.1
You may want to get a kernel now
The gentoo image provides a kernel and dtb files in /boot. Your uboot should be configured to boot the kernel listed below (vmlinux.UBoot), unless you supply your own kernel and configure uboot appropriately. If you want to use a different kernel, you should place it in /boot now and configure uboot appropriately. Note, the kernel supplied with the image disables the AVR watchdog at bootup, so the image assumes this is taken care of. If your kernel does not do this, you need to provide it somehow, otherwise your box will be reset after 5 minutes by the watchdog. This issue has been noted in bugtracker, and a package to disable the AVR watchdog should become available soon.
The kernel supplied was built from gentoo-sources. The uname -a looks like:
Linux gmyth 2.6.22-gentoo-r5 #1 Tue Oct 16 03:22:32 EDT 2007 ppc 82xx Linkstation I/Kurobox(HG) GNU/Linux
The contents of the /boot directory supplied in the image are:
-rw-r--r-- 1 root root 653994 Oct 16 22:09 System.map lrwxrwxrwx 1 root root 1 Oct 2 23:42 boot -> . -rw-r--r-- 1 root root 37690 Oct 16 22:09 config -rw-r--r-- 1 root root 2180 Oct 16 22:10 kuroboxHD.dtb -rw-r--r-- 1 root root 3338 Oct 16 22:08 kuroboxHD.dts -rw-r--r-- 1 root root 2196 Oct 16 22:10 kuroboxHG.dtb -rw-r--r-- 1 root root 3369 Oct 16 22:08 kuroboxHG.dts -rw-r--r-- 1 root root 1588842 Oct 16 22:08 vmlinux.UBoot
Clean up and Reboot
Unmount everything
# cd / # # (umount any partitions you may have mounted if you departed from the provided fstab) # umount /gentoo
Set the box to boot to the new system. By the way, that device is FL3 in lowercase. (This step is optional nowadays with uboot).
# echo -n "OKOK" > /dev/fl3
and then restart the system
# shutdown -r now
Wait a few minutes and then log onto your kuro/LS with putty or ssh. The first time the system boots it will take about 3 minutes as it needs to generate the certificates used by sshd.
Login as root with the password: kuroadmin.
What if it doesn't seem to boot? Give it plenty of time -- it might be doing a fsck. If you still cannot connect, see #Troubleshooting.
Post Installation Tasks
First we set the root password and create a new user who is a member of wheel so they can su to root.
# cd / # passwd New UNIX password: Retype new UNIX password: passwd: password updated successfully # useradd dtaylor -m -G users,wheel -s /bin/bash # passwd dtaylor New UNIX password: Retype new UNIX password: passwd: password updated successfully #
Now would be a good time to update everything. Let's sync the overlay with the svn server. First, I suggest optionally backing up the installed overlay:
# cd /usr/local/portage/layman # cp -r ls-wiki ../ls-wiki.bak
Then sync the overlay with the subversion server:
# layman -S
Since we used the latest portage snapshot, you can probably skip this next step, but to be sure you have the latest portage tree, you can sync it now with this command:
# emerge --sync
Then, you should check what packages are out of date with a command like this:
# emerge --pretend --update --deep world
This will show you what packages are out-of-date since the image was created. I always like to do --pretend to see what it's going to do before doing it for real (some people may prefer to use --ask instead of --pretend to avoid waiting if the update is chosen). To really update everything, use this command:
# emerge --update --deep world
Last, if anything was updated and portage says we need to update our config files we run etc-update. Don't do this blindly as you can easily break your brand new system. You need to understand what the configuration files mean and choose what lines you want to edit. On the other hand, the box is plain vanilla at this point so the configuration files supplied with the updated packages are probably ok to accept.
# etc-update
That's it. You're done. If you are new to Gentoo, check out the Gentoo Handbook "Where to go from here?". Also, you should consider going to the Administrate Your Gentoo System page and installing some system utilities (note, the last time I checked, that page on the wiki was woefully obsolete - there are no bin packages available for this image so don't bother with the PORTAGE_BINHOST setting).
Notes on initial configuration
The timezone in the image is set for New York, or EST/EDT. If you live in a different timezone, you should change this link. Look for your timezone in /usr/share/zoneinfo/ and then create a link to your desired timezone:
# cd /etc # rm localtime # ln -s ../usr/share/zoneinfo/<your-desired-timezone-here> localtime
Check your setting with the 'date' command. Also if you need to change the clock, use the 'hwclock' command. You also may want to emerge the ntp package to set your clock in sync with Internet time servers.
There is a timezone setting in this file as well. You can set the timezone to the same one as the link above.
# vi /etc/conf.d/clock (set the TIMEZONE to something like TIMEZONE="America/New_York")
This file contains a setting for the AVR device. Since the image contains a kernel that uses /dev/ttyS0 for the AVR device, the file contains a line like this:
This file is run whenever the box is shutting down for halt or reboot. There is a little bit of code in this file such that if "shutdown -r now" or "shutdown -h now" is run from the command line, the AVR is told to turn of the power or start a reset. The following code is in the /etc/conf.d/local.stop file:
#AVR_DEVICE should come from /etc/rc.conf [ -z "${AVR_DEVICE}" ] && AVR_DEVICE=/dev/ttyS0 # on halt [ "${RUNLEVEL}X" = "0X" ] && echo -n "EEEE" > ${AVR_DEVICE} # on reboot [ "${RUNLEVEL}X" = "6X" ] && echo -n "CCCC" > ${AVR_DEVICE}
Note the avr_evtd package does this when the power button on the front panel is pushed (once long to halt or twice quick to reboot), and it seems ok to have it done twice when using the power button.
The image as delivered has just a few packages emerged beyond the basic system. The contents of the world file are:
app-admin/showconsole app-editors/vim app-portage/gentoolkit app-portage/layman dev-util/subversion net-misc/dhcpcd sys-apps/avr_evtd sys-apps/hotplug sys-fs/udev
list of all emerged packages
# equery list [ Searching for all packages in all categories among: ] * installed packages [I--] [ ] app-admin/apache-tools-2.2.6 (0) [I--] [ ] app-admin/eselect-1.0.10 (0) [I--] [ ] app-admin/eselect-vi-1.1.4 (0) [I--] [ ] app-admin/perl-cleaner-1.04.3 (0) [I--] [ ] app-admin/python-updater-0.2 (0) [I--] [ ] app-admin/showconsole-1.08 (0) [I--] [ ] app-arch/bzip2-1.0.4 (0) [I--] [ ] app-arch/cpio-2.9-r1 (0) [I--] [ ] app-arch/gzip-1.3.12 (0) [I--] [ ] app-arch/tar-1.18-r2 (0) [I--] [ ] app-crypt/hashalot-0.3-r2 (0) [I--] [ ] app-editors/nano-2.0.6 (0) [I--] [ ] app-editors/vim-7.1.042 (0) [I--] [ ] app-editors/vim-core-7.1.042 (0) [I--] [ ] app-misc/ca-certificates-20070303-r1 (0) [I--] [ ] app-misc/mime-types-7 (0) [I--] [ ] app-misc/pax-utils-0.1.16 (0) [I--] [ ] app-portage/gentoolkit-0.2.3-r1 (0) [I--] [ ] app-portage/layman-1.1.1 (0) [I--] [ ] app-shells/bash-3.2_p17 (0) [I--] [ ] app-vim/gentoo-syntax-20070506 (0) [I--] [ ] dev-lang/perl-5.8.8-r2 (0) [I--] [ ] dev-lang/python-2.4.4-r6 (2.4) [I--] [ ] dev-libs/apr-1.2.8 (1) [I--] [ ] dev-libs/apr-util-1.2.8 (1) [I--] [ ] dev-libs/expat-2.0.1 (0) [I--] [ ] dev-libs/libpcre-7.3-r1 (3) [I--] [ ] dev-libs/libusb-0.1.12-r1 (0) [I--] [ ] dev-libs/libxml2-2.6.28 (2) [I--] [ -] dev-libs/openssl-0.9.8f (0) [I--] [ ] dev-libs/popt-1.10.7 (0) [I--] [ ] dev-perl/Locale-gettext-1.05 (0) [I--] [ ] dev-python/pycrypto-2.0.1-r6 (0) [I--] [ ] dev-python/python-fchksum-1.7.1 (0) [I--] [ ] dev-util/ctags-5.5.4-r2 (0) [I--] [ ] dev-util/pkgconfig-0.21-r1 (0) [I--] [ ] dev-util/subversion-1.3.2-r4 (0) [I--] [ ] dev-util/unifdef-1.20 (0) [I--] [ ] net-misc/dhcpcd-3.1.5-r1 (0) [I--] [ ] net-misc/iputils-20070202 (0) [I--] [ ] net-misc/neon-0.26.3 (0) [I--] [ ] net-misc/openssh-4.7_p1-r1 (0) [I--] [ ] net-misc/rsync-2.6.9-r3 (0) [I--] [ ] net-misc/wget-1.10.2 (0) [I--] [ ] perl-core/PodParser-1.35 (0) [I--] [ ] perl-core/Test-Harness-2.64 (0) [I--] [ ] sys-apps/acl-2.2.45 (0) [I--] [ ] sys-apps/attr-2.4.39 (0) [I--] [ ] sys-apps/avr_evtd-1.7.2 (0) [I--] [ ] sys-apps/baselayout-1.12.9-r2 (0) [I--] [ ] sys-apps/busybox-1.5.1 (0) [I--] [ ] sys-apps/coreutils-6.9-r1 (0) [I--] [ ] sys-apps/debianutils-2.17.5 (0) [I--] [ ] sys-apps/diffutils-2.8.7-r2 (0) [I--] [ ] sys-apps/file-4.21-r1 (0) [I--] [ ] sys-apps/findutils-4.3.8-r1 (0) [I--] [ ] sys-apps/gawk-3.1.5-r5 (0) [I--] [ ] sys-apps/grep-2.5.1a-r1 (0) [I--] [ ] sys-apps/groff-1.19.2-r1 (0) [I--] [ ] sys-apps/hdparm-7.7 (0) [I--] [ ] sys-apps/help2man-1.36.4 (0) [I--] [ ] sys-apps/hotplug-20040923-r2 (0) [I--] [ ] sys-apps/hotplug-base-20040401 (0) [I--] [ ] sys-apps/less-406 (0) [I--] [ ] sys-apps/man-1.6e-r3 (0) [I--] [ ] sys-apps/man-pages-2.66 (0) [I--] [ ] sys-apps/mktemp-1.5 (0) [I--] [ ] sys-apps/module-init-tools-3.2.2-r3 (0) [I--] [ ] sys-apps/net-tools-1.60-r13 (0) [I--] [ ] sys-apps/pciutils-2.2.4-r3 (0) [I--] [ ] sys-apps/portage-22.214.171.124 (0) [I--] [ ] sys-apps/sandbox-188.8.131.52-r2 (0) [I--] [ ] sys-apps/sed-4.1.5 (0) [I--] [ -] sys-apps/setarch-2.0 (0) [I--] [ ] sys-apps/shadow-184.108.40.206-r1 (0) [I--] [ ] sys-apps/sysvinit-2.86-r13 (0) [I--] [ ] sys-apps/tcp-wrappers-7.6-r8 (0) [I--] [ ] sys-apps/texinfo-4.8-r5 (0) [I--] [ ] sys-apps/usbutils-0.72-r4 (0) [I--] [ ] sys-apps/util-linux-2.12r-r8 (0) [I--] [ ] sys-apps/which-2.16 (0) [I--] [ ] sys-devel/autoconf-2.61-r1 (2.5) [I--] [ ] sys-devel/autoconf-wrapper-4-r3 (0) [I--] [ ] sys-devel/automake-1.10 (1.10) [I--] [ ] sys-devel/automake-wrapper-3-r1 (0) [I--] [ ] sys-devel/binutils-2.18-r1 (0) [I--] [ ] sys-devel/binutils-config-1.9-r4 (0) [I--] [ ] sys-devel/bison-2.3 (0) [I--] [ ] sys-devel/flex-2.5.33-r3 (0) [I--] [ -] sys-devel/gcc-4.1.2 (4.1) [I--] [ ] sys-devel/gcc-config-1.3.16 (0) [I--] [ ] sys-devel/gettext-0.16.1-r1 (0) [I--] [ ] sys-devel/gnuconfig-20070118 (0) [I--] [ ] sys-devel/libperl-5.8.8-r1 (1) [I--] [ ] sys-devel/libtool-1.5.24 (1.5) [I--] [ ] sys-devel/m4-1.4.10 (0) [I--] [ ] sys-devel/make-3.81 (0) [I--] [ ] sys-devel/patch-2.5.9 (0) [I--] [ ] sys-fs/e2fsprogs-1.39-r2 (0) [I--] [ ] sys-fs/udev-115-r1 (0) [I--] [ -] sys-kernel/linux-headers-2.6.21 (0) [I--] [ ] sys-libs/com_err-1.39 (0) [I--] [ ] sys-libs/cracklib-2.8.10 (0) [I--] [ ] sys-libs/db-4.5.20_p2 (4.5) [I--] [ ] sys-libs/gdbm-1.8.3-r3 (0) [I--] [ ] sys-libs/glibc-2.6.1 (2.2) [I--] [ ] sys-libs/gpm-1.20.1-r5 (0) [I--] [ ] sys-libs/ncurses-5.6-r1 (5) [I--] [ ] sys-libs/readline-5.2_p7 (0) [I--] [ ] sys-libs/ss-1.39 (0) [I--] [ ] sys-libs/timezone-data-2007g (0) [I--] [ ] sys-libs/zlib-1.2.3-r1 (0) [I--] [ ] sys-process/procps-3.2.7 (0) [I--] [ ] sys-process/psmisc-22.5-r2 (0) [I--] [ ] virtual/editor-0 (0) [I--] [ ] virtual/init-0 (0) [I--] [ ] virtual/libiconv-0 (0) [I--] [ ] virtual/libintl-0 (0) [I--] [ ] www-servers/apache-2.2.6 (2)
The image is taking advantage of the noteworthy layman package for managing the overlay. This provides the ability to download updates from the nas-central/linkstationwiki subversion server at sourceforge. This is a very powerful utility, but perhaps should not be trusted blindly. I suggest making a backup of the /usr/local/portage/layman/ls-wiki directory tree after the first install and each time before using the "layman -S" command. Also, check occasionally in the forums at nas-central.org (in Software Development (ppc)) and kurobox.com (under the gentoo project [these two forums should eventually merge into one at nas-central]) for announcements regarding new packages that may be added to the overlay.
The kernel provided in the image was built from gentoo-sources. Then, to keep the image size smaller, the gentoo-sources package was unmerged and removed after the kernel was built. If you want to build a new kernel for some reason, you can do something like the following:
# emerge gentoo-sources # cp /boot/config /usr/src/linux # cd /usr/src/linux # make oldconfig # make menuconfig # make uImage && make modules && make modules_install
Then copy the uImage file to /boot/vmlinux.UBoot or the appropriate name for your uboot.
shutdown/reboot 5-minute delay
The box takes 5 minutes to perform a shutdown (power off) or reboot. This seems to be a feature with the AVR (if anyone knows how to improve this, let us know - the stock implementation did not seem to take this long). I believe it in fact does not take half this time to actually complete shutting down, so if you are really impatient, you can probably just cycle the power after about 3 minutes and be ok. Note, if you have installed a lot of services the shutdown process could take longer so beware.
Running gentoo on the LS/kurobox works great, but compiling is slow. If you have a x86 or other more capable CPU running linux, it can help significantly to run distcc on the more capable CPU and enable the LS/kurobox to offload some of the work for big emerge's. See this howto to set it up.
If you cannot find the box on the network, try the fallback IP address 192.168.11.150. Set your PC to 192.168.11.149 to try the connection. If you have a linux PC, use a command like "ifconfig eth0:EM 192.168.11.149".
If you still cannot find the box on the network, try to shutdown the box by holding the power button for about 3 seconds. The Power LED should start blinking to indicate the box is going to shut down. If the Power LED does not start blinking, you will probably have to pull the power cord. Go back to EM mode and mount the /dev/hda1 partition. Look in the var/log directory for a file called boot.msg. This file is created during the boot process. It may give you some clues as to what is going on. Note, this file is created because /etc/conf.d/rc has RC_BOOTLOG="yes" and the image has emerged app-admin/showconsole.
If you are still having trouble, post a message to the forums at forum.nas-central.org.
Submitting Bugs and Issues
If you cannot get a question or problem resolved in the forums, please submit bugs/issues reports in mantis at nas-central.org here: Bugtracker.


text:
Why Commissary is Important
What is an Inmate Money or Commissary Account?
5 Steps to Mailing Commissary Money to a Federal Inmate
Using Commissary to Improve a Workout Diet
Sending a Commissary MoneyGram to a Federal Inmate
Prison Commissary: 4 Reasons to Put Money on an Inmate's Account
Inmate Commissary Account: Are They Allowed to Keep Their Money When They're Transferred to Another Jail?
How Does Commissary Work?
Hundreds more 'Straight Up Answers'...
Since inmates are not allowed to possess cash money while in custody in the Webster Jail, the jail maintains a 'bank account' for the inmate to purchase products and services from their commissary (canteen) store.
Commissary funds allow inmates to purchase items such as personal hygiene products, snacks and stationery supplies from the jail store.
Inmates can use money from their account to purchase phone time credits or prepaid phone cards in order to make outside phone calls to friends and family members.
Many jails also allow an inmate to bail himself out of jail if he has the funds in his account. The bail amount is typically 10-15% of the bond amount set by the court.
Inmate accounts are also used to pay the co-payment for medication and visits to the jail's medical clinic should they become ill.
Anybody can contribute to an inmate's books or commissary fund as long as there isn't a no-contact order in place.
Because of the ability for family members and friends to deposit money online using a credit or debit card, jail inmates can now receive funds from anywhere in the world.
There are usually four choices for putting money on an inmate's books:
Bring money to the jail in person. Click here to see where to drop money off and whether it has to be cash or a money order.
Jail personnel will process the Inmate Account payment.
Some jails have self-serve kiosks in the lobbies that accept cash, debit or credit cards.
If you can't get your questions answered online call the Webster Jail at 281-332-2426.
Webster Jail and others often use a private company to process all online deposits to an inmate's account. The company charges you a small fee for doing so, but the fee probably isn't as much as gas and parking would cost to take it to the jail in person.
Click here to reach the online site for depositing funds. You will need to register an account, which is free to do and use a debit/credit card for the deposits.
Mailing a deposit takes more time to process than the other methods but can be done if you live too far away to bring it in person and you don't have a debit/credit card for online deposits. Never send cash. Always send a Money Order from the US Post Office, a reputable bank or Western Union.
Make the Money Order out to the inmate's name and put their Inmate ID# in memo section of the Money Order.
Call Webster Jail at 281-332-2426 to confirm the address to send the money order to and how they want it made out.
Failure to do this properly will delay your inmate getting his account credited and may require you to have to resubmit a second money order.
Click here to view online how to make the money order out and where to send it.
Most of the online companies will accept deposits over the phone with a debit or credit card. To do this you will need the inmate's offender # (inmate ID #) and full legal name.
Click here to find out about making a deposit over the phone.
People who have never been to jail would be surprised by the large amount of candy, snacks, art supplies, playing cards, hygiene products and clothing that can be purchased through a jail's commissary. Some jails have several hundred different items.
The Webster Jail Commissary Instructions and Information can be found here. If you need more information contact the jail by calling 281-332-2426.
Some jails have contract agreements with third party Commissary companies that ship predetermined Care Packages of candy and snacks.
These can be ordered by you online and are delivered directly to the inmate.
Jails typically have limits on how much money an inmate can have on the books at any one time.
They also have limits on how much you can deposit for an inmate at a time.
The standard monthly limit an inmate can spend is between $300 and $400.
Call Webster Jail at 281-332-2426 or click here to learn the Inmate Account deposit limits and other rules regarding depositing money on an inmate's books.
Many jails debit (charge) an inmate's commissary accounts for medical visits, any medications including over-the-counter pain reliever, jail stay fees, restitution, etc.
Taking this into consideration when deciding how much to deposit will ensure the inmate gets the amount you wanted him to have after things are deducted.
A quick call to the Webster Jail at 281-332-2426 will let you know how much is deducted from the books for each fee related to medical issues or other jail expenses.
Online you can find the medical fee information by going here, Other Webster Jail fees can be determined by going here or calling 281-332-2426.
Call the Webster Jail at 281-332-2426 and ask how you can view a commissary list. This gives you an idea of what things cost the inmate and you can make an informed decision regarding how much to deposit.
Not surprisingly much of an inmate's commissary money is used to purchase item's to pay gambling debts or purchase prescription medicine from another inmate. If your inmate is spending more than $3-4.00 a day on commissary items, you are paying for him or her to gamble or buy drugs.
Put your financial needs first and the inmate's second. Don't forget, the inmate is getting three free 2,000 calorie meals a day. The food may not be of the highest quality, but the commissary food is generally much less nutritious.
Click here to view the jail website for additional information.
Sitefinity ASP.NET CMS


text:
Brightening Up a Foggy Morning
Brightening up a foggy morning in Goleta.
Support Noozhawk Today
You are an important ally in our mission to deliver clear, objective, high-quality professional news reporting for Santa Barbara, Goleta and the rest of Santa Barbara County. Join the Hawks Club today to help keep Noozhawk soaring.
We offer four membership levels: $5 a month, $10 a month, $25 a month or $1 a week. Payments can be made using a credit card, Apple Pay or Google Pay, or click here for information on recurring credit-card payments and a mailing address for checks.
Thank you for your vital support.
Become a Noozhawk Supporter
- Ask
- Vote
- Investigate
- Answer
Noozhawk Asks: What's Your Question?
Welcome to Noozhawk Asks, a new feature in which you ask the questions, you help decide what Noozhawk investigates, and you work with us to find the answers.
Here's how it works: You share your questions with us in the nearby box. In some cases, we may work with you to find the answers. In others, we may ask you to vote on your top choices to help us narrow the scope. And we'll be regularly asking you for your feedback on a specific issue or topic.
We also expect to work together with the reader who asked the winning questions to find the answer together. Noozhawk's objective is to come at questions from a place of curiosity and openness, and we believe a transparent collaboration is the key to achieve it.
The results of our investigation will be published here in this Noozhawk Asks section. Once or twice a month, we plan to do a review of what was asked and answered.
Thanks for asking!
Reader Comments
Noozhawk is no longer accepting reader comments on our articles. Click here for the announcement. Readers are instead invited to submit letters to the editor by emailing them to [email protected]. Please provide your full name and community, as well as contact information for verification purposes only.
- 1. Claire Krock: When a Community Takes a Stand for Literacy - February 23, 2019 | 11:30 a.m.
- 2. Jim Langley: Living Well and Living Long, and 'It Is Well With My Soul' - February 23, 2019 | 10:30 a.m.
- 3. Louise Palanker: Finding a Good Girlfriend, Struggling with Sexuality, 'Love… - February 23, 2019 | 9:30 a.m.
- 4. Firefighters Quickly Douse Blaze at Downtown Santa Barbara Apartment Building - February 23, 2019 | 9:21 a.m.
- 5. UCSB Water Polo Loses to Arizona State in Kalbus Invitational Opener - February 23, 2019 | 5:17 a.m.
Daily Noozhawk
Subscribe to Noozhawk's A.M. Report, our free e-Bulletin sent out every day at 4:15 a.m. with Noozhawk's top stories, hand-picked by the editors.Sign Up Now >


text:
FreeLink for the LinkStation PRO/LIVE
Freelink is based on Debian 4 ('Etch') and dates from October 2007. Since the release of Debian 6.0 ('Squeeze') in February 2011, Etch is no longer supported by Debian. You should consider installing Squeeze instead.
The original (old hardware) model LinkStation PRO and LIVE appear to share the same hardware, but came with different firmware. Recently, a new model (new hardware) has appeared: again, the new versions of the PRO and LIVE appear identical, but differ from the older versions. The FreeLink installation procedures for old and new hardware are different. There are now four variations: old/new and PRO/LIVE.
To determine whether you have the OLD (v1) or NEW (v2) hardware, compare the following rear-view images (of LS LIVE, but valid also for LS PRO) - note the position of the power cable socket (at top in new hardware, at side in old):
- 1 Technical Notes and Limitations
- 2 Download
- 3 How to use the Buffalo updater LSUpdater.exe
- 4 Installation Steps for Linkstation versions/revisions
- 4.1 Installation on V1 (OLD hardware) LS PRO using LSUpdater
- 4.2 Installation on V1 (OLD hardware) LS LIVE using LSUpdater
- 4.3 Installation on V2 (NEW hardware) LS PRO using LSUpdater
- 4.4 Installation on V2 (NEW hardware) LS LIVE (running 2.06 or 2.10 Buffalo firmware) using LSUpdater
- 5 What to do after FreeLink is installed
- 5.1 Login
- 5.2 Cleanup / Fixes
- 5.3 Update of the Debian repository and packages
- 5.4 Set your Locale
- 5.5 Static IP address
- 5.6 Customized Partitions
- 5.7 Webmin (webbased administration)
- 5.8 Updating your kernel (not always necessary)
- 5.9 Securing Your Linkstation
- 6 Removal or Reinstall of FreeLink
- 7 Key Notes to Remember
- Freelink is currently based on the Debian "Etch" userspace
- Before you start, you may want to consider:
- repartitioning your linkstation, to make more room on the root partition for additional Debian packages
- If you wish to use the newer 2.6.16 Buffalo kernel, you should install the 1.10 Buffalo firmware before installing Freelink.
- There is not yet an official Debian kernel for the LinkStation / ARM9 - this release uses (and does not update) the kernel which is already installed on your Linkstation (i.e. the Buffalo kernel).
- Use of the Buffalo kernel has some limitations:
- The 2.6.12 Buffalo kernel does not support udev
- Some kernel features (kernel modules etc.) that you need may not be available without using a non-Buffalo kernel <links needed>
- The Buffalo kernel is built with the new Arm EABI, whereas Debian Etch is only available in the old ABI flavour - this means that some user-space <-> kernel-space interfaces will not work e.g. the "iptables" userspace command is unusable when operating with this EABI/Old ABI split.
- It is possible to use the "testing" version of the next Debian release "Lenny" instead - this is available as an Armel build.
Technical Notes and Limitations
Please read the README.1st file included with this Freelink release.
How to use the Buffalo updater LSUpdater.exe
You will have to use the Buffalo-supplied windows program LSUpdater.exe, running on Windows (or maybe WINE under Linux). This comes in separate versions for the LS PRO and LS LIVE. The Freelink package contains an older LS PRO version not suitable for new hardware. Unless you are installing Freelink on an old-hardware (v1) LS PRO, you will need to use LSUpdater.exe from a buffalo firmware package for your type of ARM-9-based Linkstation (PRO or LIVE). You will also need its files lsupdater.ini and linkstation_version.txt .(You may need to edit linkstation_version.txt to increase the version numbers of the various components listed, so they are higher than the actual Buffalo versions installed on the LinkStation; this is just to fool LSUpdater that the update really is an update, otherwise it won't get applied).
To Access the Debug Menu
Start lsupdater.exe, then
- Right-click the "Buffalo Updater Icon" on the Windows context-bar (the bar at the bottom of the screen that spans between the start menu and the clock).
- Select "Debug(D)..." and the Debug Mode menu will pop up.
If you are using the lsupdater as supplied in Buffalo's own firmware packages (e.g., if you are installing FreeLink firmware on the LS LIVE, as described below), you will not see the Debug(D) option until you have modified the file lsupdater.ini (found in the same directory as lsupdater.exe): open lsupdater.ini with a text editor, and add the following lines:
[SpecialFlags] Debug = 1
You should also change
[Flags] VersionCheck = 1
[Flags] VersionCheck = 0
Normally lsupdater does not detect a LinkStation which already running the firmware revision that came with the updater (this is specified in the file linkstation_version.txt); setting the flag VersionCheck=0 disables this behavior.
How to use the Firmware Updater with Wine
Linux users can also use the lsupdater.exe with wine. Use "winecfg" to edit the Graphics setting for the Wine windows manager to control the window by unchecking "Allow the window manager to control the windows". Then run "wine LSUpdater.exe" and you will be able to enter debug mode by right-clicking on the title bar of the window.
Installation Steps for Linkstation versions/revisions
Since it may have taken some time to get to this step here's that important warning again:
Installation on V1 (OLD hardware) LS PRO using LSUpdater
Initrd-Only Installation:
(This step is NOT for NEW-version hardware, ONLY for OLD-version hardware.)
Important: Users that have not installed a lb_worm's custom initrd or firmwares containing lb_worm's custom initrd must install the "initrd-only" package before installing FreeLink. Failure to do so may result in a failed install or a bricked old-hardware-version box. The initrd-only package is included in the FreeLink package. Use the updater found in the initrd-only folder to install the initrd-only package (for Live, use Live version of LSUpdater.exe and LSUpdater.ini, see below).
- See LS_PRO_modified_initrd for more information about the modified initrd.
Warning Notices: When installing the initrd-only package, there will be an error saying "hddrootfs.img not found", "uImage.buffalo not found". That is expected as we are only updating initrd. The errors can be overridden by using the "Debug Mode" for the Buffalo Updater.
- Right click on the Buffalo Updater icon in the Windows takbar. If lsupdater.ini has been edited as described above to allow Debug mode to be activated, you will see a choice Debug(D): select it.
- In the upper left-hand corner of the menu is an "Update" section. Deselect everything in that section except "Update initrd" and hit "ok".
- Then update as usual.
FreeLink Installation
Users may install FreeLink by using the buffalo updater supplied with the FreeLink package. The FreeLink firmware will be installed in the same manner as the stock firmware except you will skip installing boot (u-boot bootloader) as there is different versions of u-boot.
- Please use a wired-ethernet connection to install FreeLink. Wireless-ethernet connections are known to cause problems.
- Follow instructions above to use Debug mode. In Debug mode, uncheck Update BOOT as one of the Update options.
- Ignore the "Waited for 240[s] seconds but couldn't confirm..." message at the end of the update and click "No" when the updater asks whether it should wait again for a response.
- Also ignore any error messages afterwards. The error messages are cause by the fact that FreeLink does not contain the Buffalo Updater Daemon.
ACP_STATE_FAILURE error??:
If you receive the ACP_STATE_FAILURE error message, that means that the /boot partition of the hard drive is filled to capacity. The easiest way to resolve this is with Georg's ACP Commander:
- Read the http://downloads.nas-central.org/TOOLS/ALL_LS_KB_ARM9/ACP_COMMANDER/README Make sure you understand what the acp_commander is for & how you can use it.
- Download http://downloads.nas-central.org/TOOLS/ALL_LS_KB_ARM9/ACP_COMMANDER/acp_commander.jar to somewhere you will remember.
- Get console access, dos, terminal, shell it doesn't really matter as long as you can execute the java command.
- cd to the directory where you saved acp_commander.jar
- Disable your firewall temporarily. (If applicable)
Enter the following (Replacing <IP ADDRESS> with the IP Address of your Linkstation)
java -jar acp_commander.jar -t <IP ADDRESS> -cb
This will clear the boot partition, and now you can retry the firmware update, hopefully with success.
Installation on V1 (OLD hardware) LS LIVE using LSUpdater
(old v1 hardware) LS Live (HS-DHGL): Please follow the same procedure as for old hardware LS PRO, except that you must first replace the LS PRO version of the LSUpdater that is supplied with the FreeLink distribution with the LS LIVE version of LSUpdater.exe and LSUpdater.ini, These are in the firmware for the LS LIVE which can be downloaded from Buffalo site (it's inside 1.03 or 2.03 firmware for LinkStation Live). http://www.buffalo-technology.com/support/downloads/linkstation-live/
You will have to modify the LSUpdater.ini file as described above to allow Debug mode to be activated, and to suppress firmware version checking.
Installation on V2 (NEW hardware) LS PRO using LSUpdater
Only the 1.10 and 1.11 firmware is available for the (new hardware) LS PRO at http://www.buffalo-technology.com/support/downloads/linkstation-pro/ or http://www.buffalotech.com/support/downloads/linkstation-pro.
(There is no "1.06" firmware for the PRO that resembles the 2.06 firmware for the LS LIVE).
According to a procedure reported in the forum by LS Pro user ado, for 1.10 or 1.11 LSPRO firmware on new hardware, (and confirmed to work by others) what you must do is:
1. Download FreeLink_arm9-1.0rev2 2. Use LSUpdater.exe (any version, within stock firmware 1.10 or 1.11, or within FreeLink_arm9-1.0rev2) (in Debug mode) Flash the Linkstation with FreeLink firmware as follows: Start LSUpdater, and enter Debug mode, as described above: On the left Debug panel of the Debug mode window, select the boxes for KERNEL,initrd and rootfs (all of these will be taken from FreeLink_arm9-1.0rev2) , but DO NOT SELECT BOOT . On the right panel, check "Do not check version", and "force update". Important: make sure the checkbox for BOOT is NOT checked: leaving "update BOOT" checked when flashing WILL brick your new-hardware LinkStation (by replacing the u-boot bootloader with an older one incompatible with new hardware))
Suggestion: As an extra precaution against mistakes, delete the FreeLink file u-boot.buffalo.updated which contains the incompatible bootloader (or replace it with u-boot.buffalo.updated from the stock firmware package(1.10 or 1.11) corresponding to the firmware version you are running. Go back to the Main Menu, press the "Update" Button.
Reboot the Linkstation, try a ssh-login with user: root, password: lspro. Works? fine, that's it. If this is not working, you will need the next step.
3. The initial reboot of the Linkstation may fail. To fix this, you now need to get into EM mode, which will happen after three failed attempts to boot. Each time the LinkStation boots, it will check 3 things to decide whether to boot into EM mode: (i) Does a file /etc/hddrootmode exist? (ii) Does a file /etc/rootfs_ok exist? (iii) Is the version information in the file /etc/linkstation_release too old? After you have installed FreeLink and the LinkStation has failed to boot 3 times, since the LinkStation has not found a file /etc/rootfs_ok, and three failed boot attempts are recorded in /etc/rootfs_booting, the next boot will boot the LinkStation into EM mode. When your LinkStation is running in EM mode, you can use acp_commander ("java -jar acp_commander.jar -t <IP ADDRESS> -o") to remove the root password and start the telnet service. Then telnet to the LinkStation and login as root (no password). Once you are logged in as root in EM mode, modify the script in /etc/init.d/miconapl from note: execute following commands if you cannot find miconapl in /etc/init.d -> mount /dev/sda1 /boot -> mount /dev/sda2 /rootfs -> find / -iname "miconapl" hdd() { ## Use same files as linuxrc ROOTFS_OK=/boot/rootfs_ok ROOTFS_BOOTING=/boot/rootfs_booting INITRDMODE=/boot/initrdmode ## Update the filesystem okay flag date > $ROOTFS_OK ## delete booting file rm -f $ROOTFS_BOOTING rm -f $INITRDMODE } to: hdd() { ## Use same files as linuxrc ROOTFS_OK=/boot/rootfs_ok ROOTFS_BOOTING=/boot/rootfs_booting INITRDMODE=/boot/initrdmode ## Update the filesystem okay flag date > $ROOTFS_OK ## delete booting file rm -f $ROOTFS_BOOTING rm -f $INITRDMODE ## Added to resolve initial freelink boot into EM mode (v2 hardware) ETC_ROOTFS_OK=/etc/rootfs_ok ETC_ROOTFS_BOOTING=/etc/rootfs_booting ETC_INITRDMODE=/etc/initrdmode date > $ETC_ROOTFS_OK rm -f $ETC_ROOTFS_BOOTING rm -f $ETC_INITRDMODE } (The modifications above are shown in red). Now reboot again, the modifications you made will get you out of EM mode. After this final boot, you should have a working LinkStation PRO running FreeLink.
This procedure is reported to work starting with both 1.10 and 1.11 LSPRO firmware on the new hardware LS PRO.
DO NOT TRY TO FLASH BACK TO 1.03 FIRMWARE, this will brick the (new hardware) LS PRO because the 1.03 bootloader does not support new hardware.
Check the discussion in the forum about LS PRO new hardware. Successful FreeLink installations of new hardware LS PRO have been reported.
Installation on V2 (NEW hardware) LS LIVE (running 2.06 or 2.10 Buffalo firmware) using LSUpdater
The LSLIVE currently comes with 2.06 firmware (with linux kernel 188.8.131.52), but the US buffalo site supplies an update to 2.10 firmware (linux 184.108.40.206, and a slightly new u-boot). The procedued described here works for LSLIVES's running either 2.06 or 2.10 firmware. It will leave the system running FreeLink (Debian Etch) with a 188.8.131.52 kernel.
I recommend updating to 2.10 firmware before moving to freelink, to get the newer u-boot bootloader installed. You will not be able to upgrade it after installating FreeLink. (it is always possible to remove Freelink and go back to Buffalo firmware, if you need to update u-boot),
0. Start with a v2 LinkStation LIVE running Buffalo 2.06 or 2.10 firmware.
1. Download the FreeLink rev2 distribution. FreeLink_arm9-1.0rev2.zip Unzip it. Go to the directory FreeLink_arm9-1.0rev2-Live, and immediately delete the file u-boot.buffalo.updated. (This file is POISON to any new-hardware LinkStation,and you do not want any possibility of accidently flashing it to your nice new LinkStation!).
2. (Download the Buffalo 2.06 or 2.10 firmware updater if you have not already done so.) The 2.06 firmware is at http://www.buffalo-technology.com/support/downloads/linkstation-live/ . The file is called HS-DHGL_206_013_us.zip. Unzip the file, and go to the directory with the firmware (it is called HS-DHGL_206_013_us) The 2.10 firmware is at http://www.buffalotech.com/support/downloads/linkstation-live/ Download the file LS_Live_103_WebAccess.zip. The directory with the firmware is HS-DHGL_210_001_us
3. Edit lsupdater.ini (as described above) to allow activation of Debug mode.
4. Edit linkstation_version.txt as follows: (version shwn are from 2.06 firmware) VERSION=2.06-0.13 increase version e.g. VERSION=2.20-001 BOOT=1.09 DONT CHANGE KERNEL=2007/03/07 11:16:12 make date newer e.g. KERNEL=2007/10/07 11:16:12 INITRD=2007/06/12 17:37:02 make date newer e.g. INITRD=2007/10/12 17:37:02 ROOTFS=2007/06/12 17:54:57 make date newer e.g. ROOTFS=2007/10/12 17:54:57 You are only doing this to trick LSUpdater when it checks that the update is newer than the firmware installed on the LinkStation.(It will only install newer firmware) (Perhaps checking the box "force UPDATE" will make this unnecessary? Maybe only the three dates must be changed?) (These dates are only used as a check by LSUpdater to compare with dates encoded in the firmware on the LinkStation. It only matters that they are more recent than the firmware that is running at the time you flash, and what you choose for them will not be recorded on the LinkStation.) You DO NOT WANT TO make it think that there is an updated BootLoader available, so leave the BOOT=1.xx field alone. (If you are running 1.06 or 1.10 FW, the BootLoader in Flash memory should be the 1.09 or 1.10 version anyway, so this should not in principle be dangerous, but .... just leave it alone!)
5. Delete the three Buffalo files uImage.buffalo, initrd.img and hddrootfs.img
6. Replace them with the corresponding three FreeLink files uImage.buffalo, initrd.img and hddrootfs.img from the FreeLink distribution directory FreeLink_arm9-1.0rev2. Make sure that you have replaced all three files.
7. Disable all Windows firewalls. To be safest, you should also disconnect your windows computer from the network and connect it directly to the LinkStation with a crossover ethernet cable (However, I successfully flashed though a router without problems) The one important rule is: Never use a wireless connection for flashing. Now start LSUpdater, which should find your LinkStation on the network.
8. Once your LSUpdater has found the LinkStation, right click on the Buffalo Update icon in the Windows taskbar (usually at the bottom of the screen) and activate Debug(D) mode. In the left panel of the Debug menu, uncheck the first item ("update BOOT"), and check the boxes for "update KERNEL", "update initrd", and "update rootfs". Then click on "OK" to exit the Debug menu. It is apparently very important that "update BOOT" is NOT CHECKED (to avoid bricking your new-hardware version LinkStation), though since the version of the bootloader in u-boot.buffalo.updated is presumably the same as the one in your LinkStation right now, it is probably not dangerous. What is dangerous is leaving "update boot" checked if the u-boot.buffalo.updated in the working directory is an older version (like the one that comes with FreeLink that only supports old hardware....)
O update BOOT <----NOT CHECKED x update KERNEL <----CHECKED x update initrd <----CHECKED x update rootfs <----CHECKED
9.The "moment of truth" has arrived!! To continue, click on "Update" in the LSUpdater menu.
Whatever else you do, NEVER do anything that could flash the Bootloader of a new-hardware Linkstation with an older version of u-boot.buffalo.updated (like the one that came with FreeLink )unless Debug mode with "update BOOT" NOT CHECKED is used: (You WILL brick a new-hardware LinkStation if you replace its U-boot bootloader using an incompatible u-boot..buffalo.updated designed for the old hardware.)
When the LinkStation reboots, it will be running Freelink, and the LSUpdater will no longer find it.
Do not be alarmed when the Linkstation eventually reboots (and makes the rebooting chime noises), but LSUpdater reports that it is still waiting for the LinkStation to respond.(You can ping your Linkstation at the IP address shown in the LSUpdater panel to verify that it is alive, and booted). Ignore the "Waited for 240[s] seconds but couldn't confirm..." message at the end of the update and click "No" when the updater asks whether it should wait again for a response.
What to do after FreeLink is installed
Now that your LinkStation has successfully rebooted, there are some further tasks to do.
Find your LinkStation on the network and open up an SSH session to it. In windows PuTTY is a good client
- login:root
- password: lspro
- login:admin
- password: admin
Please NOTE that if the linkstation re-starts itself 3 times then it goes into EM mode
and therefore you will need to re-start it again before you can proceed. otherwise you may think that the process hasnt worked.
You should then see the following welcome screen:
_sudZUZ#Z#XZo=_ DDDD EEEEEE BBBB IIIIII AAAA NN NN _jmZZ2!!~---~!!X##wa DD DD EE BB BB II AA AA NNN NN .<wdP~~ -!YZL, DD DD EEEEE BBBBB II AAAAAA NNNN NN .mX2' _%aaa__ XZ[. DD DD EE BB BB II AA AA NN NNNN oZ[ _jdXY!~?S#wa ]Xb; DDDD EEEEEE BBBBB IIIIII AA AA NN NN _#e' .]X2( ~Xw| )XXc .2Z` ]X[. xY| ]oZ( Linux Version 22.214.171.124-arm1 .2#; )3k; _s!~ jXf` Compiled #2 Thu Feb 8 15:00:20 JST 2007 1Z> -]Xb/ ~ __#2( One ARM ARM926EJ-Sid(wb) rev 0 (v5l) Processor, 128M RAM -Zo; +!4ZwaaaauZZXY' 266.24 Bogomips Total *#[, ~-?!!!!!!-~ LS-GL7D6 XUb;. )YXL,, +3#bc, BUFFALO INC. LinkStation series LS-GL(IESADA) admin@LS-GL7D6:~$
Cleanup / Fixes
Unfortunately there are some small issues with the ARM9-1.0rev2 release, but these are easy to fix. Some of the following changes are mandatory and are marked accordingly.
Don't forget to check out the Debian articles.
Emergency backdoor
For safety and also to provide a 'back-door' entry in the event of a problem, edit the file /usr/local/bin/initsw.sh and add the following lines to the file:
rm -f /etc/hddrootmode rm -f /boot/hddrootmode reboot
Fix hostname and /etc/hosts (mandatory)
Edit /etc/hostname to set your LinkStation Hostname, and make sure /etc/hosts is correct. The default Buffalo hostnames are LS-GLXXX (Pro) or HS-DHGLXXX (Live) where XXX are the last three characters of the MAC address (LS-GL7D6 is the default hostname of the system the FreeLink distribution was developed on). You will find the MAC address on a label on the bottom of the LinkStation.
You must also make sure that /etc/hosts contains the alias "localhost" for 127.0.0.1, i.e., a line:
127.0.0.1 localhost.localdomain localhost
127.0.0.1 localhost.localdomain localhost $HOSTNAME
where $HOSTNAME is what you put in /etc/hostname (if the alias localhost is missing, the scripts /etc/init.d/kernel-server-nfs and /etc/init.d/openbsd-inetd will not work properly, because they call rpcinfo -u localhost .... . A consequence is that nfs v3 gets disabled, and you unexpectedly only get nfs v2 which has limits on file sizes when files are transferred.)
See the Debian Manual for more details about /etc/hostname (e.g. domain is set via /etc/resolv.conf).
Activating your changed hostname without rebooting:
hostname --file /etc/hostname
Allow root login on serial console (if you use it)
root login on console is blocked if /etc/securetty is world-writable
chmod 0744 /etc/securetty
Fix kernelmon script (mandatory check)
There can be an issue with the kernelmon script, that may cause a significant amount of system resources being used and/or having a non-working shutdown button.
This issue mostly occurs when using a newer Linux kernel from Buffalo (e.g from 2.10 Stock FW).
To find out if the kernelmon script is eating up your NAS performance, call "top" and check if the kernelmon script is always at the top of the list with a high CPU load. Normally the script has a CPU usage of 0%.
To determine whether you can fix it, compare the output of "ls /proc/buffalo" and "ls /proc/driver".
If the subdirectory kernevnt is in /proc/buffalo, make this change; if it is in /proc/driver, do not. (Without it, things like the shutdown button might not work.)
This is to ensure that the micon interrupt device is pointing to the correct location in the /proc virtual filesystem that is created by the kernel when it is running.
To fix the script do the following:
- look in the file /usr/local/sbin/kernelmon script: find a line containing "cat /proc/driver/kernevnt", and change it to "cat /proc/buffalo/kernevnt".
The 18.104.22.168 buffalo kernel (the 2.06 LSLIVE firmware and the Freelink-supplied kernel) uses /proc/driver/kernevent while the 18.104.22.168 kernel (the 2.10 LSLIVE firmware) uses /proc/buffalo/kernevent
- if you needed to make this change, reboot your NAS for the change to take effect
Setting timezone (mandatory check)
To get the correct times for your files and schedules you have to set the correct timezone for the system and the users.
a) for the system in general
dpkg-reconfigure tzdata # otherwise use tzconfig, which is deprecated
b) for the user (e.g. root, admin, etc.)
tzselect # then copy/add the given line to the user's .profile in his home directory (e.g. TZ='Europe/Berlin'; export TZ) # if .profile is not available for the user, then just create it (check permissions afterwards)
c) UTC check
grep -e 'UTC' /etc/default/rcS
It should say "UTC=yes" which is the default for Linux/Unix.
Only reason to set it to "UTC=no" is if your machine is running Linux/Unix and a non-UTC-based system (non-UTC-based = local time based). For instance Windows defaults to local time rather than UTC. So if you either use these systems separately side-by-side or via a virtual machine (e.g. Debian on Windows), then "UTC=no" will help having the correct time in both systems.
Update of the Debian repository and packages
You can update your system with APT.
It is recommended, even by the Debian maintainers, to use APTITUDE instead of APT-GET, as it keeps track of automatically installed packages and does smarter and safer decisions when upgrading to a new release. Keep in mind that whenever you are told to use apt-get for maintaining packages, that you replace it with aptitude.
Note as the current UDEV package requires a higher kernel than the 22.214.171.124 kernel of Freelink ARM9 1.0rev2, the UDEV package should not be updated. Therefore hold the current UDEV package back, to avoid upgrades of it.
Holding back for aptitude:
aptitude hold udev
Another way is dselect of the dpkg-package
echo -e "udev hold" | dpkg --set-selections # When updating you HAVE to use # apt-get dselect-upgrade # aptitude dselect-upgrade
A third way would be to pin it via apt.
To get the latest versions of your installed software, first update the package list and then upgrade the packages.
As there are some scripts as left overs from the hotplug package inside the Freelink image, just purge the hotplug package before upgrading. (Maybe when the Freelink image was build the hotplug package was only removed and not purged.)
aptitude update aptitude purge hotplug aptitude upgrade (or aptitude dselect-upgrade if you choosed dselect)
If the internet connection does not work, please check your /etc/resolv.conf and your network settings in /etc/network
If the debian server hangs, you may need to edit /etc/apt/sources.list to change the server, for example from "ftp.uk.debian.org" to "ftp.us.debian.org"
If you did a fresh install of Freelink ARM9-1.0rev2 you will get the following error message when updating via apt:
W: There is no public key available for the following key IDs: B5D0C804ADB11277 W: You may want to run apt-get update to correct these problems
Then you have to retrieve the public key from the pgp server with this command
gpg --keyserver wwwkeys.eu.pgp.net --recv-keys B5D0C804ADB11277
If your behind a firewall, but can access the internet via port 80
gpg --fetch-keys "http://pgpkeys.pca.dfn.de/pks/lookup?op=get&options=mr&search=0xB5D0C804ADB11277"
Next add it permanently to your root keyring with
apt-key add /root/.gnupg/pubring.gpg
You should get an OK message, next retry to update.
To speed up the process of checking for updated packages, you can easily update apt's repository list with a cron job, which is already prepared by Debian. Just add the following lines to /etc/apt/apt.conf, then your NAS will update the list every morning and you can directly use the upgrade command.
APT { // Options for /etc/cron.daily/apt Periodic { // same as defining APT::Periodic::xyz Update-Package-Lists 1 ; Download-Upgradeable-Packages 1 ; Autoclean 1 ; }; };
If the file /etc/apt/apt.conf does not exist, then just create it via the following command and add the lines from above.
touch /etc/apt/apt.conf
To undo the holding of UDEV use
aptitude unhold udev
or for dpkg's dselect
echo -e "udev install" | dpkg --set-selections
Set your Locale
You may notice when installing from apt or in other situations that there are some errors about not having the correct locale.
You can fix this with
aptitude install locales
This will give you a few choices on what to set for your default locale.
Static IP address
You can set up a static IP address instead of DHCP. This is done by editing /etc/network/interfaces.
If you also want to state your local DNS server (e.g. your router) and local domain, then you can not directly modify /etc/resolv.conf, as Freelink 1.0rev2 comes with the resolvconf package installed. Instead you have to define all DNS data in /etc/network/interfaces for each interface.
auto lo iface lo inet loopback auto eth0 #iface eth0 inet dhcp iface eth0 inet static address 192.168.0.100 network 192.168.0.0 netmask 255.255.255.0 broadcast 192.168.0.255 gateway 192.168.0.1 dns-nameservers 192.168.0.1 dns-domain lan
NOTE: Do not blindly copy these lines into your file, rather choose the correct IP address and additional information based on your local network settings. If you don't know what these are, then don't modify this file.
To activate your changes without rebooting:
invoke-rc.d networking restart
To see that the change of the domain has occured:
hostname -f
For more information about DNS settings via resolvconf see the README file:
zcat /usr/share/doc/resolvconf/README.gz
Customized Partitions
You may not have enough space to install all the Applications you want to. If you have customised partitions, you will have enough space to install other applications (like webmin) Here you can see, how to do this:
Webmin (webbased administration)
Look here for instructions on how to install webmin:
You can reach Webmin via:
Updating your kernel (not always necessary)
For users who want to prepare the Linkstation for an updated kernel:
Securing Your Linkstation
Limit and/or remove the "guest" account
Note that the Guest account is a common attack point. This account can be used for system testing, but can be compromised due to default password in a Debian install. Further the Guest account by default in Debian 2.6 is capable of executing BASH scripts allowing system reconfiguration.
You can simply lock the Guest account ...
passwd guest -l
Change and protect your passwords
Anyone who can see your NAS on the network can of-course log into it as the root user (=full control!) with the default password, and make it their own.
Therefore change the passwords for the users root and admin using (as root):
passwd passwd admin
Please do not use the same password for both accounts.
As /etc/passwd and /etc/group must be world-readable the passwords in them can be read and cracked. Therefore it is recommended to turn on shadow passwords, so only user root can see the encrypted passwords.
pwconv (for user passwords) grpconv (for group passwords)
You should avoid group passwords, as those shared passwords are a typical security breach.
It is just as important to change the ssh server keys (see section below).
Limit which users and IPs can have access to SSH and su/sudo
If you don't want the trouble of using a ssh key pair (see below) then limit the range of IP and users that can have ssh access vis the sshd configuration file /etc/ssh/sshd_config.
Before your box has an active ssh port open to the internet, initially it is recommended that you basically shut off root access and only allow access via su or sudo for given users. This makes access to the box narrow and root execution via two passwords, via ssh and then su/sudo.
You can add the following line to /etc/ssh/sshd_config to disable root ssh access.
PermitRootLogin no
... and then restrict access to su via execution access of /bin/su.
For sudo - you can restrict user execution access via the sudo configuration file /etc/sudoers.
Create Unique SSH server keys for your machine
Due to the way that Freelink is currently installed, you will be using the ssh server keys that are distributed with the freelink archive. As these are publicly available, unless you change these, then your Linkstation will be vulnerable to both "Man-In-The-Middle" attacks - whereby someone impersonates your machine, and passes data along to the real machine (recording, and potentially altering data as they do so), and eaves-dropping (whereby they can decode the encrypted ssh data, as long as they can read the data that is being exchanged between the linkstation, and the machine which they are logging in from).
rm /etc/ssh/*host*key* dpkg-reconfigure openssh-server
Whereupon you should see:
Creating SSH2 RSA key; this may take some time ... Creating SSH2 DSA key; this may take some time ... Restarting OpenBSD Secure Shell server: sshd.
After this is finished, you can log out, and log back in again. When you try to, you will see a message like:
$ ssh root@linkstation @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is e2:74:96:43:fd:21:57:9e:94:ca:fa:8b:64:05:0c:23. Please contact your system administrator. Add correct host key in /home/user/.ssh/known_hosts to get rid of this message. Offending key in /home/user/.ssh/known_hosts:56 RSA host key for linkstation has changed and you have requested strict checking. Host key verification failed.
You are seeing this message because you have changed the host key (if someone really was doing a man-in-the-middle attack with the old key, you wouldn't see this message, as they would have the correct key to not-trigger the error report). Remove the old key from your ssh known_hosts file (in this case line 56 of /home/user/.ssh/known_hosts), and log in again... This time it should proceed as normal.
Your Linkstation is now secure - ideally, you should not have placed the Linkstation on an untrusted network before you reach this stage.
Removal or Reinstall of FreeLink
A backup of your data before doing this is always recommended.
If for some reason FreeLink must be uninstalled or re-installed, users must boot to the ramdisk (initrd) first. The ramdisk contains the Buffalo Updater Daemon that the Buffalo Updater requires. To boot to the ramdisk, access the linkstation shell via ssh. Run the follow commands:
- run "vi /boot/boot_options"
- press the [i] keyboard key to enter "edit mode".
- edit the line "MENU_TIMEOUT=4" to read "MENU_TIMEOUT=EM"
- run [Esc], ":", "wq"
- run "reboot"
The box should boot to the ramdisk after the reboot where you can install the stock kernel or any other firmware with the Firmware Updater Utility.
If during re-installation the LSUpdater complains about the harddisk structure (TARGET), then this is caused by some changed partition types (e.g. /dev/sda6 to ext3). To "fix" this, just login to your Linkstation as root via telnet once and re-try. After the re-installation login to your Linkstation via ssh and edit /etc/fstab to the correct partition formats. Mount the corrected partitions with "mount -a" for immediate access. This normally works fine for re-installation without losing any data on /dev/sda6.
Key Notes to Remember
- This version does not contain the updated kernel 2.6.2x. As a result, udev will not work in this release.
- Telnet is not installed. Use SSH for shell access.
- The FreeLinkomatix script has not incorporated this FreeLink release yet.
- The default root password is "lspro" and the default admin password is "admin". Please change these passwords.
- This contains the replacement fan controller daemon micro_evtd which monitors system temperature and adjusts fan speed to suit based on information held within /etc/default/micro_evtd.


text:
Furniture polish poisoning occurs when someone swallows or breathes in (inhales) liquid furniture polish. Some furniture polishes may also be sprayed into the eyes.
This is for information only and not for use in the treatment or management of an actual poison exposure. If you have an exposure, you should call your local emergency number (such as 911) or the National Poison Control Center at 1-800-222-1222.
Symptoms depend on how the poisoning occurred.
Swallowing such poison may cause:
If the poison touched your skin or eyes you may have:
Seek immediate medical help. Do NOT make a person throw up unless told to do so by poison Ccontrol or a health care professional.
If the chemical is on the skin or in the eyes, flush with lots of water for at least 15 minutes.
If the chemical was swallowed, immediately give the person water or milk, unless instructed otherwise by a health care provider. Do NOT give water or milk if the patient is having symptoms (such as vomiting, convulsions, or a decreased level of alertness) that make it hard to swallow.
If the person breathed in the poison, immediately move him or her to fresh air.
Determine the following information:
The National Poison Control Center (1-800-222-1222) can be called from anywhere in the United States. This national hotline number will let you talk to experts in poisoning. They will give you further instructions.
This is a free and confidential service. All local poison control centers in the United States use this national number. You should call if you have any questions about poisoning or poison prevention. It does NOT need to be an emergency. You can call for any reason, 24 hours a day, 7 days a week.
See: Poison control center - emergency number
The health care provider will measure and monitor your vital signs, including temperature, pulse, breathing rate, and blood pressure. Symptoms will be treated as appropriate. You may receive:
How well you do depends on the amount of poison swallowed and how quickly treatment is received. The faster you get medical help, the better the chance for recovery.
Swallowing such poisons can have severe effects on many parts of the body. The outcome depends on the extent of this damage. Damage can continue to occur for several weeks after the hydrocarbon was swallowed.
If the poison gets into the lungs (aspiration), the lungs can be badly damaged.
Mirkin DB. Benzene and related aromatic hydrocarbons. In: Shannon MW, Borron SW, Burns MJ, eds. Haddad and Winchester's Clinical Management of Poisoning and Drug Overdose. 4th ed. Philadelphia, Pa: Saunders Elsevier; 2007:chap 94.
Lewander WJ, Aleguas A Jr. Petroleum distillates and plant hydrocarbons. In: Shannon MW, Borron SW, Burns MJ, eds.Haddad and Winchester's Clinical Management of Poisoning and Drug Overdose. 4th ed. Philadelphia, Pa: Saunders Elsevier; 2007:chap 92.
Reviewed by: Jacob L. Heller, MD, MHA, Emergency Medicine, Virginia Mason Medical Center, Seattle, Washington. Also reviewed by David Zieve, MD, MHA, Medical Director, A.D.A.M., Inc.
Notice: The information provided herein should not be used during any medical emergency or for the diagnosis or treatment of any medical condition. A licensed physician should be consulted for diagnosis and treatment of any and all medical conditions. Call 911 for all medical emergencies. Links to other sites are provided for information only -- they do not constitute endorsements of those other sites. Copyright 1997-2012, A.D.A.M., Inc. Any duplication or distribution of the information contained herein is strictly prohibited.


text:
Welcome to MobiTog - The Original Mobile Photography Community!
THE Original Global Community for Mobile Photographers - Everywhere...
You are currently viewing our community forums as a guest user. Sign up or
Having an account grants you additional privileges, such as creating and participating in discussions.
RESULT Hipstamatic Magic Challenge #2
Discussion in 'Challenges' started by ImageArt, 27 January 2019.
Page 1 of 5
Page 1 of 5


text:
Difference between revisions of "Munnar"
Revision as of 17:19, 1 December 2012
Munnar is a hill station in the Indian state of Kerala.
Munnar is a beautiful hill station, and was the summer resort of the British. Tourists come here to see the vast tea plantations of the area. The town itself is typically Indian with the usual shops, guest houses and is really beautiful and traditional. It is a good place to stay to see the surrounding countryside. It is also a popular place for Indian honeymooners.
The town is divided into two parts, Old Munnar, where the tourist information office is, and Munnar, where the bus station and most guest houses are located.
The region in and around Munnar varies in height from 1,500 m (4,921 ft) to 2,695 m (8,842 ft) above mean sea level. It is pronounced "Moon-aar" short for "moonu aar" meaning 3 rivers. Three rivers - Madupetti, Nallathanni and Periavaru which flow through this town, but join some distance away from Munnar.
Munnar is famous for its tea plantations, many of them started by the British. The "Kannan Devan" brand of Tea from the Tata is cultivated and processed here.
The strobilanthus ("neelakurinji" in Malayalam, the local language), a blue flower which blooms only every 12 years, is found in this region. It bloomed last in December 2006. Munnar also has the highest peak in South India, Anamudi, at 2,695 m.
Eravikulam national park is one of the main tourist attraction, where you can find the endagered species of Nilgiri Tahr (mountain goat called "varayadu" in Malayalam). A treck to Rajamala ("King of hills" in Malayalam), in the morning is sure to spot a few friendly mountain goats. You can also find Gaur, Langur, Lion-tailed macaque, and Elephants depending on the season and time of travel. The altitude is 1,600-1.800 m above sea level. Temperature ranges from a minimum of 0⁰C to a maximum of 28⁰C. Warm clothes and rain gear is recommended. The tourist season is from Aug-Mar.
Malayalam and Tamil are main languages spoken here. You can manage with English or Hindi.
Get in
By air
Cochin International airport (IATA: COK, ICAO: VOCI), also known as Nedumbassery Airport and CIAL is the nearest airport. It is 110 km away from the Munnar by road.
Madurai International Airport which is 140Km from Munnar by (National Highway 49).
By train
The nearest railway station is Aluva, 110 km. Ernakulam is 130 km and Madurai is 135km You can get the direct regular buses to Munnar First Bus starts at 6AM.
By car
Distances from Munnar to various cities:
The road to Munnar is narrow with lots of bends and curves. Hire a taxi or a driver with local experience if you are not familiar with similar conditions
By bus
Munnar bus station is on the main street, Main Bazaar.
Note that most buses have boards in Malayalam and not English. At Aluva, there are no signs, schedules or dedicated bus bays for Munnar-bound buses; many of them briefly stop at Aluva en route from Kochi/ Ernakulam to Munnar. Check with a few locals every 15 minutes, or ask and hang around the bus info office, so they can point you to the right bus when it arrives.
There are also buses from Coimbatore and Pollachi.
Some of these site would be more popular to Indian tourists than to Western tourists.
Near Munnar Town
Towards Marayoor
Other places to visit:
The best things to buy are tea, coffee, spices like cinnamon, cloves, cardamom and pepper and definitely home made chocolates.
Banks/Currency Exchange
Kerala is famous for Fish Curry. For snacks, one should try local spicy cashew nut, chilly bhaji with hot tea as they are a traditional snack and makes good combination in cold weather.
Munnar has some amazing street food (try the Gobi noodles), so if you are after a cheap and delicious meal check the area around the bus stand in Munnar (not the KSRTC bus stand in Old Munnar).
Fresh tea, coffee and milk is available at most places. Hard and soft drink are also available at fair number of shops.
Packed grapes and mixed fruit juice is also available at few places.
Autumn Trees, N.H.-49, Devikulam, Munnar. Ph, +91-4865-264273/ 264399/ 208308. Fax : +91-484-4030010. Visit [[www.autumntreesmunnar.com][]1] Deluxe Rooms, Suite Rooms, Dormitory facilities & Multi cuisine Restaurant. For More details Contact : Jiji C. George (Director) +91-9447414147 / +91-9895294743. C.G.Yesudas (Director)+91-9447791191 . The above directors are from Kothamangalam in Chambakottukudiyil family http://www.genealogy.com/users/g/e/o/Jiji-C-George/ . They are younger & elder sons of C.C.Geevarghese . Yesudas's wife is Bindu managing a coputerised clothing embriodery unit , she is from Pattilakuzhiyil family in Kunnackal near Muvattupuzha and their children are Mariya Yesudas and Moses Yesudas. Jiji is an advocate and publisher of All Kerala Yellow Pages Directory Known as VANTAGE YELLOW PAGES his wife Ani Jiji, Ani is a talented interior designer & artist from Poothicote[[www.http://poothicote.net/branches.html)] family Mepral , they have two children - George Jiji Varghese & Jacob Jiji Varghese
Stay safe
Apply sunscreen lotion while you leave Munnar because as you descend the hills the weather gets warmer and causes sun burn. Hill stations tend to get dark rather early, so be sure to carry a torch or flashlight.
Emergency numbers
Ayurvedic treatments, massage
Get out


text:
Senator Jean Fuller (R-Bakersfield) and Assembly Woman Shannon Grove offered their responses to Governor Jerry Brown's State of the State address.
Fuller offered a positive, yet still critical, statement, pointing out some items in the governor's address that she did like as a member of the minority party.
"Governor Brown was given a reprieve by California voters last Fall and a rare opportunity to work across the aisle to find meaningful and long-term solutions to the state's most challenging problems," Fuller said in a statement. "While I am encouraged that the Governor highlighted the critical needs of water infrastructure, education, job creation and CEQA reform, we should be watchful for any real progress and improvements."
She did, however, find fault in a few of the governor's vision for the next year.
"And in the other areas of the Governor's Address, from implementing a new federal health care law to climate change to high-speed rail, it's important to note that over-spending on these projects will not result in any immediate economic benefit," she said.
Grove was more skeptical of the governor's plans and attacked him on spending of tax dollars and accepting of special interest money.
"The Governor just saluted public employee unions and thanked them for the millions of dollars they poured into passing the Prop. 30 tax hike last fall," Grove said. "Where's the Governor's shout-out to the small businesses whose pockets they all just raided again? Californians now pay the highest taxes in the nation because of Prop. 30, and our state's competitiveness in keeping and attracting job creators is suffering."
She said the people will be the final voice regardless of what the governor said.
"I trust that the voters won't continue to fall for the Democrats' convoluted logic that if California has one of the highest unemployment rates in the country, the answer lies in taking more money from working people and giving it to the bureaucrats in Sacramento to spend on themselves," Grove said. "Brown keeps touting his 'balanced' budget, but his numbers are based on revenues gained from $50 billion dollars' worth of higher taxes. He and the supermajority may think that they can tax away pension liabilities and the state's other IOUs, but California's challenges will only be resolved when we create a better business climate so people can get back to work."


text:
To (e-mail - use a comma between multiple address)
From (your email address)
The E-Mail Article feature is a convenient way for site visitors to forward links to articles of interest to others. JPMorgan Chase is not responsible for the use of this feature by site visitors, for the validity of any sender's e-mail address or for any message that is sent along with a forwarded article.
Copyright © 2019 JPMorgan Chase & Co. All rights reserved.


text:
I know, I know, it's not autumn anymore – and the hot days here in Sao Paulo keep me pretty aware of that… but being a rice lover it was impossible for me to resist this recipe.
I don't eat meat and you know it – and even when I did, back in the day, I would never eat pork. It's nothing religious or anything, I just don't like it.
I always have chorizo sausages in the fridge since Joao loves them – there's a kind called calabresa that is used in barbecues and also as a pizza topping. I decided to put my prejudices aside for a moment and try this recipe with the calabresa sausage. And I'm glad I did – the rice was packed with flavor and most of it due to that ingredient.
There's no rosemary in this recipe – I just thought it would make the dish look prettier. :)
This is my entry for the Weekend Herb Blogging, this time hosted by Vani, from the blog Batasari.
One last thing: the results for this DMBLGIT (in which one of the judges was yours truly) are up - congratulations to all the winners!
Autumn spicy rice
from Donna Hay magazine
1 tablespoon olive oil
1 red onion, sliced
3 chorizo sausages, sliced
200g (7oz) butternut squash, peeled and chopped
½ teaspoon chilli flakes
2 cups long-grain rice
3 cups (24fl oz) chicken stock
2 zucchinis (courgettes), thinly sliced
Heat a deep frying pan over medium heat. Add the oil, onion, chorizo, squash and chilli and cook for 2-3 minutes or until the onions are soft. Add the rice and cook, stirring for 1 minute.
Add the stock and bring to the boil. Reduce the heat to low, cover with a tight-fitting lid and cook for 15 minutes or until the stock is absorbed and the rice is cooked. Stir through the zucchini and allow to stand for 2 minutes.
Serves 4
Thursday, January 10, 2008
Autumn spicy rice
I know, I know, it's not autumn anymore – and the hot days here in Sao Paulo keep me pretty aware of that… but being a rice lover it was impossible for me to resist this recipe.
28 comments:
- Mandy said...
I love fried rice, especially a spicy one.It would be so good on a cold winter night. Thanks for the recipe, Patricia!Btw, your photo reminds me of pineapple. :)
- January 11, 2008
- Manggy said...
Ahahaha! If you'd found a squash/zucchini flower that would be a great garnish too.
You had me at "chorizo rice." A tablespoon of chili flakes for mine! :)
- January 11, 2008
- Deborah said...
This sounds delicious!! My sister-in-law doesn't like pork, either, although she does eat chicken.
- January 11, 2008
- Suzana said...
Patricia, that looks rather delicious! I have the same feeling about meat, although I eat poultry.
- January 11, 2008
- cakebrain said...
Looks yummy Patricia!
- January 11, 2008
- Bri said...
Patricia, I just wanted to thank you for judging DMBLGIT. I think you did a great job (and the fact that I was one of the winners has nothing ;) to do with it). Looks like your rice dish came together well, though since I am vegetarian, I can't speak to the sausages, sorry. Thanks again!
- January 11, 2008
- KJ said...
This looks great. I love chorizo and I love fried rice. Too perfect.
- January 11, 2008
- MyKitchenInHalfCups said...
Chorizo, butternut squash and zucchinis- that just has got to be great!
- January 11, 2008
- Peabody said...
I wish it were still Autum. Your rice looks like a great meal.
- January 11, 2008
- Susan from Food Blogga said...
Ironically, I have begun eating meat the last few months, and the first thing I ate was a sausage!
- January 11, 2008
That does look perfect for a fall meal, Patricia. So good that I may not wait! :)
- January 12, 2008
- Lydia said...
I love spicy fried rice, though I'm not a chorizo eater. I think spicy chicken sausage might be good in this recipe.
- January 12, 2008
- SteamyKitchen said...
sausage can make anything taste divine!
- January 12, 2008
- eatme_delicious said...
Yummy! I love rice dishes like this.
- January 12, 2008
- Kristen said...
Looks tasty!
- January 13, 2008
A delicious, healthy recipe, any season!
- January 13, 2008
- cakeitaly said...
Dear Blogger,
Your fantastic blog now is in the new Food Network created by cakeitaly.com.
FoodNetwork by CakeItaly
I will publish your articles in this page automatically. And you will increase your visitors and friends.
Please send my a picture in order to link your posts with beautiful photo.
If you want you can write an article about this our initiative:
FoodNetwork by CakeItaly
Best Regards
- January 13, 2008
- T.W. Barritt said...
Patricia - the use of sausage, butternut squash and rosemary sounds SO good!
- January 13, 2008
- Emiline said...
Hey- who cares if it's not Autumn? This looks great, and I'd eat it any time of year.
Way to put your prejudices aside.
- January 13, 2008
- maybahay said...
i love rice, i love chorizo. this is a fantastic combo!
- January 13, 2008
- Cynthia said...
I love rice too and can just imagine how well it goes with the chorizo.
- January 14, 2008
- Patricia Scarpin said...
Mandy, you are right, it does! :)
Mark, that's a great idea, I'll try to find it next time.
Deb, I don't like pork but love bacon. I'm crazy. :)
Suzana, I eat poultry too.
Cakebrain, thank you!
Bri, I was glad to see you on the winners list - you deserve it, sweetie!
KJ, thank you!
Tanna, they were good together!
Pea, I like autumn too, my friend.
Susan, really? So you'd love this dish!
Michelle, let me know what you think of it, sweetie.
Lydia, that idea is good, I'll try it next time!
Jaden, my husband thinks the same way. :)
Hi, darling! I'm glad you like it.
Kristen, thank you!
Ronell, and it's easy to put together.
T.W., tks!
Emiline, I agree. I love rice so much! :)
May, thank you!
Cynthia, it was really good.
- January 14, 2008
Great combination with the Squash and the Chorizo, Patricia.
Great post.
- January 14, 2008
- hannehanne said...
This DOES sound like a great combo. And it may be hot where you are, but here in Canada it's Winter (not autums, but close enough), and I love having great ideas for simple warming suppers. Thanks so much!
- January 14, 2008
- Cris said...
I love your contributions to this event, they are full of flavor, color and beauty, always.
- January 15, 2008
- Kalyn said...
It does sound very tasty. I haven't cooked with chorizo that much, but I do like it a lot.
- January 16, 2008
- kickpleat said...
yes! this is exactly what i want right now. looks perfecly healthy and comforting.
- January 16, 2008
- Arfi Binsted said...
lovely composition of meals!!
- January 17, 2008


text:
The Saints hosted two girls tennis tournaments last week and went 4-0. The toughest opponent the girls faced during that stretch was probably the weather as two of the doubles tournament matches were rained out last Wednesday.
The Saints hosted two girls tennis tournaments last week and went 4-0. The toughest opponent the girls faced during that stretch was probably the weather as two of the doubles tournament matches were rained out last Wednesday.
Head Coach Les Zellmann said he thought the girls would have won those rained out doubles matches.
The Wednesday tournament was an all doubles affair. The Saints hosted Luverne, Sibley East and Maple River.
In the match they completed, the Saints went 8-0 with most of the matches being won by comfortable margins.
The closest match was the Saints No. 3 doubles team of Hannah Christensen and Anna Haler. The girls lost the first set 6-7, won the second 6-1 and ground out the win in the third set tie breaker winning 13-11.
The Saints No. 1 doubles team were the one and two singles players of Lorena Hernandez and Julia Boeve. They won in straight sets 6-1, 6-2.
The Saints usual No. 1 doubles played at No. 2 in this match. Acacia Foss and Ashley Frederickson won 6-2, 6-0.
All the remaining Saints teams also won in straight sets.
Aubrey Eckstrom and Taylor Nordhausen teamed up to win 6-1, 6-1. Morgan Sandmeyer and Alejandra Trapero won 6-1, 6-3.
Miranda Giese and Hollie Peterson had a competitive straight set win. They won the first set in a 7-5 tie breaker and the second set 6-1.
Lil Krause and Lesley Vargas won 6-2, 6-3. Kalli Nordhausen and Mikkala Pearson won 6-2, 6-0.
The Saints were up 3-0 on Sibley East when the match was suspended.
Aubrey and Taylor won in straight sets 6-0, 6-2. At the No. 7 doubles slot Miranda Jacoby and Nicole Koenig won 6-4, 6-1.
Ana San Miguel and Shenya Johnson won 6-4, 6-0 giving the Saints a three match to zip lead when play was suspended. The Saints were comfortablely ahead in three other matches when the rains came.
On Friday the Saints played a quadrangular against Martin County West, Montevideo and YME.
The Saints beat MCW 7-0 in part because MCW forfeited the two and three doubles. The Saints dispatched the four singles players and the on doubles team that did play for MCW in straight sets.
Lorena Hernandez won 6-1,6-4, Julia Boeve won 6-1, 6-o, Aubrey Eckstrom won 6-0, 6-2 and Taylor Nordhausen won 6-3, 6-2.
Acacia Foss and Ashley Frederickson won at one doubles 6-2, 6-1.
The Saints lost at three doubles in the other two matches they played and won other matches by comfortable to commanding margins.
Against YME Hernandez won 6-0, 6-0; Boeve won 6-0, 6-1; Eckstrom won 6-0, 6-1; and Nordhausen won 6-1, 6-2.
In doubles Foss and Frederickson won 6-3, 6-0; and Anna Haler and Morgan Sandmeyer won 6-3, 6-4.
Against Montevideo the Saints won with Hernandez going 6-1, 6-1; Boeve won 6-2, 6-2; Eckstrom won 6-3, 6-0; and Nordhausen won 6-2, 7-5.
In doubles Foss and Frederickson won 6-0, 6-3; and Haler and Sandmeyer won 6-3, 6-4
In the first week of the season the Saints have jumped out to a 6-1 record with the only loss coming to big Class A school Orono. The success the Saints have had so far this year has lifted them up to the No. 3 ranking in the Class AA State Tennis Ranking this week. Lorena Hernandez in the No. 8 ranked individual player in the most recent poll.


text:
Johnston High School, Class of 1977, will have a 35th reunion Saturday, Nov. 10 at 7 p.m. at Ribs & Company, 1383 Atwood Ave., Johnston. There will be a cash bar.
Pilgrim High School, Class of 1967, is having its 45th reunion Nov. 17. They are looking for contact information on all classmates. Please send contact information to Barbara (Brennan) Napolitano, email@example.com; Jack Lyden, email@example.com; Jean (Cunningham) Friel, email@example.com; John Spagnolo, email@example.com; Janice (Bargamian) McCaughey email@example.com, John Carroll at email@example.com.
Johnston High School, Class of 1976, is planning a reunion this fall. All classmates who are interested in attending are asked to contact one of the following: Susan (Cirelli) Rose at firstname.lastname@example.com; Robin (Antonelli) Leonti at firstname.lastname@example.com or Laurie Langford at Wishes Under Wraps, located at 225 Greenville Ave. at 232-1190.
Mount Pleasant High School, Class of January 1963, is planning its 50th reunion to be held in April 2013. If you were a member of this class, please call one of the following classmate's numbers so we can include you in our contact list: Pat, 4943-0032; Annette, 4949-8981; Sandy, 4521-4443; Angela, 4885-0743; Betty Ann, 556-4319; Georgia, 647-3657; Rosemarie, 946-1599; or Carol, 4258-1084.