Re: off topic Question of the day..

2016-07-09 Thread Gene Heskett 
On Saturday 09 July 2016 21:51:52 rhkra...@gmail.com wrote:

> On Saturday, July 09, 2016 07:14:24 PM Gene Heskett wrote:
> > I believe it is. Checking, yes. If that is the correct size, and its
> > truly borderless when selected as "tabloid(borderless)", if the
> > paper guidance can be improved, that would be ideal as when I
> > trimmed it up and put it on a big sheet of light plywood this
> > morning, I was trimming about 1/2" from all 4 edges on average.  And
> > it was set for "A3(borderless)" at the time.  What size in our
> > antiquated inch system is A3?
>
> A3 is what I consider a metric size (well, it is an ISO standard)--in
> inches it is 11.7 x 16.5 in.
>
Humm, wider but shorter.

> If the only choices on that printer feed door are in the A series of
> sizes, that may explain why the feed doesn't work to align the paper
> properly.

I was just trying to set the guides, such as they are, to fit the width 
of the paper, but had to tape then down to hold them as it takes only a 
gram or maybe two to move them, so they slide equal amounts in both 
directions the instant a sheet of paper touches them.  Useless design 
other than the auto center the cross coupling enforces if you tape it 
down so it cannot move.

> I'd start by trimming one sheet of 11x17 paper to 11x16.5 and see if
> that feeds better.
>
> I don't know how easy it is to buy A series paper in the US.

It feeds the short edge in first, unlike the paper trays, both of which 
can be set for several different sizes, but they both feed long edge 
first. So once its been grabbed, there is still about 14.25 inches of 
paper hanging out in empty space with zero guidance because the curl of 
the paper as it passes over the top edge of this "door", lifts the paper 
a good 1/4" above and totally free of the guides. Most worthless design 
I have ever seen.  Paper centering and feed alignment are completely at 
the mercy of the human trying to insert the paper centered and square. 
And I do not believe that if a sheet of Lexan was added to extend the 
paper support for at least 8", and it was screwed to the plastic of the 
door, the stoppers incorporated into the plastic hinges would actually
survive a sheet of tagboard laying on it, combined with the weight of the 
Lexan, too heavy.  A sheet of 28 lb copy paper is ok, but not a hand 
laying on 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

debían jessie bug con multipath

2016-07-09 Thread Ricky Gutierrez 
Hola lista , he estado haciendo algunas pruebas con debían jessie y
una san iscsi , y he notado un comportamiento extraño en cuanto al
multipath , por ejemplo si reinicio los servidores el multipath no se
carga.

como me doy cuenta , si doy un multipath -ll no muestra nada.
Si hago un  multipath -v2 ahí carga la configuración que tengo y
muestra la redundancia , si reinicio vuelve a morir

el multipath carga al inicio

systemctl status multipath-tools

● multipath-tools.service - LSB: multipath daemon

   Loaded: loaded (/etc/init.d/multipath-tools)

   Active: active (exited) since Sat 2016-07-09 20:05:56 CST; 10min ago

  Process: 1455 ExecStart=/etc/init.d/multipath-tools start
(code=exited, status=0/SUCCESS)

alguien ha probado algo similar.

estoy usando la versión 8.5

saludos
-- 
rickygm

http://gnuforever.homelinux.com

Re: reasons to ditch LILO before upgrading to jessie?

2016-07-09 Thread Stephen Powell 
On Sat, Jul 9, 2016, at 18:25, Brian wrote:
> On Sat 09 Jul 2016 at 16:41:24 -0400, Stephen Powell wrote:
>>
>> Long live choice!
> 
> For choice to exist it does not have to be presented as such in the
> installer.
> 

Your point is well taken.  The installer does not offer choice in everything,
just the big things.  A choice of desktop, for example.  However, even
desktop choice is not presented in the installation steps.  It's hidden
in installer options.  For example, I generally install with

   expert desktop=xfce

and then, if I select "Desktop Environment" in tasksel, I get an xfce
desktop instead of a gnome3 desktop.  Perhaps the boot loader choice could be
handled in a similar fashion.  Something like

   expert desktop=xfce bootloader=lilo

with the defaults being gnome3 and grub2, respectively.

