Tuesday, May 16, 2017

Ebay history download tool

Ebay doesn't let you download your buy history.  This tool exports it in various formats.

The most useful being xml.  However the XML is actually exported as a multivalue format,
and generic parsers do not get it right.

schema is:

<order>
  <items>
     <item></item>
     <item></item>
  </items>
  <items>
    ...
</order>

within each <items> object there are multiple <item> objects each representing a separate transaction with the vendor of <items> object.  So a multi-valued database would have no problem.  However
linear xml parsing results in a mess if translating later to such as an XML or flat file.

however beats nothing as an export tool

There is a chrome plugin called "ebay purchase history report". This is the best I have found so far. Only problem is it does not show the tracking# of the ordered item.

https://chrome.google.com/webstore/detail/ebay-purchase-history-rep/ohoebnmmkndcieckfjblpdlfjpaeonbc


Posted by at No comments:
Labels: , ,

Monday, May 8, 2017

Flightaware ADSB Raspberry Pi receiver



Raspberry Pi
Piaware image
SDR radio
Clear sky exposure

https://flightaware.com/adsb/piaware/


Posted by at No comments:
Labels: , , , ,

Friday, May 5, 2017

Replies to Zos messages


http://narkive.com/OTIqXkPg:3.637.2

Issue is how to reply to messages.  

IXC208I THE RESPONSE TO MESSAGE IXC420D IS INCORRECT: IS NOT A VALID ACTION
IXC420D REPLY I TO INITIALIZE SYSPLEX ADCDPL, OR R TO REINITIALIZE XCF.
REPLYING I WILL IMPACT OTHER ACTIVE SYSTEMS.
I
IEE282A REPLY 00 EXPECTED; NO OTHER COMMANDS ACCEPTED. SPECIFY
REPLY 00.
All replies to messages in z/OS (and other versions of MVS) are done with
the reply command. The command is issued as "R <id>,<text>", where <id> is
the reply ID printed next to the message and <text> is the text of the
reply. There's no reply ID shown next to this message because the reply ID
at NIP time (before the full console display is redrawn) is always 00. That
means you need to enter the command as "R 00,'I'" (without the "").
Posted by at No comments:
Labels: , ,

Thursday, April 27, 2017

Ubuntu 16.04 exfat mount with ntfs. 128gb SD cards example




How to Mount EXFAT partition on Ubuntu 16.04 LTS

To mount exfat partition on Ubuntu, simply install the necessary packages:
$ sudo apt-get install exfat-fuse exfat-utils

If you need to mount it from the command line, you could do
$ sudo mkdir /media/exfat
$ sudo mount -t exfat /dev/sdxx /media/exfat
where /dev/sdxx could be /dev/sda1 or /dev/sda2, or so on.

If you are not sure whether the exfat partition you are looking for is /dev/sda1 or /dev/sda2, then you could also run
$ sudo lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL
This should do it!

http://unixnme.blogspot.com/2016/04/how-to-mount-exfat-partition-in-ubuntu.html 

The ghome-disks utility can also be used to start and mount this.  Since it is /dev/mmc and not /dev/sd, the system will probably have it assumed to be system owned, and will mount under root ownership only.

You can follow the above, but will then have to do a lot of crap with permissions to the mount.  If it were or is a fixed mount and not the automount /media mechanism one can do that once.  However it will be reset on every mount and be inconvenient.

Solution might be to use gnome-disks.  That has a problem however.  The FUSE exfat driver and the above asset is root owned.  Gnome-disks will not access and mount it due to the system ownership problem

So use a utility to run gnome kit stuff from a command line as su root.

apt-get -y install gksu

installs the gksudo and other stuff.

gksudo gnome-disks will mount the device and make it properly available.

Note that sudo gnome-disks makes the thing root owned again, since you are running as root user in the desktop.  gksudo will run as root, but effectivly as the user desktop user id.

Posted by at No comments:
Labels: , , , , , , ,

Thursday, April 20, 2017

support for ancient ubuntu releases


I've got a couple of machines that probably won't upgrade nicely, and the "gee why can't you upgrade them" comments are useless.  The ones I had were appliance downloads popular at the time I obtained them, and there was not the usual trail of how they were built accompanying them.

since one is my email archive I will continue to run it till SMTP POP3 and IMAP protocols die without any update.

Here is a link which worked for my oldest version, hardy, which is Ubuntu 8.  The date of the release is to probably 2006 maybe earlier.

https://superuser.com/questions/339537/where-can-i-get-the-repositories-for-old-ubuntu-versions

Here is the most useful answer (including the useless suggestion to update). 

**********************

