gmane.linux.slackware.armedslack

Re: Prompts and Slackware (general not necessarily ARMrelated)

Davide — 2013-06-18T12:22:06


It's not from an ARM device I'm getting those errors, I actually have not noticed it there yet, they're coming from  x86 and x86_64 hardware.

But this is really getting off topic. 

David_______________________________________________
ARMedslack mailing list
ARMedslack< at >lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

Re: Prompts and Slackware (general not necessarily ARMrelated)

Davide — 2013-06-18T12:18:18



Unlikely 2001 back then we only had 2.4 stable kernels  .... more like 2010 


Also unlikly as I seen it on different distributions (even enterprise ones at work) , on different hardware and in virtual machines (belonging to a vmware infrastructure system), on my scripts and on system scripts.

Well whatever ... might not be connected to that but surely it's an odd thing.

David_______________________________________________
ARMedslack mailing list
ARMedslack< at >lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

Re: Prompts and Slackware (general not necessarily ARMrelated)

Ottavio Caruso — 2013-06-17T15:14:54

Kernel.org was hacked in 2011. But I think that the segmentation faults
come from dodgy Android code. Has anybody read a dmesg on an Android
device? I can post one if nedeed. It's a mess!
_______________________________________________
ARMedslack mailing list
ARMedslack< at >lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

Re: Prompts and Slackware (general not necessarily ARM related)

Stuart Winter — 2013-06-17T14:55:57


It was ages ago - in 2001!
Chances are that your installation has installed something dodgy,
or you may even have some faulty RAM modules.

Re: Prompts and Slackware (general not necessarily ARMrelated)

Gregg Levine — 2013-06-17T14:38:24

Hello!
It's possible. But not unlikely. The other question is when was the
Kernel site hacked?

-----
Gregg C Levine gregg.drwho8< at >gmail.com
"This signature fought the Time Wars, time and again."

Re: Prompts and Slackware (general not necessarily ARMrelated)

Davide — 2013-06-17T14:35:37




I'm beginning to think that since kernel.org was hacked that things just are not the same ....
I'm seeing more and more often "segmentation fault" and "memory fault" in bash scriprs.
Now it's odd that a script that executes only internal or userland commands exibits a segmentation fault that as far as I recall means that a program is accessing memory that is not pertinent to that program. 

Should not bash and the GNU userland (shippet with stable distributions) be immune to this sort of problem ?

Ciao
David_______________________________________________
ARMedslack mailing list
ARMedslack< at >lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

Re: Raspberry Pi support for Slackware ARM 14.1

2013-06-15T19:21:16

Versatile / versatile. Yes that was a typo as I was working in the installer I could not cut and paste from either the QEmu or Raspberry Pi.
Left machines upgrading to current. Going to leave it for tonight
Sent from my BlackBerry smartphone from Virgin Media

-----Original Message-----
From: Stuart Winter <m-lists< at >biscuit.org.uk>
Sender: "ARMedslack" <armedslack-bounces< at >lists.armedslack.org>Date: Sat, 15 Jun 2013 18:38:45 
To: Slackware ARM port<armedslack< at >lists.armedslack.org>
Reply-To: Slackware ARM port  <armedslack< at >lists.armedslack.org>
Subject: Re: [ARMedslack] Raspberry Pi support for Slackware ARM 14.1

This is incorrect usage.  The '|' means 'OR', and by escaping it with '\'
you're preventing grep from mapping '|' to that 'OR' meaning.
Also, the ARM versatile platform has a capital V in /proc/cpuinfo, so if
you tested it there, then it's matching something other than 'versatile'
since you did not call grep with -i.

If you were to test it outside of the installer, the script works as it should.

Re: Prompts and Slackware (general not necessarily ARMrelated)

Gregg Levine — 2013-06-15T18:19:10

On Sat, Jun 15, 2013 at 1:51 PM, Ottavio Caruso
<ottavio2006-usenet2012< at >yahoo.com> wrote:


Hello!
It was the installer for QNX a Posix based Real Time OS who claims to
be running on a lot of business based systems. I sometimes try to
build images for applications that are slightly above the norm.

You're close enough Stuart, it was the installer mechanism for that
product who crashed things. Earlier I did find the original profile
saved as profile.backup and copied it back, and noted that it was
setup as an empty file when the thing was removed.

I also did restore the etc area and noted the presence of profile.new
as well. Mine was the backup named file.
-----
Gregg C Levine gregg.drwho8< at >gmail.com
"This signature fought the Time Wars, time and again."

Re: Prompts and Slackware (general not necessarily ARMrelated)

Ottavio Caruso — 2013-06-15T17:51:34

I haven't used slackware on intel for some time but I'm not aware of a
system uninstall utility, unless you mean uninstalling a single package.
_______________________________________________
ARMedslack mailing list
ARMedslack< at >lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

Re: Prompts and Slackware (general not necessarily ARM related)

Stuart Winter — 2013-06-15T17:47:37


What is this, exactly?
I am assuming that you got some 3rd party software that installed via
(typically) a shell script, and now you've uninstalled it using the same
script.


It's screwed up your user's profile script (~/.bash* files), or if you ran
the installer as root, then it could have edited the system-wide profile script - probably
either deleted something from /etc/profile.d, or maybe broken
/etc/profile.

mozes< at >kermit:~$ grep -r PS1 /etc/profile*
/etc/profile:#PS1='`hostname`:`pwd`# '
/etc/profile: PS1='! $ '
/etc/profile: PS1='! ${PWD/#$HOME/~}$ '
/etc/profile: PS1='%n< at >%m:%~%# '
/etc/profile: PS1='$ '
/etc/profile: PS1='\u< at >\h:\w\$ '
/etc/profile:export PATH DISPLAY LESS TERM PS1 PS2