(Dare I suggest adding initsystem=sysvinit as an option too?  No, I better not.
I don't want to get that flame war going again.)

Peace.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

Re: Debina 64bits instalar pacote 32bits

2016-07-09 Thread Alcione Ferreira 
Em 09-07-2016 18:02, Listeiro 037 escreveu:
> A mensagem de erro por não usar dpkg como root é
>
> dpkg: erro: não foi possível criar o novo ficheiro
> '/var/lib/dpkg/arch-new': Permissão negada
>
> O estranho é que o comando não criou este arquivo.
>
> O que acontece é que existe um outro arquivo no
> caminho /var/lib/dpkg/arch cujo conteúdo é
>
> amd64
> i386
>
> Tenho a impressão de que o sistema mudou e que não atualizaram a
> mensagem de erro.
>
> Confere?
>
>
> Em Sat, 9 Jul 2016 10:45:37 -0400
> Alcione Ferreira  escreveu:
>
>> Em 08-07-2016 22:03, villani escreveu:
>>> Boa noite,
>>>
>>> Tenho um debian 6 64bits, preciso instalar um pacote 32bits, estou
>>> tentando executar:
>>>
>>> dpkg --add-architecture i386
>>>
>>> dpkg: opção desconhecida --add-architecture
>>>
>>> Escreva dpkg --help para ajuda sobre instalar e desinstalar pacotes
>>> [*]; Utilize `dselect' ou `aptitude' para gestão de pacotes
>>> amigável; Escreva dpkg -Dhelp para uma lista de valores de flags de
>>> debug do dpkg; Escreva dpkg --force-help para uma lista de opções
>>> para forçar operações; Escreva dpkg-deb --help para ajuda sobre
>>> manipular ficheiros *.deb;
>>>
>>> Opções marcadas com [*] produzem muita saída de texto - utilize
>>> pipes com `less' ou `more' !
>>>
>>> dpkg --print-architecture
>>> amd64
>>>
>>> Qual seria o procedimento correto.
>>>
>>> Obrigado
>>>
>>>
>> Bom dia!
>>
>> Vc está usando o comando como root?
>>
>> O procedimento é esse mesmo:
>>
>>> root@sombra:~# dpkg --add-architecture i386
>> Se não funcionar tente um apt-get update && apt-get upgrade
>>
>> Para atualizar o sistema e tentar fazer novamente.
>>
>> Att.
>>
>

pode ser uma possibilidade, o sistema é 64 correto!? se for delete a
linha do arquivo que contém o i386 e tente adicionar novamente.

é uma forma

-- 
Paz e Bem!
Alcione Ferreira
Sombra®
101080
[http://www.alcionesytes.net/]

Liberdade e conhecimento ao alcance de todos.

Office Escritório - http://www.libreoffice.org/
Navegador Firefox - http://www.mozilla.org.br/
Email Thunderbird - http://www.mozilla.org.br/
---
Linux user number 432030 of http://counter.li.org/
---
ICQ: 377035698
Jabber: ksomb...@jabber.org
MSN: alcione.som...@hotmail.com
---
Curriculum: http://lattes.cnpq.br/0545256741852110


0x0D2F8DEF.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: off topic Question of the day..

2016-07-09 Thread rhkramer 
On Saturday, July 09, 2016 07:14:24 PM Gene Heskett wrote:
> I believe it is. Checking, yes. If that is the correct size, and its
> truly borderless when selected as "tabloid(borderless)", if the paper
> guidance can be improved, that would be ideal as when I trimmed it up
> and put it on a big sheet of light plywood this morning, I was trimming
> about 1/2" from all 4 edges on average.  And it was set for
> "A3(borderless)" at the time.  What size in our antiquated inch system is
> A3?

A3 is what I consider a metric size (well, it is an ISO standard)--in inches 
it is 11.7 x 16.5 in.

If the only choices on that printer feed door are in the A series of sizes, 
that may explain why the feed doesn't work to align the paper properly.

I'd start by trimming one sheet of 11x17 paper to 11x16.5 and see if that 
feeds better.

I don't know how easy it is to buy A series paper in the US.

Re: off topic Question of the day..

2016-07-09 Thread Gene Heskett 
On Saturday 09 July 2016 18:30:24 Jörg-Volker Peetz wrote:

> Gene Heskett wrote on 07/09/16 13:55:
> 
>
> > lpoptions -l shows.  So, what label A4, A3, ledger etc is actually
> > 11x17?  In the last 20 years, here in the US,  paper sizes other
> > than
>
> Is Tabloid
> (https://en.wikipedia.org/wiki/Paper_size#North_American_paper_sizes )
> in the list?

I believe it is. Checking, yes. If that is the correct size, and its 
truly borderless when selected as "tabloid(borderless)", if the paper 
guidance can be improved, that would be ideal as when I trimmed it up 
and put it on a big sheet of light plywood this morning, I was trimming 
about 1/2" from all 4 edges on average.  And it was set for 
"A3(borderless)" at the time.  What size in our antiquated inch system is 
A3?

I have too many projects underway. Waiting on some mahogany that won't 
warp like crazy when the Saran wrap comes off for starters.  And I am 
just beginning to make all the pieces to CNC an old Sheldon 11x36 metal 
lathe.  I had some wall reinforcement installed along with improved 
drainage in the basement, so everthing is piled in the middle of the 
floor while I get around to putting additional insulation on the walls 
before I move all the shelving and contents back to a reasonable 
facsimile of where they were. With my bad back, thats going to be slow 
as I engineer how to move stuff thats beyond my ability to pick up and 
carry, some of which will go out a 2 by 3 window about 5'6" up and into 
a trash trailer.  And someplace in the middle of all that is a full 
sized pool table I'd like to use again. If I can bend over far enough to 
run a cue stick.

> Regards,
> jvp.

Thanks JVP.

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

Re: reasons to ditch LILO before upgrading to jessie?

2016-07-09 Thread Felix Miata 

Brian composed on 2016-07-09 21:00 (UTC+0100):


...the installer inexplicably offers a choice between
GRUB and LILO. The installer manual is unhelpful on which to choose. A
newcomer wouldn't have a clue. We do them no service with this retrograde
offering. Get rid of it.


Probably a Bad idea. Apparently there are RAID and/or LVM configurations that 
are incompatible with booting via an inappropriate choice of bootloader. 
Details I cannot provide, as I use both RAID and Grub2 little, Lilo and LVM 
not at al, and don't remember of which I've repeatedly read in various help 
forums.

--
"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/

Re: off topic Question of the day..

2016-07-09 Thread Jörg-Volker Peetz 
Gene Heskett wrote on 07/09/16 13:55:


> lpoptions -l shows.  So, what label A4, A3, ledger etc is actually 
> 11x17?  In the last 20 years, here in the US,  paper sizes other than 

Is Tabloid (https://en.wikipedia.org/wiki/Paper_size#North_American_paper_sizes
) in the list?

Regards,
jvp.

Re: off topic Question of the day..

2016-07-09 Thread Gene Heskett 
On Saturday 09 July 2016 18:28:27 Doug wrote:

> On 07/08/2016 11:45 PM, Gene Heskett wrote:
> > On Friday 08 July 2016 21:35:30 Gene Heskett wrote:
> >> Greetings all;
> >>
> >> I bought, about a month ago, a big Brother MFC, proclaimed that it
> >> could do 11x17 prints when single sheet fed from the slot in the
> >> rear.
> >>
> >> Its a Brother MFC-J6920DW.
> >> So having a rockhopper output file that has been exported as a pdf
> >> by inkscape, I ordered up a ream of 11x17 28lb paper from wallies.
> >>
> >> But I'll be switched if I can find a setting anyplace that will
> >> make it use a sheet of it fed thru the rear slot/door.
> >>
> >> Anybody here got the magic incantation to keep it from shrinking
> >> the image to unusability on the paper in the two front trays?
> >>
> >> Thanks.
> >>
> >> Cheers, Gene Heskett
>
> Slightly OT: Do you have an 11 x 17 scanner? If wo, what kind?

Yes, with an ADF too, on top of the printer.  Works well too.
>
> --doug
>
> > Call in the St. Bernards, I found it. With the pdf loaded into
> > evince I was able to set "current page" in its printer dialog, then
> > it called the system gizmo, and on the 2nd tab was a paper selection
> > pulldown that had the 11x17 selection available. And darned if it
> > didn't work!  Biggest problem was getting the paper started straight
> > enough.  Very poor and downright flimsy guidance hardware for the
> > rear big sheet/odd size input port.
> >
> > Job done and now I know how. ;-)
> >
> >
> > Cheers, Gene Heskett


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

Re: reasons to ditch LILO before upgrading to jessie?

2016-07-09 Thread Brian 
On Sat 09 Jul 2016 at 16:41:24 -0400, Stephen Powell wrote:

> On Sat, Jul 9, 2016, at 16:00, Brian wrote:
> > 
> > All well and good but the installer inexplicably offers a choice between
> > GRUB and LILO. The installer manual is unhelpful on which to choose. A
> > newcomer wouldn't have a clue. We do them no service with this retrograde
> > offering. Get rid of it.
> > 
> > What is the point of a choice? Just offer GRUB; it is the bootloader for
> > Debian and  has many advantages over LILO in todayss Linux ecosystem.
> > People who have a great desire to use LILO can search it out.
> > 
> > Unmaintained in Debian, The bit-rot starts here.
> 
> I am not a member of the Debian installer team, and I am not authorized to
> speak for them.  However, I will make the observation that LILO used to be
> the default boot loader, indeed the only boot loader at one point, in the
> Debian installer for i386/amd64.  I suspect that LILO has been retained as
> an option in the Debian installer for that reason.

Historical reasons for doing something aren't necessarily bad reasons
but there comes a time when a reassessment of what goes into the
installer has to be made. For example, Stretch drops quite a few of what
in Jessie are Standard utilities. Not on technical grounds but because
of their usefulness to most users.

> The lilo package is maintained in Debian.  It's maintainer is Joachim Wiedorn.
> He is also the upstream maintainer.  He has ceased active development of
> lilo, but I believe he still accepts bug reports.  And if he wants rid of it,
> I know a couple of people who are interested in taking it over, myself 
> included.
> So I'm not concerned about it's maintenance status.  As long as there are
> PCs with a BIOS, or a CSM, lilo will remain usable.  If the BIOS/CSM goes,
> lilo goes with it.  lilo can't function without a BIOS/CSM.  But for UEFI-only
> systems, there's elilo as a grub alternative.

That's a good reason for keeping LILO in Debian. I would hope it doesn't
disappear.

> Long live choice!

For choice to exist it does not have to be presented as such in the
installer.

Re: reasons to ditch LILO before upgrading to jessie?

2016-07-09 Thread Brian 
On Sat 09 Jul 2016 at 22:05:45 +0200, Erwan David wrote:

> Le 09/07/2016 à 22:00, Brian a écrit :
> >
> > What is the point of a choice? Just offer GRUB; it is the bootloader for
> > Debian and  has many advantages over LILO in todayss Linux ecosystem.
> > People who have a great desire to use LILO can search it out.
> >
> > Unmaintained in Debian, The bit-rot starts here.
> >
> 
> What is the point of a choice, just use the windows provided with your PC...
> 
> Linux and debian is just about choice given to the user to use what
> he/she thinks is better for him/her.

This is a common misconception. Debian is about providing the best free
operating system possible.

As for choice in the installer, which was the point I made and which you
snipped: where is the choice of printing system, the choice of editor, the
choice of standard utilites such as netcat etc. Choice doesn't exist. Ok,
it does but you have to search it out and get it for yourself if you want
it at installation time.

On the other hand, LILO is presented as an alternative to the default,
well-supported and competent GRUB. No reason given; it's just there,
cluttering up the menu and most likely adding to the confusion of users
who use the expert install. Let those users who want it seek it out.

Re: Debina 64bits instalar pacote 32bits

2016-07-09 Thread Listeiro 037 

A mensagem de erro por não usar dpkg como root é

dpkg: erro: não foi possível criar o novo ficheiro
'/var/lib/dpkg/arch-new': Permissão negada

O estranho é que o comando não criou este arquivo.

O que acontece é que existe um outro arquivo no
caminho /var/lib/dpkg/arch cujo conteúdo é

amd64
i386

Tenho a impressão de que o sistema mudou e que não atualizaram a
mensagem de erro.

Confere?


Em Sat, 9 Jul 2016 10:45:37 -0400
Alcione Ferreira  escreveu:

> Em 08-07-2016 22:03, villani escreveu:
> > Boa noite,
> >
> > Tenho um debian 6 64bits, preciso instalar um pacote 32bits, estou
> > tentando executar:
> >
> > dpkg --add-architecture i386
> >
> > dpkg: opção desconhecida --add-architecture
> >
> > Escreva dpkg --help para ajuda sobre instalar e desinstalar pacotes
> > [*]; Utilize `dselect' ou `aptitude' para gestão de pacotes
> > amigável; Escreva dpkg -Dhelp para uma lista de valores de flags de
> > debug do dpkg; Escreva dpkg --force-help para uma lista de opções
> > para forçar operações; Escreva dpkg-deb --help para ajuda sobre
> > manipular ficheiros *.deb;
> >
> > Opções marcadas com [*] produzem muita saída de texto - utilize
> > pipes com `less' ou `more' !
> >
> > dpkg --print-architecture
> > amd64
> >
> > Qual seria o procedimento correto.
> >
> > Obrigado
> >
> >
> 
> Bom dia!
> 
> Vc está usando o comando como root?
> 
> O procedimento é esse mesmo:
> 
> > root@sombra:~# dpkg --add-architecture i386
> Se não funcionar tente um apt-get update && apt-get upgrade
> 
> Para atualizar o sistema e tentar fazer novamente.
> 
> Att.
>

Re: off topic Question of the day..

2016-07-09 Thread Doug 


On 07/08/2016 11:45 PM, Gene Heskett wrote:

On Friday 08 July 2016 21:35:30 Gene Heskett wrote:


Greetings all;

I bought, about a month ago, a big Brother MFC, proclaimed that it
could do 11x17 prints when single sheet fed from the slot in the rear.

Its a Brother MFC-J6920DW.
So having a rockhopper output file that has been exported as a pdf by
inkscape, I ordered up a ream of 11x17 28lb paper from wallies.

But I'll be switched if I can find a setting anyplace that will make
it use a sheet of it fed thru the rear slot/door.

Anybody here got the magic incantation to keep it from shrinking the
image to unusability on the paper in the two front trays?

Thanks.

Cheers, Gene Heskett

Slightly OT: Do you have an 11 x 17 scanner? If wo, what kind?

--doug

Call in the St. Bernards, I found it. With the pdf loaded into evince I
was able to set "current page" in its printer dialog, then it called the
system gizmo, and on the 2nd tab was a paper selection pulldown that had
the 11x17 selection available. And darned if it didn't work!  Biggest
problem was getting the paper started straight enough.  Very poor and
downright flimsy guidance hardware for the rear big sheet/odd size input
port.

Job done and now I know how. ;-)


Cheers, Gene Heskett

Re: How to prevent /tmp files from being deleted at reboot

2016-07-09 Thread MI 



/tmp is most likely a tmpfs, a filesystem in RAM which will vanish (and
all files and directories in it) as soon as the computer is rebooted.


No, it's a dedicated partition on disk.


But /tmp being wiped on (re)boot has been the norm and case for
UNIX-based operating systems since nearly forever. No program or user
should expect its/his files to persist in /tmp across a reboot. That is
what /var/tmp is for, a temporary place which will not be wiped upon
reboot.


Well, we used to have TMPTIME so that everyone could decide for himself how long 
"temporary" means.


If it's not possible anymore, it's a regression, and it's a Debian bug anyway, since 
the /etc/default/rcS file has a clearly documented setting which is in fact ignored.


But anyway, that's beside the point.

The point is that I cannot get the syntax right to achieve what the systemd 
documentation seems to imply: that it is possible to define when a file should be 
deleted in number of days, indepentently of arbitrary reboots.


So if someone knows what I'm doing wrong in trying to obtain the documented behavior, 
thanks for sharing.


MI


PS:

IMO: If you have a program that relies on files or directories in /tmp
being persistent, then that program is buggy, not Debian.


It's not a program. It's just me, mostly while setting up and testing a fresh system, 
which may need frequent reboots.

Re: reasons to ditch LILO before upgrading to jessie?

2016-07-09 Thread Stephen Powell 
On Sat, Jul 9, 2016, at 16:33, Felix Miata wrote:
> 
> All that's well and good, but I see nothing there that equates to my 
> understanding of the meaning of "editing", which includes removal as well as 
> appending.

Oh, I see what you're saying.  Well, the Linux kernel generally does it's own
overriding.  For example, if the kernel command line contains conflicting 
options,
such as "ro" and "rw", the last one supplied takes precedence.  There are some
exceptions.  For example, if the "console" parameter is specified twice, both
consoles are used.  But, strictly speaking, you're right.  LILO appends options
supplied on the command line to options specified in the "append" configuration
file statement, it does not replace them.
> 
> What I'd like to find which I've had no luck with so far, is finding a Debian 
> installer cmdline option to skip the waste of time that is installation of 
> any bootloader. My disks get generic MBR code and Grub installed by me before 
> any OS gets installed. Thus, I have no need to see warnings about blocklists 
> and unreliability from installers trying to do what I don't want or need done 

If you do the installation in expert mode, you can skip the step to install a
boot loader.  But that's in interactive mode.  I've never done an automated
installation, so I don't know what can and cannot be done in that environment.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

Re: reasons to ditch LILO before upgrading to jessie?

2016-07-09 Thread Stephen Powell 
On Sat, Jul 9, 2016, at 16:00, Brian wrote:
> 
> All well and good but the installer inexplicably offers a choice between
> GRUB and LILO. The installer manual is unhelpful on which to choose. A
> newcomer wouldn't have a clue. We do them no service with this retrograde
> offering. Get rid of it.
> 
> What is the point of a choice? Just offer GRUB; it is the bootloader for
> Debian and  has many advantages over LILO in todayss Linux ecosystem.
> People who have a great desire to use LILO can search it out.
> 
> Unmaintained in Debian, The bit-rot starts here.
> 

I am not a member of the Debian installer team, and I am not authorized to
speak for them.  However, I will make the observation that LILO used to be
the default boot loader, indeed the only boot loader at one point, in the
Debian installer for i386/amd64.  I suspect that LILO has been retained as
an option in the Debian installer for that reason.

The lilo package is maintained in Debian.  It's maintainer is Joachim Wiedorn.
He is also the upstream maintainer.  He has ceased active development of
lilo, but I believe he still accepts bug reports.  And if he wants rid of it,
I know a couple of people who are interested in taking it over, myself included.
So I'm not concerned about it's maintenance status.  As long as there are
PCs with a BIOS, or a CSM, lilo will remain usable.  If the BIOS/CSM goes,
lilo goes with it.  lilo can't function without a BIOS/CSM.  But for UEFI-only
systems, there's elilo as a grub alternative.

Long live choice!

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

Re: reasons to ditch LILO before upgrading to jessie?

2016-07-09 Thread Felix Miata 

Erwan David composed on 2016-07-09 22:05 (UTC+0200):


Brian composed:



What is the point of a choice? Just offer GRUB; it is the bootloader for
Debian...



What is the point of a choice, just use the windows provided with your PC...


:-D


Linux and debian is just about choice given to the user to use what
he/she thinks is better for him/her.


+++
--
"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/

Re: reasons to ditch LILO before upgrading to jessie?

2016-07-09 Thread Felix Miata 

Stephen Powell composed on 2016-07-09 13:19 (UTC-0400):


Felix Miata wrote:



Stephen Powell composed on 2016-07-09 08:58 (UTC-0400):



As for features, LILO has all the features that I need.



One feature it never acquired AFAIK, which Grub shares with Syslinux, is the

 ^

ability to edit the kernel cmdline at boot time, before kernel load. With

  

problematic hardware, problematic BIOS, and pre-release kernel and distro
versions, that ability is a big troubleshooting convenience. It's one of the
features that facilitated my decision to migrate from OS/2 to Linux as
primary OS.



Not true.  I use the traditional text-mode interface of LILO (install=text).
To supply kernel options during boot, press the Shift key (by itself) before
the "delay" timer expires to get a boot prompt ("boot:").  Then type the
label of the kernel you want followed by the desired boot parameters.
For example,



Linux single



to boot the kernel in single-user mode.  Or



Linux forcepae



to get a PAE-requiring kernel to boot on a Banias-class Pentium M or
Celeron M processor, if you forgot to specify



append="forcepae"



in /etc/lilo.conf before running lilo.  If you can't remember the names of
your kernel labels, press the Tab key at a "boot:" prompt.  LILO will
display the names of your kernel labels followed by another "boot:" prompt.


All that's well and good, but I see nothing there that equates to my 
understanding of the meaning of "editing", which includes removal as well as 
appending.



I've never used the menu-based interface of LILO, but I'm sure that there
is a way to supply kernel options at boot time with the menu-based interface
as well.


What I wrote probably assumed too much of the reader, as my use of Grub to 
boot virtually always begins in its Gfxboot incarnation, and on a multi-boot 
PC with various incarnations of pre-release OS installations. I keep Gfxboot 
configured in most cases to place the entirety of kernel appendages for the 
selected stanza in edit mode at the outset, so that I know exactly what to 
expect before proceeding.



See my LILO web page at



http://www.stevesdebianstuff.org/lilo.htm



for more information.



P.S.  I used to use OS/2 as well.  But I switched because OS/2, after Warp 4,
was more or less abandoned by IBM.  Besides, Linux is free.  If I had known
about Linux back then, I would probably have gone straight from DOS to Linux.


More recent incarnations of OS/2 remain the best host for a DOS application I 
still depend on constantly. Some things never get improved upon, or if they 
do, the "improvements" don't add meaningful value for every user context, or 
add complexity that outweighs putative benefit. e.g. for some, 64 bit, which 
is killing off 32 bit in more and more distros. Many don't need more power 
than it takes to run apps that can do everything needed of them in as little 
as an 8 or 16 bit OS, much less 32 or 64.


I'm glad to see Lilo remains available for those who remain content to use 
it. Debian's Grub (Legacy) is too broken for use on installations with EXT4 
filesystems even without 64 bit nodes, while openSUSE's keeps on keeping on 
pleasing me, needing no scripts to maintain to my liking.


What I'd like to find which I've had no luck with so far, is finding a Debian 
installer cmdline option to skip the waste of time that is installation of 
any bootloader. My disks get generic MBR code and Grub installed by me before 
any OS gets installed. Thus, I have no need to see warnings about blocklists 
and unreliability from installers trying to do what I don't want or need done 
in the first place.

--
"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/

Re: reasons to ditch LILO before upgrading to jessie?

2016-07-09 Thread Erwan David 
Le 09/07/2016 à 22:00, Brian a écrit :
>
> What is the point of a choice? Just offer GRUB; it is the bootloader for
> Debian and  has many advantages over LILO in todayss Linux ecosystem.
> People who have a great desire to use LILO can search it out.
>
> Unmaintained in Debian, The bit-rot starts here.
>

What is the point of a choice, just use the windows provided with your PC...

Linux and debian is just about choice given to the user to use what
he/she thinks is better for him/her.

Re: reasons to ditch LILO before upgrading to jessie?

2016-07-09 Thread Brian 
On Sat 09 Jul 2016 at 13:19:08 -0400, Stephen Powell wrote:

> On Sat, Jul 9, 2016, at 10:53, Felix Miata wrote:
> > Stephen Powell composed on 2016-07-09 08:58 (UTC-0400):
> > 
> >> As for features, LILO has all the features that I need.
> > 
> > One feature it never acquired AFAIK, which Grub shares with Syslinux, is 
> > the 
> > ability to edit the kernel cmdline at boot time, before kernel load. With 
> > problematic hardware, problematic BIOS, and pre-release kernel and distro 
> > versions, that ability is a big troubleshooting convenience. It's one of 
> > the 
> > features that facilitated my decision to migrate from OS/2 to Linux as 
> > primary OS.
> 
> Not true.  I use the traditional text-mode interface of LILO (install=text).
> To supply kernel options during boot, press the Shift key (by itself) before
> the "delay" timer expires to get a boot prompt ("boot:").  Then type the
> label of the kernel you want followed by the desired boot parameters.
> For example,
> 
>Linux single
> 
> to boot the kernel in single-user mode.  Or
> 
>Linux forcepae
> 
> to get a PAE-requiring kernel to boot on a Banias-class Pentium M or
> Celeron M processor, if you forgot to specify
> 
>append="forcepae"
> 
> in /etc/lilo.conf before running lilo.  If you can't remember the names of
> your kernel labels, press the Tab key at a "boot:" prompt.  LILO will
> display the names of your kernel labels followed by another "boot:" prompt.
> 
> I've never used the menu-based interface of LILO, but I'm sure that there
> is a way to supply kernel options at boot time with the menu-based interface
> as well.
> 
> See my LILO web page at
> 
>http://www.stevesdebianstuff.org/lilo.htm
> 
> for more information.

All well and good but the installer inexplicably offers a choice between
GRUB and LILO. The installer manual is unhelpful on which to choose. A
newcomer wouldn't have a clue. We do them no service with this retrograde
offering. Get rid of it.

What is the point of a choice? Just offer GRUB; it is the bootloader for
Debian and  has many advantages over LILO in todayss Linux ecosystem.
People who have a great desire to use LILO can search it out.

Unmaintained in Debian, The bit-rot starts here.

Re: Boot probleem

2016-07-09 Thread Frans van Berckel 
Hoi Paul,

On Sat, 2016-07-09 at 20:12 +0200, Paul van der Vlis wrote:
> Hallo,
> 
> Ik heb al vele computer problemen gezien, maar dit nog niet.
> 
> Booten gaat goed, maar na grub en initramfs volgt er alleen een
> knipperende cursor linksboven.
> 
> Als ik de tweede optie van grub kies zie ik iets meer tekst voorbij
> komen, maar niet iets waarvan ik denk dat het van belang is.
> Daarna stopt hij ook.

Als je in Grub op e klikt en naar de boot parameters kijk, ziet je daar
dan iets bijzonders? Je zou init=/bin/bash kunnen proberen.

> Als ik boot van een Debian USB-stick gebeurd er iets soortgelijks.
> Eerst komt grub, na het drukken op "rescue" of "install" niets meer.
> Met meerdere goede USB-sticks geprobeerd.

Staat hier "quiet splash" niet als defaults? Dat weghalen. En misschien
aanvullen met DEBIAN_FRONTEND=text

> Iemand een idee?

Staat mentest toevallig ook in dat rijtje?

> Deze machine heeft het altijd goed gedaan maar is wat ouder. AMD
> processor en ATI/AMD graphics in het moederbord. RAID1. Twee
> monitoren (beide geven beeld tijdens booten). Ik zit te denken aan
> een probleem met de GPU, die een bepaalde mode niet meer aankan. Dus
> misschien er een videokaart insteken.

Is er misschien iets met betrekking tot de boot (lees de EFI / UEFI /
Disk settings) in de bios veranderd? Of iets anders aan de hardware?

Met vriendelijke groet,


Frans van Berckel

Boot probleem

2016-07-09 Thread Paul van der Vlis 
Hallo,

Ik heb al vele computer problemen gezien, maar dit nog niet.

Booten gaat goed, maar na grub en initramfs volgt er alleen een
knipperende cursor linksboven.

Als ik de tweede optie van grub kies zie ik iets meer tekst voorbij
komen, maar niet iets waarvan ik denk dat het van belang is.
Daarna stopt hij ook.

Als ik boot van een Debian USB-stick gebeurd er iets soortgelijks. Eerst
komt grub, na het drukken op "rescue" of "install" niets meer. Met
meerdere goede USB-sticks geprobeerd.

Iemand een idee?

Deze machine heeft het altijd goed gedaan maar is wat ouder. AMD
processor en ATI/AMD graphics in het moederbord. RAID1. Twee monitoren
(beide geven beeld tijdens booten). Ik zit te denken aan een probleem
met de GPU, die een bepaalde mode niet meer aankan. Dus misschien er een
videokaart insteken.

Met vriendelijke groet,
Paul van der Vlis.


-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Re: How to prevent /tmp files from being deleted at reboot

2016-07-09 Thread Sven Hartge 
MI  wrote:

> In Debian Jessie, systemd ignores the TMPTIME variable in /etc/default/rcS 
> and just 
> blindly deletes everything on every reboot.

> A bug has been filed about it:  "#795269 TMPTIME not honored anymore"
> ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795269 )