Your system is End-of-Line (EOL), therefore not officially supported. Unless you have a good reason for sticking with 9.04, upgrade to a newer version. 16.04 is the next long-term supported release for Ubuntu, which will continue to receive updates.
To access old Ubuntu repositories, take a look at http://old-releases.ubuntu.com/.
There is also an official Ubuntu documentation for EOL upgrades
They say you should be able to access your packages by putting the following into /etc/apt/sources.list. Important: Change CODENAME to your distribution's code name, e.g. jaunty.


## EOL upgrade sources.list
# Required
deb http://old-releases.ubuntu.com/ubuntu/ CODENAME main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ CODENAME-updates main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu/ CODENAME-security main restricted universe multiverse

# Optional
#deb http://old-releases.ubuntu.com/ubuntu/ CODENAME-backports main restricted universe multiverse
 
 
Just run apt-get update and you can use them.

Posted by at No comments:
Labels: , , , , , , ,

Thursday, April 6, 2017

Migrating Readynas Radiator to OS 6 Readynas devices


One challenge in migrating from Sparc architecture products, to Intel or other (Arm), is that the Linux file system on sparc was built with a 4k block size, rather than 512.

On Intel linux, if you set up your disks, you can mount them with some incantations and special procedures.  Not sure how the Readynas Linux handles that problem, but there is a link showing it.

I had a bad disk and some problems with the data recovery firmware on a REadynas NV+ some years ago and got the support group to help me get around it.  In the mean time, I had mounted the 4 drives on an Intel linux system I'd built up and had recovered most of the data.

https://kb.netgear.com/29875/ReadyNAS-Migrating-disks-from-RAIDiator-to-OS-6?cid=wmt_netgear_organic

Copy of article for archival:

This articles outlines the necessary steps to access data on disks from ReadyNAS units running RAIDiator on ReadyNAS OS 6 units.
Due to differences in CPU architecture and operating system between RAIDiator and ReadyNAS OS 6, it may be necessary to take additional steps once the disks are moved to an OS 6 chassis.
If your ReadyNAS running RAIDiator is still functional, and you can access the data, we recommended you first backup the data to another location
http://kb.netgear.com/app/answers/detail/a_id/21344
If you can no longer access the data using your legacy ReadyNAS and you wish to access the data using your ReadyNAS OS 6 device, booting may not be as easy. Depending on which legacy model the disks come from, and which ReadyNAS OS 6 you posses the steps differ to make the data accessible.
After initially moving the disks from the legacy ReadyNAS to the ReadyNAS OS 6 model please be aware of the following items;
  • Do not attempt an OS reinstall
  • Do not attemp a factory reset
  • The RAID must be healthy i.e. if the RAID was broken on the legacy NAS it will not always be possible to access the data on the ReadyNAS OS 6 - an example of this would be 2 failed disks in a 4 disk RAID 5.
  • ReadyNAS OS 6 model must have at least the same amount of drive bays as the legacy ReadyNAS
  • Logging a ticket with Technical Support may be required
  • Purchasing a data recovery contract may be required
  • You may require one additional spare blank disk
  • You may require an external location to where you can recover your data to i.e. external USB HD, network share, other NAS storage.
To find the steps needed to access the data on your ReadyNAS OS 6 device, find your model below:
  • ReadyNAS OS 6
    • ARM
      • ReadyNAS 100 series (RN102, RN104)
      • ReadyNAS 200 series (RN202, RN204)
      • ReadyNAS 210 series (RN212, RN214)
      • ReadyNAS 2120 (RN2120)
    • x86
      • ReadyNAS 300 series (RN312, RN314, RN316)
      • ReadyNAS 500 series (RN516)
      • ReadyNAS 700 series (RN716X)
      • ReadyNAS 3130 (RN3130)
      • ReadyNAS 3138 (RN3138)
      • ReadyNAS 3220 (RN3220)
      • ReadyNAS 4220 (RN4220)
Find the model of your Legacy ReadyNAS running RAIDiator, click on the link and follow the instructions. X represents whether or not your model came with disks.



Posted by at No comments:
Labels: , , , ,

Tuesday, April 4, 2017

NFS Client and Server setup pages


To set up NFS Client and Server functions on Debian, et. al. here are some notes

NFS Server

apt-get install nfs-kernel-server nfs-common

NFS Client

apt-get install nfs-common

Exports

/home/jws           192.168.0.101(rw,sync,no_subtree_check)
/var/www        192.168.0.101(rw,sync,fsid=0,crossmnt,no_subtree_check,no_root_squash)

Other setup details related to mount @ boot time, etc., refer to link below.

Examples above from:

https://www.howtoforge.com/install_nfs_server_and_client_on_debian_wheezy

Posted by at No comments:
Labels: , ,
Subscribe to: Posts (Atom)