Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #159559 > unrolled thread

System Dorked -- Help!

Back to article view | Back to linux.debian.user

Contents

  System Dorked -- Help! d_baron@012.net.il - 2015-10-21 09:30 +0200
    Re: System Dorked -- Help! d_baron@012.net.il - 2015-10-21 10:20 +0200
      Re: System Dorked -- Help! d_baron@012.net.il - 2015-10-21 15:40 +0200
        Re: System Dorked -- Help! Renaud (Ron) OLGIATI <renaud@olgiati-in-paraguay.org> - 2015-10-21 16:00 +0200
          Re: System Dorked -- Help! Gene Heskett <gheskett@shentel.net> - 2015-10-21 16:20 +0200
            Re: System Dorked -- Help! Darac Marjal <mailinglist@darac.org.uk> - 2015-10-21 16:40 +0200
              Re: System Dorked -- Help! Gene Heskett <gheskett@shentel.net> - 2015-10-21 17:00 +0200
                Thread dorked. Was: Re: System Dorked -- Help! "Thomas Schmitt" <scdbackup@gmx.net> - 2015-10-21 17:30 +0200
                  Re: Thread dorked. Was: Re: System Dorked -- Help! David Wright <deblis@lionunicorn.co.uk> - 2015-10-21 20:30 +0200
                Re: Thread dorked. (was: Re: System Dorked -- Help!) Felix Miata <mrmazda@earthlink.net> - 2015-10-21 18:50 +0200
                  Re: Thread dorked. (was: Re: System Dorked -- Help!) d_baron@012.net.il - 2015-10-21 19:50 +0200
                    Thread dorked. Was: Re: System Dorked -- Help! "Thomas Schmitt" <scdbackup@gmx.net> - 2015-10-21 21:20 +0200
                    Re: Thread dorked. (was: Re: System Dorked -- Help!) Lisi Reisz <lisi.reisz@gmail.com> - 2015-10-23 00:30 +0200
          Re: System Dorked -- Help! Tony van der Hoff <tony@vanderhoff.org> - 2015-10-21 16:20 +0200
            Re: System Dorked -- Help! Gene Heskett <gheskett@shentel.net> - 2015-10-21 16:40 +0200
        Re: System Dorked -- Help! d_baron@012.net.il - 2015-10-21 19:50 +0200
          Re: System Dorked -- Help! Felix Miata <mrmazda@earthlink.net> - 2015-10-21 20:40 +0200
          Re: System Dorked -- Help! "Thomas Schmitt" <scdbackup@gmx.net> - 2015-10-21 21:40 +0200
            Re: System Dorked -- Help! d_baron@012.net.il - 2015-10-21 21:50 +0200
              Re: System Dorked -- Help! "Thomas Schmitt" <scdbackup@gmx.net> - 2015-10-21 23:00 +0200
                Re: System Dorked -- Help! d_baron@012.net.il - 2015-10-22 10:20 +0200
                  Re: System Dorked -- Help! "Thomas Schmitt" <scdbackup@gmx.net> - 2015-10-22 11:30 +0200
                    Re: System Dorked -- Help! "Thomas Schmitt" <scdbackup@gmx.net> - 2015-10-23 14:00 +0200
        Re: System Dorked -- Help! Joel Rees <joel.rees@gmail.com> - 2015-10-22 01:40 +0200
          Re: System Dorked -- Help! d_baron@012.net.il - 2015-10-22 10:40 +0200

Page 1 of 2  [1] 2  Next page →

#159559 — System Dorked -- Help!

[Multipart message — attachments visible in raw view] — view raw

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.Going into a live Debian 7, I mounted the old and new partitions, copied the 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.Fact is, with certain combination of cabling, I had the bootloader actually work, load the initrd, and start up, but the new root was not connected so could not proceed. So what can I do about this?‭‮

[toc] | [next] | [standalone]

#159560

[Multipart message — attachments visible in raw view] — view raw

----- Original Message -----From: d_baron@012.net.ilDate: Wednesday, October 21, 2015 10:24 amSubject: 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.Going into a live Debian 7, I mounted the old and new partitions, copied the 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.> Fact is, with certain combination of cabling, I had the bootloader actually work, load the initrd, and start up, but the new root was not connected so could not proceed. So what can I do about this?> ‭‮More:I installed to the live distro its lilo and ran from command line specifying the configuration file and map. This is what I get:Fatal: Trying to map files from unnamed device 0x0012 (NFS/RAID mirror down ?)Ok, no segment fault. If I use the -q option, it will display my boot choices.So, what's next?‭‮