> But I tried the suggested solution, and the files in /tmp still get deleted 
> at reboot.

> What I currently have which doesn't work:

>$ egrep -v '^(#|$)' /etc/tmpfiles.d/tmp.conf
>D /tmp 1777 root root 30d
>x /tmp/systemd-private-%b-*
>X /tmp/systemd-private-%b-*/tmp
>x /var/tmp/systemd-private-%b-*
>X /var/tmp/systemd-private-%b-*/tmp

> Would someone know what I can do so that only files older than some number of 
> days 
> get deleted?

/tmp is most likely a tmpfs, a filesystem in RAM which will vanish (and
all files and directories in it) as soon as the computer is rebooted.

But /tmp being wiped on (re)boot has been the norm and case for
UNIX-based operating systems since nearly forever. No program or user
should expect its/his files to persist in /tmp across a reboot. That is
what /var/tmp is for, a temporary place which will not be wiped upon
reboot.

I regard /tmp being cleared on (re)boot as a feature, not a bug.

The FHS says that "On most systems, this directory is cleared out at
boot or at shutdown by the local system. The basis for this was
historical precedent and common practice. However, it was not made a
requirement because system administration is not within the scope of the
FSSTND. For this reason people and programs must not assume that any
files or directories in /tmp are preserved between invocations of the
program. The reasoning behind this is for compliance with IEEE standard
P1003.2 (POSIX, part 2)."

