Re: Regarding language display issues

[Cindy-Sue Causey]

On 10/22/15, Lisi Reisz  wrote:
>
> As you say, get the fonts.
>
> Pointer:
> lisi@Tux-II:~$ aptitude search ttf | grep gujarati
> i A ttf-gujarati-fonts  - transitional dummy package
> lisi@Tux-II:~$ aptitude search ttf | grep hindi
> lisi@Tux-II:~$ aptitude search ttf | grep tamil
> i A ttf-tamil-fonts - Transitional dummy package
> lisi@Tux-II:~$
>
> I haven't explored why no hindi in that ttf list.  urdu isn't there either.


I tried it without the "ttf" and received this:

+++
$ apt-cache search urdu font
fonts-nafees - nafees free OpenType Urdu fonts
fonts-paktype - PakType free OpenType Urdu fonts
+++

Searching on "hindi" by itself brought up a very short list of
packages total. Was an interesting quick read. Searching "hindi font"
landed these:

+++
fonts-deva-extra - Free fonts for Devanagari script
fonts-gargi - OpenType Devanagari font
fonts-lohit-deva - Lohit TrueType font for Devanagari script
fonts-nakula - Free Unicode compliant Devanagari font
fonts-sahadeva - Free Unicode compliant Devanagari font
fonts-samyak-deva - Samyak TrueType font for Devanagari script
fonts-sarai - truetype font for devanagari script
emacs-intl-fonts - fonts to allow multilingual PostScript printing from Emacs
task-hindi - Hindi environment
+++

Oops because "hindi ttf" and "urdu ttf" landed nothing here, either,
yet there's the word "TrueType" a few times for "hindi". An aside to
those who write those descriptions: Don't forget to use **ALL** your
special keywords! It's times like this when they matter. :D

PS "urdu truetype" still landed no package results.

Cindy :)

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

Re: Lost LVM data - lost logical volume

[David Christensen]

On 10/22/2015 02:41 PM, Anton Bizzarri wrote:

Hello, we had lost a drive in a LVM on Debian Squeeze. I pulled the drive
and replaced it and then tried to repair it but then when I tried to
recover the LVM it turned out it was a striped volume. (Its not my server!
Never thought they put the data on a striped volume).

So I returned the original drive and I tried to see if I can recover the
data from LVM metadata.

This is Debian wheezy and lvm2 2.02.95-8

The drive that failed was sdc


...

It is not finding the logical volumes anymore.

I have a file in the archive folder /etc/lvm/archive from the morning
before I ran "vgreduce --removemissing --force data"

Is there any way to restore the metadata? Below is the contents of archive
file.

...

I want to see if its possible to try to recover the data because all the
drives are actually still in the exact same slots.  The failing drive on
/dev/sdc magically started working again when I put it back in the server.


You *do* have a back up of your data, right?

1.  Make another copy of the back up and take it off-site.

2.  Test all of your hardware:

a.  Power supply -- hardware load tester.

b.  Memory -- many hours; 24 is good.

c.  Drives -- use manufacturer diagnostics.  Understand that 
failures can be caused by data cables, power cables, connectors, HBA's, 
RAID cards, MB ports, etc..  Troubleshooting might involve a live Linux 
image and/ or hardware substitution/ process of elimination.


3.  Optional: Wipe the drives.

4.  Build a new array/ file system.  (As an aside, have you considered ZFS?)

5.  Optional: Backup/ archive your array/ file system meta data.

6.  Restore your data.

7.  Verify that you can back up the data.


David

Re: Regarding language display issues

[Lisi Reisz]

On Wednesday 21 October 2015 15:03:57 Himanshu Shekhar wrote:
> I am having trouble viewing webpages and text written in regional
> languages. Possibly, I need the right fonts but have no idea how to get the
> thing implemented.
>
> Details:
> Browser : Chromium, Iceweasel, and Google Chrome Stable
> Languages tried : Indian languages - Hindi, Gujarati, Tamil, etc. as well
> as other foreign languages
> Issue : text gets displayed but with many circles inserted in between.
>
> Need a fix!

As you say, get the fonts.

Pointer:
lisi@Tux-II:~$ aptitude search ttf | grep gujarati
i A ttf-gujarati-fonts  - transitional dummy package
lisi@Tux-II:~$ aptitude search ttf | grep hindi
lisi@Tux-II:~$ aptitude search ttf | grep tamil
i A ttf-tamil-fonts - Transitional dummy package
lisi@Tux-II:~$   

I haven't explored why no hindi in that ttf list.  urdu isn't there either. 

Lisi 

Re: Thread dorked. (was: Re: System Dorked -- Help!)

[Lisi Reisz]

On Wednesday 21 October 2015 18:39:45 d_ba...@012.net.il wrote:
> Please confirm this is plain text :-)

:-)

I can read it now.

Your OP was totally incomprehensible here too.  KMail-Trinity.  Combined with 
partial sight.

Lisi

Re: Whitelist security.debian.org

[Pascal Hambourg]

Brian a écrit :
> On Thu 22 Oct 2015 at 20:51:03 +0200, Pascal Hambourg wrote:
> 
>> Brian a écrit :
>>>
>>>   deb ftp://149.20.20.6/debian-security jessie/updates main
> 
>> - It does not work with HTTP, so you have to use FTP which is harder to
>> manage by firewalls.
> 
> I could not get http to work; don't know why. Any ideas?

HTTP virtual host setup, I guess. /dists, /pool or /debian-security seem
to only exist in the security.debian.org virtual host on these servers.

Lost LVM data - lost logical volume

[Anton Bizzarri]

Hello, we had lost a drive in a LVM on Debian Squeeze. I pulled the drive
and replaced it and then tried to repair it but then when I tried to
recover the LVM it turned out it was a striped volume. (Its not my server!
Never thought they put the data on a striped volume).

So I returned the original drive and I tried to see if I can recover the
data from LVM metadata.

This is Debian wheezy and lvm2 2.02.95-8

The drive that failed was sdc

Below is my logs.

/# pvscan -v
Wiping cache of LVM-capable devices
Wiping internal VG cache
Walking through all physical volumes
  PV /dev/sdb   VG data   lvm2 [465.76 GiB / 465.76 GiB free]
  PV /dev/sdd   VG data   lvm2 [465.76 GiB / 465.76 GiB free]
  PV /dev/sde   VG data   lvm2 [465.76 GiB / 465.76 GiB free]
  PV /dev/sdf   VG data   lvm2 [465.76 GiB / 465.76 GiB free]
  PV /dev/sdc   VG data   lvm2 [465.76 GiB / 465.76 GiB free]
  Total: 5 [2.27 TiB] / in use: 5 [2.27 TiB] / in no VG: 0 [0   ]


:/# vgscan -v
Wiping cache of LVM-capable devices
Wiping internal VG cache
  Reading all physical volumes.  This may take a while...
Finding all volume groups
Finding volume group "data"
  Found volume group "data" using metadata type lvm2


/# lvscan -v
Finding all logical volumes

It is not finding the logical volumes anymore.

I have a file in the archive folder /etc/lvm/archive from the morning
before I ran "vgreduce --removemissing --force data"

Is there any way to restore the metadata? Below is the contents of archive
file.

# Generated by LVM2 version 2.02.95(2) (2012-03-06): Thu Oct 22 09:44:12
2015

contents = "Text Format Volume Group"
version = 1

description = "Created *before* executing 'vgreduce --removemissing --force
data'"