[toc] | [prev] | [next] | [standalone]

#159570

[Multipart message — attachments visible in raw view] — view raw

----- Original Message -----From: d_baron@012.net.ilDate: Wednesday, October 21, 2015 11:18 amSubject: Re: System Dorked -- Help!To: debian-user@lists.debian.org> ----- Original Message -----> From: d_baron@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.Going into a live Debian 7, I mounted the old and new partitions, copied the 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.> > Fact is, with certain combination of cabling, I had the bootloader actually work, load the initrd, and start up, but the new root was not connected so could not proceed. So what can I do about this?> > ‭‮More:I installed to the live distro its lilo and ran from command line specifying the configuration file and map. This is what I get:Fatal: Trying to map files from unnamed device 0x0012 (NFS/RAID mirror down ?)> Ok, no segment fault. If I use the -q option, it will display my boot choices.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.Boots up with a load of errors but I am now in a machine called "Kali Linux" 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.)‭‮

[toc] | [prev] | [next] | [standalone]

#159571

On Wed, 21 Oct 2015 16:32:40 +0300
d_baron@012.net.il wrote:

> ----- Original Message -----From: d_baron@012.net.ilDate: Wednesday, October 21, 2015 11:18 amSubject: Re: System Dorked -- Help!To: >debian-user@lists.debian.org> ----- Original Message -----> From: d_baron@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.Going into a live Debian 7, I mounted the old and new partitions, copied the 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.> > Fact is, with certain combination of cabling, I had the bootloader actually work, load the initrd, >and start up, but the new root was not connected so could not proceed. So what can I do about this?> > ‭‮More:I installed to the live distro >lo and ran from command line specifying the configuration file and map. This is what I get:Fatal: Trying to map files from unnamed>device 12 (NFS/RAID mirror down ?)> Ok, no segment fault. If I use the -q option, it will display my boot choices.So, what's next?> ‭‮An 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.Boots up with a load of errors but I am now in a machine called "Kali Linux" 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.)<‭‮

Quoting the relevant query: "So what can I do about this?"

Send properly formatted mail, so it is legible ?
 
Cheers,
 
Ron.
-- 
                  Si vous étiez venue, O belle que j'admire,
                  Je vous aurais offert un dîner sans rival:
                J'aurais tué Pégase et je l'aurais fait cuire
                   Afin de vous servir une aile de cheval.
                                               -- Victor Hugo
                                    
                   -- http://www.olgiati-in-paraguay.org --
 

[toc] | [prev] | [next] | [standalone]

#159574

On Wednesday 21 October 2015 09:56:18 Renaud  OLGIATI wrote:

> On Wed, 21 Oct 2015 16:32:40 +0300
>
> d_baron@012.net.il wrote:
> > ----- Original Message -----From: d_baron@012.net.ilDate: Wednesday,
> > October 21, 2015 11:18 amSubject: Re: System Dorked -- Help!To:
> > >debian-user@lists.debian.org> ----- Original Message -----> From:
> > d_baron@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.Going into a live Debian 7, I mounted the
> > old and new partitions, copied the 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.> > Fact is, with certain combination of cabling, I had the
> > bootloader actually work, load the initrd, >and start up, but the
> > new root was not connected so could not proceed. So what can I do
> > about this?> > ‭‮More:I installed to the live distro >lo and ran
> > from command line specifying the configuration file and map. This is
> > what I get:Fatal: Trying to map files from unnamed>device 12
> > (NFS/RAID mirror down ?)> Ok, no segment fault. If I use the -q
> > option, it will display my boot choices.So, what's next?> ‭‮An
> > 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.Boots up with a
> > load of errors but I am now in a machine called "Kali Linux" 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.)<‭‮
>
> Quoting the relevant query: "So what can I do about this?"
>
> Send properly formatted mail, so it is legible ?
>
> Cheers,
>
> Ron.

+1, this stuff isn't readable.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#159579

[Multipart message — attachments visible in raw view] — view raw