IMO: If you have a program that relies on files or directories in /tmp
being persistent, then that program is buggy, not Debian.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: reasons to ditch LILO before upgrading to jessie?

2016-07-09 Thread Stephen Powell 
On Sat, Jul 9, 2016, at 10:53, Felix Miata wrote:
> Stephen Powell composed on 2016-07-09 08:58 (UTC-0400):
> 
>> As for features, LILO has all the features that I need.
> 
> One feature it never acquired AFAIK, which Grub shares with Syslinux, is the 
> ability to edit the kernel cmdline at boot time, before kernel load. With 
> problematic hardware, problematic BIOS, and pre-release kernel and distro 
> versions, that ability is a big troubleshooting convenience. It's one of the 
> features that facilitated my decision to migrate from OS/2 to Linux as 
> primary OS.

Not true.  I use the traditional text-mode interface of LILO (install=text).
To supply kernel options during boot, press the Shift key (by itself) before
the "delay" timer expires to get a boot prompt ("boot:").  Then type the
label of the kernel you want followed by the desired boot parameters.
For example,

   Linux single

to boot the kernel in single-user mode.  Or

   Linux forcepae

to get a PAE-requiring kernel to boot on a Banias-class Pentium M or
Celeron M processor, if you forgot to specify

   append="forcepae"