creation_host = "" # Linux  3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u5
x86_64
creation_time = 1445521452  # Thu Oct 22 09:44:12 2015

data {
id = "0UcXlh-1lXG-udrp-T6QJ-fqMt-G5mz-mgpLmN"
seqno = 6
format = "lvm2" # informational
status = ["RESIZEABLE", "READ", "WRITE"]
flags = []
extent_size = 8192  # 4 Megabytes
max_lv = 0
max_pv = 0
metadata_copies = 0

physical_volumes {

pv0 {
id = "mKQGfL-Fs0C-bRIv-rcKT-jbWs-7olM-R2VCCw"
device = "/dev/sdb" # Hint only

status = ["ALLOCATABLE"]
flags = []
dev_size = 976773168# 465.762 Gigabytes
pe_start = 384
pe_count = 119234   # 465.758 Gigabytes
}

pv1 {
id = "KLL51K-SwV9-6VU6-9ulL-DOJy-L9uJ-T5k43a"
device = "unknown device"   # Hint only

status = ["ALLOCATABLE"]
flags = ["MISSING"]
dev_size = 976773168# 465.762 Gigabytes
pe_start = 384
pe_count = 119234   # 465.758 Gigabytes
}

pv2 {
id = "98S7nn-R4sG-OMBc-HR9Y-kHPM-Du8q-ZBNJ3c"
device = "/dev/sdd" # Hint only
dev_size = 976773168# 465.762 Gigabytes
pe_start = 384
pe_count = 119234   # 465.758 Gigabytes
}

pv3 {
id = "d1CHzd-91uQ-7c0X-XA02-0Tlh-bBtv-rusTsj"
device = "/dev/sde" # Hint only

status = ["ALLOCATABLE"]
flags = []
dev_size = 976773168# 465.762 Gigabytes
pe_start = 384
pe_count = 119234   # 465.758 Gigabytes
}

pv4 {
id = "vK0cGK-zz71-rpGC-IcP3-gsKU-EHjx-fY70SB"
device = "/dev/sdf" # Hint only

status = ["ALLOCATABLE"]
flags = []
dev_size = 976773168# 465.762 Gigabytes
pe_start = 384
pe_count = 119234   # 465.758 Gigabytes
}
}

logical_volumes {

home {
id = "DM6HzG-mgeC-Hj4M-MyKk-k8UT-ZjHU-t74qTe"
status = ["READ", "WRITE", "VISIBLE"]
flags = []
segment_count = 5

segment1 {
start_extent = 0
extent_count = 119234   # 465.758 Gigabytes

type = "striped"
stripe_count = 1# linear

stripes = [
"pv0", 0
]
}
  

Re: Reporting Bug

[Piyavkin]

On 22.10.2015 17:03, Brian wrote:

On Thu 22 Oct 2015 at 16:15:27 +0300, Piyavkin wrote:


On 22.10.2015 10:18, Ondřej Grover wrote:

Hello Adrian,

could you please be more specific about a few points?
- what installer ISO did you use
- did you use the text or graphical installer
- what was the error message or what failed or happened exactly that
stopped the installation

I wasn't able to reproduce your problem in VirtualBox using the network
installation ISO 
http://cdimage.debian.org/debian-cd/8.2.0/i386/iso-cd/debian-8.2.0-i386-netinst.iso
and with almost all the default choices with the excpetion of these
prompts
- Full name of new user: "Adrian O'Dell"
- user name: "adrian"

I understand that you may not feel like reading a large page of text if
you are in a hurry or feel you may not understand it. However, the Debian
and other open-source projects keep living thanks to individuals like you
that go the extra mile, devote some time to the cause and are willing to
learn new things. Please consider supporting Debian (and through it all
other projects based on it, including Linux Mint) through your extra
effort in filing bug reports when needed.

Kind regards,
Ondřej Grover

On Thu, Oct 22, 2015 at 8:15 AM, Adrian O'Dell mailto:crimsonm...@gmail.com>> wrote:

There appears to be a bug which has Plagued me for years. Oddly I
don't have the bug in Linux Mint. Did they edit this part of the
installer?

My name contains an apostrophe, which causes the Debian installer
to not create my user account. Long time ago when I tried to seek
help via IRC was told I must have done something wrong. Two days
ago I confirmed through multiple installs that the apostrophe is
the culprit.

This is the only attempt I will make at filing a bug report.
Anyone more familiar with filing a bug report, it would be greatly
appreciated if you would make sure it gets filed properly so it
may be resolved. https://www.debian.org/Bugs/Reporting is an ugly
wall of text which immediately discouraged me from wanting to file
a bug report anymore.

Thanks.

I agree with the topic starter: the Debian's bug reporting process is
horrible and not userfriendly from user's viewpoint. If an organization
cares about usability and effectiveness of bug reporting process, it
shouldn't be like that.

If a user cares about the usability and effectiveness of the bug
reporting process, more detail to back up the complaint would be
welcome.

.

«more details» — that's exactly a good point for a good bug reporting 
system (or similar one).

But before that, in the first place, there should be: «less details».

*Problem*

The purpose of a bug reporting system is to gather from end users and 
nodes all relevant information on issues with the real product behaviour 
to be aware of current situation (what will you do with the information 
then — is another question).
It's better if the process is completely automated (invisible for 
users). If it is not, it should be as simple for user as possible, so as 
many involved users as possible could complete it.


The problem with the Debian bug reporting process is that it is not so 
simple for ordinary user. And if you do it first time or rarely you 
should first investigate how to do it, manually (and unnecessarily) 
gather bits of information from different sources to finish the quest 
and just to send report. It involves a good deal of searching, reading, 
studying and tweaking settings, even if it is simplest case. For 
ordinary user it seems very annoying and frustrating. And even if the 
user's willing to report to help developers, he/she probably gives up 
and remains silent. And in result the information in the bug reporting 
system reflects only the part of the real picture: only the reports from 
users who were skilled or stubborn enough to break through the reporting 
process (and it is skewed bit of picture too, because the machines of 
the skilled users maintained better and differently than machines of 
ordinary/average users).


*Example (case)*

I've got some critical issue with kernel updates which prevented me from 
starting my system.

So the only options I had to work through other PC or to start from LiveCD.

First of all, what should I do to report the issue? I've searched and 
found the mentioned above page https://www.debian.org/Bugs/Reporting 
with instructions.
I was even not sure if I should address my report to the list. And I 
first asked here at debian-user. The participants here suggested that I 
probably should report bug.


I've returned to the web-page. And had to plough through the wall of 
text on the page and its links, to understand what's significant here 
and what's not, and what exactly should I do. I couldn't use the 
«strongly recommended» reportbug program in the situation.


And even if I could, there was no difference. Using hints from 
net-search I've played with boot-up parameters and somehow managed to 
star

Re: Whitelist security.debian.org

[Brian]

On Thu 22 Oct 2015 at 20:51:03 +0200, Pascal Hambourg wrote:

> Brian a écrit :
> > On Thu 22 Oct 2015 at 11:44:41 +0200, Sven Hartge wrote:
> > 
> >> Pascal Hambourg  wrote:
> >>> Greencopper a écrit :
> >>  
>  Most likely OpenDNS has some load balancing of their own perhaps
>  forwarding the request to different internal servers.
> 
>  Perhaps the only solution is to fix a specific IP address for
>  security.debian.org in my local DNS server and then only use that!
> >>>
> >>> Or don't use OpenDNS servers.
> >>
> >> Or don't try to build firewall rules based on DNS lookups.
> > 
> > Or amend sources.list to not require DNS. 149.20.20.6 is schein; use
> > villa if preferred.
> > 
> >   deb ftp://149.20.20.6/debian-security jessie/updates main
> 
> I don't second that suggestion because it has several drawbacks.
> - It cancels the redundancy provided by security.debian.org.

True. It pins down getting security updates fron a designated IP.

> - It does not work with HTTP, so you have to use FTP which is harder to
> manage by firewalls.

I could not get http to work; don't know why. Any ideas?

> - If one day this one address does not serve as a Debian security mirror
> any more, you're stuck.

Correct. So, use

   deb ftp://schein.debian.org/debian-security jessie/updates main
   deb ftp://villa.debian.org/debian-security jessie/updates main

Untested, so your objection could still stand.

> - Changing a mirror forces APT to reload all the package list at the
> next update. This can be annoying with a low speed link.

Probably not relevant for the OP. But a reasonable point.
 
> I was serious when suggesting not tu use OpenDNS. Why use it if you have
> your own local recursive DNS cache ?

You could be right, I'll not argue that at length. unbound returns

; <<>> DiG 9.9.5-12-Debian <<>> security.debian.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23557
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 3, AUTHORITY: 3, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;security.debian.org.   IN  A

  ;; ANSWER SECTION:
  security.debian.org.300 IN  A   195.20.242.89
  security.debian.org.300 IN  A   212.211.132.250
  security.debian.org.300 IN  A   212.211.132.32

  ;; AUTHORITY SECTION:
  security.debian.org.28800   IN  NS  geo1.debian.org.
  security.debian.org.28800   IN  NS  geo3.debian.org.
  security.debian.org.28800   IN  NS  geo2.debian.org.

  ;; Query time: 430 msec
  ;; SERVER: 127.0.0.1#53(127.0.0.1)
  ;; WHEN: Thu Oct 22 20:26:22 BST 2015
  ;; MSG SIZE  rcvd: 153

Traceroutes to the machines in the ANSWER SECTION lead today to wieck.
villa and lobos respectively.

I'm also not inclined to second the suggestion but, failing sorting out
his firewall, it can work for the OP.

Re: Debian 8.2 RAID conf. problem

[Pascal Hambourg]

Cindy-Sue Causey a écrit :
> 
> Was only a couple months ago that I found out that update-grub was at
> least one thing about the boot flag that *appeared* to matter, at
> least *IN MY CASE* *that day*. After a very long afternoon of not
> understanding why GRUB kept reverting to its old config setup, I
> accidentally discovered that changing that boot flag from one
> partition to another one created instant success on the next
> update-grub run I did.

You obviously misinterpreted what happened. GRUB as a whole ignores the
boot flag. My guess is there was a different GRUB on each partition, and
update-grub applied to the inactive one, so changing the boot flag just
changed which GRUB was booted.

> Many months ago there was a thread about
> longevity of hard drives related to how many boots in their lifetimes.

Nonsense. If the boot count mattered for hard disk longevity, there
would be a SMART attribute for it. There is none.

Re: Reporting Bug

[Adrian O'Dell]

I'm well versed in bash. It just never occurred to me to escape the 
apostrophe in the real name field since it is supposed to be a string 
variable.


Mint treats my input correctly, creating my user account as it should. 
Debian does not.


I'll try escaping the apostrophe one of these days, but that's hardly 
the issue. The issue is the installer should sanitize user input.


Thanks for the reply. Did you by chance create a bug report for this?


On 10/22/2015 02:16 AM, Jude DaShiell wrote:
Normally I would put a backslash character in front of that apostrophe 
since it's a special character to bash at least and I suspect several 
other shell envioonments.  Perhaps try O\'Dell by way of an example.  
I suspect mint hasn't been modified at all and that you haven't 
interacted so far with the shell environment in mint which may be why 
you haven't found this error in that distro yet.


On Thu, 22 Oct 2015, Adrian O'Dell wrote:


Date: Thu, 22 Oct 2015 02:15:10
From: Adrian O'Dell 
To: debian-user@lists.debian.org
Subject: Reporting Bug
Resent-Date: Thu, 22 Oct 2015 06:33:12 + (UTC)
Resent-From: debian-user@lists.debian.org

There appears to be a bug which has Plagued me for years. Oddly I 
don't have the bug in Linux Mint. Did they edit this part of the 
installer?


My name contains an apostrophe, which causes the Debian installer to 
not create my user account. Long time ago when I tried to seek help 
via IRC was told I must have done something wrong. Two days ago I 
confirmed through multiple installs that the apostrophe is the culprit.


This is the only attempt I will make at filing a bug report. Anyone 
more familiar with filing a bug report, it would be greatly 
appreciated if you would make sure it gets filed properly so it may 
be resolved. https://www.debian.org/Bugs/Reporting is an ugly wall of 
text which immediately discouraged me from wanting to file a bug 
report anymore.


Thanks.

Re: Whitelist security.debian.org

[Pascal Hambourg]

Brian a écrit :
> On Thu 22 Oct 2015 at 11:44:41 +0200, Sven Hartge wrote:
> 
>> Pascal Hambourg  wrote:
>>> Greencopper a écrit :
>>  
 Most likely OpenDNS has some load balancing of their own perhaps
 forwarding the request to different internal servers.

 Perhaps the only solution is to fix a specific IP address for
 security.debian.org in my local DNS server and then only use that!
>>>
>>> Or don't use OpenDNS servers.
>>
>> Or don't try to build firewall rules based on DNS lookups.
> 
> Or amend sources.list to not require DNS. 149.20.20.6 is schein; use
> villa if preferred.
> 
>   deb ftp://149.20.20.6/debian-security jessie/updates main

I don't second that suggestion because it has several drawbacks.
- It cancels the redundancy provided by security.debian.org.
- It does not work with HTTP, so you have to use FTP which is harder to
manage by firewalls.
- If one day this one address does not serve as a Debian security mirror
any more, you're stuck.
- Changing a mirror forces APT to reload all the package list at the
next update. This can be annoying with a low speed link.

I was serious when suggesting not tu use OpenDNS. Why use it if you have
your own local recursive DNS cache ?

Re: Reporting Bug

[Sven Arvidsson]

On Thu, 2015-10-22 at 18:53 +0100, Brian wrote:
> There is no need to use GMail, a mailserver on the machine or an SMTP
> host. The novice operating mode of 'reportbug' has in its prompts:
> 
>Do you have a "mail transport agent" (MTA) like Exim,
>Postfix or SSMTP configured on this computer to send
>mail to the Internet? [y|N|q|?]? n
> 
>Please enter the name of your SMTP host. Usually it's
>called something like "mail.example.org" or "smtp.example.org".
>If you need to use a different port than default, use the
>: alternative format.
> 
>Just press ENTER if you don't have one or don't know, and so
>a Debian SMTP host will be used.
> 
> ~/.reportbugrc will have 'smtp reportbug.debian.org' in the file if
> ENTER is pressed.
> 
> Not exactly a gotcha.

Wow, did not know that, very handy!

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5





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

kde5 programs crash

[Ariel Molinuevo]

Hello,

I'm writing this mail following the instructions of reportbug, since I do
not know which package has the bug.

I use debian sid, and after this series of updates

[UPGRADE] libsidplayfp4:amd64 1.8.1-1 -> 1.8.2-1
[UPGRADE] libsigc++-2.0-0v5:amd64 2.6.1-2 -> 2.6.1-3
[UPGRADE] libsqlite3-0:amd64 3.8.11.1-1 -> 3.9.1-1
[UPGRADE] python-bs4:amd64 4.4.0-1 -> 4.4.1-1
[UPGRADE] python-cffi-backend:amd64 1.2.1-1+b1 -> 1.3.0-1
[UPGRADE] qml-module-qtgraphicaleffects:amd64 5.4.2-2+b1 -> 5.5.1-2
[UPGRADE] qt5-default:amd64 5.4.2+dfsg-9 -> 5.5.1+dfsg-2
[UPGRADE] sqlite3:amd64 3.8.11.1-1 -> 3.9.1-1
[UPGRADE] distro-info-data:amd64 0.27 -> 0.28
[UPGRADE] libqt5clucene5:amd64 5.4.2-3 -> 5.5.1-3
[UPGRADE] libqt5x11extras5:amd64 5.4.2-2+b1 -> 5.5.1-2
[UPGRADE] qttranslations5-l10n:amd64 5.4.2-2 -> 5.5.1-2

Kate and Dolphin do not start. The output running them from a command line
is "Segmentation Fault".

Gwenview and Konsole also crashes. The ouput tells a little bit more:

For gwenview:
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = gwenview path = /usr/bin pid = 4269
KCrash: Arguments: /usr/bin/gwenview
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1000/kdeinit5__0
Warning: connect() failed: : No such file or directory
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
directly

For Konsole:
KCrash: Application Name = konsole path = /usr/bin pid = 4318
KCrash: Arguments: /usr/bin/konsole
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1000/kdeinit5__0
Warning: connect() failed: : No such file or directory
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
directly

This 3 programs are using kde5, so I guess the problem is there. Kile, for
example, is using kde4 and is working fine.

Hope this helps.

Best regards.

Ariel

ps: I attached the log of aptitude with my last two updates.


aptitude_log
Description: Binary data

Re: Reporting Bug

[Brian]

On Thu 22 Oct 2015 at 16:19:49 +0200, Sven Arvidsson wrote:

> On Thu, 2015-10-22 at 01:15 -0500, Adrian O'Dell wrote:
> > There appears to be a bug which has Plagued me for years. Oddly I
> > don't have the bug in Linux Mint. Did they edit this part of the
> > installer?
> > 
> > My name contains an apostrophe, which causes the Debian installer to
> > not create my user account. Long time ago when I tried to seek help
> > via IRC was told I must have done something wrong. Two days ago I
> > confirmed through multiple installs that the apostrophe is the
> > culprit.
> > 
> > This is the only attempt I will make at filing a bug report. Anyone
> > more familiar with filing a bug report, it would be greatly
> > appreciated if you would make sure it gets filed properly so it may
> > be resolved.  https://www.debian.org/Bugs/Reporting is an ugly wall
> > of text which immediately discouraged me from wanting to file a bug
> > report anymore.
> 
> You can pretty much stop right after the first sentence and just use
> reportbug. 

Strongly recommended.
 
> The one gotcha is that reportbug needs either a working mail server
> configuration or an SMTP host. In your case you could use GMail:
> https://wiki.debian.org/reportbug#Using_GMail.27s_SMTP_Server

There is no need to use GMail, a mailserver on the machine or an SMTP
host. The novice operating mode of 'reportbug' has in its prompts:

   Do you have a "mail transport agent" (MTA) like Exim,
   Postfix or SSMTP configured on this computer to send
   mail to the Internet? [y|N|q|?]? n

   Please enter the name of your SMTP host. Usually it's
   called something like "mail.example.org" or "smtp.example.org".
   If you need to use a different port than default, use the
   : alternative format.

   Just press ENTER if you don't have one or don't know, and so
   a Debian SMTP host will be used.

~/.reportbugrc will have 'smtp reportbug.debian.org' in the file if
ENTER is pressed.

Not exactly a gotcha.

Re: Debian 8.2 RAID conf. problem

[Dan Ritter]

On Wed, Oct 21, 2015 at 05:46:55PM +0100, Tony van der Hoff wrote:
> On 21/10/15 17:35, Mario Castelán Castro wrote:
> >El 21/10/15 a las 11:11, erdal daghan escribió:
> >>Hi,
> >>
> >>I have a problem with install debian. When I trying to install the Debian
> >>8.2 with RAID1 configuration it does NOT add bootable flag in guided
> >>partitioning mode. It Doesn't on option.
> >
> >The problem seems to be your perception, not Debian. Why do you think
> >you need that flag?. As far as I know, GRUB ignores it, so it makes no
> >difference regarding booting the system. Also, if you use guided
> >partitioning, you can manually adjust the suggested partitioning scheme
> >before proceeding, so if you really need it, you can easily toggle it.
> >
> >El 21/10/15 a las 11:11, erdal daghan escribió:
> >>Please help me.. I have two ssd disks(240gb). I want to make RAID1
> >>configuration.
> >
> >You probably refer to ordinary solid state drives which are NOT disks.
> >
> 
> This raises a question in my mind: Should SSDs be used in RAID arrays?

As always, it depends on what you want to do.

RAID1 is done as a mechanism to give you a window between disk
failure and the need to replace the disk. Using identical SSDs
might not be a good strategy here, because identical write
patterns might produce identical failures.

I would consider something that keeps the secondary disk less
used than the primary - for instance, rsyncing primary to
secondary every so often. Once a day at minimum, once every 30 
minutes or so max.

On the other hand, a database server might make good use of a
RAID10 of two kinds of similar but not identical disks - a disk 
controller on a PCIe x8 slot can be saturated by 16 SATA3 SSDs
all running full-out.

Or you might want to use SSDs as caches for large spinning
disks. Generically, you can do this with bcache; if you use ZFS,
ZIL and L2ARC are what you are looking for.

-dsr-

Re: Backup solutions without reinventig the wheel these days

[Glenn English]

On Oct 20, 2015, at 10:57 AM, Ondřej Grover  wrote:

> I'm looking for recommendations for backup solutions that don't reinvent the 
> wheel and are reliable and used.

Have you considered Amanda? It's been around for quite a long time, it's worked 
very reliably for me for the past 15 or so years, it'll do an entire net, it's 
free, and apt-get will install it for you. It uses tar or dump (your choice) to 
write the backup, so if you lose the program, you can recover with standard 
*nix utilities.

I don't know what you use for backup media. I use tape, and that's what Amanda 
was originally designed for, but I hear it does disks now as well.

> I want to backup two servers to a backup server. The main data content is 
> several hundred GB in many very small files.

Amanda doesn't require another box; one of the two can do it -- lots of free 
CPU cycles if you're using tape. But it does require a big hunk of disk space 
for a cache. 

-- 
Glenn English

Re: Tracking down memory leaks

[David Wright]

Quoting Marc Shapiro (marcns...@gmail.com):
> On 10/20/2015 11:33 PM, Jörg-Volker Peetz wrote:
> >Marc Shapiro wrote on 10/21/2015 06:52:
> >
> >>Something is not freeing up memory.  It may, or may not be Firefox, but...  
> >>I
> >>can exit all programs and all instances of X, leaving only a single console
> >>running.  Top will show itself and bash, nothing else, but free can show 
> >>over
> >>2GB used.  If I then reboot, free will show only about 250 MB used.  
> >>Obviously
> >>something was tying up nearly 2 GB and it took a reboot to free it up.
> >>
> >>Marc
> >>
> >Which version of free you are using?
> >Where does it show 2 GB?
> >Do the 2 GB comprise buffered and cached data?
> >Please, show the the output of free.
> Don Armstrong had also suggested checking the cache and buffers,
> which I had forgotten to do when I restarted.  I checked them
> yesterday and, yes, that is where most of the memory was going after
> I had exited all X sessions.  Google was my friend and showed me how
> to free up that memory ('free && sync && echo 3 >
> /proc/sys/vm/drop_caches && free' as root) and all is now good with
> the world.
> 
> Thanks, everyone, for the help.  If I had just looked more closely
> at the output of 'free' I could have done this myself.   (Forehead
> slap).

I notice you've flagged this posting with SOLVED. However, I can't
find where you reported a problem. The original posting only says:

"I could run for months without having a memory problem. Now it's every
few days. When this happens,..."

So what was the problem? What happens?

Cheers,
David.

Re: Tracking down memory leaks (SOLVED)

[Nicolas George]

Le primidi 1er brumaire, an CCXXIV, Marc Shapiro a écrit :
> Google was my friend and showed me how to free up that memory ('free && sync
> && echo 3 > /proc/sys/vm/drop_caches && free' as root) and all is now good
> with the world.

I hope you realize this is only useful for debugging purposes.

The memory used by the cache and buffers is already free, or more precisely
immediately available for applications that need it. By flushing the caches,
you just prevent the system from making use of it while nobody else does,
and therefore reduce the performances.

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

Re: Tracking down memory leaks (SOLVED)

[Marc Shapiro]

On 10/20/2015 11:33 PM, Jörg-Volker Peetz wrote:

Marc Shapiro wrote on 10/21/2015 06:52:


Something is not freeing up memory.  It may, or may not be Firefox, but...  I
can exit all programs and all instances of X, leaving only a single console
running.  Top will show itself and bash, nothing else, but free can show over
2GB used.  If I then reboot, free will show only about 250 MB used.  Obviously
something was tying up nearly 2 GB and it took a reboot to free it up.

Marc


Which version of free you are using?
Where does it show 2 GB?
Do the 2 GB comprise buffered and cached data?
Please, show the the output of free.
Don Armstrong had also suggested checking the cache and buffers, which I 
had forgotten to do when I restarted.  I checked them yesterday and, 
yes, that is where most of the memory was going after I had exited all X 
sessions.  Google was my friend and showed me how to free up that memory 
('free && sync && echo 3 > /proc/sys/vm/drop_caches && free' as root) 
and all is now good with the world.


Thanks, everyone, for the help.  If I had just looked more closely at 
the output of 'free' I could have done this myself.   (Forehead slap).


Marc

Re: Debian 8.2 RAID conf. problem

[Cindy-Sue Causey]

On 10/21/15, Mario Castelán Castro  wrote:
> El 21/10/15 a las 11:11, erdal daghan escribió:
>> Hi,
>>
>> I have a problem with install debian. When I trying to install the Debian
>> 8.2 with RAID1 configuration it does NOT add bootable flag in guided
>> partitioning mode. It Doesn't on option.
>
> The problem seems to be your perception, not Debian. Why do you think
> you need that flag?. As far as I know, GRUB ignores it, so it makes no
> difference regarding booting the system. Also, if you use guided
> partitioning, you can manually adjust the suggested partitioning scheme
> before proceeding, so if you really need it, you can easily toggle it.


Because it's there as an option in Gparted, I consciously, *manually*
apply the boot flag to a favored partition as soon as I've completed
the initial partition reconfiguring on a hard drive. SO FAR the
only place I've ever seen the boot flag matter was with respect to
rerunning GRUB after a newly (debootstrap) installed distro. It's
actually one of those topics I'd experienced and thought about
starting a thread on soon after in case others had feedback for
newcomers.

Was only a couple months ago that I found out that update-grub was at
least one thing about the boot flag that *appeared* to matter, at
least *IN MY CASE* *that day*. After a very long afternoon of not
understanding why GRUB kept reverting to its old config setup, I
accidentally discovered that changing that boot flag from one
partition to another one created instant success on the next
update-grub run I did.

Prior to stumbling on that factor, I'd gone so far as to take the
chance of purging and then reinstalling GRUB hoping it would somehow
cleanse the system (not to mention hoping the hard drive didn't
suddenly fritz in those few seconds it was GRUB-less). What I had set
up then actually let me reinstall GRUB into.. is it MBR (?) which I
had *thought MIGHT* be the problem at that time. And still update-grub
failed. Wasn't until I changed that boot flag that there was
success immediate success for whatever reason known to the
software... :)

Outside of that, nothing I've ever done to date has openly been
reflected as being somehow dependent on that flag. For the record, I
*do* make that change on purpose just because I did waste a LOT of
time that afternoon. Many months ago there was a thread about
longevity of hard drives related to how many boots in their lifetimes.
THAT THREAD came to mind THAT AFTERNOON I ate a few boots off my
hard drive's lifetime supply that day. *grin*

Cindy :)

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

Re: Reporting Bug

[Sven Arvidsson]

On Thu, 2015-10-22 at 01:15 -0500, Adrian O'Dell wrote:
> There appears to be a bug which has Plagued me for years. Oddly I
> don't 
> have the bug in Linux Mint. Did they edit this part of the installer?
> 
> My name contains an apostrophe, which causes the Debian installer to
> not 
> create my user account. Long time ago when I tried to seek help via
> IRC 
> was told I must have done something wrong. Two days ago I confirmed 
> through multiple installs that the apostrophe is the culprit.
> 
> This is the only attempt I will make at filing a bug report. Anyone
> more 
> familiar with filing a bug report, it would be greatly appreciated if
> you would make sure it gets filed properly so it may be resolved. 
> https://www.debian.org/Bugs/Reporting is an ugly wall of text which 
> immediately discouraged me from wanting to file a bug report anymore.

You can pretty much stop right after the first sentence and just use
reportbug. 

The one gotcha is that reportbug needs either a working mail server
configuration or an SMTP host. In your case you could use GMail:
https://wiki.debian.org/reportbug#Using_GMail.27s_SMTP_Server

Figuring out which package to file the bug against is another problem,
but I'm sure the list can help out there too. 

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5





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

Re: Backup solutions without reinventig the wheel these days

[Sarunas Burdulis]

On 10/22/2015 02:47 AM, Ondřej Grover wrote:
> Thank you Sarunas for the graphs, it is most illuminating. That's pretty
> much how I imagine a storage server should behave.
> Atomic snapshots are very appealing indeed. In my case cp -lr or
> --link-dest solutions would take a long time as the FS hierarchy is both
> very broad and deep.

Ondřej, you're are welcome. “For the sake of science” I restarted the
backups' server yesterday with a kernel boot parameter mem=1G. All the
nightly rsync jobs and btrfs snapshot manipulations went as usual, and
the server is running fine:

https://math.dartmouth.edu/owncloud/index.php/s/fYO81CfmuV5yrpZ

So 1G RAM might still do just fine for such basic tasks.

-- 
Sarunas Burdulis
Systems Administrator
Department of Mathematics, Dartmouth College
http://math.dartmouth.edu/~sarunas

Re: Reporting Bug

[Brian]

On Thu 22 Oct 2015 at 16:15:27 +0300, Piyavkin wrote:

> On 22.10.2015 10:18, Ondřej Grover wrote:
> >Hello Adrian,
> >
> >could you please be more specific about a few points?
> >- what installer ISO did you use
> >- did you use the text or graphical installer
> >- what was the error message or what failed or happened exactly that
> >stopped the installation
> >
> >I wasn't able to reproduce your problem in VirtualBox using the network
> >installation ISO 
> >http://cdimage.debian.org/debian-cd/8.2.0/i386/iso-cd/debian-8.2.0-i386-netinst.iso
> >and with almost all the default choices with the excpetion of these
> >prompts
> >- Full name of new user: "Adrian O'Dell"
> >- user name: "adrian"
> >
> >I understand that you may not feel like reading a large page of text if
> >you are in a hurry or feel you may not understand it. However, the Debian
> >and other open-source projects keep living thanks to individuals like you
> >that go the extra mile, devote some time to the cause and are willing to
> >learn new things. Please consider supporting Debian (and through it all
> >other projects based on it, including Linux Mint) through your extra
> >effort in filing bug reports when needed.
> >
> >Kind regards,
> >Ondřej Grover
> >
> >On Thu, Oct 22, 2015 at 8:15 AM, Adrian O'Dell  >> wrote:
> >
> >There appears to be a bug which has Plagued me for years. Oddly I
> >don't have the bug in Linux Mint. Did they edit this part of the
> >installer?
> >
> >My name contains an apostrophe, which causes the Debian installer
> >to not create my user account. Long time ago when I tried to seek
> >help via IRC was told I must have done something wrong. Two days
> >ago I confirmed through multiple installs that the apostrophe is
> >the culprit.
> >
> >This is the only attempt I will make at filing a bug report.
> >Anyone more familiar with filing a bug report, it would be greatly
> >appreciated if you would make sure it gets filed properly so it
> >may be resolved. https://www.debian.org/Bugs/Reporting is an ugly
> >wall of text which immediately discouraged me from wanting to file
> >a bug report anymore.
> >
> >Thanks.
> 
> I agree with the topic starter: the Debian's bug reporting process is
> horrible and not userfriendly from user's viewpoint. If an organization
> cares about usability and effectiveness of bug reporting process, it
> shouldn't be like that.

If a user cares about the usability and effectiveness of the bug
reporting process, more detail to back up the complaint would be
welcome.

Re: Reporting Bug

[Piyavkin]

On 22.10.2015 10:18, Ondřej Grover wrote:

Hello Adrian,

could you please be more specific about a few points?
- what installer ISO did you use
- did you use the text or graphical installer
- what was the error message or what failed or happened exactly that 
stopped the installation


I wasn't able to reproduce your problem in VirtualBox using the 
network installation ISO 
http://cdimage.debian.org/debian-cd/8.2.0/i386/iso-cd/debian-8.2.0-i386-netinst.iso 
and with almost all the default choices with the excpetion of these 
prompts

- Full name of new user: "Adrian O'Dell"
- user name: "adrian"

I understand that you may not feel like reading a large page of text 
if you are in a hurry or feel you may not understand it. However, the 
Debian and other open-source projects keep living thanks to 
individuals like you that go the extra mile, devote some time to the 
cause and are willing to learn new things. Please consider supporting 
Debian (and through it all other projects based on it, including Linux 
Mint) through your extra effort in filing bug reports when needed.


Kind regards,
Ondřej Grover

On Thu, Oct 22, 2015 at 8:15 AM, Adrian O'Dell > wrote:


There appears to be a bug which has Plagued me for years. Oddly I
don't have the bug in Linux Mint. Did they edit this part of the
installer?

My name contains an apostrophe, which causes the Debian installer
to not create my user account. Long time ago when I tried to seek
help via IRC was told I must have done something wrong. Two days
ago I confirmed through multiple installs that the apostrophe is
the culprit.

This is the only attempt I will make at filing a bug report.
Anyone more familiar with filing a bug report, it would be greatly
appreciated if you would make sure it gets filed properly so it
may be resolved. https://www.debian.org/Bugs/Reporting is an ugly
wall of text which immediately discouraged me from wanting to file
a bug report anymore.

Thanks.




I agree with the topic starter: the Debian's bug reporting process is 
horrible and not userfriendly from user's viewpoint. If an organization 
cares about usability and effectiveness of bug reporting process, it 
shouldn't be like that.


Piyavkin

Re: make system boot straight to browser connection

[Lisi Reisz]

On Wednesday 21 October 2015 14:03:34 Richard Owlett wrote:
> 2. A. set system for autologin
>       B. start browser, go to desired page
>       C. save session in Xfce
>       D. on next power up, system would go to desired page

Just for the record, and not because I think taht it would be of any interest 
to Richard,

1. Install TDE
2. Set up auto-login
3. Start up Konqueror.
4.Shut down

Next time you boot up Konqueror will open on boot-up.  If it was on a specific 
webpage when you shut down, that one will open automatically.  If you were on 
several tabs, then several tabs will open.

This is the default.  If it has been turned off, it can be turned on again.

This applies to any TDE application.  I keep my calendar and email running all 
the time, and they open up automatically when I reboot.

Lisi

Re: Reporting Bug

[Brian]

On Thu 22 Oct 2015 at 09:18:24 +0200, Ondřej Grover wrote:

> On Thu, Oct 22, 2015 at 8:15 AM, Adrian O'Dell 
> wrote:
>
> > There appears to be a bug which has Plagued me for years. Oddly I don't
> > have the bug in Linux Mint. Did they edit this part of the installer?
> >
> > My name contains an apostrophe, which causes the Debian installer to not
> > create my user account. Long time ago when I tried to seek help via IRC was
> > told I must have done something wrong. Two days ago I confirmed through
> > multiple installs that the apostrophe is the culprit.
> >
> > This is the only attempt I will make at filing a bug report. Anyone more
> > familiar with filing a bug report, it would be greatly appreciated if you
> > would make sure it gets filed properly so it may be resolved.
> > https://www.debian.org/Bugs/Reporting is an ugly wall of text which
> > immediately discouraged me from wanting to file a bug report anymore.

> could you please be more specific about a few points?
> - what installer ISO did you use
> - did you use the text or graphical installer
> - what was the error message or what failed or happened exactly that
> stopped the installation
> 
> I wasn't able to reproduce your problem in VirtualBox using the network
> installation ISO
> http://cdimage.debian.org/debian-cd/8.2.0/i386/iso-cd/debian-8.2.0-i386-netinst.iso
> and with almost all the default choices with the excpetion of these prompts
> - Full name of new user: "Adrian O'Dell"
> - user name: "adrian"

My install was on bare metal. The outcome was identical to yours.

> I understand that you may not feel like reading a large page of text if you
> are in a hurry or feel you may not understand it. However, the Debian and
> other open-source projects keep living thanks to individuals like you that
> go the extra mile, devote some time to the cause and are willing to learn
> new things. Please consider supporting Debian (and through it all other
> projects based on it, including Linux Mint) through your extra effort in
> filing bug reports when needed.

The second line on the page says:

  We strongly recommend that you report bugs in Debian using the
  reportbug program.

Making sure "it gets filed properly so it may be resolved" is not a
responsibility of some third party unfamiliar with the details,
especially if it is not reproducible for them.

Re: Whitelist security.debian.org

[Brian]

On Thu 22 Oct 2015 at 11:44:41 +0200, Sven Hartge wrote:

> Pascal Hambourg  wrote:
> > Greencopper a écrit :
>  
> >> Most likely OpenDNS has some load balancing of their own perhaps
> >> forwarding the request to different internal servers.
> >> 
> >> Perhaps the only solution is to fix a specific IP address for
> >> security.debian.org in my local DNS server and then only use that!
> 
> > Or don't use OpenDNS servers.
> 
> Or don't try to build firewall rules based on DNS lookups.

Or amend sources.list to not require DNS. 149.20.20.6 is schein; use
villa if preferred.

  deb ftp://149.20.20.6/debian-security jessie/updates main

Re: Whitelist security.debian.org

[Sven Hartge]

Pascal Hambourg  wrote:
> Greencopper a écrit :
 
>> Most likely OpenDNS has some load balancing of their own perhaps
>> forwarding the request to different internal servers.
>> 
>> Perhaps the only solution is to fix a specific IP address for
>> security.debian.org in my local DNS server and then only use that!

> Or don't use OpenDNS servers.

Or don't try to build firewall rules based on DNS lookups.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: System Dorked -- Help!

[Thomas Schmitt]

Hi,

> From mount of root partition in Debian live session, moun --bind /dev to
> root partition's dev,

Do i get it right that are trying to start your hard disk installed
Linux from a running LiveCD Linux ?
Interesting stunt. But far from being standard.


> On booting, get errors. Can get to console login titled Kali, but cannot log
> in to it, not previous users, "user," root, nada.

Whatever started up, it is incomplete.
If it says "Kali" then it can hardly be vanilla Debian.


> Loads of LSB cannot do something

This statement is too condensed for me to understand.
LSB = Linux Standard Base , Least Significant Bit ?
I guess it is about the former, but still get no grip on
what you experience there.

Whatever, you seem to be beyond boot loader when the errors
happen.
So your problem is either in your GNU/Linux initrd, or in
the system files, or in the way the boot loader started the
Linux kernel.


> Tried restoring previous boot loader: lilo -i  ... -M  mbr
> Was not bootable.

This is then probably a separate problem.


Too many problems to propose a small solution from what
i know meanwhile.

In your situation i would try to get a trustworthy hard
disk and install a new Debian 8. I'd give up LILO, because
GRUB2 is mainstream now and gives more hope to find an expert
who can help.
Then i would customize the new system by help of the files
on the old disks and copy any valuable user data from the not
trustworthy disks.

My own hardware failure happened 4 months ago. After a month
i had my new machine quite in the shape of the old one.


Have a nice day :)

Thomas

Re: No monitor in GNOME Control Center - Color

[Pascal Obry]

I've just filed a bug for this on the Debian bug tracker:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802655

Cheers,

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://v2p.fr.eu.org
  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B



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

Re: Debian 8.2 RAID conf. problem

[Darac Marjal]

On Wed, Oct 21, 2015 at 05:46:55PM +0100, Tony van der Hoff wrote:


On 21/10/15 17:35, Mario Castelán Castro wrote:


El 21/10/15 a las 11:11, erdal daghan escribió:


[cut]


El 21/10/15 a las 11:11, erdal daghan escribió:

Please help me.. I have two ssd disks(240gb). I want to make RAID1 
configuration.


You probably refer to ordinary solid state drives which are NOT disks.



This raises a question in my mind: Should SSDs be used in RAID arrays?



I don't see a problem with it. RAID is a method to overcome the 
deficiencies of inexpensive disks. With traditional disks, one of those 
major deficiencies is access time, so spreading your data across 
multiple disks may improve access time by allowing you to read from a 
different disk, rather than waiting for a single slow disk.


SSD has good access time, but it deficiencies are size and possibly bulk 
throughput. In terms of size, RAID0 will allow you to combine several 
small SSDs into a single large logical drive. RAID0 would also allow for 
faster throughput than might be achievable with a single disk.


signature.asc
Description: PGP signature

Re: System Dorked -- Help!

[d_baron]

- Original Message -
From: Joel Rees 
Date: Thursday, October 22, 2015 2:34 am
Subject: Re: System Dorked -- Help!
To: d_ba...@012.net.il
Cc: debian-user 

> On Wed, Oct 21, 2015 at 10:32 PM,   wrote:
> >
> > - Original Message -
> > From: d_ba...@012.net.il
> > Date: Wednesday, October 21, 2015 11:18 am
> > Subject: Re: System Dorked -- Help!
> > To: debian-user@lists.debian.org
> >
> >> - Original Message -
> >> From: d_ba...@012.net.il
> >> Date: Wednesday, October 21, 2015 10:24 am
> >> Subject: System Dorked -- Help!
> >> To: debian-user@lists.debian.org
> >
> >> > After being warned of impending failure of my oldie but 
> goodie 80gig
> >> > disk -- I had placed my root directory there because the 
> installation's>> > partition was too small and did this 
> successfully -- I moved the root
> >> > directory to a partition on another disk, edited files, ran 
> lilo, seemingly
> >> > successfully, and voile: No boot. Get 99's or nothing at all.
> 
> Moved or copied? Did the impending actually fail?

cp -ax  oldrootpartition newrootpartition

> When I do something like this, I generally copy and make sure the
> thing works before abandoning the old boot disk.

Yeah, should have had lilo place the mbr to a different disk. Too late now.

> Is LVM involved? or RAID? Do you have a second disk controller 
> off the
> motherboard and end up using both controllers so that something thinks
> you were trying to use RAID?
> 

No LVM, no RAID

> > Going into a live Debian 7,
> 
> I'm guessing that's Kali?

64-bit Debian 7 live.

> 
> > I mounted the old and new partitions, copied the
> 
> At this point, I'm completely lost about where your boot 
> partition and
> other partitions are. Sorry.
> 

Partition contents successfully copied before hand. I had neglected to copy the 
edited fstab and  lilo.conf so copied these over in the live session.

> > modified files (which had been done on the old version :-( ) 
> and chroot and
> > tried to re-run lilo. Segmentation fault. I had been running 
> an up-to-date
> > Sid so maybe that is the problem. The lilo is on the 
> partition, not on the
> > live distro.
> 
> Yeah, but which partition?
>

chroot was to new root partition containing /boot directory and /etc/lilo.conf
The lilo here would not run, segfault.

 
> >> > Fact is, with certain combination of cabling,
> 
> I assume you are using parallel ATA here like my old box?
> 
> master/slave and position on those cables is always a bit of a mess.
> 
> >> > I had the bootloader
> >> > actually work, load the initrd, and start up, but the new 
> root was not
> >> > connected
> 
> not connected to what?

I had two of the three disks plugged in. The boot disk was, the root disk was 
not. Forget about this.

> 
> >> > so could not proceed. So what can I do about this?
> >> > ‭‮
> >
> > More:
> > I installed to the live distro its lilo
> 
> I'm having a real problem parsing that. You installed a live distro's
> lilo to the live distro?
> 

Yes, I guess from Debian 7, stable?

> Is the live distro on a USB drive or something?

Live CD. It, of course, installs to memory.

> 
> > and ran from command line specifying
> > the configuration file and map.
> 
> Ran what on what command line?

sudo lilo -C pathtonewextlilo.conf -M pathtonewmapfile
or
sudo lilo -r newrootpartition

> 
> > This is what I get:
> > Fatal: Trying to map files from unnamed device 0x0012 
> (NFS/RAID mirror down?)
> >
> 
> So, I'm not the only one having trouble figuring out what you are
> doing where. ;-)
> 
> >> Ok, no segment fault. If I use the -q option, it will display 
> my boot
> >> choices.
> 
> So is this now in the chroot or booting up in lilo on which device?
> 

sudo lilo -r newrootpartition
does the change root and runs the installed lilo there.


> > So, what's next?
> >
> >> ‭‮
> >
> > And more::
> >
> > Found by Googling that I can bind /proc, /dev to chroot and 
> then the
> > installed lilo will run! Same results with or without /proc 
> binding. /dev
> > binding got rid of the original error.
> 
> In the chroot or from BIOS?

sudo mount --bind newrootpartion/dev /dev

> 
> > Boots up with a load of errors but I am now in a machine 
> called "Kali Linux"
> 
> Is Kali the live distro you are using?

NO, but apparently, somewhere on it, is is.

> 
> > I cannot log on to anything. Errors too numerous and fast to 
> see. ACPI, does
> > not work on this system anyway. Login service failed to start. Etc.
> >
> > So maybe!! almost there. What else need I do get back to where 
> I was?
> > Something else to bind?
> > Copy to restore from the original root directory?
> >
> > (Possibly the "user" login from the live distro might work 
> (password?), and
> > I could recreate previous users if need be but that does not 
> touch the other
> > errors.)
> 
> (Talk about chewing gum and bailing wire.)
> 
> First, what was your original partition layout? What was the boot
> disk, where were your other partitions?

Original parti

Re: Virtual box

[Catalin Soare]

On Tue, Oct 20, 2015 at 5:33 AM, Mitch Nuss  wrote:

> I am wanting to install Debian into a pic tower I have and want to use it
> as a headless server and use a tight VNC so I can access it anywhere. Do
> you have any advice for me and will I need to install virtual box? Amy info
> you have for me would be great thanks.
>
> Sent from my iPhone
>


Hello,

If you want some virtualization, then yes, you'll have to install some
virtualization software, out of which I guess Virtualbox is the easiest to
setup.
But you don't really need VNC, unless you plan to install many VMs and then
remove them, and then install others (so unless you really need a GUI).

The way I do this: I setup my VMs (webserver / other servers), then:
1. I turn on my PC with wakeonlan from another device;
2. I ssh into my PC
3. I turn on the VMs that I want to work on from the ssh session:
vboxmanage startvm "VM_name" --type headless.

The name of the VMs can be found by "vboxmanage list vms".

Good luck!

-- 
Regards,
*Catalin Soare *

Re: System Dorked -- Help!

[d_baron]

- Original Message -
From: Thomas Schmitt 
Date: Wednesday, October 21, 2015 11:53 pm
Subject: Re: System Dorked -- Help!
To: debian-user@lists.debian.org

> Hi,
> 
> > Hope all those >'s do not foul this up.
> 
> No danger.
> The only problem with ">" is the dreaded ">From" mailbox escape
> which might be confused with ">From" meant as quote.
> 
> 
> > I am using a Debian live CD. So that Kali business comes from 
> there but is
> > nowhere shown when running of the CD.
> 
> Strange. Afaik, Kali is based on Debian but not part of it.
> 
> 
> > The new root not connected -- the SATA cable was not in. As I 
> said, I was
> > experimenting with the cables.
> 
> So what is your system dork intensity, currently ?
> 
> Still lots of error messages from LILO (or booting kernel)
> and no login ?
> 
> 
> Have a nice day :)
> 
> Thomas
> 

Current status:
>From mount of root partition in Debian live session, moun --bind /dev to root 
>partition's dev,
Lilo runs, seemingly OK.

On booting, get errors. Can get to console login titled Kali, but cannot log in 
to it, not previous users, "user," root, nada.

Errors:
Loads of LSB cannot do something
including LVM, but I am not using it.
login daemon.

Tried restoring previous boot loader: lilo -i  ... -M  mbr
Was not bootable.

Re: Whitelist security.debian.org

[Pascal Hambourg]

Greencopper a écrit :
> 
> Most likely OpenDNS has some load balancing of their own perhaps forwarding
> the request to different internal servers.
> 
> Perhaps the only solution is to fix a specific IP address for
> security.debian.org in my local DNS server and then only use that!

Or don't use OpenDNS servers.

Re: Reporting Bug

[Ondřej Grover]

Hello Adrian,

could you please be more specific about a few points?
- what installer ISO did you use
- did you use the text or graphical installer
- what was the error message or what failed or happened exactly that
stopped the installation

I wasn't able to reproduce your problem in VirtualBox using the network
installation ISO
http://cdimage.debian.org/debian-cd/8.2.0/i386/iso-cd/debian-8.2.0-i386-netinst.iso
and with almost all the default choices with the excpetion of these prompts
- Full name of new user: "Adrian O'Dell"
- user name: "adrian"

I understand that you may not feel like reading a large page of text if you
are in a hurry or feel you may not understand it. However, the Debian and
other open-source projects keep living thanks to individuals like you that
go the extra mile, devote some time to the cause and are willing to learn
new things. Please consider supporting Debian (and through it all other
projects based on it, including Linux Mint) through your extra effort in
filing bug reports when needed.

Kind regards,
Ondřej Grover

On Thu, Oct 22, 2015 at 8:15 AM, Adrian O'Dell 
wrote:

> There appears to be a bug which has Plagued me for years. Oddly I don't
> have the bug in Linux Mint. Did they edit this part of the installer?
>
> My name contains an apostrophe, which causes the Debian installer to not
> create my user account. Long time ago when I tried to seek help via IRC was
> told I must have done something wrong. Two days ago I confirmed through
> multiple installs that the apostrophe is the culprit.
>
> This is the only attempt I will make at filing a bug report. Anyone more
> familiar with filing a bug report, it would be greatly appreciated if you
> would make sure it gets filed properly so it may be resolved.
> https://www.debian.org/Bugs/Reporting is an ugly wall of text which
> immediately discouraged me from wanting to file a bug report anymore.
>
> Thanks.
>
>

Re: Reporting Bug

[Jude DaShiell]

Normally I would put a backslash character in front of that apostrophe 
since it's a special character to bash at least and I suspect several 
other shell envioonments.  Perhaps try O\'Dell by way of an example.  I 
suspect mint hasn't been modified at all and that you haven't interacted 
so far with the shell environment in mint which may be why you haven't 
found this error in that distro yet.


On Thu, 22 Oct 2015, Adrian O'Dell wrote:


Date: Thu, 22 Oct 2015 02:15:10
From: Adrian O'Dell 
To: debian-user@lists.debian.org
Subject: Reporting Bug
Resent-Date: Thu, 22 Oct 2015 06:33:12 + (UTC)
Resent-From: debian-user@lists.debian.org

There appears to be a bug which has Plagued me for years. Oddly I don't have 
the bug in Linux Mint. Did they edit this part of the installer?


My name contains an apostrophe, which causes the Debian installer to not 
create my user account. Long time ago when I tried to seek help via IRC was 
told I must have done something wrong. Two days ago I confirmed through 
multiple installs that the apostrophe is the culprit.


This is the only attempt I will make at filing a bug report. Anyone more 
familiar with filing a bug report, it would be greatly appreciated if you 
would make sure it gets filed properly so it may be resolved. 
https://www.debian.org/Bugs/Reporting is an ugly wall of text which 
immediately discouraged me from wanting to file a bug report anymore.


Thanks.




--