On Wed, Oct 21, 2015 at 10:14:05AM -0400, Gene Heskett wrote:
> On Wednesday 21 October 2015 09:56:18 Renaud  OLGIATI wrote:
> 
> > On Wed, 21 Oct 2015 16:32:40 +0300
> >
> > d_baron@012.net.il wrote:
> > > ----- Original Message -----From: d_baron@012.net.ilDate: Wednesday,
> > > October 21, 2015 11:18 amSubject: Re: System Dorked -- Help!To:
> > > >debian-user@lists.debian.org> ----- Original Message -----> From:
> > > d_baron@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.Going into a live Debian 7, I mounted the
> > > old and new partitions, copied the 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.> > Fact is, with certain combination of cabling, I had the
> > > bootloader actually work, load the initrd, >and start up, but the
> > > new root was not connected so could not proceed. So what can I do
> > > about this?> > ‭‮More:I installed to the live distro >lo and ran
> > > from command line specifying the configuration file and map. This is
> > > what I get:Fatal: Trying to map files from unnamed>device 12
> > > (NFS/RAID mirror down ?)> Ok, no segment fault. If I use the -q
> > > option, it will display my boot choices.So, what's next?> ‭‮An
> > > 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.Boots up with a
> > > load of errors but I am now in a machine called "Kali Linux" 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.)<‭‮
> >
> > Quoting the relevant query: "So what can I do about this?"
> >
> > Send properly formatted mail, so it is legible ?
> >
> > Cheers,
> >
> > Ron.
> 
> +1, this stuff isn't readable.

For the record, the HTML is somewhat more readable than the 
plain text.  
What might be the problem there?

> X-Mailer: Oracle Communications Messenger Express 
> 7u4-23.01(7.0.4.23.0) 64bit (built Aug 10 2011) 

Yeah, that might be the problem. :)

> 
> Cheers, Gene Heskett
> -- 
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page <http://geneslinuxbox.net:6309/gene>
> 

-- 
For more information, please reread.

[toc] | [prev] | [next] | [standalone]

#159582

On Wednesday 21 October 2015 10:35:25 Darac Marjal wrote:

> On Wed, Oct 21, 2015 at 10:14:05AM -0400, Gene Heskett wrote:
> > On Wednesday 21 October 2015 09:56:18 Renaud  OLGIATI wrote:
> > > On Wed, 21 Oct 2015 16:32:40 +0300
> > >
> > > d_baron@012.net.il wrote:
> > > > ----- Original Message -----From: d_baron@012.net.ilDate:
> > > > Wednesday,
> > > >
> > > > October 21, 2015 11:18 amSubject: Re: System Dorked -- Help!To:
> > > > >debian-user@lists.debian.org> ----- Original Message ----->
> > > > > From:
> > > >
> > > > d_baron@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.Going into a live Debian 7, I
> > > > mounted the old and new partitions, copied the 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.> > Fact is, with certain
> > > > combination of cabling, I had the bootloader actually work, load
> > > > the initrd, >and start up, but the new root was not connected so
> > > > could not proceed. So what can I do about this?> > ‭‮More:I
> > > > installed to the live distro >lo and ran from command line
> > > > specifying the configuration file and map. This is what I
> > > > get:Fatal: Trying to map files from unnamed>device 12 (NFS/RAID
> > > > mirror down ?)> Ok, no segment fault. If I use the -q option, it
> > > > will display my boot choices.So, what's next?> ‭‮An 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.Boots up
> > > > with a load of errors but I am now in a machine called "Kali
> > > > Linux" 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.)<‭‮
> > >
> > > Quoting the relevant query: "So what can I do about this?"
> > >
> > > Send properly formatted mail, so it is legible ?
> > >
> > > Cheers,
> > >
> > > Ron.
> >
> > +1, this stuff isn't readable.
>
> For the record, the HTML is somewhat more readable than the
> plain text.
> What might be the problem there?
>
> > X-Mailer: Oracle Communications Messenger Express
> > 7u4-23.01(7.0.4.23.0) 64bit (built Aug 10 2011)
>
> Yeah, that might be the problem. :)

Same as the OP's email agent, but one of the other replies here is using 
icedove, whatever that is.  So there are at least 2 problem children 
here in terms of the email agents being used. I am on several other 
mailing lists, and the use of the Oracle email agent seems to be a 
fairly common problem.

> > Cheers, Gene Heskett
> > --
> > "There are four boxes to be used in defense of liberty:
> >  soap, ballot, jury, and ammo. Please use in that order."
> > -Ed Howdershelt (Author)
> > Genes Web page <http://geneslinuxbox.net:6309/gene>


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#159584 — Thread dorked. Was: Re: System Dorked -- Help!