in /etc/lilo.conf before running lilo.  If you can't remember the names of
your kernel labels, press the Tab key at a "boot:" prompt.  LILO will
display the names of your kernel labels followed by another "boot:" prompt.

I've never used the menu-based interface of LILO, but I'm sure that there
is a way to supply kernel options at boot time with the menu-based interface
as well.

See my LILO web page at

   http://www.stevesdebianstuff.org/lilo.htm

for more information.

P.S.  I used to use OS/2 as well.  But I switched because OS/2, after Warp 4,
was more or less abandoned by IBM.  Besides, Linux is free.  If I had known
about Linux back then, I would probably have gone straight from DOS to Linux.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

How to prevent /tmp files from being deleted at reboot

2016-07-09 Thread MI 
In Debian Jessie, systemd ignores the TMPTIME variable in /etc/default/rcS and just 
blindly deletes everything on every reboot.


A bug has been filed about it:  "#795269 TMPTIME not honored anymore"
( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795269 )

But I tried the suggested solution, and the files in /tmp still get deleted at 
reboot.

What I currently have which doesn't work:

   $ egrep -v '^(#|$)' /etc/tmpfiles.d/tmp.conf
   D /tmp 1777 root root 30d
   x /tmp/systemd-private-%b-*
   X /tmp/systemd-private-%b-*/tmp
   x /var/tmp/systemd-private-%b-*
   X /var/tmp/systemd-private-%b-*/tmp


