Good News

[Mr.Friedrich Mayrhofer]

Good Day,
 
 This is the second time i am sending you this mail.
 
 I, Friedrich Mayrhofer Donate $ 1,000,000.00 to You, Email
 Me personally for more details.
 
 Regards.
 Friedrich Mayrhofer

Re: Limiting internet access by time

[Mark Fletcher]

On Sun, Aug 7, 2016 at 9:57 AM Dan Ritter  wrote:

> On Sat, Aug 06, 2016 at 04:56:06AM +, Mark Fletcher wrote:
> > On Sat, Aug 6, 2016 at 2:48 AM Dan Ritter  wrote:
>
> Got it. You can change that by removing NAT from the AP. For
> instance, plug your switch into a LAN port instead of the WAN
> port:
>
> cable modem -- LFS -- switch  (LAN port) AP  wifi client
>  |  \___ wifi client
>  |
>   other wired machines
>
> You can either set up a flat addressing space, perhaps with a
> range reserved for DHCP machines and the rest doing static, or
> you can route at the LFS machine and the AP. I would recommend
> a flat space unless you have a really large (>25) number of
> machines. That's what I do.
>
> I also have my equivalent of your LFS running dhcpd for the
> whole network, rather than having another configuration point
> on the AP to worry about. All filtering can be done there.
>
> -dsr-
>

In the end I got what I needed by using Lars' pointer of the iptables
extensions. I copied the iptables systemd service unit from my LFS box to
the machine in question, and then created a script in /etc/systemd/scripts
that first sets the iptables output chain policy to DROP, then adds these
rules:

iptables -A OUTPUT -m time --starttime 00:00 --stoptime 12:00 -j ACCEPT
iptables -A OUTPUT -d 192.168.11.0/24 -j ACCEPT

followed by rules specifying protocols and ports to allow DHCP, NTP and
Avahi to work at all times.

The first of the above rules matches every single outgoing packet and lets
them through between the hours of 9am and 9pm JST (midnight to noon UTC)
and matches nothing the rest of the time. Since Japan does not observe
daylight saving time I don't have that wrinkle to worry about. So between
9am and 9pm the other rules are superfluous and get no exercise. Once 9pm
arrives the first rule stops matching anything and the others start getting
work to do. The second allows anything aimed at my local network through,
except connections to my firewall which isn't on the 192.168.11.xxx subnet,
but I don't need this box to be able to ssh into the firewall so that's no
problem. I could have made it 192.168.0.0/16 but then I would have been
allowing a bunch of other subnet addresses I don't need. In this case, not
a major problem, but generally a bad habit when it comes to packet filter
rules.

The other rules allow DHCP, NTP and Avahi to work (the second rule doesn't
allow Avahi to work as it uses a broadcast address). Without the Avahi
rule, I found that the machine could talk to the rest of my network by ip
address but not by network name during the out-of-hours period. Duh, hadn't
thought of that.

So between 9am and 9pm everything hits the first rule and gets allowed.
Between 9pm and 9am anything not specifically aimed at my local nework that
isn't DHCP, NTP or Avahi falls all the way through the rules and hits the
policy rule, which is DROP. No changes needed anywhere else on the network.
If the machine can't get requests out, it isn't going to get any responses
back. And the firewall at the front door of my network is blocking anything
trying to come in from the internet that wasn't invited.

# systemctl enable iptables.service

makes sure this gets run every time the machine is booted. And that's it.

However, I'm finding the discussion with Dan very interesting so I'd like
to continue it if you don't mind, albeit on a hypothetical basis.

The first problem I'd have with Dan's suggestion is that the firewall box
only has 2 network ports -- one built into it and one I added using a
USB3.0 to Ethernet adaptor. So the cable modem is plugged into the native
Ethernet port and the USB-to-Ethernet passes on through an Ethernet cable
to the WAN port of the AP. This would be the connection that Dan suggests
shifting to a LAN port of the AP. Despite some clucking from various
sources about the performance I'd get from using a USB to Ethernet adaptor,
in practice I see no practical difference in internet access speed by
having used such an adaptor. I guess I'd need to add a third Ethernet port
to the firewall to migrate the wired devices, using another USB to Ethernet
adaptor, and plug some kind of hub device into it so I could plug in more
than one wired Ethernet device.

Then the firewall would have to be a dhcp client of the AP, instead of the
other way round as now, as I can't turn the AP'S DHCP server off since I
need it to supply IP addresses to my wireless devices. But I'd need to keep
the DHCP server on the firewall so it could supply IP addresses to the
wired machines. I am not a fan of static IP addressing on a home LAN,
although I can see why it isn't a big problem for the wired part since
wired devices tend not to wander about. :)

But part of me is thinking that if I were going to migrate my wired devices
away from the AP and to the firewall, I 

Re: IceWeasel (Firefox) Update?

[Marc Shapiro]

I have added:

debhttp://mozilla.debian.net/  jessie-backports firefox-release