Hi,

as a bystander i must say that the involved mail clients
invest much effort in making this thread a mess.

In the archives, the initial message is quite readable
but with seriously oversized lines:
  https://lists.debian.org/debian-user/2015/10/msg01079.html

The two follow-ups by the original poster don't make it
better, but also not much worse.

Then comes
  https://lists.debian.org/debian-user/2015/10/msg01091.html
where Renaud's client obviously copied the previous text
in a way which, after running through the archive's web server,
makes my Iceweasel go mad.
Text snippets like
  "pam ot gniyrT :lataF"
reveil their origin only if i read them backwards
  "Fatal: Trying to map"

My local mail client alpine shows the older texts as large
paragraphs with no line breaks and interjected ">" or "<".
Also there are placeholder characters for undisplayable UTF-8
characters.

My mailbox file contains stuff like
  "=E2=80=AD=E2=80=AEMore:I installed to the"
According to https://en.wikipedia.org/wiki/UTF-8, "E2" indicates
a three-byte character.
  http://www.ltg.ed.ac.uk/~richard/utf-8.cgi?input=E2+80+AD&mode=bytes
says its LEFT-TO-RIGHT OVERRIDE.
The other
  http://www.ltg.ed.ac.uk/~richard/utf-8.cgi?input=E2+80+AE&mode=bytes
is RIGHT-TO-LEFT OVERRIDE.

This brings me to
  http://krebsonsecurity.com/2011/09/right-to-left-override-aids-email-attacks/

Well, i cannot spot an .exe file in disguise, at least. :))


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#159598 — Re: Thread dorked. Was: Re: System Dorked -- Help!

Quoting Thomas Schmitt (scdbackup@gmx.net):
> as a bystander i must say that the involved mail clients
> invest much effort in making this thread a mess.
> 
> In the archives, the initial message is quite readable
> but with seriously oversized lines:
>   https://lists.debian.org/debian-user/2015/10/msg01079.html
> 
> The two follow-ups by the original poster don't make it
> better, but also not much worse.
> 
> Then comes
>   https://lists.debian.org/debian-user/2015/10/msg01091.html
> where Renaud's client obviously copied the previous text
> in a way which, after running through the archive's web server,
> makes my Iceweasel go mad.
> Text snippets like
>   "pam ot gniyrT :lataF"
> reveil their origin only if i read them backwards
>   "Fatal: Trying to map"
> 
> My local mail client alpine shows the older texts as large
> paragraphs with no line breaks and interjected ">" or "<".
> Also there are placeholder characters for undisplayable UTF-8
> characters.
> 
> My mailbox file contains stuff like
>   "=E2=80=AD=E2=80=AEMore:I installed to the"
> According to https://en.wikipedia.org/wiki/UTF-8, "E2" indicates
> a three-byte character.
>   http://www.ltg.ed.ac.uk/~richard/utf-8.cgi?input=E2+80+AD&mode=bytes
> says its LEFT-TO-RIGHT OVERRIDE.
> The other
>   http://www.ltg.ed.ac.uk/~richard/utf-8.cgi?input=E2+80+AE&mode=bytes
> is RIGHT-TO-LEFT OVERRIDE.

I deleted the original email because I couldn't be of any help. But I
looked at Renaud's email after seeing your post. I read my emails on
wheezy, and emacs there couldn't see anything odd. However, I
transferred the file to my laptop where I've processed Hebrew text in
music scores and am familiar with the bizarre (to Latin eyes) way the
cursor moves in emacs. Sure enough, jessie's emacs displays a large
chunk of Renaud's email "backwards" because of the RLOs.

In mutt (both versions), the LRO/RLOs are displayed as blobs, but if I
try to reply (which uses emacs), wheezy shows all the text LtoR
whereas jessie reverses much of it.

The apparent weirdness is compounded if you press return in the
reversed text. Now the (new) paragraphs are no longer surrounded by
RLOs so some of the text instantly switches to normal. (Not all of it:
there are embedded marks at "An more:".)

So the people with "a problem" may merely be those running more modern
capable software.

Where did the LRO/RLOs come from; well one might suppose that it could
be connected with the OP's locale appropriate to residing in IL.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

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