Would someone know what I can do so that only files older than some number of days 
get deleted?

Re: reasons to ditch LILO before upgrading to jessie?

2016-07-09 Thread Felix Miata 

Stephen Powell composed on 2016-07-09 08:58 (UTC-0400):


As for features, LILO has all the features that I need.


One feature it never acquired AFAIK, which Grub shares with Syslinux, is the 
ability to edit the kernel cmdline at boot time, before kernel load. With 
problematic hardware, problematic BIOS, and pre-release kernel and distro 
versions, that ability is a big troubleshooting convenience. It's one of the 
features that facilitated my decision to migrate from OS/2 to Linux as 
primary OS.

--
"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/

Re: Debina 64bits instalar pacote 32bits

2016-07-09 Thread Alcione Ferreira 
Em 08-07-2016 22:03, villani escreveu:
> Boa noite,
>
> Tenho um debian 6 64bits, preciso instalar um pacote 32bits, estou tentando 
> executar:
>
> dpkg --add-architecture i386
>
> dpkg: opção desconhecida --add-architecture
>
> Escreva dpkg --help para ajuda sobre instalar e desinstalar pacotes [*];
> Utilize `dselect' ou `aptitude' para gestão de pacotes amigável;
> Escreva dpkg -Dhelp para uma lista de valores de flags de debug do dpkg;
> Escreva dpkg --force-help para uma lista de opções para forçar operações;
> Escreva dpkg-deb --help para ajuda sobre manipular ficheiros *.deb;
>
> Opções marcadas com [*] produzem muita saída de texto - utilize pipes com 
> `less' ou `more' !
>
> dpkg --print-architecture
> amd64
>
> Qual seria o procedimento correto.
>
> Obrigado
>
>

Bom dia!

