debian-user@lists.debian.org your Ref is 52114-975

[Admin Email]

Attn: % debian-user@lists.debian.org %

Some days ago your email debian-user@lists.debian.org was rewarded, please did 
you get the details of the email?

Angy Omari
(Contact Manager)
omaria...@yandex.com

Console fonts, was Re: Jessie for Udoo X86?

[David Wright]

On Sun 23 Apr 2017 at 18:55:03 (-0700), Larry Dighera wrote:

> I'd like to have more lines/rows and columns on the console tty.  I've read
> that 'vidcontrol' may do what I want, unfortunately 'apt-cache show
> vidcontrol' reports that it is virtual (unavailable).  
> 
> I am grateful for any clues you may be able to provide.

Best to start a new thread with a new subject, but anyway…

The Debian Way to set a default font for dmesg output, login prompt,
etc is (I think) to edit /etc/default/console-setup
I like Terminus fonts (package console-setup-linux, I think),
so I have:

ACTIVE_CONSOLES="/dev/tty[1-6]"
CHARMAP="UTF-8"
CODESET="Lat15"
#FONTFACE="Fixed"
FONTFACE="Terminus"
FONTSIZE="10x20"
#FONTSIZE="12x24"
#FONTSIZE="14x28"
#FONTSIZE="16x32"
VIDEOMODE=

in there, with various sizes available.

However, I prefer using aliases like:

alias my-font-tiny="setfont Lat15-Terminus12x6"
alias my-font-small="setfont Lat15-Terminus14"
alias my-font-medium="setfont Lat15-Terminus20x10"
alias my-font-large="setfont Lat15-Terminus24x12"
alias my-font-huge="setfont Lat15-Terminus28x14"
alias my-font-vast="setfont Lat15-Terminus32x16"

because you can then have different font sizes on each VC.
I also have a bash function to choose an arbitrary font:

function my-font-usr-share-consolefonts {
[ -z "$1" ] && printf '%s\n' "Usage: $FUNCNAME 
/usr/share/consolefonts/.psf.gz
sets the specified font on the current VC.
The command name serves as a reminder of the fonts' location.
Use filename-completion to specify the appropriate filename.
Redundant elements of the filename are stripped out before use.
Typically, filenames start Lat15- or Uni." >&2 && return 1
local FILENAME="$(basename "$1")"
setfont "${FILENAME%%.*}"
}

Typing my-font reminds me of the name of the command,
and the name of the command reminds me of the path to type in.
 then lists the font files to use filename completion on.

Cheers,
David.

Re: funny times

[Rick Thomas]

Do you use ntp?  

 sudo aptitude install ntp

Rick

On Apr 23, 2017, at 6:33 PM, songbird  wrote:

>  when my computer is turned off the clock
> runs slow.
> 
>  when my computer is turned on the clock 
> runs fast.
> 
>  so any single adjustment in /etc/adjtime
> doesn't work (as my number of hours off or
> on the computer each day may change).
> 
>  *chuckles*
> 
> 
>  songbird
> 

Re: OT Big Dummy mutt question

[songbird]

Bob Bernstein wrote:
> On Sun, 23 Apr 2017, songbird wrote:
>
>>  i'm using the version of mutt in testing/stretch
>> and can say that i have no setting in .muttrc at
>> all and it just works.
>
> I tried the "no setting in .muttrc" and that did the trick.
>
> Which strikes me as sorta weird, but then, with so much 
> weirdness around nowadays, why pick on mutt?
>
> What should we call that approach, Alt-Minimalist?
>
> Incidentally:
>
> $ mutt -v | grep SPELL
> -ISPELL

  ha!  interesting!  :)


> $ which ispell
> /usr/bin/ispell
>
> Thanks all!

  y.w.  :)  glad it is working.


  also interesting to compare:

$  mutt -v | grep SPELL

ISPELL="/usr/bin/ispell"

  (currently at version: NeoMutt 20170113 (1.7.2) on i386)


  songbird

Re: OT Big Dummy mutt question

[Bob Bernstein]

On Sun, 23 Apr 2017, songbird wrote:


 i'm using the version of mutt in testing/stretch
and can say that i have no setting in .muttrc at
all and it just works.


I tried the "no setting in .muttrc" and that did the trick.

Which strikes me as sorta weird, but then, with so much 
weirdness around nowadays, why pick on mutt?


What should we call that approach, Alt-Minimalist?

Incidentally:

$ mutt -v | grep SPELL
-ISPELL

$ which ispell
/usr/bin/ispell

Thanks all!

--
"Natasha! First we shoot jet, then we go after moose and squirrel."

Re: Jessie for Udoo X86?

[Larry Dighera]

David,

Thank you for you great response to my inquiry.  Very much appreciated.

My comments in-line below:


On Thu, 20 Apr 2017 14:14:40 -0500, David Wright 
wrote:

>On Thu 20 Apr 2017 at 07:11:53 (-0700), Larry Dighera wrote:
>
>> What I have discovered thus far, is that Debian wants to launch X11 by
>> default, instead of the command line UI.  That appears to result in a black
>> screen with a frozen system.  
>> 
>> At this point, I have no idea of the correct way to boot to the command line
>> interface, so I temporarily renamed lightdm, and now it boots to the command
>> line interface apparently after X11 fails to launch.  So, it appears that it
>> is X11 that has possible issues with the hardware or is misconfigured.
>> Perhaps there is something in X11's /var/log file that will provide a clue
>> about why it was failing to successfully launch.
>> 
>> So, it appears that grub is correctly configured after all.  
>> 
>> What is the correct way to configure the system to boot to the command line
>> UI instead of X11?  Do I need to edit things, or add files to, /etc/rc.d
>> someplace?  Or is there a higher-level way to tell systemd that I prefer to
>> manually launch X11?  
>
>For jessie/systemd,
>
># systemctl set-default multi-user.target
>
>and, to revert,
>
># systemctl set-default graphical.target
>

That worked perfectly.  Thank you very much.

>
>Removing the display manager was, I think, the old way.
>Not installing one, OTOH, is still the normal way if
>you don't want a DE (like me).
>
>> I'm aware that running the startx script is a reasonable way to launch X11
>> when I want it, but I'll have to diagnose its issue(s) first.  My past
>> familiarity with AT Unix from the early '80s through the '90s was pre-X11,
>> so I'm going to have to learn how to administrate X11 now I suppose.  
>> 
>> I sincerely appreciate your kind efforts in guiding me.  I gives me the
>> motivation to continue spending the time to get Jessie up on the new Udoo
>> X86 platform.
>
>There are several recent threads in this list about getting the
>right video drivers and X servers installed. Most of it goes
>over my head because my hardware is so old.
>
>Cheers,
>David.