Gene Heskett composed on 2015-10-21 10:53 (UTC-0400):

>> > > Quoting the relevant query: "So what can I do about this?"

>> > > Send properly formatted mail, so it is legible ?

>> > +1, this stuff isn't readable.

Readable as in legible, yes, but an unintelligible mess, so not really readable.

>> For the record, the HTML is somewhat more readable than the plain text.
>> What might be the problem there?

>> > X-Mailer: Oracle Communications Messenger Express
>> > 7u4-23.01(7.0.4.23.0) 64bit (built Aug 10 2011)

>> Yeah, that might be the problem. :)

+1

> Same as the OP's email agent, but one of the other replies here is using 
> icedove, whatever that is. 

Debian debrands Mozilla products:

1: Ice <> Fire

2a: Weasel <> Fox

2b: Dove <> (Thunder)Bird (rv31.0)

2c: Ape <> (Sea)Monkey

2d: Owl <> (Ice)Owl

iceweasel=Firefox	https://wiki.debian.org/Iceweasel
icedove=Thunderbird	https://wiki.debian.org/Icedove
iceape=SeaMonkey
https://en.wikipedia.org/wiki/Mozilla_Corporation_software_rebranded_by_the_Debian_project#Iceape
iceowl=Sunbird		ibid.

> So there are at least 2 problem children
> here in terms of the email agents being used. I am on several other
> mailing lists, and the use of the Oracle email agent seems to be a
> fairly common problem.

I'm on more than 70 mailing lists. I can't recall Oracle being a "common"
problem, but it is nevertheless a problem as used by OP in this thread, and
the Claws and Icedove responses compounded the problem.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

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

I apologize for any unreadable gibberish. It does not look like that here, only in quoted replies from the thread.

Due to the system dorked problem, I am stuck on the live distro. I can only sensibly due email from the provider's mail site. Those gt signs which are really what is fowling things up. HTML is marked up using lt tag gt. Line breaks are also being disrupted.

If someone can plow through any of the version and help me solve my problem, it would be of great help.
This should be plain text formatted. Mail composer highlights the "alternative" rather than actual option, it seems.
Please confirm this is plain text :-)

[toc] | [prev] | [next] | [standalone]

#159605 — Thread dorked. Was: Re: System Dorked -- Help!

Hi,

d_baron@012.net.il wrote:
> I apologize for any unreadable gibberish. It does not look like that here,
> only in quoted replies from the thread.

It seems to become consensus that several different mail clients
were needed to mess it up.
So it seems wise to just give them all no chance by using plain
7 bit US-ASCII and lines shorter than 80 characters.
(My QWERTY keyboard helps to stay disciplined.)


> Please confirm this is plain text :-)

Looks good in my mailbox file, when only vim is interpreting it
and no browser functionality can hide any HTML tags.


David Wright wrote:
> The apparent weirdness is compounded if you press return in the
> reversed text.

My local weirdness was when i tried to copy+paste the salad text
from the web archive and my xterm insisted in showing readable
english text.
I needed several tries until i remembered Franquin's Zorglub
and his secret language. "Eviv Bulgroz !"


> Where did the LRO/RLOs come from; well one might suppose that it could
> be connected with the OP's locale appropriate to residing in IL.

To me it looks like the follow-up quotation got it wrong first.
We'd need to find the list archive in mailbox format in order
to see what changed when.

But d_baron got the mails ASCII-fied meanwhile.


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

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

On Wednesday 21 October 2015 18:39:45 d_baron@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

[toc] | [prev] | [next] | [standalone]

#159576

On 21/10/15 14:56, Renaud (Ron) OLGIATI wrote:
> On Wed, 21 Oct 2015 16:32:40 +0300
> d_baron@012.net.il wrote:
>
>> ----- Original Message -----From: d_baron@012.net.ilDate: Wednesday, October 21, 2015 11:18 amSubject: Re: System Dorked -- Help!To: >debian-user@lists.debian.org> ----- Original Message -----> From: d_baron@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.Going into a live Debian 7, I mounted the old and new partitions, copied the 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.> > Fact is, with certain combination of cabling, I had the bootloader actually work, load the initrd, >and start up, but the new root was not connected so could not proceed. So what can I do about this?> > ‭‮More:I installed to the live distro >lo and ran from command line specifying the configuration file and map. This is what I get:Fatal: Trying to map files from unnamed>device 12 (NFS/RAID mirror down ?)> Ok, no segment fault. If I use the -q option, it will display my boot choices.So, what's next?> ‭‮An 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.Boots up with a load of errors but I am now in a machine called "Kali Linux" 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 t
 o
 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.)<‭‮