Vc está usando o comando como root?

O procedimento é esse mesmo:

> root@sombra:~# dpkg --add-architecture i386
Se não funcionar tente um apt-get update && apt-get upgrade

Para atualizar o sistema e tentar fazer novamente.

Att.

-- 
Paz e Bem!
Alcione Ferreira
Sombra®
101080
[http://www.alcionesytes.net/]

Liberdade e conhecimento ao alcance de todos.

Office Escritório - http://www.libreoffice.org/
Navegador Firefox - http://www.mozilla.org.br/
Email Thunderbird - http://www.mozilla.org.br/
---
Linux user number 432030 of http://counter.li.org/
---
ICQ: 377035698
Jabber: ksomb...@jabber.org
MSN: alcione.som...@hotmail.com
---
Curriculum: http://lattes.cnpq.br/0545256741852110


0x0D2F8DEF.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: "sources.list" para Debian 6.0 Squeeze que funcione.

2016-07-09 Thread Camaleón 
El Fri, 08 Jul 2016 18:51:47 -0500, limpia escribió:

> Saludos,
>   Gracias, Estaba pensando en publicar lo mismo, pero lo veo todo listo
> es contestada, por lo que sólo añadir, también utilizo este:
> https://archive.debian.net/squeeze-backports/
>   Si me sierve buen, todos los
> paguettes por Debian 6 y atraz es en los  archivos, de
> https://archive.debian.net/
>   Bueno, es todo,
> Hasta luego

Yo usaría mejor el dominio "oficial":

Paquetes y parches
http://archive.debian.org

Archivador de versiones
http://snapshot.debian.org/

Saludos,

-- 
Camaleón

Re: particionado en preseed con varios discos

2016-07-09 Thread Camaleón 
El Fri, 08 Jul 2016 17:22:20 -0300, Javier Marcon escribió:

> El 08/07/16 a las 14:35, Camaleón escribió:

(...)

>>> Gracias, eso fué lo primero que había pensado pero necesito elegir el
>>> disco cuando hay mas de un disco.

>> Entendido. Pero es lógico que si tienes que elegir el disco manualmente
>> también te pregunte por la partición ¿no?

> A mi me parece que no es tan así, porque yo le digo expresamente como
> particionar pero no le digo cual disco particionar, entonces lo lógico
> sería que cuando le especifico el disco aplique el esquema de
> particinado que le digo. Para ponerlo mas entendible, es como si a mi
> esposa le digo "Pagale $ 300 cuando venga a cobrar." y vienen 2 juntos a
> cobrar, entonces mi esposa me pregunta a cual de los 2 le da los $ 300.

Tienes que ponerte en las carnes del instalador no de tu esposa :-)

¿Y si tienes en el mismo disco duro dos (o más) particiones cifradas? 
¿Cuál elije? Para que el instalador vaya a tiro fijo (automático) tienes 
que buscar un parámetro primero que lo reconozca y segundo que no admita 
ambigüedades y que sólo pueda devolver una opción. En cualquier otro caso 
dará error o te tendrá que preguntar.

>> Claro, porque no existe ese disco. Mira a ver qué valores te permite
>> definir la opción pero me temo que el modo automático no es compatible
>> con el modo manual y lo que buscas es una mezcla de ambos:
>>
>> d-i partman-auto/init_automatically_partition
>>
> Le puse sdz por las dudas para que no me sobreescriba de prepo un disco
> sin preguntar, previendo que podia no funcionar la opcion seen.
> 
> Yo tengo comentada la opción d-i
> partman-auto/init_automatically_partition en el archivo preseed, y en
> www.debian.org/releases/stable/i386/apbs05.html.en dice que puedo usar
> seen false para que fuerce a que me muestre las preguntas. Por eso creí
> que iba a mostrarme la pregunta del disco y luego aplicar el
> particionado que le digo.

Pues mira a ver si puedes hacer algo con ese valor para que te permita 
seleccionar automáticamente la partición que quieres.

> El d-i partman/early_command corre en background o puedo hacer un script
> bash que me permita especificar el disco con read y luego se lo pase a
> la opción partman-auto/disk ? Si hago el script, como puedo hacer que el
> script muestre para elegir tipo combo (en modo texto) los discos para
> elegir uno?

No sé si permite hacer eso, pregunta mejor en la lista debian-boot¹ que 
seguro te podrán indicar mejro si es posible lo que buscas y cómo hacerlo.

¹https://lists.debian.org/debian-boot/

Saludos,

-- 
Camaleón

Re: particionado en preseed con varios discos

2016-07-09 Thread Javier Marcon 
El 08/07/16 a las 17:22, Javier Marcon escribió:
> ...
Hice un script para que me pregunte que disco quiero usar (el script
está en http://pastebin.com/D0QdqX6V ) y en el archvo preseed puse la
opción:

d-i partman/early_command string sh select_disk.sh

Pero al ejecutar el instalador, en lugar de mostrarme la pregunta, el
instalador me dice que el script devolvió código de error 2. Si ejecuto
el script desde la consola del instalador (apretando ctrl+alt+F2).
Alguien sabe como puedo hacer que el script corra en foreground y me
pida la pregunta para elegir el disco y hacer el particionado automático
en el disco elegido?

Gracias,

Javier.

Re: reasons to ditch LILO before upgrading to jessie?

2016-07-09 Thread Stephen Powell 
On Thu, Jul 7, 2016, at 20:53, Felix Miata wrote:
> Stephen Powell composed on 2016-07-07 20:30 (UTC-0400):
> 
> > If your system has a BIOS and a traditional DOS-style partition table,
> > there's no reason not to use LILO, unless you just don't want to.
> 
> Or, if you like to be able to boot without hunting down rescue media even 
> though you forgot to "rerun" some configuration utility after a kernel 
> upgrade. Once you understand how Grub's shell works, which includes command 
> history and tab completion much the same as *ash, it is simple (maybe not so 
> much in Grub2, which I don't use, as in Grub, which accounts for about 97% of 
> my bootloader installations). Grub's shell has built-in help. With Grub, 
> there's no reason to be scared when an expected boot menu doesn't show up.
> ...

I've been using LILO for about 16 years, and I've never had to use rescue
media because I forgot to run lilo.  Modern Debian systems make sure that
lilo gets run when it needs to be run.  As for features, LILO has all the
features that I need.  Chiefly, it has the feature of being able to load the
Linux kernel into storage (and it's initial RAM file system image) and transfer
control to it.  It does one thing, and it does that one thing very well: it
loads the Linux kernel.  I believe in the KISS philosophy (Keep It Simple,
Stupid).  If you're happy with grub-legacy, great.  I'm happy for you.
Keep using it.  I'm happy with LILO, and I intend to keep using it.  And
apparently, the OP is happy with LILO too; and there's no reason, at least
at this point, why *he* shouldn't keep using it. 

Inside every large program is a small program struggling to get out -- Hoare's
law of large programs.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

Re: off topic Question of the day..

2016-07-09 Thread Gene Heskett 
On Saturday 09 July 2016 02:56:38 Jörg-Volker Peetz wrote:

> With cups-client all printer specific options can be listed with
>
>   lpoptions -l
>
> To select a specific printer add '-p '. See 'man
> lpoptions' or http://localhost:631/help .
>
> Regards,
> jvp.

Thats informative, but the printers rear input door, which doesn't open 
far enough to make reading its markings embossed in black plastic easily 
readable, and is marked in similar labeling as the output of 
lpoptions -l shows.  So, what label A4, A3, ledger etc is actually 
11x17?  In the last 20 years, here in the US,  paper sizes other than 
letter have become special order only. One of the reasons I bought this 
printer was its large size capability greatly simplify's this particular 
modern machine shop need, although I am less than impressed with its 
paper guidance facility. It seriously needs a longer input tray than the 
teeny little 2" door it has.

Because the cross-coupled guides on this door are only about 1/8" high, I 
was forced to fix them in position with scotch-tape because they move so 
easily. And I may yet build a longer table for it, with additional 
guides to help align the sheet during the insertion process.  OTOH, a 
500 sheet ream will be more than a lifetime supply. :)  And I'll have to 
make a box to hold this paper, and mount it else the corners will be 
damaged as its moved around here in this midden heap called the 
coyote.den.  But that's my problem isn't it? :-)

Many Thanks.  When nearly everything now has a gui, one tends to forget 
the command line attack.

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

Re: debian wifi install

2016-07-09 Thread Curt 
On 2016-07-08, Jude DaShiell  wrote:
> Install was successful this time since I now have rt2870.bin available for 
> debian to install and use.  Unfortunately, the installer did not save the 
> network configuration it figured out and used to my new system.  Has 
> anyone got a good url describing what to do with iwconfig and other 
> utilities to get a ralink 2870 adapter running post-install?
>

What about all this stuff on the innertubes?

https://wiki.debian.org/rt2800usb
https://wiki.debian.org/WiFi/HowToUse

-- 
Même l’avenir n’est plus ce qu’il était. 
Paul Valéry

Re: Gestionnaire de paquets Synaptic

2016-07-09 Thread Bernard Schoenacker 
Le Sat, 09 Jul 2016 02:42:15 +,
Alex PADOLY  a écrit :

>  
> 
> Bonjour à tous, 
> 
> La commande apt-get à renvoyé les informations
> suivantes à la fin du procéssus: 
> 
> W: Impossible de récupérer
> http://ftp.debian.org/debian/wheezy-updates/dists/main/contrib/binary-i386/Packages
> 404 Not Found [IP : 130.89.148.12 80]
> 
> W: Impossible de récupérer
> http://ftp.debian.org/debian/wheezy-updates/dists/main/non-free/binary-i386/Packages
> 404 Not Found [IP : 130.89.148.12 80]
> 
> W: Impossible de récupérer
> http://ftp.us.debian.org/debian/dists/main/contrib/binary-i386/Packages
> 404 Not Found [IP : 128.61.240.89 80]
> 
> W: Impossible de récupérer
> http://ftp.us.debian.org/debian/dists/main/non-free/binary-i386/Packages
> 404 Not Found [IP : 128.61.240.89 80]
> 
> W: Impossible de récupérer
> http://security.debian.org/wheezy/updates/dists/main/contrib/binary-i386/Packages
> 404 Not Found [IP : 149.20.20.19 80]
> 
> W: Impossible de récupérer
> http://security.debian.org/wheezy/updates/dists/main/non-free/binary-i386/Packages
> 404 Not Found [IP : 149.20.20.19 80]
> 
> W: Impossible de récupérer
> http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/Debian_7.0/./Release
> 
> 
> W: Le téléchargement de quelques fichiers d'index a échoué, ils
> ont été ignorés, ou les anciens ont été utilisés à la
> place.
> 
> Concernant mon fichier source.list, voici son contenu: 
> 
> deb
> http://ftp.us.debian.org/debian main contrib non-free
> deb
> http://ftp.debian.org/debian/wheezy-updates main contrib non-free
> deb
> http://security.debian.org/wheezy/updates main contrib non-free
> deb
> cdrom:[Debian GNU/Linux 7 _Wheezy_ - Official Snapshot i386
> LIVE/INSTALL Binary 20150114-04:46]/ wheezy main
> deb
> http://http.us.debian.org/debian/ wheezy contrib non-free main
> deb
> http://download.opensuse.org/repositories/home:/DarkPlayer:/Pipelight/Debian_7.0/
> ./
> # deb http://download.jitsi.org/deb unstable/ 
> 
> Merci pour vos
> réponses. 
> 
> Le 2016-07-08 13:05, Bernard Schoenacker a écrit : 
> 
> > Le
> Fri, 08 Jul 2016 12:18:19 +,
> > Alex PADOLY
>  a écrit :
> > 
> >> Bonjour à tous, Depuis
> quelques temps, mon gestionnaire ne peut télécharger entièrement les
> paquets d' une application , il indique l'information suivante:
> "Certains paquets ne peuvent pas être téléchargés depuis le serveur,
> voulez-vous continuez" Qu'en pensez-vous? Merci beaucoup. Alex PADOLY
> >
> 
> > bonjour,
> > 
> > serait il possible d'essayer de lancer (?) :
> > 
> > sudo
> apt-get update --fix-missing
> > 
> > ensuite quel est ton sources.list ?
> >
> (à comparer avec la piéce jointe)
> > 
> > slt
> > bernard
> 
>  

bonjour,

ci joint le sources.list qui est à jour pour wheezy :

https://wiki.debian.org/StableUpdates
https://wiki.debian.org/DebianWheezy#Debian_Wheezy_Life_cycle


et il faut essayer de faire :

sudo apt-get update --fix-missing

slt
bernard

sources.list
Description: Binary data

Re: off topic Question of the day..

2016-07-09 Thread Jörg-Volker Peetz 
With cups-client all printer specific options can be listed with

  lpoptions -l

To select a specific printer add '-p '. See 'man lpoptions' or
http://localhost:631/help .

Regards,
jvp.