My /etc/profile is the standard Slackware one which checks which shell
you're running, and if it's anything that isn't ksh, ash and some others,
it sets PS1 to the user< at >machine.

You might want to look at the 'etc' package (in 'a' series) for your
particular Slackware release.  If you unpack it and copy the
'etc/pro

Re: Raspberry Pi support for Slackware ARM 14.1

Stuart Winter — 2013-06-15T17:38:45


This is incorrect usage.  The '|' means 'OR', and by escaping it with '\'
you're preventing grep from mapping '|' to that 'OR' meaning.
Also, the ARM versatile platform has a capital V in /proc/cpuinfo, so if
you tested it there, then it's matching something other than 'versatile'
since you did not call grep with -i.


If you were to test it outside of the installer, the script works as it should.

Calling 'grep' from a symlink called 'egrep' simply saves you passing
the -E option to grep.   I suspect that the issue is because in the
installer, the grep binary is called 'grep.bin' (probably legacy - I can't find
any reason for it to be named this - I can only guess that we had the
'grep' functionality of busybox available in the past, and wanted to be
able to use both versions) and when named as such, it doesn't respect
the name it was originally called as, thus not switching on the '-E'
functionality.

I've changed the script to use grep -E rather than 'egrep', and it works
inside the installer now.  I'll

Prompts and Slackware (general not necessarily ARMrelated)

Gregg Levine — 2013-06-15T15:50:02

Hello!
Earlier today I had my Slackware (on Intel) system uninstall system.
Its installer removal program told me that I'd need to log out and log
back in before there would be any changes seen. Well I did that. On
logging back in I saw that the process had eaten the prompt.

It replaced the <user name>< at ><machine name> that's been a mainstay of
Linux since I first started using the OS many years earlier, with just
the shell name. Which is of course Bash.

I don't suppose all of you have any ideas for recovering things,
outside of reinstalling the works? In that eventually I made sure I
had downloaded a fresh DVD image of Slackware, and of the version that
the system is currently running. And I'm making plans for backing up
everything important that I put on the system since it was installed
about two years ago December. I also asked on a list that I fellow I
know runs where everyone runs everything else, and advice is rarely
Slackware friendly.
-----
Gregg C Levine gregg.drwho8< at >gmail.com
"This signature fough

Re: Raspberry Pi support for Slackware ARM 14.1

stanley garvey — 2013-06-15T15:34:13



On Jun 15, 2013 15:31 "stanley garvey" <stanley< at >stanleygarvey.com>
wrote:

ARMedslack mailing list
ARMedslack< at >lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

Re: Raspberry Pi support for Slackware ARM 14.1

stanley garvey — 2013-06-15T14:31:38

ARMedslack mailing list
ARMedslack< at >lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

Re: Exagerate XZPDA700

Davide — 2013-06-14T13:01:01

 still

Ok here's some info on the device (I've not yet rooted the device but I got is as root so I guess this one is not locked) :

root< at >darkstar:~/ac100/devel/android-sdk-linux_x86/platform-tools# ./adb  shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
root< at >android:/ # 
root< at >android:/ # cat /proc/partitions                                          
major minor  #blocks  name

   7        0       3150 loop0
   7        1      14585 loop1
  93        0      16384 nanda
  93        8      16384 nandb
  93       16      32768 nandc
  93       24     393216 nandd
  93       32    1048576 nande
  93       40      16384 nandf
  93       48      32768 nandg
  93       56     262144 nandh
  93       64     131072 nandi
  93       72    1981440 nandj
 254        0       3150

Re: Exagerate XZPDA700

Davide — 2013-06-14T07:12:56




Ooops ... XZPAD700 
I have one ... I got in in hypermarket Carrefour in offer 69 Euro.
I'm sure it's a re branded Chinese thing but for that price I can stick up with it.

I've got a bit of work to do now ... but I'll connect it via ADB and dump a bit of usefull info asap.

Ciao
David
_______________________________________________
ARMedslack mailing list
ARMedslack< at >lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

Re: Raspberry Pi support for Slackware ARM 14.1

stanley garvey — 2013-06-13T20:49:48

ARMedslack mailing list
ARMedslack< at >lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

Re: Raspberry Pi support for Slackware ARM 14.1

Stuart Winter — 2013-06-13T20:39:34


Actually, can you test it? I just edited it and haven't tested it.  It's
really just cosmetic, so it should be fine:

http://armed.slackware.com/tmp/armedslack-nofscheck

Re: Raspberry Pi support for Slackware ARM 14.1

Stuart Winter — 2013-06-13T20:35:51

Cool. How'd it go?!


Ok I've changed it and will upload the new installers once I've got Linux
3.9.6 kernels built.

Re: Raspberry Pi support for Slackware ARM 14.1

stanley garvey — 2013-06-13T20:22:34

ARMedslack mailing list
ARMedslack< at >lists.armedslack.org
http://lists.armedslack.org/mailman/listinfo/armedslack

Re: gcc 4.8.1 in -current

Stuart Winter — 2013-06-13T17:51:56

Hi LS


The current problem with 4.8.0 is the same as here - it does not produce a
bootable kernel.

https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1178847

I am going to build gcc 4.8.1 soon and see whether it can compile a
bootable kernel.   If it can, I'll upgrade it in the 'd' series; if not
4.8.1 will upgrade 4.8.0 in /extra.