>
> Quoting the relevant query: "So what can I do about this?"
>
> Send properly formatted mail, so it is legible ?
>
well, it was perfectly legible here, suggesting the problem may be at 
your end. ;)


-- 
Tony van der Hoff        | mailto:tony@vanderhoff.org
Buckinghamshire, England |

[toc] | [prev] | [next] | [standalone]

#159578

On Wednesday 21 October 2015 10:13:21 Tony van der Hoff wrote:

> On 21/10/15 14:56, Renaud (Ron) OLGIATI wrote:
> > On Wed, 21 Oct 2015 16:32:40 +0300
> >
> > d_baron@012.net.il wrote:
> >> ----- Original Message -----From: d_baron@012.net.ilDate:
> >> Wednesday, October 21, 2015 11:18 amSubject: Re: System Dorked --
> >> Help!To: >debian-user@lists.debian.org> ----- Original Message
> >> -----> From: d_baron@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.Going
> >> into a live Debian 7, I mounted the old and new partitions, copied
> >> the 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.> > Fact is, with certain combination of cabling, I had the
> bootloader actually work, load the initrd, >and start up, but the new
> root was not connected so could not proceed. So what can I do about
> this?> > ‭‮More:I installed to the live distro >lo and ran from
> command line specifying the configuration file and map. This is what I
> get:Fatal: Trying to map files from unnamed>device 12 (NFS/RAID mirror
> down ?)> Ok, no segment fault. If I use the -q option, it will display
> my boot choices.So, what's next?> ‭‮An 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.Boots up with a load of errors but I am now in a
> machine called "Kali Linux" 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 ge t back t
>  o
>  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.)<‭‮
>
> > Quoting the relevant query: "So what can I do about this?"
> >
> > Send properly formatted mail, so it is legible ?
>
> well, it was perfectly legible here, suggesting the problem may be at
> your end. ;)

Sorry to disagree, but both his and your, emails appear to have been 
composed in an html editor, but neither contains a mime-type or mime 
boundary marker header lines.  Without those an email reader cannot tell 
what format the message is in. html encoded text contains lots of html 
markup language as extra text, sometimes even mid-word, and no line 
breaks.

So it is one continuous mass of text, full of giberish html markup 
commands, and is basically an unreadable mess to an email agent 
expecting to see normal ascii text because of the lack of proper mime 
typing.

The solution is to either turn off the html in the editors configuration, 
or enable mime-typing, or change editors.  Whatever works, but this is 
not working for a fully mime compliant email agent.

As for list prefs, the preferences are for plain text, and mid-message or 
bottom posting, preferably inserting your replies to a given question 
immediately after the question has been asked.  In the same order as a 
normal back and forth conversation would be heard by a 3rd party 
listening to it.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#159597

Version without any markup-interpreted markings and should!! be formatted as plain text. Mail site composer box highlights the alternative rather than actual option as it is a link (to a script?). Sorry for any inconvenience.

----- Original Message -----
From: Renaud OLGIATI <renaud@olgiati-in-paraguay.org> (Ron)
Date: Wednesday, October 21, 2015 4:58 pm
Subject: Re: System Dorked -- Help!
To: debian-user@lists.debian.org

On Wed, 21 Oct 2015 16:32:40 +0300
d_baron@012.net.il wrote:

 ----- Original Message -----
From: d_baron@012.net.ilDate:
 Wednesday, October 21, 2015 11:18 amSubject: Re: System Dorked --
 Help!
To: debian-user@lists.debian.org ----- Original Message -
From: d_baron@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.

Going into a live Debian 7, I mounted the old and new
partitions, copied the 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. Fact is, with certain combination of
cabling, I had the bootloader actually work, load the initrd,
and start up, but the new root was not connected so could not
proceed.

So what can I do about this?

More:
Tried lilo installed to the live distro  and ran from command
line specifying the configuration file and map. This is what I get:
Fatal: Trying to  map files from unnamed device 12 (NFS/RAID mirror down ?)
Ok, no segment fault. If I use the -q option, it will display my
boot choices.So, what's next?

And more::
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.