to my sources.list and installed firefox.  Well and good.  I have 
version 47.0.1.  I assume that we will catch up with Mozilla and get 
48.0 soon.


My actual question, though, is this:  Has anything been said about when, 
or if, the Mozilla team will be doing the same for Thunderbird?  I have 
my box set up to very easily update both Firefox and Thunderbird direct 
from the Mozilla site.  One click on a bookmark and running one script 
for each of them.  If I still have to get Thunderbird manually then it 
is really not that much more effort to upgrade Firefox directly, as well.


Marc


On 08/06/2016 03:37 PM, Lisi Reisz wrote:

On Saturday 06 August 2016 23:23:22 Bob Holtzman wrote:

On Fri, Aug 05, 2016 at 12:24:43AM +0100, Lisi Reisz wrote:

On Thursday 04 August 2016 20:48:41 afamilyofbetatesters hendersonpark

wrote:

This may not even be possible, but how can I update the IceWeasel
(Firefox) from 45 (old) to the current 47? I need it on 47 to be able
to use a platform I use instead of skype :)

What version of Debian are you using?  In jessie, I did:

# aptitude install firefox

and kept my system fully updated, and I have 47.0.1.

What repo and/or mirror are you using? I can only get v45.3 even from
backports. My bank is bitching at me to udate my browser. I can d/l from
the mozilla site but I would rather get a binary from a repo.

Yes, I'm sorry.  I was misremembering.  I have this in my sources.list:

deb http://ftp.debian.org/debian jessie-backports main
deb http://mozilla.debian.net/ jessie-backports firefox-release

So I must originally have done:
# aptitude install -t jessie-backports firefox

I omitted the -t jessie-backports from my original line.

But I now just do aptitude update, aptitude upgrade, and it gets upgraded
along with everything else!!

See:
http://mozilla.debian.net/

Lisi

Re: Limiting internet access by time

[Dan Ritter]

On Sat, Aug 06, 2016 at 04:56:06AM +, Mark Fletcher wrote:
> On Sat, Aug 6, 2016 at 2:48 AM Dan Ritter  wrote:
> 
> > On Fri, Aug 05, 2016 at 03:49:28PM +, Mark Fletcher wrote:
> > > On Fri, Aug 5, 2016 at 11:04 PM Brian  wrote:
> > >
> > > I didn't mention earlier, and I'm not sure if it is relevant, but the
> > > computer connects via WiFi to my access point, which is also my network's
> > > internet gateway -- with an LFS box between it and the cable modem as a
> > > dedicated firewall. I don't trust the non-free firewall in the AP,
> > although
> > > I have left it on. The rest of my network is not to be subject to this
> > 9pm
> > > curfew. And I would ideally like connectivity between this machine and
> > the
> > > rest of my local network to remain even when the internet is denied to
> > this
> > > machine, so I can do remote maintenance when he's not using the machine,
> > > for example.
> >
> >
> > I have a new suggestion, based on this.
> >
> > Do all the filtering on your LFS box.
> >
> > Match your kid's machine by MAC address.
> >
> > Write two tiny scripts:
> >
> > #!/bin/sh
> > iptables -D FORWARD -m mac --mac-source 58:63:1a:af:71:72 -j DROP
> >
> >
> > #!/bin/sh
> > iptables -I FORWARD -m mac --mac-source 58:63:1a:af:71:72 -j DROP
> >
> > (substituting in the appropriate MAC address for the machine, of
> > course)
> >
> > and run the first one at 9 PM to disable internet access, and
> > run the second one at 8 AM or whatever to re-enable it. Cron is
> > your friend.
> >
> > The LFS box (and yes that is Linux From Scratch, all my other "real"
> computers are Debian) sits between my AP (wireless & wired) and the cable
> modem ie the wilds of the Internet. Used to be that the AP was plugged
> straight into the cable modem, but about 6 months ago or so I set up this
> LFS box using an ASUS mini PC, about 10% out of concern for what weaknesses
> my AP's firewall might have that I didn't and never would know about, and
> 90% just to see if I could. The WAN port of the AP goes into one interface
> of the firewall, the other goes to the cable modem. All my computers other
> than the firewall itself are connected, wired or wireless, to the AP. The
> wireless card built into the firewall box is disabled.
> 
> Since the AP is doing NAT, as I believe is normal for such a device that
> thinks it is the last line of defence between the network and the Internet,
> I am not sure that the LFS firewall machine will be able to see the MAC
> addresses of the computers on my LAN. I just tried to do an experiment
> involving logging in iptables on the firewall, but the logged information
> doesn't seem to include MAC address so I couldn't check.
> 
> If in fact, I can expect the firewall to be able to see source computer LAN
> mac addresses in this configuration, that has all sorts of other positive
> implications which I would get excited about. I'd just assumed it wouldn't
> be possible due to the layer of indirection provided by the AP.
> 

