[gentoo-user] Access device on 192.168.1.1 network

[thelma]

My local network is 10.0.0.1 - 

I have an external device that is pre-set from factory to 192.168.1.100 and I 
need to access to it via browser to change its network setting.
So I do: 
ifconfig net0:1 192.168.1.1 up

nmap -sn 192.168.1.1/24

Starting Nmap 6.47 ( http://nmap.org ) at 2017-02-12 00:54 MST
Nmap scan report for 192.168.1.100
Host is up (0.00015s latency).
MAC Address: 00:09:45:41:73:D1 (Palmmicro Communications)
Nmap scan report for 192.168.1.1
Host is up.
Nmap done: 256 IP addresses (2 hosts up) scanned in 3.78 seconds

The device is showing up but I can not ping it, 100% packet loss.

-- 
Thelma

Re: [gentoo-user] Access device on 192.168.1.1 network

[thelma]

On 02/12/2017 01:01 AM, the...@sys-concept.com wrote:
> My local network is 10.0.0.1 - 
> 
> I have an external device that is pre-set from factory to 192.168.1.100 and I 
> need to access to it via browser to change its network setting.
> So I do: 
> ifconfig net0:1 192.168.1.1 up
> 
> nmap -sn 192.168.1.1/24
> 
> Starting Nmap 6.47 ( http://nmap.org ) at 2017-02-12 00:54 MST
> Nmap scan report for 192.168.1.100
> Host is up (0.00015s latency).
> MAC Address: 00:09:45:41:73:D1 (Palmmicro Communications)
> Nmap scan report for 192.168.1.1
> Host is up.
> Nmap done: 256 IP addresses (2 hosts up) scanned in 3.78 seconds
> 
> The device is showing up but I can not ping it, 100% packet loss.

ifconfig is showing:

net0:1: flags=4163  mtu 1500
inet 192.168.1.1  netmask 255.255.255.0  broadcast 192.168.1.255
ether 00:1b:21:b8:27:b6  txqueuelen 1000  (Ethernet)
device interrupt 16  memory 0xfddc-fdde

--
Thelma

Re: [gentoo-user] Access device on 192.168.1.1 network

[Mick]

On Sunday 12 Feb 2017 01:07:09 the...@sys-concept.com wrote:
> On 02/12/2017 01:01 AM, the...@sys-concept.com wrote:
> > My local network is 10.0.0.1 -
> > 
> > I have an external device that is pre-set from factory to 192.168.1.100
> > and I need to access to it via browser to change its network setting. So
> > I do:
> > ifconfig net0:1 192.168.1.1 up
> > 
> > nmap -sn 192.168.1.1/24
> > 
> > Starting Nmap 6.47 ( http://nmap.org ) at 2017-02-12 00:54 MST
> > Nmap scan report for 192.168.1.100
> > Host is up (0.00015s latency).
> > MAC Address: 00:09:45:41:73:D1 (Palmmicro Communications)
> > Nmap scan report for 192.168.1.1
> > Host is up.
> > Nmap done: 256 IP addresses (2 hosts up) scanned in 3.78 seconds
> > 
> > The device is showing up but I can not ping it, 100% packet loss.
> 
> ifconfig is showing:
> 
> net0:1: flags=4163  mtu 1500
> inet 192.168.1.1  netmask 255.255.255.0  broadcast 192.168.1.255
> ether 00:1b:21:b8:27:b6  txqueuelen 1000  (Ethernet)
> device interrupt 16  memory 0xfddc-fdde
> 
> --
> Thelma

Are you sure the device is configured to respond to pings?

Are your routes on the PC configured correctly, if you are using a secondary 
interface on the same NIC?

Does nmap -A -T4 -Pn -vvv 192.168.1.100 show any services running to which you 
can connect?

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Access device on 192.168.1.1 network

[Adam Carter]

On Sun, Feb 12, 2017 at 7:07 PM,  wrote:

> On 02/12/2017 01:01 AM, the...@sys-concept.com wrote:
> > My local network is 10.0.0.1 -
> >
> > I have an external device that is pre-set from factory to 192.168.1.100
> and I need to access to it via browser to change its network setting.
> > So I do:
> > ifconfig net0:1 192.168.1.1 up
> >
> > nmap -sn 192.168.1.1/24
> >
> > Starting Nmap 6.47 ( http://nmap.org ) at 2017-02-12 00:54 MST
> > Nmap scan report for 192.168.1.100
> > Host is up (0.00015s latency).
> > MAC Address: 00:09:45:41:73:D1 (Palmmicro Communications)
> > Nmap scan report for 192.168.1.1
> > Host is up.
> > Nmap done: 256 IP addresses (2 hosts up) scanned in 3.78 seconds
> >
> > The device is showing up but I can not ping it, 100% packet loss.
>
> ifconfig is showing:
>
> net0:1: flags=4163  mtu 1500
> inet 192.168.1.1  netmask 255.255.255.0  broadcast 192.168.1.255
> ether 00:1b:21:b8:27:b6  txqueuelen 1000  (Ethernet)
> device interrupt 16  memory 0xfddc-fdde
>

Are both 192.168.1 devices on the same layer 2 segment (if not it wont
work).

arp -a will show if the IP address was resolvable to a MAC address, If it
says  you have a layer two problem.

Re: [gentoo-user] Access device on 192.168.1.1 network

[Naveen Narayanan]

On Sun, Feb 12, 2017 at 01:01:01AM -0700, the...@sys-concept.com wrote:
> My local network is 10.0.0.1 - 
> 
> I have an external device that is pre-set from factory to 192.168.1.100 and I 
> need to access to it via browser to change its network setting.
> So I do: 
> ifconfig net0:1 192.168.1.1 up
> 
> nmap -sn 192.168.1.1/24
> 
> Starting Nmap 6.47 ( http://nmap.org ) at 2017-02-12 00:54 MST
> Nmap scan report for 192.168.1.100
> Host is up (0.00015s latency).
> MAC Address: 00:09:45:41:73:D1 (Palmmicro Communications)
> Nmap scan report for 192.168.1.1
> Host is up.
> Nmap done: 256 IP addresses (2 hosts up) scanned in 3.78 seconds
> 
> The device is showing up but I can not ping it, 100% packet loss.
> 
> -- 
> Thelma
> 

Hi Thelma,

Does the device have a firewall ? Is it set to drop ICMP packets by
default ?

Regards,
Naveen

[gentoo-user] logrotate ... won't!

[Mick]

I am perplexed why box of mine will not logrotate system logs, which have now 
grown into gigs.  kern.log, syslog, messages, etc. are eating up space 
unconstrained, to the point where the partition run out of it.

Trying to run /etc/cron.daily/logrotate from a terminal does not show anything 
in messages, or syslog.

Particulars below:

# ls -la /etc/cron.daily/logrotate
-rwxr-xr-x 1 root root 179 Feb 12 16:09 /etc/cron.daily/logrotate


# cat /etc/cron.daily/logrotate
#!/bin/sh

/usr/bin/logrotate /etc/logrotate.conf
EXITVALUE=$?
if [ $EXITVALUE != 0 ]; then
/usr/bin/logger -t logrotate "ALERT exited abnormally with [$EXITVALUE]"
fi
exit 0


This is an installation I have not really changed much from default settings.  
Comparing with other systems which work as expected I can't see anything 
amiss. How could I troubleshoot/fix this problem?

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] logrotate ... won't!

[Alexander Kapshuk]

On Sun, Feb 12, 2017 at 6:57 PM, Mick  wrote:
> I am perplexed why box of mine will not logrotate system logs, which have now
> grown into gigs.  kern.log, syslog, messages, etc. are eating up space
> unconstrained, to the point where the partition run out of it.
>
> Trying to run /etc/cron.daily/logrotate from a terminal does not show anything
> in messages, or syslog.
>
> Particulars below:
>
> # ls -la /etc/cron.daily/logrotate
> -rwxr-xr-x 1 root root 179 Feb 12 16:09 /etc/cron.daily/logrotate
>
>
> # cat /etc/cron.daily/logrotate
> #!/bin/sh
>
> /usr/bin/logrotate /etc/logrotate.conf
> EXITVALUE=$?
> if [ $EXITVALUE != 0 ]; then
> /usr/bin/logger -t logrotate "ALERT exited abnormally with [$EXITVALUE]"
> fi
> exit 0
>
>
> This is an installation I have not really changed much from default settings.
> Comparing with other systems which work as expected I can't see anything
> amiss. How could I troubleshoot/fix this problem?
>
> --
> Regards,
> Mick

I had a similar problem a while back, and Alex Corkwell suggested
removing the executable bit on /etc/cron.hourly/0anacron, which did
the trick for me.

See gentoo-user archives for an email exchange with 'portage summary
logs not rotated any more' as the subject for full details.

Hope this helps.

Re: [gentoo-user] logrotate ... won't!

[Mick]

On Sunday 12 Feb 2017 19:11:23 Alexander Kapshuk wrote:
> On Sun, Feb 12, 2017 at 6:57 PM, Mick  wrote:
> > I am perplexed why box of mine will not logrotate system logs, which have
> > now grown into gigs.  kern.log, syslog, messages, etc. are eating up
> > space unconstrained, to the point where the partition run out of it.
> > 
> > Trying to run /etc/cron.daily/logrotate from a terminal does not show
> > anything in messages, or syslog.
> > 
> > Particulars below:
> > 
> > # ls -la /etc/cron.daily/logrotate
> > -rwxr-xr-x 1 root root 179 Feb 12 16:09 /etc/cron.daily/logrotate
> > 
> > 
> > # cat /etc/cron.daily/logrotate
> > #!/bin/sh
> > 
> > /usr/bin/logrotate /etc/logrotate.conf
> > EXITVALUE=$?
> > if [ $EXITVALUE != 0 ]; then
> > 
> > /usr/bin/logger -t logrotate "ALERT exited abnormally with
> > [$EXITVALUE]"
> > 
> > fi
> > exit 0
> > 
> > 
> > This is an installation I have not really changed much from default
> > settings. Comparing with other systems which work as expected I can't see
> > anything amiss. How could I troubleshoot/fix this problem?
> > 
> > --
> > Regards,
> > Mick
> 
> I had a similar problem a while back, and Alex Corkwell suggested
> removing the executable bit on /etc/cron.hourly/0anacron, which did
> the trick for me.
> 
> See gentoo-user archives for an email exchange with 'portage summary
> logs not rotated any more' as the subject for full details.
> 
> Hope this helps.

Thanks Alexander, it pays going back to basics ... for some reason my cronie 
service was not running.  o_O

I added it to default runlevel and hopefully it will do its magic from now on.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Access device on 192.168.1.1 network

[thelma]

On 02/12/2017 04:26 AM, Adam Carter wrote:
> On Sun, Feb 12, 2017 at 7:07 PM,  > wrote:
> 
> On 02/12/2017 01:01 AM, the...@sys-concept.com
>  wrote:
> > My local network is 10.0.0.1 -
> >
> > I have an external device that is pre-set from factory to 192.168.1.100 
> and I need to access to it via browser to change its network setting.
> > So I do:
> > ifconfig net0:1 192.168.1.1 up
> >
> > nmap -sn 192.168.1.1/24 
> >
> > Starting Nmap 6.47 ( http://nmap.org ) at 2017-02-12 00:54 MST
> > Nmap scan report for 192.168.1.100
> > Host is up (0.00015s latency).
> > MAC Address: 00:09:45:41:73:D1 (Palmmicro Communications)
> > Nmap scan report for 192.168.1.1
> > Host is up.
> > Nmap done: 256 IP addresses (2 hosts up) scanned in 3.78 seconds
> >
> > The device is showing up but I can not ping it, 100% packet loss.
> 
> ifconfig is showing:
> 
> net0:1: flags=4163  mtu 1500
> inet 192.168.1.1  netmask 255.255.255.0  broadcast 192.168.1.255
> ether 00:1b:21:b8:27:b6  txqueuelen 1000  (Ethernet)
> device interrupt 16  memory 0xfddc-fdde
> 
> 
> Are both 192.168.1 devices on the same layer 2 segment (if not it wont
> work).
> 
> arp -a will show if the IP address was resolvable to a MAC address, If
> it says  you have a layer two problem.

Thank you all for your input.

The device is a tiny PA168V phone gateway. I was able to connect to via
browser interface but it had a password set in (which I don't have it
anymore). So I decided to reset to factory default and its factory
default IP is 192.168.1.100

The device has a WAN and LAN line.

When I reset it according to their instructions I on line line get and
IP as 192.168.1.100
but there are no ports open.

nmap -A -T4 -Pn -vvv 192.168.1.100

Starting Nmap 6.47 ( http://nmap.org ) at 2017-02-12 10:46 MST
NSE: Loaded 118 scripts for scanning.
NSE: Script Pre-scanning.
NSE: Starting runlevel 1 (of 2) scan.
NSE: Starting runlevel 2 (of 2) scan.
Initiating ARP Ping Scan at 10:46
Scanning 192.168.1.100 [1 port]
Completed ARP Ping Scan at 10:46, 0.21s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 10:46
Completed Parallel DNS resolution of 1 host. at 10:46, 0.00s elapsed
DNS resolution of 1 IPs took 0.00s. Mode: Async [#: 1, OK: 0, NX: 1, DR:
0, SF: 0, TR: 1, CN: 0]
Initiating SYN Stealth Scan at 10:46
Scanning 192.168.1.100 [1000 ports]
Completed SYN Stealth Scan at 10:47, 21.07s elapsed (1000 total ports)
Initiating Service scan at 10:47
Initiating OS detection (try #1) against 192.168.1.100
Retrying OS detection (try #2) against 192.168.1.100
NSE: Script scanning 192.168.1.100.
NSE: Starting runlevel 1 (of 2) scan.
Initiating NSE at 10:47
Completed NSE at 10:47, 0.00s elapsed
NSE: Starting runlevel 2 (of 2) scan.
Nmap scan report for 192.168.1.100
Host is up (0.00012s latency).
All 1000 scanned ports on 192.168.1.100 are filtered
MAC Address: 00:09:45:41:73:D1 (Palmmicro Communications)
Too many fingerprints match this host to give specific OS details
TCP/IP fingerprint:
SCAN(V=6.47%E=4%D=2/12%OT=%CT=%CU=%PV=Y%DS=1%DC=D%G=N%M=000945%TM=58A09F9F%P=x86_64-pc-linux-gnu)
U1(R=N)
IE(R=N)

Network Distance: 1 hop

TRACEROUTE
HOP RTT ADDRESS
1 0.12 ms 192.168.1.100

NSE: Script Post-scanning.
NSE: Starting runlevel 1 (of 2) scan.
NSE: Starting runlevel 2 (of 2) scan.
Read data files from: /usr/bin/../share/nmap
OS and Service detection performed. Please report any incorrect results
at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 24.38 seconds

---
arp -a

? (192.168.0.100) at  on net0
DD-WRT (10.0.0.1) at 90:e6:ba:2e:ec:5c [ether] on net0
? (192.168.1.100) at 00:09:45:41:73:d1 [ether] on net0
? (192.168.1.1) at  on net0
? (10.0.0.135) at 38:d5:47:7e:61:52 [ether] on net0
VOIP_TA1S1O (10.0.0.131) at 00:09:45:41:73:d1 [ether] on net0
SipuraSPA (10.0.0.118) at 00:0e:08:ca:17:b3 [ether] on net0
-

When I boot and try WAN port the device gets two local IP from DHCP, and
I see two ports open on IP: 10.0.0.131 (WAN)

23/tcp open  telnet?
80/tcp open  http

But I need to ask the manufacture what is the password, the default
suppose be be: 1234
Maybe I didn't reset it completely

--
Thelma

Re: [gentoo-user] Access device on 192.168.1.1 network

[Mick]

On Sunday 12 Feb 2017 10:59:38 the...@sys-concept.com wrote:
> On 02/12/2017 04:26 AM, Adam Carter wrote:
> > On Sun, Feb 12, 2017 at 7:07 PM,  > 
> > > wrote:
> > On 02/12/2017 01:01 AM, the...@sys-concept.com
> > 
> >  wrote:
> > > My local network is 10.0.0.1 -
> > > 
> > > I have an external device that is pre-set from factory to
> > > 192.168.1.100 and I need to access to it via browser to change its
> > > network setting. So I do:
> > > ifconfig net0:1 192.168.1.1 up
> > > 
> > > nmap -sn 192.168.1.1/24 
> > > 
> > > Starting Nmap 6.47 ( http://nmap.org ) at 2017-02-12 00:54 MST
> > > Nmap scan report for 192.168.1.100
> > > Host is up (0.00015s latency).
> > > MAC Address: 00:09:45:41:73:D1 (Palmmicro Communications)
> > > Nmap scan report for 192.168.1.1
> > > Host is up.
> > > Nmap done: 256 IP addresses (2 hosts up) scanned in 3.78 seconds
> > > 
> > > The device is showing up but I can not ping it, 100% packet loss.
> > 
> > ifconfig is showing:
> > 
> > net0:1: flags=4163  mtu 1500
> > 
> > inet 192.168.1.1  netmask 255.255.255.0  broadcast
> > 192.168.1.255
> > ether 00:1b:21:b8:27:b6  txqueuelen 1000  (Ethernet)
> > device interrupt 16  memory 0xfddc-fdde
> > 
> > Are both 192.168.1 devices on the same layer 2 segment (if not it wont
> > work).
> > 
> > arp -a will show if the IP address was resolvable to a MAC address, If
> > it says  you have a layer two problem.
> 
> Thank you all for your input.
> 
> The device is a tiny PA168V phone gateway. I was able to connect to via
> browser interface but it had a password set in (which I don't have it
> anymore). So I decided to reset to factory default and its factory
> default IP is 192.168.1.100
> 
> The device has a WAN and LAN line.
> 
> When I reset it according to their instructions I on line line get and
> IP as 192.168.1.100
> but there are no ports open.
> 
> nmap -A -T4 -Pn -vvv 192.168.1.100
> 
> Starting Nmap 6.47 ( http://nmap.org ) at 2017-02-12 10:46 MST
> NSE: Loaded 118 scripts for scanning.
> NSE: Script Pre-scanning.
> NSE: Starting runlevel 1 (of 2) scan.
> NSE: Starting runlevel 2 (of 2) scan.
> Initiating ARP Ping Scan at 10:46
> Scanning 192.168.1.100 [1 port]
> Completed ARP Ping Scan at 10:46, 0.21s elapsed (1 total hosts)
> Initiating Parallel DNS resolution of 1 host. at 10:46
> Completed Parallel DNS resolution of 1 host. at 10:46, 0.00s elapsed
> DNS resolution of 1 IPs took 0.00s. Mode: Async [#: 1, OK: 0, NX: 1, DR:
> 0, SF: 0, TR: 1, CN: 0]
> Initiating SYN Stealth Scan at 10:46
> Scanning 192.168.1.100 [1000 ports]
> Completed SYN Stealth Scan at 10:47, 21.07s elapsed (1000 total ports)
> Initiating Service scan at 10:47
> Initiating OS detection (try #1) against 192.168.1.100
> Retrying OS detection (try #2) against 192.168.1.100
> NSE: Script scanning 192.168.1.100.
> NSE: Starting runlevel 1 (of 2) scan.
> Initiating NSE at 10:47
> Completed NSE at 10:47, 0.00s elapsed
> NSE: Starting runlevel 2 (of 2) scan.
> Nmap scan report for 192.168.1.100
> Host is up (0.00012s latency).
> All 1000 scanned ports on 192.168.1.100 are filtered

It's running a firewall and/or there are no ports open and it does not return 
any packets to confirm so.


> MAC Address: 00:09:45:41:73:D1 (Palmmicro Communications)
> Too many fingerprints match this host to give specific OS details
> TCP/IP fingerprint:
> SCAN(V=6.47%E=4%D=2/12%OT=%CT=%CU=%PV=Y%DS=1%DC=D%G=N%M=000945%TM=58A09F9F%P
> =x86_64-pc-linux-gnu) U1(R=N)
> IE(R=N)
> 
> Network Distance: 1 hop
> 
> TRACEROUTE
> HOP RTT ADDRESS
> 1 0.12 ms 192.168.1.100
> 
> NSE: Script Post-scanning.
> NSE: Starting runlevel 1 (of 2) scan.
> NSE: Starting runlevel 2 (of 2) scan.
> Read data files from: /usr/bin/../share/nmap
> OS and Service detection performed. Please report any incorrect results
> at http://nmap.org/submit/ .
> Nmap done: 1 IP address (1 host up) scanned in 24.38 seconds
> 
> ---
> arp -a
> 
> ? (192.168.0.100) at  on net0
> DD-WRT (10.0.0.1) at 90:e6:ba:2e:ec:5c [ether] on net0
> ? (192.168.1.100) at 00:09:45:41:73:d1 [ether] on net0
> ? (192.168.1.1) at  on net0
> ? (10.0.0.135) at 38:d5:47:7e:61:52 [ether] on net0
> VOIP_TA1S1O (10.0.0.131) at 00:09:45:41:73:d1 [ether] on net0
> SipuraSPA (10.0.0.118) at 00:0e:08:ca:17:b3 [ether] on net0
> -
> 
> When I boot and try WAN port the device gets two local IP from DHCP, and
> I see two ports open on IP: 10.0.0.131 (WAN)
> 
> 23/tcp open  telnet?
> 80/tcp open  http
> 
> But I need to ask the manufacture what is the password, the default
> suppose be be: 1234
> Maybe I didn't reset it completely
> 
> --
> Thelma


Assuming you have the basics right (IP address, login username and passwd) you 
can try to flash the device with the latest firmware before you try to

Re: [gentoo-user] [OT] KDE config problem

[Frank Steinmetzger]

On Sat, Feb 11, 2017 at 10:21:36AM +, Peter Humphrey wrote:

> > Something which will help is if you clear out as much of your USE flags in
> > make.conf and package.use as you can, before you run emerge -e.

> You may have it there. Goodness knows how long they'd been there, being 
> copied from one system to another, but I had pch, vaapi and vdpau in USE. I 
> don't know how much difference pch makes in practice, but I'm running emerge 
> -e world without those three. I'll let you know. This is USE now:

My standard recommendation for a use flag “manager” – ufed – helps in this
regard: it shows the description of flags in its flag table. And since
obsolete flags have no description, they are easily spotted.

-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me with any social network.

- “What impressed you most about the LilyPond code base?” - “No comment.”
- “But I really want to know!” - “I just told you!”
– David Kastrup, Lilypond mailing list


signature.asc
Description: Digital signature

Re: [gentoo-user] Access device on 192.168.1.1 network

[Adam Carter]

>
> ---
> arp -a
>
> ? (192.168.0.100) at  on net0
> DD-WRT (10.0.0.1) at 90:e6:ba:2e:ec:5c [ether] on net0
> ? (192.168.1.100) at 00:09:45:41:73:d1 [ether] on net0
>

This shows that the IP is correct and communication may be possible.


> When I boot and try WAN port the device gets two local IP from DHCP, and
> I see two ports open on IP: 10.0.0.131 (WAN)
>
> 23/tcp open  telnet?
> 80/tcp open  http
>
> But I need to ask the manufacture what is the password, the default
> suppose be be: 1234
> Maybe I didn't reset it completely
>
>
Ok, so you tried telnet and web to 10.0.0.131 both of which connected, but
using the default username and password failed, right? If so, that does
sound like it hasnt been reset.

[gentoo-user] WARNING: Crucial MX300 drives SUUUUUCK!!!!

[Alan Grimes]

Dear god, I think I have come in contact with one of the suckiest things
in the universe!

I mean first there are supermassive black holes... OK... Then there's
Crucial MX300 SSDs, and in a distant third there's Justin Beiber.

I mean the absolute suckyness of MX300 SSDs defy human comprehension. I
mean you could connect one of these:
http://www.zmescience.com/science/biggest-most-poweful-engine-world/ to
a suction pump and it couldn't possibly suck one quintillionth as much
as this SSD...

I mean if the power goes out, and you want to do some vacuuming, just
put your MX300 behind the bag in your vacuum and it'll work better than
normal.

Seriously, what could possibly suck harder than a SSD which dies stone
cold dead after only 20 days?!?!?! Thank god I had done nothing worse
than store my rusty old Velociraptor on a shelf, and by good fortune it
only took about two days to get it updated... I really hadn't intended
to ever use it again. =\

I'm not sure what lesson I should take away from this except that
Crucial does not have any business selling SSDs. =\

I'm not sure where to go from here. My 'raptor is very close to
exceeding it's reliable lifespan, by some standards it already has...
But now the QC of these SSDs has been shown to be outrageously bad. =(

So does anyone have any evidence of a current generation SSD lasting
more than 20 days?

-- 
Strange Game.
The only winning move is not to play. 

Powers are not rights.

Re: [gentoo-user] [OT] KDE config problem

[Peter Humphrey]

On Saturday 11 Feb 2017 10:21:36 I wrote:
> On Friday 10 Feb 2017 10:15:10 Mick wrote:
> > Peter, some years ago I also reverted from testing to stable arch,
> > because I was spending more time fixing breakages than actually using
> > the OS. From what I recall it took more than a month for things to
> > settle.
> I did it the easy way, by building a new system from scratch, so there
> shouldn't be any settling down in this case.
> 
> > Something which will help is if you clear out as much of your USE flags
> > in make.conf and package.use as you can, before you run emerge -e.
> 
> You may have it there. Goodness knows how long they'd been there, being
> copied from one system to another, but I had pch, vaapi and vdpau in USE.
> I don't know how much difference pch makes in practice, but I'm running
> emerge -e world without those three. I'll let you know.

Nope. I had to create a new user for myself - again. Now it works as it 
should.

Supplementary question to the list: pch says in use.desc that it gives 
faster compilation at the expense of disk space and memory. Does that mean 
just during compilation, or does it refer to the resulting object code? 
Compilation space is no problem, but I'd rather the binaries didn't occupy 
too much space.

-- 
Regards
Peter

Re: [gentoo-user] WARNING: Crucial MX300 drives SUUUUUCK!!!!

[Jigme Datse Yli-RAsku]

I have 3 of these class of device (if I recall) 3 Crucial SSDs where I have 
only had issues with the one install of the device, and I'm not really sure 
*why* that might be causing problems, but I suspect that a good part of why it 
"just won't work" is because of the UEFI system on that machine, or something 
installed "inside" the UEFI which makes it confuse the heck out of the machine. 
 I have intended to boot into and install Gentoo on it, to see if doing so is 
"doable" or if I should strip the machine, and hope I can get some useful 
components out of it.  Perhaps the optical drive would work well, on this 
machine, though I don't really have a reason to switch this machine's optical 
drive out right now. 

My suggestion is the drive *should* be under warranty, so get a replacement 
that way, and hit up some other manufacturer if you can afford to.  I have 
heard people say that they have had drives running for 10 years, but I may have 
misheard.

On 2017-02-12 14:40, Alan Grimes wrote:
> Dear god, I think I have come in contact with one of the suckiest things
> in the universe!
>
> I mean first there are supermassive black holes... OK... Then there's
> Crucial MX300 SSDs, and in a distant third there's Justin Beiber.
>
> I mean the absolute suckyness of MX300 SSDs defy human comprehension. I
> mean you could connect one of these:
> http://www.zmescience.com/science/biggest-most-poweful-engine-world/ to
> a suction pump and it couldn't possibly suck one quintillionth as much
> as this SSD...
>
> I mean if the power goes out, and you want to do some vacuuming, just
> put your MX300 behind the bag in your vacuum and it'll work better than
> normal.
>
> Seriously, what could possibly suck harder than a SSD which dies stone
> cold dead after only 20 days?!?!?! Thank god I had done nothing worse
> than store my rusty old Velociraptor on a shelf, and by good fortune it
> only took about two days to get it updated... I really hadn't intended
> to ever use it again. =\
>
> I'm not sure what lesson I should take away from this except that
> Crucial does not have any business selling SSDs. =\
>
> I'm not sure where to go from here. My 'raptor is very close to
> exceeding it's reliable lifespan, by some standards it already has...
> But now the QC of these SSDs has been shown to be outrageously bad. =(
>
> So does anyone have any evidence of a current generation SSD lasting
> more than 20 days?
>

-- 
Jigme Datse Yli-Rasku
jigme.da...@datsemultimedia.com (Preferred address for new messages)
250-505-6117

Jigme Datse Yli-Rasku
PO Box 270
Rossland, BC V0G 1Y0
Canada

...
... This message should be electronically signed, and if the sender ...
... has your public key, may also be encrypted. ...
... If you have any questions about this, please email, or call. ...
... ...
... Note, unknown calls likely will go to voicemail. ...
... Please leave a message if you get voicemail. ...
...

Re: [gentoo-user] [OT] KDE config problem

[Peter Humphrey]

On Sunday 12 Feb 2017 23:08:41 Frank Steinmetzger wrote:
> On Sat, Feb 11, 2017 at 10:21:36AM +, Peter Humphrey wrote:
> > > Something which will help is if you clear out as much of your USE
> > > flags in make.conf and package.use as you can, before you run emerge
> > > -e.
> > 
> > You may have it there. Goodness knows how long they'd been there, being
> > copied from one system to another, but I had pch, vaapi and vdpau in
> > USE. I don't know how much difference pch makes in practice, but I'm
> > running emerge
> > -e world without those three. I'll let you know. This is USE now:
> My standard recommendation for a use flag “manager” – ufed – helps in this
> regard: it shows the description of flags in its flag table. And since
> obsolete flags have no description, they are easily spotted.

Thanks Frank, but I just have a mini-script

$ cat /usr/local/bin/gu
#!/bin/bash
grep -s --color=auto $1 $2 /usr/portage/profiles/use*

The extra parameter is so's I can add a -w to grep.

-- 
Regards
Peter

Re: [gentoo-user] logrotate ... won't!

[Peter Humphrey]

On Sunday 12 Feb 2017 17:32:30 Mick wrote:

> Thanks Alexander, it pays going back to basics ... for some reason my
> cronie service was not running.  o_O
> 
> I added it to default runlevel and hopefully it will do its magic from now
> on.

I'm glad I'm not the only one prone to this kind of thing. :(

-- 
Regards
Peter

Re: [gentoo-user] WARNING: Crucial MX300 drives SUUUUUCK!!!!

[Mick]

On Sunday 12 Feb 2017 17:40:35 Alan Grimes wrote:
> Dear god, I think I have come in contact with one of the suckiest things
> in the universe!
> 
> I mean first there are supermassive black holes... OK... Then there's
> Crucial MX300 SSDs, and in a distant third there's Justin Beiber.
> 
> I mean the absolute suckyness of MX300 SSDs defy human comprehension. I
> mean you could connect one of these:
> http://www.zmescience.com/science/biggest-most-poweful-engine-world/ to
> a suction pump and it couldn't possibly suck one quintillionth as much
> as this SSD...
> 
> I mean if the power goes out, and you want to do some vacuuming, just
> put your MX300 behind the bag in your vacuum and it'll work better than
> normal.
> 
> Seriously, what could possibly suck harder than a SSD which dies stone
> cold dead after only 20 days?!?!?! Thank god I had done nothing worse
> than store my rusty old Velociraptor on a shelf, and by good fortune it
> only took about two days to get it updated... I really hadn't intended
> to ever use it again. =\
> 
> I'm not sure what lesson I should take away from this except that
> Crucial does not have any business selling SSDs. =\
> 
> I'm not sure where to go from here. My 'raptor is very close to
> exceeding it's reliable lifespan, by some standards it already has...
> But now the QC of these SSDs has been shown to be outrageously bad. =(
> 
> So does anyone have any evidence of a current generation SSD lasting
> more than 20 days?

LOL!

I did laugh reading this, thanks!

I have no experience with SSDs badged by Crucial.  I have been using a 240GB 
OCZ-ARC100 on a daily basis for more than two years now, and it is still 
working.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] WARNING: Crucial MX300 drives SUUUUUCK!!!!

[Poison BL.]

On Sun, Feb 12, 2017 at 5:40 PM, Alan Grimes  wrote:

> Dear god, I think I have come in contact with one of the suckiest things
> in the universe!
>
> I mean first there are supermassive black holes... OK... Then there's
> Crucial MX300 SSDs, and in a distant third there's Justin Beiber.
>
> I mean the absolute suckyness of MX300 SSDs defy human comprehension. I
> mean you could connect one of these:
> http://www.zmescience.com/science/biggest-most-poweful-engine-world/ to
> a suction pump and it couldn't possibly suck one quintillionth as much
> as this SSD...
>
> I mean if the power goes out, and you want to do some vacuuming, just
> put your MX300 behind the bag in your vacuum and it'll work better than
> normal.
>
> Seriously, what could possibly suck harder than a SSD which dies stone
> cold dead after only 20 days?!?!?! Thank god I had done nothing worse
> than store my rusty old Velociraptor on a shelf, and by good fortune it
> only took about two days to get it updated... I really hadn't intended
> to ever use it again. =\
>
> I'm not sure what lesson I should take away from this except that
> Crucial does not have any business selling SSDs. =\
>
> I'm not sure where to go from here. My 'raptor is very close to
> exceeding it's reliable lifespan, by some standards it already has...
> But now the QC of these SSDs has been shown to be outrageously bad. =(
>
> So does anyone have any evidence of a current generation SSD lasting
> more than 20 days?
>
> --
> Strange Game.
> The only winning move is not to play.
>
> Powers are not rights.
>


I've had all manner of drives fall on the leading edge of the failure rate
'bathtub curve', both SSDs and spinning rust (including hybrid drives), and
many more of each last far past what should typically be the tail end
'spike' that occurs on that curve (including a few of WD's raptor drives of
various vintage). A single drive failure is an anecdote, not an indicator
of a systemic failure of the entire production line (let alone brand),
especially if it lasted 20 days past install... which is well outside
anything a quick, every Nth drive, QA test on the production line is going
to pick up unless they happened to grab that single, specific, drive. As 20
days is also well inside the warranty they give on that drive, a
replacement's not likely to be difficult to get from the manufacturer (and
if you purchased it within the past 30 days, from typical vendors if you
prefer).

I don't *think* I have any of the MX series, but I have had good luck with
the one BX200 I have in my work desktop, and I've heard good things on the
handfull of BX series drives my boss's deployed in various desktops and
laptops. I haven't done any deliberate performance testing on them, but I
can attest to much better speeds out of my BX200 than the spinning 500GB
sitting under it in the same machine.

As for the failure *mode* of your drive, simply, completely, dead... that's
been my experience on every failed SSD I've seen, be it a samsung 850 pro,
an early crucial drive, corsair, and even intels. I suspect either the
controller itself is the point of failure on them, or it's simply incapable
of working around a failure of some other component.

Lastly, while drive failures do, very much, suck... they happen. That's why
backups are essential, and also exactly why raid levels outside of raid0
exist (one is not a replacement for the other, 'course).

-- 
Poison [BLX]
Joshua M. Murphy

Re: [gentoo-user] [OT] KDE config problem

[Neil Bothwick]

On Sun, 12 Feb 2017 22:54:29 +, Peter Humphrey wrote:

> Thanks Frank, but I just have a mini-script
> 
> $ cat /usr/local/bin/gu
> #!/bin/bash
> grep -s --color=auto $1 $2 /usr/portage/profiles/use*
> 
> The extra parameter is so's I can add a -w to grep.

You could use $* instead of $1 $2, or you could emerge euses, which does
a similar thing with some optional extras.


-- 
Neil Bothwick

PC DOS Error #03: Windows not found: (C)heer (P)arty (D)ance


pgp9484jG8hpO.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Bad luck with new installation: Compilation issues (eudev)

[Meino . Cramer]

Miroslav Rovis  [17-02-12 14:03]:
> On 170207-01:11+0100, meino.cra...@gmx.de wrote:
> > Hi Alexander,
> > 
> > it was documente in a bugreport by someone else.
> > I did exactle the same.
> Great, no everybody interested use the search engine, or maybe browse
> all the thousands of bugs if you want to know which bug Meino reported
> it in...
> 
> C'mon, give people the link to that bug that you reported, pls.! Thanks!
> Thanks! Thanks! Thanks!
> 
> -- 
> Miroslav Rovis
> Zagreb, Croatia
> http://www.CroatiaFidelis.hr


>From the first answer in this thread: 

Alexander Openkowski  [17-02-05 18:28]:
> Have you seen this thread in the forums? It looks like your problem:
> 
> https://forums.gentoo.org/viewtopic-t-1057500-view-previous.html?sid=9c8b57325eef824a0748ec4ca94ac8b1
> 
> Found via a quick google search. Keywords: "eudev 3.2.1 error gentoo".
> No offense, really. But you do not need to wait for an answer if you
> search for yourself. :-)
> 

Re: [gentoo-user] logrotate ... won't!

[Dale]

Peter Humphrey wrote:
> On Sunday 12 Feb 2017 17:32:30 Mick wrote:
>
>> Thanks Alexander, it pays going back to basics ... for some reason my
>> cronie service was not running.  o_O
>>
>> I added it to default runlevel and hopefully it will do its magic from now
>> on.
> I'm glad I'm not the only one prone to this kind of thing. :(
>


You're not.  ;-)

Dale

:-)  :-) 

[gentoo-user] Building a new root for my Gentoo: Permission denied?

[Meino . Cramer]

Hi,

got a mysterious error message this morning (still building a new 
root...)

One of the updates was gnutls:
It ends with:
...
checking for i686-pc-linux-gnu-pkg-config... 
/usr/bin/i686-pc-linux-gnu-pkg-config
checking pkg-config is at least version 0.9.0... 
/var/tmp/portage/net-libs/gnutls-3.5.9/work/gnutls-3.5.9/configure: line 5020: 
/usr/bin/i686-pc-linux-gnu-pkg-config: Permission denied
no
checking for i686-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc -m32
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... configure: error: in 
`/var/tmp/portage/net-libs/gnutls-3.5.9/work/gnutls-3.5.9-abi_x86_32.x86':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details
...

I tried:
computer# ldd /usr/bin/i686-pc-linux-gnu-pkg-config
not a dynamic executable
computer# /usr/bin/i686-pc-linux-gnu-pkg-config 
zsh: permission denied: /usr/bin/i686-pc-linux-gnu-pkg-config

computer# file /usr/bin/i686-pc-linux-gnu-pkg-config
/usr/bin/i686-pc-linux-gnu-pkg-config: ELF 32-bit LSB executable, Intel 80386, 
version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for 
GNU/Linux 2.6.32, stripped, with debug_info

I choosed multilib right from the beginning of this adventure ...

How can I check, whether the problem is caysed by gnutls or by the 
system setup (regarding 32bit)?

Cheers
Meino