Boots up with a load of errors but I am now in a machine called "Kali
Linux" 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.

So what can I do about this?
‭‮ 

[toc] | [prev] | [next] | [standalone]

#159599

d_baron@012.net.il composed on 2015-10-21 20:45 (UTC+0300):

> ...So what can I do about this?

I'm unable to follow what happened due to lack of partition and disk details.
Maybe others who would try to help have the same problem. Provide output from
fdisk -l or gdisk -l and maybe the help limitation will go away.

Possibly the original problem could be worked around or even solved by chroot
installing Grub to replace Lilo.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#159607

Hi,

Disclaimer: I am much more programmer than sysadmin.

d_baron@012.net.il wrote:
> I had been running an up-to-date Sid so
> maybe that is the problem. The lilo is on the partition,

It is unusual to combine Debian Sid with bootloader LILO.
Installation plants GRUB2 by default.

I never installed GRUB2 other than by netinst ISO and zero-expert
setup. But it is said to automatically recognize partitions with
installed operating systems. Only any special kernel options
would then have to be transplanted from LILO to GRUB2 configuration
file.

Given the dangers of such rescue attempts, i would advise to make
a double backup of any valuable data first.


> but the new root was not connected so could not proceed.

Maybe the Linux kernel is looking for the UUID of the old disk ?
(Would have learned it from initrd or bootloader kernel arguments.)


> I am now in a machine called "Kali Linux"

"Penetration Testing and Ethical Hacking". Probably not what you
need now.
Maybe you are better of with a Knoppix or a Debian LiveCD.
For the minimalist there is RIPLinux.


But how does Kali fail to boot for you ?
I have kali-linux-dev-amd64.iso from last year and it looks like
bootable from DVD and USB stick. Quite like a Debian ISO.

http://docs.kali.org/introduction/kali-linux-default-passwords
"should you decide to boot the live image [...], the i386, amd64,
 VMWare and ARM images are configured with the default root password
 – “toor“, without the quotes."


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#159609

----- Original Message -----
From: Thomas Schmitt <scdbackup@gmx.net>
Date: Wednesday, October 21, 2015 10:31 pm
Subject: Re: System Dorked -- Help!
To: debian-user@lists.debian.org

> Hi,
> 
> Disclaimer: I am much more programmer than sysadmin.
> 
> d_baron@012.net.il wrote:
> > I had been running an up-to-date Sid so
> > maybe that is the problem. The lilo is on the partition,
> 
> It is unusual to combine Debian Sid with bootloader LILO.
> Installation plants GRUB2 by default.
> 
> I never installed GRUB2 other than by netinst ISO and zero-expert
> setup. But it is said to automatically recognize partitions with
> installed operating systems. Only any special kernel options
> would then have to be transplanted from LILO to GRUB2 configuration
> file.
> 
> Given the dangers of such rescue attempts, i would advise to make
> a double backup of any valuable data first.
> 
> 
> > but the new root was not connected so could not proceed.
> 
> Maybe the Linux kernel is looking for the UUID of the old disk ?
> (Would have learned it from initrd or bootloader kernel arguments.)
> 
> 
> > I am now in a machine called "Kali Linux"
> 
> "Penetration Testing and Ethical Hacking". Probably not what you
> need now.
> Maybe you are better of with a Knoppix or a Debian LiveCD.
> For the minimalist there is RIPLinux.
> 
> 
> But how does Kali fail to boot for you ?
> I have kali-linux-dev-amd64.iso from last year and it looks like
> bootable from DVD and USB stick. Quite like a Debian ISO.
> 
> http://docs.kali.org/introduction/kali-linux-default-passwords
> "should you decide to boot the live image [...], the i386, amd64,
>  VMWare and ARM images are configured with the default root 
> password – “toor“, without the quotes."
> 
> 
> Have a nice day :)
> 
> Thomas
> 

Hope all those >'s do not foul this up.

I am using a Debian live CD. So that Kali business comes from there but is nowhere shown when running of the CD. I used to like the Knoppix but his stuff has gone too far out and I cannot use it.

I do not know how to use Grub. The installation had it but when I wanted two kernels around, I had to go back to Lilo. At least I know how that (is supposed to) works.

The new root not connected -- the SATA cable was not in. As I said, I was experimenting with the cables.

[toc] | [prev] | [next] | [standalone]

#159611

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

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web