Got it. You can change that by removing NAT from the AP. For
instance, plug your switch into a LAN port instead of the WAN
port:

cable modem -- LFS -- switch  (LAN port) AP  wifi client
 |  \___ wifi client
 |
  other wired machines

You can either set up a flat addressing space, perhaps with a
range reserved for DHCP machines and the rest doing static, or
you can route at the LFS machine and the AP. I would recommend
a flat space unless you have a really large (>25) number of
machines. That's what I do.

I also have my equivalent of your LFS running dhcpd for the
whole network, rather than having another configuration point
on the AP to worry about. All filtering can be done there.

-dsr-

enregistrer un flux audio à partir de espeak

[Bernard Schoenacker]

bonjour,


je redcherche le moyen de le faire sachant que pour le texte en
question, je n'arrive pas à le faire ingérer à pico :

(exemple)
 pico2wave -l fr-FR -w test.wav "$`cat test.txt`"

application :

pico2wave -l fr-FR -w reconstitutionnaliser.wav "$`cat
reconstitutionnaliser.txt`" bash: /usr/bin/pico2wave: Liste d'arguments
trop longue


voici les caractéristiques du texte en français:
wc -m -l -w  reconstitutionnaliser.txt
  6766  46636 299827 reconstitutionnaliser.txt


bref, je ne sais pas par quel bout prendsre le problème pour le résoudre

slt
bernard

Re: open on nfs server -> resource temporarily unavailable

[Mike Kupfer]

Andrey wrote:

> me@cli:~$ mount
> ...
> serv:/home/me/data-t on /home/me/dt type nfs4 
> (ro,nosuid,nodev,noexec,relatime,sync,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,acregmin=0,acregmax=0,acdirmin=0,acdirmax=0,hard,noac,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.209.174,local_lock=none,addr=192.168.238.113,user=me)
> 
> It could be provoked in a few minutes by running on the server serv:~$
> while : ; do date > data-t/now.txt; sleep 1; done
> 
> while on the client computer
> me@cli:~$ while : ; do cat dt/now.txt; sleep 1; done
> 
> After a while (it's unpredictable might take up 10 minutes or a few seconds,
> but in average about 2 minutes)
> on the server I get:
> data-t/now.txt: Resource temporarily unavailable

It's likely that the server is granting the client a read delegation
on the file, which would have to be recalled before the server can write
to the file.

Try mounting with version 3 instead of version 4.

Is there much of a network delay between the client and server?  If not,
I'd open a bug.

regards,
mike

Sopcast (Olympics) on OMX?

[Emanuel Berg]

Anyone had any luck watching the Olympics on
RPi3/Raspbian/OMX?

I found this site with Sopcast and Ace streams

http://livetv.sx/en/eventinfo/433241_olympic_games/

This tutorial

https://www.raspberrypi.org/forums/viewtopic.php?t=46342

seems to be the way but I can't get it to work.

I don't get it past the 'start_omxplayer' loop.

Ideas?

-- 
underground experts united  http://user.it.uu.se/~embe8573
Emacs Gnus Blogomatic . http://user.it.uu.se/~embe8573/blogomatic
   - so far: 64 Blogomatic articles -   

Re: Changing background for GDM3 in /etc/gdm3/greeter.gconf-defaults not working

[Brian]

On Sat 06 Aug 2016 at 21:37:53 +, ML mail wrote:

> I have a Debian 8 desktop with GNOME and would like to change the default
> dark grey background of the GDM3 login screen. For that I just adapted the
> etc/gdm3/greeter.gconf-defaults file and ran "dpkg-reconfigure gdm3" as
> documented on the GDM page of wiki.debian.org. Unfortunately that does not
> work, neither the setting to use a plain color as background.
> 
> Is this a bug or am I missing something?

Please post the adapted file.

Re: IceWeasel (Firefox) Update?

[Lisi Reisz]

On Saturday 06 August 2016 23:23:22 Bob Holtzman wrote:
> On Fri, Aug 05, 2016 at 12:24:43AM +0100, Lisi Reisz wrote:
> > On Thursday 04 August 2016 20:48:41 afamilyofbetatesters hendersonpark 
wrote:
> > > This may not even be possible, but how can I update the IceWeasel
> > > (Firefox) from 45 (old) to the current 47? I need it on 47 to be able
> > > to use a platform I use instead of skype :)
> >
> > What version of Debian are you using?  In jessie, I did:
> >
> > # aptitude install firefox
> >
> > and kept my system fully updated, and I have 47.0.1.
>
> What repo and/or mirror are you using? I can only get v45.3 even from
> backports. My bank is bitching at me to udate my browser. I can d/l from
> the mozilla site but I would rather get a binary from a repo.

Yes, I'm sorry.  I was misremembering.  I have this in my sources.list:

deb http://ftp.debian.org/debian jessie-backports main
deb http://mozilla.debian.net/ jessie-backports firefox-release

So I must originally have done:
# aptitude install -t jessie-backports firefox

I omitted the -t jessie-backports from my original line.

But I now just do aptitude update, aptitude upgrade, and it gets upgraded 
along with everything else!!

See:
http://mozilla.debian.net/

Lisi

Re: IceWeasel (Firefox) Update?

[Bob Holtzman]

On Fri, Aug 05, 2016 at 12:24:43AM +0100, Lisi Reisz wrote:
> On Thursday 04 August 2016 20:48:41 afamilyofbetatesters hendersonpark wrote:
> > This may not even be possible, but how can I update the IceWeasel (Firefox)
> > from 45 (old) to the current 47? I need it on 47 to be able to use a
> > platform I use instead of skype :)
> 
> What version of Debian are you using?  In jessie, I did:
> 
> # aptitude install firefox
> 
> and kept my system fully updated, and I have 47.0.1.

What repo and/or mirror are you using? I can only get v45.3 even from
backports. My bank is bitching at me to udate my browser. I can d/l from
the mozilla site but I would rather get a binary from a repo.

-- 
Bob Holtzman
A man is a man who will fight with a sword or
conquer Mt. Everest in snow. But the bravest of all
owns a '34 Ford and tries for six thousand in low.

Re: Problem with NON-STANDARD install

[Felix Miata]

Pascal Hambourg composed on 2016-08-06 23:59 (UTC+0200):


Felix Miata:



Pascal Hambourg composed on 2016-08-06 12:01 (UTC+0200):


I misread what you wrote. If I knew how to edit or delete a list posting as 
is typically possible in forums, I would. It shouldn't have been written, 
much less sent. :-(



...

If the boot image is in a PBR, the BIOS won't load it directly



It will if the PBR is on a primary partition on the same disk.



On the same disk as what ?



Do you mean that the BIOS can load directly the boot sector of a primary
partition instead of the MBR ?



It's how
all my systems boot if I'm not using IBM Boot Manager as the primary
bootloader.



What do you call "IBM Boot Manager" ? Is it the boot manager used by
OS/2, or the generic/legacy boot code in the MBR used by MSDOS and
Windows, which loads the PBR of the primary partition with the boot flag ?



Also, what does your MBR contains ? Only the partition table, no boot
code at all ?



After reading your reply I made a quick test on three different PCs.
I installed a generic MBR boot code on a USB stick and checked that it
could boot on each PC and load the PBR of the primary partition with the
boot flag.
Then I erased the boot code (first 440 bytes in the MBR) with zeroes and
observed that the boot hanged on all my test PCs, so I concluded that
the BIOS still tried to load and execute the MBR because of the boot
signature at the end of the MBR. Then I also removed the boot signature
in the MBR and observed that the BIOS said the device was not bootable,
as expected.

--
"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: Problem with NON-STANDARD install

[Pascal Hambourg]

Le 06/08/2016 à 16:18, Felix Miata a écrit :

Pascal Hambourg composed on 2016-08-06 12:01 (UTC+0200):
...

If the boot image is in a PBR, the BIOS won't load it directly


It will if the PBR is on a primary partition on the same disk.


On the same disk as what ?

Do you mean that the BIOS can load directly the boot sector of a primary 
partition instead of the MBR ?



It's how
all my systems boot if I'm not using IBM Boot Manager as the primary
bootloader.


What do you call "IBM Boot Manager" ? Is it the boot manager used by 
OS/2, or the generic/legacy boot code in the MBR used by MSDOS and 
Windows, which loads the PBR of the primary partition with the boot flag ?


Also, what does your MBR contains ? Only the partition table, no boot 
code at all ?


After reading your reply I made a quick test on three different PCs.
I installed a generic MBR boot code on a USB stick and checked that it 
could boot on each PC and load the PBR of the primary partition with the 
boot flag.
Then I erased the boot code (first 440 bytes in the MBR) with zeroes and 
observed that the boot hanged on all my test PCs, so I concluded that 
the BIOS still tried to load and execute the MBR because of the boot 
signature at the end of the MBR. Then I also removed the boot signature 
in the MBR and observed that the BIOS said the device was not bootable, 
as expected.

Re: Aplication's Help cant find iceweasel

[humbert . olivier . 1]

Hi Gary,

> I recently switched to Firefox-esr and removed iceweasel from my system. 
> Some application help files now error out with: KDEInit could not launch 
> '/usr/lib/iceweasel/iceweasel. As an example Rosegarden has the problem. 
> How can I fix this.

su -c "update-alternatives --set x-www-browser /usr/bin/firefox-esr"
su -c "update-alternatives --set gnome-www-browser /usr/bin/firefox-esr"

Hope that helps
Olivier

Aplication's Help cant find iceweasel

[Gary Roach]

Hi all,

Running Debian Stretch on KDE Desktop

I recently switched to Firefox-esr and removed iceweasel from my system. 
Some application help files now error out with: KDEInit could not launch 
'/usr/lib/iceweasel/iceweasel. As an example Rosegarden has the problem. 
How can I fix this.


Gary R

nosh version 1.28

[Jonathan de Boyne Pollard]

The nosh package is now up to version 1.28 .

* https://jdebp.eu./Softwares/nosh/
* 
https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project

* http://jdebp.info./Softwares/nosh/

There's a lot in this one: MySQL and MariaDB changes; more prophylaxis 
for Desktop Bus bus activation; improvements to systemd unit conversion; 
support for the old svc -x; machineenv; improvements to service 
management; fixes for the per-user manager; improvements to the console 
terminal emulator; BSD boot mode changes; the ability to pass more open 
sockets to connection-accepting programs; cron; and OpenBSD.


Italics and colour
==

* https://jdebp.eu./Softwares/nosh/italics-in-manuals.html

This isn't a toolset change, per se.  But the WWW site now has a guide 
to seeing actual italic text in manual pages.  The nosh toolset's 
user-space virtual terminals support true italics (if one has the fonts) 
or obliquing, and this works with them.


MySQL and MariaDB changes
=

* https://jdebp.eu./Softwares/nosh/mariadb-and-mysql.html

New in version 1.28 is a different and up-to-date way of managing MySQL 
and MariaDB server services — where "new" translates to finally getting 
rid of that unnecessary mysql_safe wrapper and doing things the way that 
daemontools-family toolset users have wanted to do them since the turn 
of the century.


There's a lengthy exposition on the WWW site, q.v..  The major visible 
effect is that your "mysql" or "mariadb" service is now an alias, for 
something like a "mysql@" or "mysql@01" (if you have [mysql01] in your 
my.cnf) service.  The configuration file import mechanism tries to 
construct/update mariadb@NN and mysql@NN service bundles for you, based 
upon your MariaDB and MySQL configuration files.


Further prophylaxis for Desktop Bus bus activation
==

* https://jdebp.eu./Softwares/nosh/avoid-dbus-bus-activation.html

The nosh toolset now comes with a dbus-daemon-launch-helper 
replacement.  The purpose of this is to sit in your 
/usr/local/etc/dbus-1/system.conf (or equivalent) and redirect to 
service management attempts, by the Desktop Bus broker daemon, to 
demand-start services.  It is slightly fiddly to install, requiring 
manual setup by the system administrator, there being no simple way to 
add overrides to /usr/local/etc/dbus-1/system.conf and it requiring that 
you allow the "messagebus" user the necessary access for starting and 
stopping services (but not necessarily *superuser* access — rembember ACLs).


To assist with this, several popular Desktop Bus "services" now exist as 
alias names for service management services.  These are just symbolic 
links to the service bundle directories, of course. So, for example: 
With the helper in place, Desktop Bus bus activation will try to 
demand-start a service named "org.freedesktop.PackageKit" using service 
management.  This is just an alias for the "packagekit" service.


Improvements to systemd unit conversion
===

Ideal mode is now closer to the daemontools-family mainstream, 
defaulting to the daemontools-family norm of always restarting 
services.  Quirks mode, conversely, now implements more of the 
non-daemontools redirection semantics for standard I/O, in particular 
with regard to listening socket units.  Some more Linuxisms have been 
added.  Limits (where applicable) can now take SI and IEC suffixes (so 
you can, say, express limits in kiloseconds).  This latter is actually 
an augmentation to the underlying softlimit command.


Passing more open sockets to connection-accepting programs
==

The improvements to systemd unit conversion also allow passing more than 
one listen()ing socket to connection-accepting programs.  You can use, 
say, ListenStream and ListenDatagram and the conversion utility will 
translate this into an appropriate chain of multiple invocations of 
udp-socket-listen and tcp-socket-listen.  It will do 
local-stream-socket-listen, local-datagram-socket-listen, 
netlink-datagram-socket-listen, and fifo-listen too.


The motivator for this was Daniel J. Bernstein's dnscache.  I have 
modified versions of tinydns, dnscache, and taiclockd that understand 
the LISTEN_FDS protocol for their being told about listening sockets 
that have been opened for them, and don't open their own sockets in that 
case.  dnscache, in particular, takes a UDP socket and a listening TCP 
socket.  The UCSPI tools in this version of the toolset can now provide 
these two to a dnscache process.  One simply chains through 
udp-socket-listen and tcp-socket-listen to dnscache, using the 
--systemd-compatibility flag.


The sharp-eyed will notice that the tinydns and dnscache services are 
following in the footsteps of the mariadb and mysql services, being 
instantiated for relevant IP addresses by the configuration import 

Re: Wheezy Xfce losing mouse clicks

[David Christensen]

On 08/04/2016 03:54 AM, Mark Fletcher wrote:
> If your mouse is Bluetooth / wireless, it could be the battery needs
> replacing or you could be near the limit of its range to the receiver. I
> had a similar problem to this until I used a usb extension lead to allow me
> to have the receiver on the desk near the mouse. That fixed it for me.

The mouse connected when malfunctions occurred is a Microsoft Wheel
Mouse Optical USB and PS/2 Compatible, P/N X802382-018.

The mouse currently under test is a Microsoft Wheel Mouse Optical USB
and PS/2 Compatible, P/N X05-87477.  So for, there have been very few
malfunctions.


Both connect through an IOGEAR MiniView 8 port PS/2 KVM switch GCS78,
which has known EDID (VGA) problems with Debian.


The next time I am using my laptop stand-alone, I will do more mouse
testing.


David

Re: gcc-doc in stretch

[Steven Tan]

Thanks for clarifying.

On Sat, Aug 6, 2016 at 7:32 AM, Christian Seiler  wrote:

> On 08/06/2016 04:08 PM, Steven Tan wrote:
> > https://packages.debian.org/search?keywords=gcc-doc;
> searchon=names=all=all
> > It looks like the package gcc-doc is not provided in stretch, not even in
> > contrib or non-free, but the package is provided in jessie and sid.
> >
> > Is this a bug or intended?
>
> Well, it's a bug, but in gcc-doc. It currently fails to build
> from source, and the maintainer hasn't fixed it yet, so it
> was autoremoved from testing a month or so ago:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825320
> https://tracker.debian.org/news/782354
>
> Once that bug is fixed, it can reenter testing. (Assuming no
> other RC bug is filed in the mean time.)
>
> Regards,
> Christian
>

Re: gcc-doc in stretch

[Christian Seiler]

On 08/06/2016 04:08 PM, Steven Tan wrote:
> https://packages.debian.org/search?keywords=gcc-doc=names=all=all
> It looks like the package gcc-doc is not provided in stretch, not even in
> contrib or non-free, but the package is provided in jessie and sid.
> 
> Is this a bug or intended?

Well, it's a bug, but in gcc-doc. It currently fails to build
from source, and the maintainer hasn't fixed it yet, so it
was autoremoved from testing a month or so ago:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825320
https://tracker.debian.org/news/782354

Once that bug is fixed, it can reenter testing. (Assuming no
other RC bug is filed in the mean time.)

Regards,
Christian

Re: Problem with NON-STANDARD install

[Felix Miata]

Pascal Hambourg composed on 2016-08-06 12:01 (UTC+0200):
...

If the boot image is in a PBR, the BIOS won't load it directly


It will if the PBR is on a primary partition on the same disk. It's how all 
my systems boot if I'm not using IBM Boot Manager as the primary bootloader.


...

- or as a regular file in a filesystem appearing as
/boot/grub/i386-pc/core.img (or /boot/grub/core.img with older versions
of GRUB such as the one in Wheezy). This option is not recommended as
the filesystem may move the blocks around and the location of the core
image is hardcoded into the boot image.


This "not recommended" philosophy corresponds almost perfectly with the 
practice universally complained about that Windows' installer replaces Grub 
code that it finds in the MBR with its own legacy/generic boot code, code 
which is just as capable of loading Grub code from a primary partition's PBR 
as it is loading Windows code from a primary partition's PBR, which is how 
Windows normally boots. When Grub is installed to a primary partition's PBR 
in the first place, Windows "hijacking" the MBR is a non-issue.[1]


As a practical matter, moving core image blocks around is uncommon, and just 
as easily fixed if and when it does occur as is reinstalling Grub to the MBR.


[1]

--
"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: nosh and redo have moved

[Andy Smith]

Hello,

On Fri, Aug 05, 2016 at 07:52:54PM +0200, Andre Majorel wrote:
> In a nutshell, Virgin Media shut http://homepage.ntlworld.com/
> down without warning.

A poster child for the virtues of serving content you care about
under a domain name you control (as much as one can control a domain
name).

Cheers,
Andy

RE: Executar script na inicialização

[Leandro Moreira]

Pessoal, bom dia!

Segue abaixo o script que mencionei em meu email anterior, é um script básico 
de setup do sistema operacional, ele executa no boot mas não interage com o 
usuário que esta fazendo o setup, ficando o /etc/network/interfaces conforme 
abaixo.

iface eth0 inet static
 address
 netmask
 gateway
 dns-domain
 dns-nameservers ,

Depois do primeiro boot, ele nunca mais será executado, eu me pergunto ser já 
não há algo desse tipo pronto e eu não estou sabendo como procurar e em virtude 
disso estou tentando reinventar a roda.

#!/bin/bash
# Script de setup linux
# Author: Leandro Moreira
# Release: 0.1
# Date: 05/08/2018
# Email: lean...@leandromoreirati.com.br


# -
# VARIAVEL
# -
ECHO=$(which echo)
HOSTNAME=$(which hostname)
RED='\033[0;31m'
NC='\033[0m' # No Color
INTERFACE="/etc/network/interfaces"
REBOOT=${which reboot}
PASS=${which passwd}

$ECHO -e "${RED}# -${NC}"
$ECHO -e "${RED}# ${RED}HOSTNAME${NC}"
$ECHO -e "${RED}# -${NC}"


$ECHO -n "Insira o Hostname do servidor: "

read a

$HOSTNAME $a

$ECHO -e "${RED}# -${NC}"
$ECHO -e "${RED}# ${RED}NETWORK${NC}"
$ECHO -e "${RED}# -${NC}"

$ECHO -n "Insira o endereço IP do servidor" `$HOSTNAME`": "
read b

$ECHO -n "Insira mascarra de rede" `$HOSTNAME`": "
read c

$ECHO -n "Insira o dafault gateway da rede" `$HOSTNAME`": "
read d

$ECHO -n "Insira o nome de domínio da rede" `$HOSTNAME`": "
read e

$ECHO -n "Insira o nome DNS primário da rede" `$HOSTNAME`": "
read f

$ECHO -n "Insira o nome DNS secundário da rede" `$HOSTNAME`": "
read g

$ECHO "allow-hotplug eth0" >> $INTERFACE
$ECHO "iface eth0 inet static" >> $INTERFACE
$ECHO " address $b" >> $INTERFACE
$ECHO " netmask $c" >> $INTERFACE
$ECHO " gateway $d" >> $INTERFACE
$ECHO " dns-domain $e" >> $INTERFACE
$ECHO " dns-nameservers $f,$g" >> $INTERFACE

$REBOOT

Desde já agradeço a todos a atenção

__
Leandro Moreira
Network Administrator
LPIC1 - Linux Professional Institute Certified
e-mail/msn: lean...@leandromoreira.eti.br
Tel.: + 55(32) 9906-5713 


From: lean...@leandromoreira.eti.br
To: debian-user-portuguese@lists.debian.org
Subject: Executar script na inicialização
Date: Fri, 5 Aug 2016 22:42:56 -0300




Prezados, boa noite!

Desenvolvi um script para realizar em servidores algumas configurações iniciais 
tais como como hostname e rede.

Preciso que ele seja executado na inicialização do linux (preferenciamente 
antes de aparecer o login do usuário), tentei fazer ele executar o script 
colocando-o no /etc/rc.local, tentei colocando ele no /etc/init.d e excutando o 
systemctl enable script.sh e nada.

Alguém tem alguma sugestão de como posso fazer essa configuração.

Desde já agradeço a todos pela atenção.

Att.

__
Leandro Moreira
Network Administrator
LPIC1 - Linux Professional Institute Certified
e-mail/msn: lean...@leandromoreira.eti.br
Tel.: + 55(32) 9906-5713 
  
  

gcc-doc in stretch

[Steven Tan]

Hi,

https://packages.debian.org/search?keywords=gcc-doc=names=all=all
It looks like the package gcc-doc is not provided in stretch, not even in
contrib or non-free, but the package is provided in jessie and sid.

Is this a bug or intended?

Thank you.

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

[Jonathan de Boyne Pollard]

Jonathan de Boyne Pollard:

Untrue. The OpenRC people have had a tmpfiles utility since 2012.


Michael Biebl:

I didn't know that. Thanks for the info.
Can you post some more details? Where can I find the sources for that?
Is it packaged for Debian?



Here's the Gentoo OpenRC repository:

* https://gitweb.gentoo.org/proj/openrc.git/log/sh/tmpfiles.sh.in

Here's a mirror:

* https://github.com/OpenRC/openrc

Here are the Debian packages:

* https://tracker.debian.org/pkg/openrc

Re: Problem with NON-STANDARD install

[Richard Owlett]

On 8/6/2016 5:01 AM, Pascal Hambourg wrote:

[snip details of where GRUB files are which I'm going have to study closely]

So, what did you mean exactly by "install GRUB on its own
partition" ?


I suspect my visualization of GRUB and the entire boot process is 
flawed. Some of my early reading may have been over simplified 
leading to some things I "know" just don't match reality. As I've 
said before "If retirement isn't for learning, what use is it?"


Thank you.

Re: Problem with NON-STANDARD install

[Pascal Hambourg]

Le 06/08/2016 à 12:01, Pascal Hambourg a écrit :


The first chunk is the "boot image" and must be stored into a MBR (whole
disk boot sector) or PBR (partition boot sector). As it must fit into a
512-sector size


Oops. I meant 512-byte sector size.

Re: Problem with NON-STANDARD install

[Pascal Hambourg]

Le 01/08/2016 à 21:15, Joe a écrit :


There are two chunks of storage for grub:


Actually three, or even four.


the files, stored in a normal filesystem and available under /boot,


Actually /boot/grub. GRUB does not store anything directly in /boot.


and the bootloader itself, which
generally lives in the drive MBR, but can also live in a partition. The
bootloader is machine code which is stored outside any filesystem.


The files in /boot/grub are also part of the bootloader. GRUB cannot 
display its menu or boot any OS without them.


The first chunk is the "boot image" and must be stored into a MBR (whole 
disk boot sector) or PBR (partition boot sector). As it must fit into a 
512-sector size, all it does is load the next chuck using a hardcoded 
block list.


If the boot image is in a PBR, the BIOS won't load it directly so it 
must be chainloaded by another (primary) bootloader. The primary 
bootloader can be a standard MBR boot code (MSDOS style) which just 
loads and boot the PBR of the primary partition which has the "boot" 
flag set, or another bootloader such as LILO or another GRUB instance 
installed in the MBR.


The second chunk is the "core image". For historical technical reasons 
its size is about 30 kB, sometimes a bit more. It has three possible 
locations :
- on an MSDOS-partitionned disk, in the unallocated space between the 
MBR and the first partition (MBR gap). This space used to be 31 KiB when 
partitions were aligned on cylinder boundaries, but is now ~1 MB since 
partitions are aligned on 1 MiB boundaries ;
- on a GPT-partitionned disk, in a dedicated unformatted "BIOS boot" 
partition ;
- or as a regular file in a filesystem appearing as 
/boot/grub/i386-pc/core.img (or /boot/grub/core.img with older versions 
of GRUB such as the one in Wheezy). This option is not recommended as 
the filesystem may move the blocks around and the location of the core 
image is hardcoded into the boot image. Also this option is not possible 
when /boot/grub is not on the same disk as the boot image or not on a 
plain partition, e.g. on LVM, some software RAID levels, encrypted volume...


The first two locations (not in /boot/grub) are called "embedded".

Now, the confusion comes when you select the device to install GRUB. 
Actually this only selects the location of the boot image, i.e. in an 
MBR (if selecting a whole disk /dev/sdX) or a PBR (when selecting a 
partition /dev/sdXN). The location of the core image will be chosen 
automatically : embedded if possible, as a file otherwise.


Embedding is not possible if the core image is larger than the MBR gap 
on an MSDOS disk, if there is no BIOS boot partition on a GPT disk, or 
if the boot image is stored in a PBR.


In any case, AFAIK the boot image and the core image must be on the same 
disk.


The third chunk is the files in /boot/grub. In order to be able to read 
them, the core image will include the required modules to read the 
partition table and filesystem and optionally software RAID, LVM if 
needed. Not sure about encryption. I never managed to boot with 
/boot/grub on an encrypted volume.


The fourth chunk is the kernel and initrd/initramfs files that GRUB 
loads to boot an OS, as they are part of the boot process (but not part 
of GRUB itself). It can be located anywhere GRUB with all its modules 
can read. It is usually in /boot.


If the boot image fails to load the core image, you'll get an error and 
can do nothing but reboot. This happens when the core image was not 
embedded and either filesystem blocks were moved around or the partition 
containing /boot/grub was deleted.


If the core image fails to find the modules in /boot/grub/i386-pc/, it 
will drop into a rescue shell with limited capabilities, allowing to 
display known devices and correct the $prefix variable. This typically 
happens after the partition which contained /boot/grub has been deleted.


If it fails to find the /boot/grub/grub.cfg file, it will drop into a 
full-featured shell (the same you start by pressing 'c' in the boot 
menu) instead of displaying the boot menu.


So, what did you mean exactly by "install GRUB on its own partition" ?

Re: IceWeasel (Firefox) Update?

[Curt]

On 2016-08-04, afamilyofbetatesters hendersonpark 
 wrote:
>
> This may not even be possible, but how can I update the IceWeasel (Firefox)
> from 45 (old) to the current 47? I need it on 47 to be able to use a
> platform I use instead of skype :)
>

I don't believe Iceweasel gets updated to Firefox 47; many us go here

http://mozilla.debian.net/

where you can obtain (follow the instructions) the backported release
version of Firefox (which will give you 47.0.1 in Wheezy or Jessie, one
of which I assume you're running).

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

Re: Info

[Mark Fletcher]

On Tue, Jul 26, 2016 at 9:27 PM Satya Prakash Prasad <
satyaprakash.pra...@gmail.com> wrote:

> I am in need to build gcc-4.9/libgcc1_4.9.2-10_amd64.deb locally so that I
> can copy this deb file to another host for installation.
>
> I am aware that we can build .deb & install file using below steps:
>
> # apt-get source gcc-4.9
> # apt-get build-dep gcc-4.9
> # cd 
> # dpkg-buildpackage -uc -us
> # dpkg -i 
>
> I tried out the steps and found that during build process a lot of test
> suites where also executed - is there a way confirm its acceptance criteria
> or certify the package build?
>
> Is there a report where can refer of the test suite it ran during the
> build operation - which failed / which passed / issues or concern if any?
>
> Regards,
> Prakash
>
> Look at the output of the build process. Especially the "make check" step.
It should tell you where it put the report.

Mark