I'll have to search the list archives.  Thank you for the pointer.


I'd like to have more lines/rows and columns on the console tty.  I've read
that 'vidcontrol' may do what I want, unfortunately 'apt-cache show
vidcontrol' reports that it is virtual (unavailable).  

I am grateful for any clues you may be able to provide.

Best regards,
Larry

Re: new firefox for wheezy last night, can't do squat on the net today.

[Patrick Bartek]

On Sun, 23 Apr 2017 19:33:12 -0500 David Wright
 wrote:

> [Big Snip]
> > > None of which ever worked 100% because the web pages all seemed
> > > to be using a different version.  The "it works here" syndrome,
> > > essentially the same as the N.I.H. beliefs. :(
> > 
> > Well, I'm glad flash is dying.  Wish it would do so faster.
> 
> If you don't like flash, then don't use it. Don't install it if
> you're worried you might accidently use it involuntarily.
> But why the spite? Can't people who don't like flash just leave
> the flash users alone? Where's the freedom in that attitude?

I don't for the vast majority of my web browsing.  Unfortunately, a few
sites I need for my business or frequent otherwise won't work properly
without it. So, I have little choice.  For those I use Firefox with
flashplayer installed. For all others, I use Chrome with pepperflash
disabled.

The spite?  Maybe, it's from having to repeatably, clean friends'
systems -- Windows -- where Flash videos have been used to infect them
with various and sundry malwares, over and over..

I never criticize flash users, only flash and Adobe for the security
issues. If you want to use it, go ahead.

B

funny times

[songbird]

  when my computer is turned off the clock
runs slow.

  when my computer is turned on the clock 
runs fast.

  so any single adjustment in /etc/adjtime
doesn't work (as my number of hours off or
on the computer each day may change).

  *chuckles*


  songbird

Re: OT Big Dummy mutt question

[songbird]

Bob Bernstein wrote:
> Mutt (1.5.23) is rebuffing my every attempt to get ispell 
> working. Currently I have in .muttrc:
>
> set ispell="ispell --mode=email"
>
> This threw no error when mutt launched, so it was with high 
> spirits that I tried to send off deliberately misspelled emails. 
> Alas and alack. these arrived at their intended destinations 
> with their test misspellings intact.
>
> Could it be (he asked) that spell-checking in mutt does not 
> follow on auto-magically (if that is the word I'm looking for 
> here) via the bare expedient of creating an entry in .muttrc 
> such as is on display several lines above?
>
> Throwing myself on Google's mercy leads me to believe that the 
> only editor permitted (so to speak) with mutt is vim. I refuse 
> to accept this, and, if found to be true, would protest in the 
> strongest available terms through proper channels.
>
> Please help.

  i'm using the version of mutt in testing/stretch
and can say that i have no setting in .muttrc at
all and it just works.

  what does mutt -v | grep SPELL say?

and/or:

  if you remove your set line does it work?

  or if you use /usr/bin/ispell?



  songbird

Re: OT Big Dummy mutt question

[Bob Bernstein]

On Sun, 23 Apr 2017, David Wright wrote:

According to my key bindings, you should press i when in the 
compose menu [...]


Yes, my 'help' there also shows i associated with ispell. But 
pressing i only causes the screen to blip very momentarily 
without showing any ispell activity and then return to where it 
was. No change is made to the message.


ispell seems functional when tried from the command line.

:(


--
"Natasha! First we shoot jet, then we go after moose and squirrel."

Re: OT Big Dummy mutt question

[David Wright]

On Sun 23 Apr 2017 at 19:47:49 (-0400), Bob Bernstein wrote:
> Mutt (1.5.23) is rebuffing my every attempt to get ispell working.
> Currently I have in .muttrc:
> 
> set ispell="ispell --mode=email"
> 
> This threw no error when mutt launched, so it was with high spirits
> that I tried to send off deliberately misspelled emails. Alas and
> alack. these arrived at their intended destinations with their test
> misspellings intact.
> 
> Could it be (he asked) that spell-checking in mutt does not follow
> on auto-magically (if that is the word I'm looking for here) via the
> bare expedient of creating an entry in .muttrc such as is on display
> several lines above?

According to my key bindings, you should press i when in the compose
menu, the one where you then press y to send it, or e to edit it again.
At this point, the message is in /tmp or /var/tmp or wherever you
configured it.

> Throwing myself on Google's mercy leads me to believe that the only
> editor permitted (so to speak) with mutt is vim. I refuse to accept
> this, and, if found to be true, would protest in the strongest
> available terms through proper channels.

Eh? You can use any editor; I use emacs. You should put
set editor="invocation command and parameters"
in the same file as the ispell setting.

/usr/share/doc/mutt/manual.txt*

Cheers,
David.

Re: new firefox for wheezy last night, can't do squat on the net today.

[David Wright]

On Sun 23 Apr 2017 at 15:42:35 (-0700), Patrick Bartek wrote:
> On Sun, 23 Apr 2017 15:41:30 -0400 Gene Heskett 
> wrote:
> 
> > On Sunday 23 April 2017 15:15:05 Patrick Bartek wrote:
> > 
> > > On Sun, 23 Apr 2017 00:21:28 -0400 Gene Heskett
> > > 
> > >
> > > wrote:
> > > > On Saturday 22 April 2017 23:22:45 Patrick Bartek wrote:
> > > > > On Sat, 22 Apr 2017 12:24:32 -0400 Gene Heskett
> > > > > 
> > > > >
> > > > > wrote:
> > > > > > Went to newegg.com to look for some optical fiber but the
> > > > > > front page, while I think its alive, did not respond to a
> > > > > > mouse click on any product link. I hope its not contagious.
> > > > > >
> > > > > > Many news sites are saying "request entity too large" also.
> > > > >
> > > > > Works fine here.  Although rendering sometimes is sluggish -- a
> > > > > few seconds longer.  Could be Cox Internet.  They get slow at
> > > > > times.  Version 45.9.0 with the latest flashpalyer 25.0.0.148
> > > > > installed yesterday
> > > > >
> > > > > B
> > > >
> > > > And how do you get that 10 year newer flash?  The adobe site
> > > > doesn't show me anything newer than the 11.xx.xx.xxx stuff.
> > >
> > > That's strange.  In your other posts you said you found that "new"
> > > version, but I get mine just by going to www.adobe.com, and at the
> > > bottom of the page, right side, click on "flashplayer."  That takes
> > > me to the download page with Linux 64bit already picked, I choose
> > > the tar.gz file even though there's a .deb one.  Download, unpack
> > > and copy as root libflashplayer.so to /usr/lib/mozilla/plugins/
> > > after mv'ing the old version just in case. Done!
> > >
> > >  For years while using Fedora, manually was the ONLY way to install
> > > the flashplayer.  And since "install-flashplayer-nonfree" stopped
> > > working months ago, I reverted to my old Fedora habits..
> > >
> > > I noted as you did that there are a lot of other places for the
> > > player, mostly symbolic links, but the above works for me, so I keep
> > > doing it that way.
> > >
> > > As to how to find out when a new version is out, I wait until
> > > Firefox during my normal browsing notifies me my version is old and
> > > my system "..is at risk."  Then just do the manual download/install
> > > thing.  I don't use the Firefox link to the new version.  Have had
> > > problems with it before.
> > >
> > > B
> > 
> > Problems is an understatement and I blame that for the mess I have
> > now.
> > 
> > Its as if they intended to poison it. They just didn't use a strong 
> > enough dose of arsenic, and created a monster with all the
> > workarounds.  
> > 
> > None of which ever worked 100% because the web pages all seemed to be 
> > using a different version.  The "it works here" syndrome, essentially 
> > the same as the N.I.H. beliefs. :(
> 
> Well, I'm glad flash is dying.  Wish it would do so faster.

If you don't like flash, then don't use it. Don't install it if
you're worried you might accidently use it involuntarily.
But why the spite? Can't people who don't like flash just leave
the flash users alone? Where's the freedom in that attitude?

> On my
> Wheezy system my primary browser is Chrome, deprecated and
> unsupported for over a year now.  Or has it been two?  No new versions
> available. Pepperflash stopped working a few months ago. Never could
> fix it.  So, just disabled it. And the funny thing is, I rarely run
> into sites now that require it anymore.  HTML5 is being adopted rapidly.
> Still there are hold-outs. To be expected.
> 
> As far as "works here," my primary system is a very non-standard install
> of Wheezy 64-bit on a box I built 10 years ago. (Hardware's been
> upgraded numerous times since.) Started with a Base Install Terminal
> Only, and built it up from there. Window manager only.  No display
> manager, no udisks, etc. Even wrote my own udev rules. Anyway, I figure
> if something works on my system, it should work on any "standard" system
> with all the Bells and Whistles, Linux or otherwise.

Cheers,
David.

OT Big Dummy mutt question

[Bob Bernstein]

Mutt (1.5.23) is rebuffing my every attempt to get ispell 
working. Currently I have in .muttrc:


set ispell="ispell --mode=email"

This threw no error when mutt launched, so it was with high 
spirits that I tried to send off deliberately misspelled emails. 
Alas and alack. these arrived at their intended destinations 
with their test misspellings intact.


Could it be (he asked) that spell-checking in mutt does not 
follow on auto-magically (if that is the word I'm looking for 
here) via the bare expedient of creating an entry in .muttrc 
such as is on display several lines above?


Throwing myself on Google's mercy leads me to believe that the 
only editor permitted (so to speak) with mutt is vim. I refuse 
to accept this, and, if found to be true, would protest in the 
strongest available terms through proper channels.


Please help.

Thank you.

--
"Natasha! First we shoot jet, then we go after moose and squirrel."

Re: Jessie for Udoo X86?

[songbird]

Larry Dighera wrote:
...
> What I have discovered thus far, is that Debian wants to launch X11 by
> default, instead of the command line UI.  That appears to result in a black
> screen with a frozen system.  
>
> At this point, I have no idea of the correct way to boot to the command line
> interface, so I temporarily renamed lightdm, and now it boots to the command
> line interface apparently after X11 fails to launch.  So, it appears that it
> is X11 that has possible issues with the hardware or is misconfigured.
> Perhaps there is something in X11's /var/log file that will provide a clue
> about why it was failing to successfully launch.

  hope so!  also check the session logs in lightdm...


> So, it appears that grub is correctly configured after all.  
>
> What is the correct way to configure the system to boot to the command line
> UI instead of X11?  Do I need to edit things, or add files to, /etc/rc.d
> someplace?  Or is there a higher-level way to tell systemd that I prefer to
> manually launch X11?  

  install the base system to start and then add the
next layers after.

  lightdm by default should not take you any further
than the lightdm greeter login screen without you
adjusting the configuration files.

  is there some reason not to give the current 
testing images for the installer a try?  it may
have better support for newer hardware.


> I'm aware that running the startx script is a reasonable way to launch X11
> when I want it, but I'll have to diagnose its issue(s) first.  My past
> familiarity with AT Unix from the early '80s through the '90s was pre-X11,
> so I'm going to have to learn how to administrate X11 now I suppose.  
>
> I sincerely appreciate your kind efforts in guiding me.  I gives me the
> motivation to continue spending the time to get Jessie up on the new Udoo
> X86 platform.

  the keyword being "new" there makes me go "hmm..."  :)

  [i have no idea what a Udoo is...]


  songbird

Re: new firefox for wheezy last night, can't do squat on the net today.

[Patrick Bartek]

On Sun, 23 Apr 2017 15:41:30 -0400 Gene Heskett 
wrote:

> On Sunday 23 April 2017 15:15:05 Patrick Bartek wrote:
> 
> > On Sun, 23 Apr 2017 00:21:28 -0400 Gene Heskett
> > 
> >
> > wrote:
> > > On Saturday 22 April 2017 23:22:45 Patrick Bartek wrote:
> > > > On Sat, 22 Apr 2017 12:24:32 -0400 Gene Heskett
> > > > 
> > > >
> > > > wrote:
> > > > > Went to newegg.com to look for some optical fiber but the
> > > > > front page, while I think its alive, did not respond to a
> > > > > mouse click on any product link. I hope its not contagious.
> > > > >
> > > > > Many news sites are saying "request entity too large" also.
> > > >
> > > > Works fine here.  Although rendering sometimes is sluggish -- a
> > > > few seconds longer.  Could be Cox Internet.  They get slow at
> > > > times.  Version 45.9.0 with the latest flashpalyer 25.0.0.148
> > > > installed yesterday
> > > >
> > > > B
> > >
> > > And how do you get that 10 year newer flash?  The adobe site
> > > doesn't show me anything newer than the 11.xx.xx.xxx stuff.
> >
> > That's strange.  In your other posts you said you found that "new"
> > version, but I get mine just by going to www.adobe.com, and at the
> > bottom of the page, right side, click on "flashplayer."  That takes
> > me to the download page with Linux 64bit already picked, I choose
> > the tar.gz file even though there's a .deb one.  Download, unpack
> > and copy as root libflashplayer.so to /usr/lib/mozilla/plugins/
> > after mv'ing the old version just in case. Done!
> >
> >  For years while using Fedora, manually was the ONLY way to install
> > the flashplayer.  And since "install-flashplayer-nonfree" stopped
> > working months ago, I reverted to my old Fedora habits..
> >
> > I noted as you did that there are a lot of other places for the
> > player, mostly symbolic links, but the above works for me, so I keep
> > doing it that way.
> >
> > As to how to find out when a new version is out, I wait until
> > Firefox during my normal browsing notifies me my version is old and
> > my system "..is at risk."  Then just do the manual download/install
> > thing.  I don't use the Firefox link to the new version.  Have had
> > problems with it before.
> >
> > B
> 
> Problems is an understatement and I blame that for the mess I have
> now.
> 
> Its as if they intended to poison it. They just didn't use a strong 
> enough dose of arsenic, and created a monster with all the
> workarounds.  
> 
> None of which ever worked 100% because the web pages all seemed to be 
> using a different version.  The "it works here" syndrome, essentially 
> the same as the N.I.H. beliefs. :(

Well, I'm glad flash is dying.  Wish it would do so faster.  On my
Wheezy system my primary browser is Chrome, deprecated and
unsupported for over a year now.  Or has it been two?  No new versions
available. Pepperflash stopped working a few months ago. Never could
fix it.  So, just disabled it. And the funny thing is, I rarely run
into sites now that require it anymore.  HTML5 is being adopted rapidly.
Still there are hold-outs. To be expected.

As far as "works here," my primary system is a very non-standard install
of Wheezy 64-bit on a box I built 10 years ago. (Hardware's been
upgraded numerous times since.) Started with a Base Install Terminal
Only, and built it up from there. Window manager only.  No display
manager, no udisks, etc. Even wrote my own udev rules. Anyway, I figure
if something works on my system, it should work on any "standard" system
with all the Bells and Whistles, Linux or otherwise.

B

Re: Jessie for Udoo X86?

[GiaThnYgeia]

Larry Dighera:
> What is the correct way to configure the system to boot to the command
line
> UI instead of X11?  Do I need to edit things, or add files to, /etc/rc.d
> someplace?  Or is there a higher-level way to tell systemd that I
prefer to
> manually launch X11?

I don't have an appropriate answer but if you have a fast i/net
connection you may want to remove lightdm or whatever desktop and
display manager you have installed and that will leave the system login
in the command line.  $ apt remove lightdm   will probably do it.

$ inxi -c10 -v3
Will list basic system info and hardware

$ lshw
will list more hardware details

$ more /var/log/Xorg.*.log*

Will tell you the what the logs were like for when X11 tried to come up
but run into problems.


> It happens very quickly.  There is a brief flash of color, and perhaps
a few
> lines of text, then an interminable black screen with no response to
> keyboard/mouse input.

I know, sometimes I get that on stretch but on jessie it seems to be
working better.  The prompt where it tells you to hit CtrlD or enter the
root password sometimes doesn't show up.  So when you see the screen
stop rolling hit return and it clears up.

You then have to research online to see if there is firmware that
relates to the hardware that is causing the problem.  It might exist in
the contrib or non-free repositories.  To add them you edit (I use nano)
root$ nano /etc/apt/sources.list  and add at the end of the lines where
it says main contrib non-free   This makes apt look into the three
directories of that repository.  With nano once you edit hit Ctrl-O to
save or Ctrl-X to exit where it prompts you to save and you say yes if
you are sure of the editing.

Let's say the firmware missing is in misc-firmware-non-free
root$ apt install misc-firmware-non-free

If you find somewhere else a package in ***.deb format you use dpkg to
install it after you download it.

Keep us up to date

Larry Dighera:
> On Tue, 18 Apr 2017 08:30:00 +, GiaThnYgeia
>  wrote:
> 
>>
>> Larry Dighera:
>>> I found the 'debian-8.7.1-amd64-DVD-1.iso' image here:
>>> , burned it to
>>> SD card in a USB reader with Rufus , and booted it
>>> from USB on the Udoo X86 Advanced hardware (Intel quad-core Celeron N3160
>>> 2.24 GHz & Intel® Quark SE core 32 MHz plus 32-bit ARC core 32 MHz, Intel HD
>>> Graphics 400 Up to 640 MHz 12 execution units, 4 GB DDR3L Dual Channel RAM
>>> and 32GB eMMC Storage). 
>>
>> The link I sent you was for live versions where a complete Debian
>> installation boots up (if it is possible based on the hardware) which is
>> a very good indication that your installation will act just like it.
>> You can select any desktop and then switch and install any desktop you
>> like from the system once it is running.  I always use lxde as it is
>> lean and mean.  This live version includes the debian installer which
>> you can reboot and run from scratch or run it within the live debian
>> system.  I prefer to reboot and run the installer alone after I have
>> made sure live runs fine.  This gives the installer maximum resources
>> and there are less things to confuse it.  You see from live when grub is
>> installed it picks up the live drive as one of the installed systems.
>> You have to keep an eye on what you select on the grub installation.
>> But this would be a small problem, having an invalid boot option on your
>> grub.
>>
>>> I selected the GUI Install from the menu, and all proceeded remarkably fast
>>> and smooth without a hitch (except the WiFi, but gigabit Ethernet enabled
>>> downloading all required additional files) until the last when it came to
>>> grub.  
>>
>> Don't get me started down that path ;)
>>
>>> The installer advised that it had detected another OS being installed, and
>>> presented me with a few choices to which I wasn't sure of the correct one,
>>> so I took the default.  That must have been wrong, as now Debian won't boot
>>> with grub from the eMMC "Hard Drive."  I'm not at all familiar with grub.
>>
>> Were you aware that there was an installed system on that disk and what
>> it is?  Is it now an option on the grub boot-up screen? Remember that if
>> you move the arrow up and down within the first 5" the default autostart
>> that is timed to 5" is deactivated and you now have time to study it.
>> Your first option on the base screen should be the debian you installed.
>> The second should be for recovery which opens up a second screen where
>> recovery is the 2nd option.  Is that what you used?
>> Then on the base screen you should have 3 lines of memtest options, and
>> at the bottom the "other" system that was previously installed.  It may
>> be freedos or something factory???
>>
>>> I can boot into recovery mode though, and from the command line it appears
>>> the install was successful.  So I'm close, but don't know exactly how to
>>> proceed 

Re: ouvrir des ports pour amule

[Klaus Becker]

On vendredi 21 avril 2017 13:43:13 CEST babouchko wrote:
> Salut
> Configure ta VM virtual box en mode pont.

j'ai essayé, mais en mode NAT Pont je n'ai plus accès au web.

> Comme actuellement elle est en nat tu dois aussi rediriger les ports entre
> ton PC et ta VM.
> 
> Cdt
> 
> Bab

[...]


Finalement je suis arrivé à une connexion High-ID et sans pare-feu sous 
Magéia. Il a fallu désactiver le pare-feu et redémarrer la machine (je ne sais 
pas si c'est vraiment nécessaire).

Puis amule me signale d'abord être derrière un pare-feu, mais ce message 
disparaît au bout de qq secondes et amule me signale bien fonctionner en High-
ID. Mais le résultat cad la vitesse de téléchargement n'est pas meilleure 
qu'avant !

Puis hier sous Magéia et avec le pare-feu activé, j'ai vu par moments des 
vitesses de téléchargement de plus 1300 kp/s ce qui je n'ai jamais vu avant.

C'est à ne rien y comprendre.

J'abandonne Debian dans Virtualbox pour l'utilisation d'amule parce que je ne 
pourrai pas faire mieux qu'actuellement avec Magéia sur un 2e ordi et je 
préfère consacrer un portable pour amule et ainsi libérer mon ordi principal 
de bureau avec Debian Sid pour le reste.

merci pour votre aide et bonne soirée

Klaus

Re: Possibly erroneous "device not present" message during boot

[Brian]

On Wed 12 Apr 2017 at 06:18:51 -0500, Richard Owlett wrote:

> Due to circumstances, will note rule out any of hardware, software, or
> confused operator as underlying cause.
> 
> BACKGROUND:
> The hardware is a used Lenovo T510 laptop purchased a couple of months ago.

This machine has an internal card reader.

> Jessie with MATE desktop has been running fine.
> Yesterday I purchased a Kingston Technology 512GB SD, primarily for backups.
> 
> As this individual unit had never had an SD card installed, the agreement
> with the store was if the card did not work in this machine I would not have
> to purchase it. My acceptance test was to install Jessie using a flash drive
> with DVD 1 of 13 of Debian 8.6.0.

We suppose the flash drive was a USB stick.
 
> It was my standard install which does NOT include either a swap partition
> being activated during install NOR installing a boot loader.

First (and the most important question): was the SD card inserted in a
slot of the *machine's* internal card reader when installing Debian to
it?

> I booted into my primary OS and ran update-grub with no problems.
> I rebooted, choosing the SD card from the Grub2 menu. No apparent problem.
> Also verified my other Debian installs could read/write the SD card.
> 
> These tests were performed before leaving the store.
> 
> THE SYMPTOM:
> 
> When I got home and booted to the SD card I noticed a message appeared for
> ~10 seconds reporting that a device was not found giving the UUID of the SD
> card.

If I had carried out the procedure you describe (something that had not
been done before) my eyes would have been glued to the screen when the
OS on the SD card had been booted for the first time. Yet, at the store,
there was no "device not found" message observed. Did your attention
wander for the 10 seconds such a message would have been on the screen? :)

-- 
Brian.

Re: new firefox for wheezy last night, can't do squat on the net today.

[Gene Heskett]

On Sunday 23 April 2017 15:15:05 Patrick Bartek wrote:

> On Sun, 23 Apr 2017 00:21:28 -0400 Gene Heskett 
>
> wrote:
> > On Saturday 22 April 2017 23:22:45 Patrick Bartek wrote:
> > > On Sat, 22 Apr 2017 12:24:32 -0400 Gene Heskett
> > > 
> > >
> > > wrote:
> > > > Went to newegg.com to look for some optical fiber but the front
> > > > page, while I think its alive, did not respond to a mouse click
> > > > on any product link. I hope its not contagious.
> > > >
> > > > Many news sites are saying "request entity too large" also.
> > >
> > > Works fine here.  Although rendering sometimes is sluggish -- a
> > > few seconds longer.  Could be Cox Internet.  They get slow at
> > > times.  Version 45.9.0 with the latest flashpalyer 25.0.0.148
> > > installed yesterday
> > >
> > > B
> >
> > And how do you get that 10 year newer flash?  The adobe site doesn't
> > show me anything newer than the 11.xx.xx.xxx stuff.
>
> That's strange.  In your other posts you said you found that "new"
> version, but I get mine just by going to www.adobe.com, and at the
> bottom of the page, right side, click on "flashplayer."  That takes me
> to the download page with Linux 64bit already picked, I choose the
> tar.gz file even though there's a .deb one.  Download, unpack and
> copy as root libflashplayer.so to /usr/lib/mozilla/plugins/ after
> mv'ing the old version just in case. Done!
>
>  For years while using Fedora, manually was the ONLY way to install
> the flashplayer.  And since "install-flashplayer-nonfree" stopped
> working months ago, I reverted to my old Fedora habits..
>
> I noted as you did that there are a lot of other places for the
> player, mostly symbolic links, but the above works for me, so I keep
> doing it that way.
>
> As to how to find out when a new version is out, I wait until Firefox
> during my normal browsing notifies me my version is old and my system
> "..is at risk."  Then just do the manual download/install thing.  I
> don't use the Firefox link to the new version.  Have had problems with
> it before.
>
> B

Problems is an understatement and I blame that for the mess I have now.

Its as if they intended to poison it. They just didn't use a strong 
enough dose of arsenic, and created a monster with all the workarounds.  

None of which ever worked 100% because the web pages all seemed to be 
using a different version.  The "it works here" syndrome, essentially 
the same as the N.I.H. beliefs. :(

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: Jessie for Udoo X86?

[Larry Dighera]

On Tue, 18 Apr 2017 08:30:00 +, GiaThnYgeia
 wrote:

>
>Larry Dighera:
>> I found the 'debian-8.7.1-amd64-DVD-1.iso' image here:
>> , burned it to
>> SD card in a USB reader with Rufus , and booted it
>> from USB on the Udoo X86 Advanced hardware (Intel quad-core Celeron N3160
>> 2.24 GHz & Intel® Quark SE core 32 MHz plus 32-bit ARC core 32 MHz, Intel HD
>> Graphics 400 Up to 640 MHz 12 execution units, 4 GB DDR3L Dual Channel RAM
>> and 32GB eMMC Storage). 
>
>The link I sent you was for live versions where a complete Debian
>installation boots up (if it is possible based on the hardware) which is
>a very good indication that your installation will act just like it.
>You can select any desktop and then switch and install any desktop you
>like from the system once it is running.  I always use lxde as it is
>lean and mean.  This live version includes the debian installer which
>you can reboot and run from scratch or run it within the live debian
>system.  I prefer to reboot and run the installer alone after I have
>made sure live runs fine.  This gives the installer maximum resources
>and there are less things to confuse it.  You see from live when grub is
>installed it picks up the live drive as one of the installed systems.
>You have to keep an eye on what you select on the grub installation.
>But this would be a small problem, having an invalid boot option on your
>grub.
>
>> I selected the GUI Install from the menu, and all proceeded remarkably fast
>> and smooth without a hitch (except the WiFi, but gigabit Ethernet enabled
>> downloading all required additional files) until the last when it came to
>> grub.  
>
>Don't get me started down that path ;)
>
>> The installer advised that it had detected another OS being installed, and
>> presented me with a few choices to which I wasn't sure of the correct one,
>> so I took the default.  That must have been wrong, as now Debian won't boot
>> with grub from the eMMC "Hard Drive."  I'm not at all familiar with grub.
>
>Were you aware that there was an installed system on that disk and what
>it is?  Is it now an option on the grub boot-up screen? Remember that if
>you move the arrow up and down within the first 5" the default autostart
>that is timed to 5" is deactivated and you now have time to study it.
>Your first option on the base screen should be the debian you installed.
> The second should be for recovery which opens up a second screen where
>recovery is the 2nd option.  Is that what you used?
>Then on the base screen you should have 3 lines of memtest options, and
>at the bottom the "other" system that was previously installed.  It may
>be freedos or something factory???
>
>> I can boot into recovery mode though, and from the command line it appears
>> the install was successful.  So I'm close, but don't know exactly how to
>> proceed to make it bootable.
>
>In order to get to the grub part of the installation the system was
>completely installed and it is there.  There is an option to install
>grub to handle booting of all systems on the drive (possibly sda) and/or
>the partition itself where Debian was installed in which case it makes
>the partition bootable.  I assume the default is the first.
>
>> Any clues sincerely appreciated.
>
>When you pick the first option of Debian to boot, what do you see on the
>screen?  

It happens very quickly.  There is a brief flash of color, and perhaps a few
lines of text, then an interminable black screen with no response to
keyboard/mouse input.

>Lines of white text running some green and maybe red stuff?
>If it is all green you are in good shape, if it is red you have to
>concentrate on that first red tag and tell us what it says.
>

I'm familiar with the dmesg output at boot time.  I see that when I choose
to boot into recovery mode from the grub menus.  When the scrolling text
stops, I'm left with what I thought was a frozen screen, but it turns out to
be login, without a prompt, waiting for me to provide the root password.
Once I submit the root password, I have a command line interface to a
reasonably functional Debian system.

>
>Again, if there was a hardware issue the live system would have
>identified and displayed what the obstacle was.  Possibly you have to go
>into recovery, edit the sources (/etc/apt/sourced.list) and add "main
>contrib non-free" to where it says "main" if such firmware exist.  Then
>$apt update, $apt upgrade but then you have to know what you are missing
>to find the appropriate package to add if it exists.
>

What I have discovered thus far, is that Debian wants to launch X11 by
default, instead of the command line UI.  That appears to result in a black
screen with a frozen system.  

At this point, I have no idea of the correct way to boot to the command line
interface, so I temporarily renamed lightdm, and now it boots to the command
line interface apparently 

Re: new firefox for wheezy last night, can't do squat on the net today.

[Patrick Bartek]

On Sun, 23 Apr 2017 00:21:28 -0400 Gene Heskett 
wrote:

> On Saturday 22 April 2017 23:22:45 Patrick Bartek wrote:
> 
> > On Sat, 22 Apr 2017 12:24:32 -0400 Gene Heskett
> > 
> >
> > wrote:
> > > Went to newegg.com to look for some optical fiber but the front
> > > page, while I think its alive, did not respond to a mouse click on
> > > any product link. I hope its not contagious.
> > >
> > > Many news sites are saying "request entity too large" also.
> >
> > Works fine here.  Although rendering sometimes is sluggish -- a
> > few seconds longer.  Could be Cox Internet.  They get slow at
> > times.  Version 45.9.0 with the latest flashpalyer 25.0.0.148
> > installed yesterday
> >
> > B
> And how do you get that 10 year newer flash?  The adobe site doesn't
> show me anything newer than the 11.xx.xx.xxx stuff.

That's strange.  In your other posts you said you found that "new"
version, but I get mine just by going to www.adobe.com, and at the
bottom of the page, right side, click on "flashplayer."  That takes me
to the download page with Linux 64bit already picked, I choose the
tar.gz file even though there's a .deb one.  Download, unpack and
copy as root libflashplayer.so to /usr/lib/mozilla/plugins/ after
mv'ing the old version just in case. Done!

 For years while using Fedora, manually was the ONLY way to install the
flashplayer.  And since "install-flashplayer-nonfree" stopped
working months ago, I reverted to my old Fedora habits..  

I noted as you did that there are a lot of other places for the player,
mostly symbolic links, but the above works for me, so I keep doing it
that way.

As to how to find out when a new version is out, I wait until Firefox
during my normal browsing notifies me my version is old and my system
"..is at risk."  Then just do the manual download/install thing.  I
don't use the Firefox link to the new version.  Have had problems with
it before.

B

Chamada de propostas para o Dia Livre (Open Day) na DebConf17

[Paulo Henrique de Lima Santana]

Olá,

O time da DebConf gostaria de anunciar a chamada de propostas para o Dia Livre 
(Open Day) na DebConf17, um dia inteiro dedicado a sessões sobre Debian e 
Software Livre, e destinado ao público em geral. O Dia Livre antecederá a 
DebConf17 e será realizado em Montreal, Canadá, no dia 05 de agosto de 2017.

O Dia Livre na DebConf será uma grande oportunidade para usuários, 
desenvolvedores, e pessoas simplesmente curiosas sobre o nosso trabalho, 
conhecerem e aprenderem sobre o Projeto Debian, Software Livre em geral e 
tópicos relacionados.
Submeta sua proposta

Nós estamos recebendo as submissões de oficinas, apresentações ou qualquer 
outra atividade que envolva Debian e Software Livre. São aceitas atividades em 
inglês e francês.

Aqui estão algumas ideias de conteúdos que nós adoraríamos oferecer durante o 
Dia Livre. Essa lista não é definitiva, sinta-se livre para propor outras 
ideias!

* Uma introdução aos vários aspectos do Projeto Debian
* Palestras sobre Debian e Software Livre nas artes, educação e/ou pesquisas
* Um passo a passo sobre como contribuir com projetos de Software Livre
* Software Livre & Privacidade/Vigilância
* Uma introdução a programação e/ou manuseio de hardware
* Uma oficina sobre a sua parte favorita do Software Livre
* Uma apresentação sobre o seu projeto relacionado a Software Livre favorito 
(grupo de usuários, grupo de militantes, etc)

Para submeter a sua proposta, por favor preencha o formulário em:
https://debconf17.debconf.org/talks/new/

- Voluntários

Nós precisamos de voluntários para ajudar a garantir que o Dia Livre será um 
sucesso! Nós estamos procurando especialmente pessoas acostumadas com o 
instalador do Debian para participarem do install fest Debian, como suporte 
para as pessoas que procuram ajuda para instalar o Debian em suas máquinas.

Se você está interessado, por favor adicione o seu nome na nossa wiki:
https://wiki.debconf.org/wiki/DebConf17/OpenDay#Installfest

- Participação

A participação no Dia Livre é gratuita e não é obrigatório nenhuma inscrição.

A programação do Dia Livre será anunciada em junho de 2017.


-- 
Paulo Henrique de Lima Santana (phls)
Curitiba - Brasil
Membro da Comunidade Curitiba Livre
Fone: +55 (41) 99198-1897
Site: http://www.phls.com.br
GNU/Linux user: 228719  GPG ID: 0443C450

Apoie a campanha pela igualdade de gênero #HeForShe (#ElesPorElas)  
http://www.heforshe.org/pt

Re: new firefox for wheezy last night, can't do squat on the net today.

[Gene Heskett]

On Sunday 23 April 2017 07:35:36 Frank de Bruijn wrote:

> Op 23-04-17 om 12:37 schreef Gene Heskett:
> > On Sunday 23 April 2017 01:54:21 Frank wrote:
> >> Op 23-04-17 om 06:21 schreef Gene Heskett:
> >>> And how do you get that 10 year newer flash?  The adobe site
> >>> doesn't show me anything newer than the 11.xx.xx.xxx stuff.
> >>
> >> Really? Both https://www.adobe.com/software/flash/about/ and
> >> https://get.adobe.com/nl/flashplayer/ definitely show 25.0.0.148
> >> for me.
> >>
> >> Regards,
> >> Frank
> >
> > After writing that, I did a google search, which gave me a slightly
> > different adobe url and that link gave me a tarball of 25.0.0.148. 
> > The installation instructions were a bit confusing, so I wound up
> > overwriting libflashplayer.so in 5 locations with this newer
> > version. Leftovers from previous attempts to arrive at a working 75%
> > of the time flash player.  No one, including me, has a clue where
> > the one being used actually is.
>
> I usually look in /usr/lib/mozilla/plugins, but the plugin file there
> may actually be a symlink pointing to something in /etc/alternatives,
> which in turn will probably point to some other item somewhere in
> /usr/lib...
>
> Regards,
> Frank

The link in /etc/alternatives points at the new version 
in /usr/lib/flashplayer-mozilla/libflashplayer.so

So I think I'm ok.  Thank you for reminding me about alternatives.
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: new firefox for wheezy last night, can't do squat on the net today.

[Curt]

On 2017-04-23, Frank de Bruijn  wrote:

> I usually look in /usr/lib/mozilla/plugins, but the plugin file there 
> may actually be a symlink pointing to something in /etc/alternatives, 
> which in turn will probably point to some other item somewhere in 
> /usr/lib...

To cover all the bases, I have it in

/home/curty/.mozilla/plugins/libflashplayer.so
/usr/lib/firefox/plugins/libflashplayer.so
/usr/lib/mozilla/plugins/libflashplayer.so

The mozilla help site says to put it in

https://support.mozilla.org/en-US/kb/install-flash-plugin-view-videos-animations-games?cache=no

usr/lib/mozilla/plugins 

It might search there first and then in the user's home directory, or
vice-versa. 

It's working now; I could rename the files one by one, or two by two,
leaving only one libflashplayer.so, and see at which point I broke my
flash, if Gene's really interested in knowing what no one knows, which
is a pretty big affair if you ask me.

> Regards,
> Frank
>
>


-- 
"It might be a vision--of a shell, of a wheelbarrow, of a fairy kingdom on the
far side of the hedge; or it might be the glory of speed; no one knew." --Mrs.
Ramsay, speculating on why her little daughter might be dashing about, in "To
the Lighthouse," by Virginia Woolf.

Re: new firefox for wheezy last night, can't do squat on the net today.

[Frank de Bruijn]

Op 23-04-17 om 12:37 schreef Gene Heskett:

On Sunday 23 April 2017 01:54:21 Frank wrote:


Op 23-04-17 om 06:21 schreef Gene Heskett:

And how do you get that 10 year newer flash?  The adobe site doesn't
show me anything newer than the 11.xx.xx.xxx stuff.


Really? Both https://www.adobe.com/software/flash/about/ and
https://get.adobe.com/nl/flashplayer/ definitely show 25.0.0.148 for
me.

Regards,
Frank


After writing that, I did a google search, which gave me a slightly
different adobe url and that link gave me a tarball of 25.0.0.148.  The
installation instructions were a bit confusing, so I wound up
overwriting libflashplayer.so in 5 locations with this newer version.
Leftovers from previous attempts to arrive at a working 75% of the time
flash player.  No one, including me, has a clue where the one being used
actually is.


I usually look in /usr/lib/mozilla/plugins, but the plugin file there 
may actually be a symlink pointing to something in /etc/alternatives, 
which in turn will probably point to some other item somewhere in 
/usr/lib...


Regards,
Frank

Re: new firefox for wheezy last night, can't do squat on the net today.

[Gene Heskett]

On Sunday 23 April 2017 01:54:21 Frank wrote:

> Op 23-04-17 om 06:21 schreef Gene Heskett:
> > And how do you get that 10 year newer flash?  The adobe site doesn't
> > show me anything newer than the 11.xx.xx.xxx stuff.
>
> Really? Both https://www.adobe.com/software/flash/about/ and
> https://get.adobe.com/nl/flashplayer/ definitely show 25.0.0.148 for
> me.
>
> Regards,
> Frank

After writing that, I did a google search, which gave me a slightly 
different adobe url and that link gave me a tarball of 25.0.0.148.  The 
installation instructions were a bit confusing, so I wound up 
overwriting libflashplayer.so in 5 locations with this newer version. 
Leftovers from previous attempts to arrive at a working 75% of the time 
flash player.  No one, including me, has a clue where the one being used 
actually is.  OLd debian wheezy install, 100% uptodate a few hours ago.

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 

FMIT KMail-Trinity

[GiaThnYgeia]

Lisi Reisz:
> Or, in KMail-Trinity, left click on the address, et voilà!  A _new_, 
> correctly 
> addressed message with a pristine subject line.
> 
> Lisi

Please don't say trinity it gets the matrix disturbed
I turned my head and the shiskebap was gone

kAt(s)

> 

-- 
 "The most violent element in society is ignorance" rEG

"Who died and made you the superuser?"  Brooklinux

"keep rocking in the non-free world" Neilznotyoung

Measuring aggregate internet useage?

[Richard Owlett]

I have always installed Debian from purchased DVD sets as up until about 
a year ago I was on dialup. I wish to experiment with using netinst. I 
have a minimal data cap but have accumulated enough unused capacity that 
I should be able a normal install.


I'm not sure of my search terms as the hits I get are for grossly more 
fine detail than needed. I wish to measure total usage over the time 
period of the install process.


I connect over the cell network using a T-Mobile 4G Hotspot Z915 using 
its USB connection.


Can I do what I want?
What background reading should I do?
A major motivation is self education.
TIA

Re: (deb-cat) Patrocinis de l'empresa Mozilla

[Alex Muntada]

Narcis Garcia:

> Havent esmentat allò de la «duplicitat de codi», no tinc clar si
> s'admetria l'empaquetat a Debian. Com es fa pels derivats (fork)
> d'un programari ja existent?

Suposo que depèn de cada cas, no hi ha una resposta fàcil. Pel cas
del mariadb, l'equip que l'empaqueta és pkg-mysql però tenen dos
repositoris diferents de codi (no en conec més detalls):

https://anonscm.debian.org/git/pkg-mysql/mysql.git
https://anonscm.debian.org/git/pkg-mysql/mariadb-10.1.git

> Essencialment IceCat és un derivat de Firefox amb quatre retocs, com les
> preferències predeterminades, el complement SpyBlock i alguna cosa més
> sobre el JavaScript.
> Bona part d'això seria aplicable a la política d'empaquetat de Firefox
> sense necessitar IceCat, igual com es fa per Ubuntu amb el mateix Firefox.

Crec que la forma més fàcil de trobar la manera seria que els
mantenidors del paquet a Trisquel s'ofereixin a adaptar el
paquet per a Debian i a partir d'aquí esbrinin com caldria
fer-ho parlant amb els mantenidors del paquet de firefox.

Salut,
Alex

Re:

[En-No]

PS es tu amigo .. solo tienes que leer el man.
pero aqui te dejo unos ejemplos ..

procesos que consumen memoria RAM o CPU
ps -eo pid,ppid,cmd,%mem,%cpu --sort=-%mem | head
ps -e -o pcpu,cpu,nice,state,cputime,args --sort pcpu | sed '/^ 0.0 /d'
ps -e -orss=,args= | sort -b -k1,1n | pr -TW$COLUMNS

mostrar los 10 procesos que más memoria consumen
ps aux --width 30 --sort -rss | head


O usa top o htop .. pero también hay que leer el man.

Suerte

El día 8 de abril de 2017, 22:24, luis godoy  escribió:
> Hola, como puedo verificar que proceso está ocupando cpu, el monitor de
> recursos dice que consume un 95 porciento y sólo ocupo el navegador en
> YouTube,. Y el proceso de Firefox dice ocupar sólo 70 o 65 porciento, los
> demás procesos se mantienen en 0.
>

Re: new firefox for wheezy last night, can't do squat on the net today.

[Curt]

On 2017-04-23, Gene Heskett  wrote:

What I do is check periodically for updates and when there is one, I
open the tar.gz archive from Adobe in Firefox, extract the
libflashplayer.so file into my home directory, and copy it over the
obsolete libflashplayer.so files on my machine.

> And how do you get that 10 year newer flash?  The adobe site doesn't show 
> me anything newer than the 11.xx.xx.xxx stuff.

(Ten years?)

That is puzzling because here (Wheezy Firefox ESR 45.9.0) they're
showing me "Version 25.0.0.148"

https://get.adobe.com/flashplayer/

> Cheers, Gene Heskett


-- 
"It might be a vision--of a shell, of a wheelbarrow, of a fairy kingdom on the
far side of the hedge; or it might be the glory of speed; no one knew." --Mrs.
Ramsay, speculating on why her little daughter might be dashing about, in "To
the Lighthouse," by Virginia Woolf.

Re: provant debian 9

[Alex Muntada]

Narcis Garcia:

> Jo sovint faig servir màquines virtuals per fer assajos i comprovacions,
> per això és habitual que deixi moltes opcions predeterminades de les que
> no estic posant a prova.
> Puc plantejar-me fer 10 instal·lacions simultànies de Debian en mitja
> hora obrint 10 màquines virtuals, perquè vario algun mètode, maquinari,
> tantejar els diferents camins d'instal·lació, etc.

Aleshores et recomano que utilitzis «preseeding» per no dependre
dels valors per defecte:

https://wiki.debian.org/DebianInstaller/Preseed

Nosaltres utilitzem el preseeding amb el d-i per fer qualsevol
instal·lació dels diferents servidors que gestionem a la feina
(virtuals i físics). Fa temps que no fem instal·lacions guiades
amb el d-i.

Salut,
Alex

Re: new firefox for wheezy last night, can't do squat on the net today.

[Ben Caradoc-Davies]

On 23/04/17 16:21, Gene Heskett wrote:

And how do you get that 10 year newer flash?  The adobe site doesn't show
me anything newer than the 11.xx.xx.xxx stuff.


flashplugin-nonfree is often broken. Here is my workaround:
https://lists.debian.org/debian-user/2017/03/msg00491.html

See also:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851066

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand