List Partners and Email Brokers

[Noah Parker]

Hi,

Would you be interested in list acquisition specifically like Email list 
purchase, marketing list purchase, company profiling and email marketing?

We are a comprehensive data solutions provider, helping SMBs and large 
enterprises successfully manage data for marketing and communication. We 
provide with hand crafted, individual solutions to suit your business needs. We 
compile and maintain the 30 million US multi-channel business contacts with 
email addresses, 45 million Global multi-channel business contacts with email 
addresses and 210 million Consumer records with email addresses and over 300 
demographic, lifestyle, interest, and transaction fields.

Please let me know your interest and I'll get back to you with more information 
for your requirement along with few sample data to check the quality of our 
services.

I look forward for your response,

Best regards,
Noah Parker
Business Development Manager

Multichannel Prospect Lists | Email Appending | Email Verification & Validation 
| Contact Finder | 360 Degree Profiling | B2B Modeling | Tier 1/Tier 2 
Real-time Tele-validation | Business Database

Multiple independent terminals on a single machinde

[Richard Owlett]

I use the MATE desktop. I had originally thought I could achieve my 
goals using MATE's workspaces.


I found one reference stating explicitly that it cannot be done.

Workspaces in Mate can be individually named, but they share the same 
wallpaper and desktop icons with each other.


Therefore I'll change my metaphor.
It is routine for one machine to support multiple independent terminals.
Logically one expect that those terminals could appear on the host device.

How might this be done?
TIA

Re: Something eating diskspace in Testing

[David Christensen]

On 02/16/18 21:51, Johan DS wrote:

hi
I have testing installed with a separete /Home partition.

My root partition /dev/sda2 is slowly filling up. In a few hours it goes
from 7GB to 15GB.
Until there is no more space. I used ncdu. And also did
ls and finds for big files and/or directories . But I can not find a file
or directory that eats up space.

Any body a clou?


Unix has a feature whereby a program can open a file, save the file 
handle, and then unlink the file.  Once unlinked, the file is 
inaccessible to most (all?) other programs, but the originating program 
can still access the file contents via the saved file handle.  When the 
program closes the file handle, the file contents on disk are freed. 
See unlink(2).



So, you could have a process that uses the above trick to create and 
write to a file (likely a temporary file), but never stops writing.



In any case, I would try lsof(8).


David

Something eating diskspace in Testing

[Johan DS]

hi
I have testing installed with a separete /Home partition.

My root partition /dev/sda2 is slowly filling up. In a few hours it goes
from 7GB to 15GB.
Until there is no more space. I used ncdu. And also did
ls and finds for big files and/or directories . But I can not find a file
or directory that eats up space.

Any body a clou?

Remote Commands to mplayer Seem to Trigger Multiple Responses.

[Martin McCormick]

If I ssh from one jessie system to another, I am noticing that
keyboard commands that should be received by the remote system
seem to live on and cause secondary responses that generally do
nothing but produce odd error messages but something is not quite
normal.

As an example, I use one system as a terminal in to
another via ssh.  I will tell that system to start mplayer and
play a file and it does mostly just fine but if I, for example,
use the { or } to halve or double playback speed, I also see the
following message:

[AO_ALSA] Unable to find simple control 'Master',0.

Obviously, alsa thinks I am trying to do something to
that virtual pot in amixer but the system in question has no
control named 'Master',0 so nothing else happens but many
commands to mplayer cause that same message to appear even though
the desired effect also occurred.

I think this is not necessarily a mplayer or alsa issue
but may have something to do with the way the shell cleans up
after user input.

This is all relatively recent so it has me baffled.

Any ideas as to why or even better, what can one do to
prevent this behavior?

I almost forgot that the terminal type I am using is
Linux on everything.  For many years, I used vt100 or vt102 as
the terminal type but then discovered that it was probably better
to use linux which appears to be rather vt100-like.

Any ideas as to what is happening and best yet, how to fix it are
appreciated as this is not a show stopper but in the category of
kind of odd and not supposed to be happening.

Martin McCormick WB5AGZ

[likely out of luck] was -- Re: Using MATE's workspaces effectively

[Richard Owlett]

On 02/16/2018 06:32 AM, Richard Owlett wrote:

I have no problem with different applications being open in each workspace.

What I would like would be to be able to do is have differing sets of 
applications available in each workspace.


Currently all workspaces have icons to access _identical sets_ of 
applications.


For example one might have one workspace having a set of tools for 
writing/debugging software, another with a set of tools for researching 
Mesopotamian Architecture, and one focused on creating a weekly blog 
discussing advances in fly fishing.


I chose disparate sets too convey an idea I couldn't describe well.
Is there a more appropriate tool that maintains the "look and feel" of 
the MATE desktop? Comments?

TIA


Doing a web search I found 2 references suggesting what I want can't be 
done:




Workspaces in Mate can be individually named, but they share the same wallpaper 
and
desktop icons with each other.


 
post of "Jan 30 '15" asked:> I'm running MATE 1.8 in Linux Mint 17 
Qiana. I have three workspaces set up,

and panels at the top and bottom of the screen. I have a bunch of items in the
top panels that launch various applications and documents etc.

Is it possible to get the set of items to differ per-workspace, by having either
panels or items in them only show up in particular workspaces?

There has not yet been a response.

Both are good descriptions of what I want.
If it cannot be done in MATE, is there another desktop or approach that 
will accomplish my goal?

TIA

Re: Using MATE's workspaces effectively

[Richard Owlett]

On 02/16/2018 03:41 PM, Cindy-Sue Causey wrote:

On 2/16/18, songbird  wrote:

Richard Owlett wrote:
...

What I would like would be to have differing sets of applications
available in each workspace.


   i understood you the first time you wrote that.



Currently all workspaces have icons to access *_identical sets_* of
applications.


   something is set to do that then, because i can set all of
my workspaces with different applications open in each of them.

   do you have "Always on Visible Workspace" set instead of
"Only on this Workspace"?  [right click on window or on item
at the bottom of the screen...]

   i never shutdown without checking all desktops for things that
need to be saved.  but more importantly remember that if you
don't use shutdown after the first time it will restart them all
as you had them when you did shutdown.

   my normal end of session routine is to use the "shutdown -h now"
command as root which kills everything and does not alter what is
opened next time.

   when i want to make changes to my desktops then i do use
the menu shutdown and that then records the changes as
desired.



What about a new personalized "panel"?

Cindy.



If PANELa was visible only in WORKSPACE1
AND
IF PANELb was visible only in WORKSPACE2

That might be even a better solution -- leaving things you *ALWAYS* want 
available to reside on desktop.


How?
TIA

Re: Using MATE's workspaces effectively

[Richard Owlett]

On 02/16/2018 02:51 PM, songbird wrote:

Richard Owlett wrote:
...

What I would like would be to have differing sets of applications
available in each workspace.


   i understood you the first time you wrote that.


 and/or 
I beg to differ ;<

In my initial post I attempted to describe what I wanted.
In my last post I gave a concrete {even if contrived} example of goal.

This time I'll borrow from set theory.
*CAVEAT LECTOR* Last time I saw set theory was in Introduction to Logic"> circa 1962.

Currently all workspaces have icons to access *_identical sets_* of
applications.


This may be crux of issue.
I used "set" in the set theory sense.
I said *nothing" about what was open anywhere/anywhen.
IOW
WORKSPACE1's desktop displays only launch icons from SETalpha
WORKSPACE2's desktop displays launch icons from SETbeta and SETgamma
WORKSPACE3's desktop displays only launch icons from the intersection of 
SETomicron and SETzeta






   something is set to do that then, because i can set all of
my workspaces with different applications open in each of them.

   do you have "Always on Visible Workspace" set instead of
"Only on this Workspace"?  [right click on window or on item
at the bottom of the screen...]

   i never shutdown without checking all desktops for things that
need to be saved.  but more importantly remember that if you
don't use shutdown after the first time it will restart them all
as you had them when you did shutdown.

   my normal end of session routine is to use the "shutdown -h now"
command as root which kills everything and does not alter what is
opened next time.

   when i want to make changes to my desktops then i do use
the menu shutdown and that then records the changes as
desired.


   songbird

Re: Using MATE's workspaces effectively

[Cindy-Sue Causey]

On 2/16/18, songbird  wrote:
> Richard Owlett wrote:
> ...
>> What I would like would be to have differing sets of applications
>> available in each workspace.
>
>   i understood you the first time you wrote that.
>
>
>> Currently all workspaces have icons to access *_identical sets_* of
>> applications.
>
>   something is set to do that then, because i can set all of
> my workspaces with different applications open in each of them.
>
>   do you have "Always on Visible Workspace" set instead of
> "Only on this Workspace"?  [right click on window or on item
> at the bottom of the screen...]
>
>   i never shutdown without checking all desktops for things that
> need to be saved.  but more importantly remember that if you
> don't use shutdown after the first time it will restart them all
> as you had them when you did shutdown.
>
>   my normal end of session routine is to use the "shutdown -h now"
> command as root which kills everything and does not alter what is
> opened next time.
>
>   when i want to make changes to my desktops then i do use
> the menu shutdown and that then records the changes as
> desired.


What about a new personalized "panel"?

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

* runs with duct tape *

Re: Using MATE's workspaces effectively

[songbird]

Richard Owlett wrote:
...
> What I would like would be to have differing sets of applications 
> available in each workspace.

  i understood you the first time you wrote that.


> Currently all workspaces have icons to access *_identical sets_* of 
> applications.

  something is set to do that then, because i can set all of
my workspaces with different applications open in each of them.

  do you have "Always on Visible Workspace" set instead of
"Only on this Workspace"?  [right click on window or on item
at the bottom of the screen...]

  i never shutdown without checking all desktops for things that
need to be saved.  but more importantly remember that if you
don't use shutdown after the first time it will restart them all
as you had them when you did shutdown.

  my normal end of session routine is to use the "shutdown -h now"
command as root which kills everything and does not alter what is 
opened next time.

  when i want to make changes to my desktops then i do use
the menu shutdown and that then records the changes as 
desired.


  songbird

Re: Using MATE's workspaces effectively

[Richard Owlett]

On 02/16/2018 10:53 AM, songbird wrote:

Richard Owlett wrote:

I have no problem with different applications being open in each workspace.

What I would like would be to be able to do is have differing sets of
applications available in each workspace.

...

   under System->Preferences->Personal->Options make sure
you have checked the box for automatically remembering
started applications.

   then, set up your workspaces and when you turn off the
machine use System->Shutdown->Shutdown and it should remember
all of your open windows and where they were located.

   works for me...


That's not quite what I'm trying to accomplish.
When I shut down the machine for the day I want to exit all apps.
I currently get pretty much that. If an application has modified a file 
but not saved it, I'm prompted for instructions.



What I would like would be to have differing sets of applications 
available in each workspace.


Currently all workspaces have icons to access *_identical sets_* of 
applications.


I wish each workspace to have a set of tools applicable for a specific 
project.


For example:
Workspace 1 devoted to programming would have a programmer's text 
editor, compile/link/load utilities, and an IDE.
Workspace 2 devoted to a dissertation on Mesopotamian Architecture 
would have a word processor, note taking software, an outlining utility, 
and a link to a browser to bring up the university's online catalog.

Workspace 3 devoted to a fishing blog would have web authoring tools.

Re: wiki

[Brian]

On Fri 16 Feb 2018 at 16:58:49 +, Andy Smith wrote:

> Hello,
> 
> On Fri, Feb 16, 2018 at 10:38:49AM -0500, Greg Wooledge wrote:
> > There have been several similar complaints in #debian IRC over the last
> > year or two, with random people coming in and saying that they get a
> > "403 Forbidden" on the Debian wiki, but the one thing they all have in
> > common is a LACK OF DETAIL.
> 
> I seem to recall some comments made by someone in the know that
> there is extensive IP-based blocking used on wiki.debian.org within
> the web server and this sometimes causes collateral damage, i.e.
> some people unable even to read the site, let alone modify it.
> Unfortunately I can't remember any more details than that.

IP-based blocking is most probably the cause. The reason for it is
to prevent the wiki being spammed and reducing its usefulness for all
users. 

> I was going to say that it could be worth OP's time to create a bug
> against the wiki, and I already see this one:
> 
> 
> 
> I think this would tend to support the possibility of this being
> the culprit, though the lack of resolution here does suggest the OP
> may have a long road ahead if that is the case.

No bug reports, please. The preferred way is to report the details of
the issue by mail to w...@debian.org.

-- 
Brian.

Re: Re (2): Configuration of router.

[David Wright]

On Fri 16 Feb 2018 at 07:28:45 (-0800), pe...@easthope.ca wrote:
> * From: David Wright €deb...@lionunicorn.co.uk€
> * Date: Thu, 15 Feb 2018 15:18:45 -0600
> > Write …bashrc ; wake ; sleep 5'
> > and give yourself 5 seconds to read what it says in the xterm.
> 
> Interactively.
> peter@hertz:~$ declare -f wake
> wake () 
> { 
> input="";
> until [[ $input != "" ]]; do
> echo Beginning loop.;
> /usr/bin/play /usr/share/sounds/ekiga/ring.wav;
> read -n 1 -t 4 input;
> done
> }
> 
> Therefore my .bashrc creates wake.
> 
> Nevertheless,
> peter@hertz:~$ xterm -display :0 -e bash -c '. ~/.bashrc; declare -f wake; 
> sleep 5'
> shows a black xterm, which, after 5 s, closes.  Appears that this 
> declaration fails.

This is odd. The attached shows what happens here. I should explain
that my .bashrc is noisy when interactive, as you can see in the outer
window. I changed wake to inform as I have that self-defined function
available, and I gave myself 15 seconds for taking the screenshot.
(BTW I would normally use type, it's shorter.)

> That has become a secondary problem.  My current priority is to find 
> why at fails to open the xterm at the specified future time. None of 
> the at documents I've found mention error reporting.  Can a failure of 
> at be investigated without changing and recompiling the source?

I can't help you there as I've never used "at" in anger. My strategy
for a decade or more has been to use cron. Every minute cron runs a
python program which:

  Looks for directory entries of the form 2000-02-29-12-34-foo[-*]
  (where the year, month, day, hour and minute all match the current
  time) in the {crondir} directory and, if found, executes {bindir}/foo from
  the home directory thus:

. $HOME/{init} ; $HOME/{bindir}/foo -c $HOME/{crondir}/entry

  The entry can be a file, link, or any other kind of directory entry.
  Environment variables needed can be set in {init}.
  Any backup entries *~ are ignored.

Foo gets handed its commandline (to find out what symlink it was called
by) and extracts the [-*] information above to get its arguments, from
which it knows things like what channel the radio is tuned to (for
setting input gain), and how many minutes to record from it.

So it's a little similar to what I think you're doing, but more flexible.
In terms of simplicity, it has nothing to do with X etc and doesn't
use stdin/out. Instead, recording is controlled by its touching a file
at startup called "2000-02-29-12-34-stoprecording" which is processed
in exactly the same way. This allows recordings to be curtailed or
extended by renaming the file without having to communicate with the
recording program itself (normally running headless): it runs until
stoprecording pops up and kills it.

It's all integrated into my arrangements for recording vinyl/cassettes
to file, and making recordings of arbitrary length on the spur of the
moment. I have a showtimes program that checks all the files to make
sure there are no time overlaps, and estimates diskspace requirements.

Cheers,
David.

Re: failed to set console font and keymap

[Anil Duggirala]

> I tried "dpkg-reconfigure keyboard-configuration", choosing UK Int
> w/dead keys. I am still getting the same error. I had also before,
> tried setting the layout with the Gnome tool. My layout is working
> perfectly, but I keep getting the same error, "failed to set console
> font and keymap" at boot time.
> thanks
> 

Actually, the error says. "Failed to start Set console font and
keymap".

Re: failed to set console font and keymap

[Anil Duggirala]

> Is this a place where "dpkg-reconfigure keyboard-configuration" might
> come into play? I only know that one because of debootstrap. :)
> 
> Cindy :)

I tried "dpkg-reconfigure keyboard-configuration", choosing UK Int
w/dead keys. I am still getting the same error. I had also before,
tried setting the layout with the Gnome tool. My layout is working
perfectly, but I keep getting the same error, "failed to set console
font and keymap" at boot time.
thanks

Re: wiki

[Gene Heskett]

On Friday 16 February 2018 11:53:44 Reco wrote:

>   Hi.
>
> On Fri, Feb 16, 2018 at 10:38:49AM -0500, Greg Wooledge wrote:
> > On Fri, Feb 16, 2018 at 10:30:31AM -0500, Gene Heskett wrote:
> > > On Friday 16 February 2018 07:08:57 Rodary Jacques wrote:
> > > > Le vendredi 16 février 2018, 06:42:52 CET rhkra...@gmail.com a 
écrit :
> > > > > On Thursday, February 15, 2018 08:42:14 PM Rodary Jacques 
wrote:
> > > > > > Why can't I access wikis from a Debian box:
> > > > > > Forbidden
> > > > > > You are not allowed to access this!
> > > > > > is the message I get.
> > > > >
> > > > > I think we need more information--which wiki are you having
> > > > > trouble with? (What is its URL?)
> > > >
> > > > I first had this message on  https://wiki.debian.org, then on
> > > > various problems.
> > >
> > > Old but uptodate wheezy install here. firefox had no problems
> > > navigating the site.
> > > Perhaps your http->S<- is defective somehow.
> >
> > The original message was so incredibly vague that it could mean
> > anything.
> >
> > But.
> >
> > If the actual complaint is "I get 403 Forbidden on
> > https://wiki.debian.org"; then we need additional detail: what
> > version of Debian the OP is using, what browser, and any unusual
> > aspects of the OP's network that could be relevant (workplace
> > firewall, China firewall, etc.).
>
> My crystal ball says that OP is using home connection, and no, these
> details aren't needed. tcpdump/wireshark capture, combined with the
> SSL session key - that's what needed.
> Or someone from 11AS12322 willing to provide a temporary shell
> account.
>
> E-mail headers say that e-mail came from 11AS12322 belonging to some
> French provider:
>
> Received: from ns.rodary.net (unknown [88.170.1.143])
> by smtp5-g21.free.fr (Postfix) with ESMTP id 154405FF27
> for ; Fri, 16 Feb 2018 02:42:15
> +0100 (CET)
>
> With MUA which is uncommon in dull enterprise world:
>
> User-Agent: KMail/5.2.3 (Linux/4.9.0-5-amd64; KDE/5.28.0; x86_64; ; )
>
> I believe we can exclude such possibilities as China Great Firewall
> (unless they installed it in France for some reason), or workplace SSL
> Bump (else OP won't see HTTP 403).
>
> > There have been several similar complaints in #debian IRC over the
> > last year or two, with random people coming in and saying that they
> > get a "403 Forbidden" on the Debian wiki, but the one thing they all
> > have in common is a LACK OF DETAIL.
>
> Whose who know they way around don't have such problems. Whose who
> don't are unable to describe it. I see nothing unusual in this.
>
> My suggestion to OP - try Tor, see if it works.
>
> > At this point nobody knows how to diagnose the problem, because
> > nobody who HAS the problem is willing or able to come forward and
> > just say what is happening and why.  Is it a DNS resolution error,
> > in which they're getting the wrong IP address?
>
> No. Browsers do certificate validation, "wrong IP address" would be
> possible if the third party somehow produced a valid certificate for
> wiki.debian.org (you have to be a CA *or* the government to do this)
> and faked a DNS record (that's easy part).
>
> > Does the wiki or its front-end web server have a firewall that
> > blacklists certain IP address ranges?
>
> Even if it did, the firewall have not come into play.
> Since the user saw HTTP 403 it means that HTTPS connection was
> established successfully, and a front-end (or back-end) webserver gave
> 403 code, which was transferred to a user.
>
> >  Is it a web browser bug?  Nobody knows!
>
> Hardly. Of course OP could use some ancient toy browser that does not
> do SNI, but wiki.debian.org provides a correct certificate even for
> *those*. It's easy to check with (openssl does not use SNI unless you
> ask for it):
>
> openssl s_client -host wiki.debian.org -port 443
>
> Reco

That is quite a verbose tool, thank you Reco for enlightening me.


-- 
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: failed to set console font and keymap

[Gene Heskett]

On Friday 16 February 2018 11:17:22 Cindy-Sue Causey wrote:

> On 2/16/18, Cindy-Sue Causey  wrote:
> > On 2/16/18, Anil Duggirala  wrote:
> >> All I did was change "us" for "gb" in my /etc/default/keyboard
> >> file. I am now getting a "failed to set console font and keymap"
> >> message at bootup. The default keymap appears to have been changed,
> >> and everything works well otherwise.
> >> please help.
> >
> > Is this a place where "dpkg-reconfigure keyboard-configuration"
> > might come into play? I only know that one because of
> > debootstrap. :)
>
> I'm sorry, computer mouse must have stuck or double clicked again.
> It's just plum worn out. Will try to remember to tab over to the Send
> button if I send anything else

That is a classic mouse problem Cindy, one that I've had to repair at the 
tv station quite a few times. What happens is that the switch under the 
button was not seated in the pcb as it went thru the wave solder when it 
was originally made. So the switch may be sitting just a bit proud of 
the board. This leaves the solder joint at the only restriction of the 
switches movement. Eventually this breaks the bond between the copper 
foil of the pcb, and of course the foil then cracks at the edge of the 
blob of solder.

The cure is to take it apart, press the switches solidly to the board and 
put a teeny drop of cyanide glue into that contact to help immobilize 
the switch.  Give the glue time to work, an hour perhaps, then turn it 
over. Remove most of the solder on the switch legs, then scrape the 
green solder resist away from the now visible crack in the trace, form a 
short piece of stripped wrapping wire around the switch leg, extending 
out a bit past the crack, and resolder it, a solder with 2 or 3% silver 
is much tougher stuff, making sure to get the little bridging 
wire "wet". Put it back together and Voila! Brand new mouse again.

You may run with duct tape (I chuckle ever time I read your sig), but I 
am a C.E.T. and can walk with a hot soldering iron. But mine isn't a $20 
toy, its a $100+ workstation that can even do hot air soldering.

-- 
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: wiki

[Andy Smith]

Hello,

On Fri, Feb 16, 2018 at 10:38:49AM -0500, Greg Wooledge wrote:
> There have been several similar complaints in #debian IRC over the last
> year or two, with random people coming in and saying that they get a
> "403 Forbidden" on the Debian wiki, but the one thing they all have in
> common is a LACK OF DETAIL.

I seem to recall some comments made by someone in the know that
there is extensive IP-based blocking used on wiki.debian.org within
the web server and this sometimes causes collateral damage, i.e.
some people unable even to read the site, let alone modify it.
Unfortunately I can't remember any more details than that.

I was going to say that it could be worth OP's time to create a bug
against the wiki, and I already see this one:



I think this would tend to support the possibility of this being
the culprit, though the lack of resolution here does suggest the OP
may have a long road ahead if that is the case.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Using MATE's workspaces effectively

[songbird]

Richard Owlett wrote:
> I have no problem with different applications being open in each workspace.
>
> What I would like would be to be able to do is have differing sets of 
> applications available in each workspace.
...

  under System->Preferences->Personal->Options make sure
you have checked the box for automatically remembering
started applications.

  then, set up your workspaces and when you turn off the
machine use System->Shutdown->Shutdown and it should remember
all of your open windows and where they were located.

  works for me...


  songbird

Re: wiki

[Reco]

Hi.

On Fri, Feb 16, 2018 at 10:38:49AM -0500, Greg Wooledge wrote:
> On Fri, Feb 16, 2018 at 10:30:31AM -0500, Gene Heskett wrote:
> > On Friday 16 February 2018 07:08:57 Rodary Jacques wrote:
> > 
> > > Le vendredi 16 février 2018, 06:42:52 CET rhkra...@gmail.com a écrit :
> > > > On Thursday, February 15, 2018 08:42:14 PM Rodary Jacques wrote:
> > > > > Why can't I access wikis from a Debian box:
> > > > > Forbidden
> > > > > You are not allowed to access this!
> > > > > is the message I get.
> > > >
> > > > I think we need more information--which wiki are you having trouble
> > > > with? (What is its URL?)
> > >
> > > I first had this message on  https://wiki.debian.org, then on various
> > > problems.
> > 
> > Old but uptodate wheezy install here. firefox had no problems navigating 
> > the site.
> > Perhaps your http->S<- is defective somehow.
> 
> The original message was so incredibly vague that it could mean anything.
> 
> But.
> 
> If the actual complaint is "I get 403 Forbidden on https://wiki.debian.org";
> then we need additional detail: what version of Debian the OP is using,
> what browser, and any unusual aspects of the OP's network that could
> be relevant (workplace firewall, China firewall, etc.).

My crystal ball says that OP is using home connection, and no, these
details aren't needed. tcpdump/wireshark capture, combined with the SSL
session key - that's what needed.
Or someone from 11AS12322 willing to provide a temporary shell account.

E-mail headers say that e-mail came from 11AS12322 belonging to some
French provider:

Received: from ns.rodary.net (unknown [88.170.1.143])
by smtp5-g21.free.fr (Postfix) with ESMTP id 154405FF27
for ; Fri, 16 Feb 2018 02:42:15 +0100 
(CET)

With MUA which is uncommon in dull enterprise world:

User-Agent: KMail/5.2.3 (Linux/4.9.0-5-amd64; KDE/5.28.0; x86_64; ; )

I believe we can exclude such possibilities as China Great Firewall
(unless they installed it in France for some reason), or workplace SSL
Bump (else OP won't see HTTP 403).


> There have been several similar complaints in #debian IRC over the last
> year or two, with random people coming in and saying that they get a
> "403 Forbidden" on the Debian wiki, but the one thing they all have in
> common is a LACK OF DETAIL.

Whose who know they way around don't have such problems. Whose who don't
are unable to describe it. I see nothing unusual in this.

My suggestion to OP - try Tor, see if it works.


> At this point nobody knows how to diagnose the problem, because nobody
> who HAS the problem is willing or able to come forward and just say what
> is happening and why.  Is it a DNS resolution error, in which they're
> getting the wrong IP address?

No. Browsers do certificate validation, "wrong IP address" would be
possible if the third party somehow produced a valid certificate for
wiki.debian.org (you have to be a CA *or* the government to do this) and
faked a DNS record (that's easy part).

> Does the wiki or its front-end web server have a firewall that
> blacklists certain IP address ranges?

Even if it did, the firewall have not come into play.
Since the user saw HTTP 403 it means that HTTPS connection was
established successfully, and a front-end (or back-end) webserver gave
403 code, which was transferred to a user.

>  Is it a web browser bug?  Nobody knows!

Hardly. Of course OP could use some ancient toy browser that does not do
SNI, but wiki.debian.org provides a correct certificate even for
*those*. It's easy to check with (openssl does not use SNI unless you
ask for it):

openssl s_client -host wiki.debian.org -port 443

Reco

Re: wiki

[Gene Heskett]

On Friday 16 February 2018 10:38:49 Greg Wooledge wrote:

> On Fri, Feb 16, 2018 at 10:30:31AM -0500, Gene Heskett wrote:
> > On Friday 16 February 2018 07:08:57 Rodary Jacques wrote:
> > > Le vendredi 16 février 2018, 06:42:52 CET rhkra...@gmail.com a 
écrit :
> > > > On Thursday, February 15, 2018 08:42:14 PM Rodary Jacques wrote:
> > > > > Why can't I access wikis from a Debian box:
> > > > > Forbidden
> > > > > You are not allowed to access this!
> > > > > is the message I get.
> > > >
> > > > I think we need more information--which wiki are you having
> > > > trouble with? (What is its URL?)
> > >
> > > I first had this message on  https://wiki.debian.org, then on
> > > various problems.
> >
> > Old but uptodate wheezy install here. firefox had no problems
> > navigating the site.
> > Perhaps your http->S<- is defective somehow.
>
> The original message was so incredibly vague that it could mean
> anything.
>
> But.
>
> If the actual complaint is "I get 403 Forbidden on
> https://wiki.debian.org"; then we need additional detail: what version
> of Debian the OP is using, what browser, and any unusual aspects of
> the OP's network that could be relevant (workplace firewall, China
> firewall, etc.).
>
> There have been several similar complaints in #debian IRC over the
> last year or two, with random people coming in and saying that they
> get a "403 Forbidden" on the Debian wiki, but the one thing they all
> have in common is a LACK OF DETAIL.
>
> At this point nobody knows how to diagnose the problem, because nobody
> who HAS the problem is willing or able to come forward and just say
> what is happening and why.  Is it a DNS resolution error, in which
> they're getting the wrong IP address?  Does the wiki or its front-end
> web server have a firewall that blacklists certain IP address ranges? 
> Is it a web browser bug?  Nobody knows!

That also is spot on Greg. Which is why I specified my install in my 
comment, but failed to mention it is a 32 bit install. Thats linuxcnc 
driven because a context switch takes measurably longer on a 64 bit 
system.

The changeover to 64 bit is forceing some of us to spend upwards of 200 
dollars to offload some of linuxcnc's work to fpga cards because even 
the rtai patched kernels just aren't fast enough to generate in 
software, the steady step signals the stepper motors need.  Thats about 
how much I have in the 4 card stack driving an 11x36 Sheldon lathe from 
a raspberry pi-3b. But we still need IRQ responses in not less than 
millisecond times. So we patch kernels, and on real machinery, then pin 
them so the software updater cannot kill the machine. But I think that 
has been discussed here previously.

-- 
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: Re (2): Configuration of router.

[Greg Wooledge]

On Fri, Feb 16, 2018 at 07:28:45AM -0800, pe...@easthope.ca wrote:
> peter@hertz:~$ declare -f wake
> wake () 
> { 
> input="";
> until [[ $input != "" ]]; do
> echo Beginning loop.;
> /usr/bin/play /usr/share/sounds/ekiga/ring.wav;
> read -n 1 -t 4 input;
> done
> }
> 
> Therefore my .bashrc creates wake.

This only demonstrates that *something* defined your function.  It
doesn't prove that it was ~/.bashrc.  The obvious way to prove
whether it's ~/.bashrc doing it would be to read ~/.bashrc and see
what it says.

> Nevertheless,
> peter@hertz:~$ xterm -display :0 -e bash -c '. ~/.bashrc; declare -f wake; 
> sleep 5'
> shows a black xterm, which, after 5 s, closes.  Appears that this 
> declaration fails.

Use "type wake" instead of "declare -f wake", so that you at least get
an *error* if it's not defined.

wooledg:~$ declare -f wake
wooledg:~$ type wake
bash: type: wake: not found

> That has become a secondary problem.  My current priority is to find 
> why at fails to open the xterm at the specified future time. None of 
> the at documents I've found mention error reporting.  Can a failure of 
> at be investigated without changing and recompiling the source?

   An at - or batch - command invoked from a su(1) shell will  retain  the
   current  userid.   The  user will be mailed standard error and standard
   output from his commands, if any.  Mail will be sent using the  command
   /usr/sbin/sendmail.  If at is executed from a su(1) shell, the owner of
   the login shell will receive the mail.

This is rather poorly written, but if you ignore the leading and
trailing sentences about su, or if you simply *try* things and see
what happens, you should see that you will indeed be sent the stdout
and stderr from your at(1) jobs in email, just like with crontab jobs.

Testing now:

wooledg:~$ echo echo hello | at now + 1 minute
warning: commands will be executed using /bin/sh
job 2 at Fri Feb 16 11:19:00 2018

And yes, I got the expected email.

Re: failed to set console font and keymap

[Cindy-Sue Causey]

On 2/16/18, Cindy-Sue Causey  wrote:
> On 2/16/18, Anil Duggirala  wrote:
>> All I did was change "us" for "gb" in my /etc/default/keyboard file. I
>> am now getting a "failed to set console font and keymap" message at
>> bootup. The default keymap appears to have been changed, and everything
>> works well otherwise.
>> please help.
>
> Is this a place where "dpkg-reconfigure keyboard-configuration" might
> come into play? I only know that one because of debootstrap. :)


I'm sorry, computer mouse must have stuck or double clicked again.
It's just plum worn out. Will try to remember to tab over to the Send
button if I send anything else

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

* runs with duct tape *

Re: failed to set console font and keymap

[Cindy-Sue Causey]

On 2/16/18, Anil Duggirala  wrote:
> All I did was change "us" for "gb" in my /etc/default/keyboard file. I
> am now getting a "failed to set console font and keymap" message at
> bootup. The default keymap appears to have been changed, and everything
> works well otherwise.
> please help.


Is this a place where "dpkg-reconfigure keyboard-configuration" might
come into play? I only know that one because of debootstrap. :)

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

* runs with duct tape *

Re (2): Configuration of router.

[peter]

*   From: David Wright deb...@lionunicorn.co.uk
*   Date: Thu, 15 Feb 2018 15:18:45 -0600
> Write …bashrc ; wake ; sleep 5'
> and give yourself 5 seconds to read what it says in the xterm.

Interactively.
peter@hertz:~$ declare -f wake
wake () 
{ 
input="";
until [[ $input != "" ]]; do
echo Beginning loop.;
/usr/bin/play /usr/share/sounds/ekiga/ring.wav;
read -n 1 -t 4 input;
done
}

Therefore my .bashrc creates wake.

Nevertheless,
peter@hertz:~$ xterm -display :0 -e bash -c '. ~/.bashrc; declare -f wake; 
sleep 5'
shows a black xterm, which, after 5 s, closes.  Appears that this 
declaration fails.

That has become a secondary problem.  My current priority is to find 
why at fails to open the xterm at the specified future time. None of 
the at documents I've found mention error reporting.  Can a failure of 
at be investigated without changing and recompiling the source?

Thanks,  ... Peter E.



-- 

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202  Pender Is.: +1 250 629 3757
http://easthope.ca/Peter.html  Bcc: peter at easthope. ca

Re: wiki

[Greg Wooledge]

On Fri, Feb 16, 2018 at 10:30:31AM -0500, Gene Heskett wrote:
> On Friday 16 February 2018 07:08:57 Rodary Jacques wrote:
> 
> > Le vendredi 16 février 2018, 06:42:52 CET rhkra...@gmail.com a écrit :
> > > On Thursday, February 15, 2018 08:42:14 PM Rodary Jacques wrote:
> > > > Why can't I access wikis from a Debian box:
> > > > Forbidden
> > > > You are not allowed to access this!
> > > > is the message I get.
> > >
> > > I think we need more information--which wiki are you having trouble
> > > with? (What is its URL?)
> >
> > I first had this message on  https://wiki.debian.org, then on various
> > problems.
> 
> Old but uptodate wheezy install here. firefox had no problems navigating 
> the site.
> Perhaps your http->S<- is defective somehow.

The original message was so incredibly vague that it could mean anything.

But.

If the actual complaint is "I get 403 Forbidden on https://wiki.debian.org";
then we need additional detail: what version of Debian the OP is using,
what browser, and any unusual aspects of the OP's network that could
be relevant (workplace firewall, China firewall, etc.).

There have been several similar complaints in #debian IRC over the last
year or two, with random people coming in and saying that they get a
"403 Forbidden" on the Debian wiki, but the one thing they all have in
common is a LACK OF DETAIL.

At this point nobody knows how to diagnose the problem, because nobody
who HAS the problem is willing or able to come forward and just say what
is happening and why.  Is it a DNS resolution error, in which they're
getting the wrong IP address?  Does the wiki or its front-end web server
have a firewall that blacklists certain IP address ranges?  Is it a
web browser bug?  Nobody knows!

Re: wiki

[Gene Heskett]

On Friday 16 February 2018 07:08:57 Rodary Jacques wrote:

> Le vendredi 16 février 2018, 06:42:52 CET rhkra...@gmail.com a écrit :
> > On Thursday, February 15, 2018 08:42:14 PM Rodary Jacques wrote:
> > > Why can't I access wikis from a Debian box:
> > > Forbidden
> > > You are not allowed to access this!
> > > is the message I get.
> >
> > I think we need more information--which wiki are you having trouble
> > with? (What is its URL?)
>
> I first had this message on  https://wiki.debian.org, then on various
> problems.
>
> > Maybe you have to register and then login on that wiki.
>
> and I was never asked to register before you mention it.
>   Jacques

Old but uptodate wheezy install here. firefox had no problems navigating 
the site.
Perhaps your http->S<- is defective somehow.

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

colord[xxxxx]: failed to get session [pid yyyyy]: No data available

[Thomas Vaughan]

I've noticed this message about once per day just after midnight.

Googling about it did not seem (to me) to produce anything definitive,
but perhaps I did not try hard enough.

Does anybody here know
1. why this is being printed to the system log
2. whether I should just tell logcheck to ignore it, or
3. whether I should do something to make it stop?

-- 
Thomas E. Vaughan

Re: IT decision makers leads

[Jacob Matthew]

Thanks,



Jacob Matthew

Inside Sales Executive



*Our services includes-* List Acquisition; Email Appending; Email Campaign;
Company Profiling and Web Designing

We respect your privacy. If you want to stop receiving emails from us,
please send a reply with the email subject line as *"Leave Out**”*


On Thu, Feb 15, 2018 at 11:17 AM, Jacob Matthew 
wrote:

> Hi,
>
>
>
> Would you be interested in acquiring our recently updated contact list of *“IT
> decision makers”* with emails address? If so, please let me know your
> target audience. I will get back to you with counts and best pricing option.
>
>
>
> Note: If IT decision makers is not relevant to you please reply back with
> your requirement, we have all type of lists that would meet your quality
> prospecting-
>
>
>
> *Target Industry:  _; Geography:  __; Job Title
> (Any):  _:*
>
>
>
> Look forward to hearing from you.
>
>
>
> Thanks,
>
>
>
> Jacob Matthew
>
> Inside Sales Executive
>
>
>
> *Our services includes-* List Acquisition; Email Appending; Email
> Campaign; Company Profiling and Web Designing
>
> We respect your privacy. If you want to stop receiving emails from us,
> please send a reply with the email subject line as *"Leave Out”*
>
>

Re: BIND and iptables config

[Henning Follmann]

On Fri, Feb 16, 2018 at 04:26:14AM +0100, Rodary Jacques wrote:
> Le jeudi 15 février 2018, 11:44:36 CET Henning Follmann a écrit :
> > On Thu, Feb 15, 2018 at 05:01:52PM +0100, Rodary Jacques wrote:
> > > With NetworkManager, /etc/network/interfaces has only the loopbak 
> > > interface, and I can't use wicd which can't deal with two wired 
> > > interfaces. And, Henning Follmann, my English is too poor to explain 
> > > clearly my setup which is the standard one when your ISP gives you one 
> > > routable address and you want your home LAN to have access to internet.
> > >   Thanks for your interest anyway.
> > >   Jacques
> > > 
> > 
> > Hello,
> > no your english was good enough to describe your setup. And I would say
> > that 90% of "us" have a form of "dialup" with on routable ip address and a
> > NAT setup.
> > First bind is not "standard" in this kind of situation and makes things
> > overly complicated. I would recommend dnsmasq instead. It is much more
> > staight forward for a NAT box to setup. It will also provide you with a
> > dhcp server.
> > And in your situation you also want to disable/avoid the NetworkManager. 
> I told before that wiced can't deal with two wired interfaces.

That is not true, but lets ignore this for now.

> > It is quite easy because evry device you list in /e/n/i 
> i don't know ( with my poor English :-)) what is /e/n/i

Again your English is fine it's me being lazy.
/e/n/i is short for /etc/network/interfaces
This is the "old" way to configure your network interfaces.
 
> > will be
> > automaticaaly ignored by the NetworkManager.
> > And clearly because you have difficulties in setting this up doesn't make
> > all of this a bug.
> I don't find it normal to try to use interfaces before they are up! It's 
> obvously not a bug, but it's just  telling  users they shouldn't  try to 
> understand. When I fist tried Debian in april 2016, with Jessie, I read in 
> the bind9 doc something like "there are some issues about changing bind9 
> configuration, as future upgrade will loose your changes". without any more 
> details. 

Again, everything is behaving as expected. It is how you do things. And to
repeat myself, bind is not best in this situation. But if you insist in
using bind make sure it listens on your inside network interface, which
should be up without delay. You do not want ( and most likely neither does
your ISP) a full recursive resolver on your public interface.

You insisting to stick to this setup because you already invested too much
time in it is kind of stubborn (and I thought that was a German trait). You
either have to invest a lot more time to understand this or you could
switch to something more suited like dnsmasq. 

> > Also I want to mention to setup a router with Red Hat or with debian is
> > possible but there a distributions which are much more suited for this 
> > purpose. 
> I switched to Debian not to find it easier (Redhat wasn't) but because of 
> safety and coherence.
> But NetworkManager, which was on Fedora long before that on Debian, did not 
> the stupid things it does with resolv.conf and interfaces.

You most likely have resolvconf installed which updates /etc/resolv.conf.
Anything you change in there will be overwritten whenever something happens
on any network device.

> > I personally like pfsense and opnsense. Both are based on BSD but
> > they are excellent for SOHO routing. 
> Thanks to Wikipedia, I understood SOHO :-Da

And have you looked up OPNSense or pfsense?


-H



-- 
Henning Follmann   | hfollm...@itcfollmann.com

failed to set console font and keymap

[Anil Duggirala]

All I did was change "us" for "gb" in my /etc/default/keyboard file. I
am now getting a "failed to set console font and keymap" message at
bootup. The default keymap appears to have been changed, and everything
works well otherwise.
please help.

Re: wiki

[Richard Owlett]

On 02/16/2018 06:08 AM, Rodary Jacques wrote:

Le vendredi 16 février 2018, 06:42:52 CET rhkra...@gmail.com a écrit :

On Thursday, February 15, 2018 08:42:14 PM Rodary Jacques wrote:

Why can't I access wikis from a Debian box:
Forbidden
You are not allowed to access this!
is the message I get.


I think we need more information--which wiki are you having trouble with?
(What is its URL?)

I first had this message on  https://wiki.debian.org, then on various problems.

Maybe you have to register and then login on that wiki.

and I was never asked to register before you mention it.



I checked, https://wiki.debian.org is up and it is not a site requiring 
a login to view.


The next set of questions:
  1. What browser are you using?
   Do have any extensions/add-ons/etc enabled?
   Does your browser have a "safe" mode that disables them?
  2. Do other sites work?
(e.g. can you access your preferred search engine?)
  3. Are there other sites with problems? Which?
HTH

Using MATE's workspaces effectively

[Richard Owlett]

I have no problem with different applications being open in each workspace.

What I would like would be to be able to do is have differing sets of 
applications available in each workspace.


Currently all workspaces have icons to access _identical sets_ of 
applications.


For example one might have one workspace having a set of tools for 
writing/debugging software, another with a set of tools for researching 
Mesopotamian Architecture, and one focused on creating a weekly blog 
discussing advances in fly fishing.


I chose disparate sets too convey an idea I couldn't describe well.
Is there a more appropriate tool that maintains the "look and feel" of 
the MATE desktop? Comments?

TIA

Re: squid ssl bump

[Roberto C . Sánchez]

On Fri, Feb 16, 2018 at 08:16:28AM +0300, Gokan Atmaca wrote:
> Hello
> 
> I am installing as follows. But "ssl_crtd" is not found ...
> 
> installation steps ?
> 
> apt-get build-dep squid3
> apt-get install build-essential sharutils ccze libzip-dev libssl-dev
> apt-get install devscripts build-essential fakeroot
> apt-get install libssl-dev libcrypto++-dev  libssl1.0-dev
> apt source squid3
> 
> cd squid3-3.5.23
> vim debian/rules
>  –enable-ssl (add)
> ./configure
> make all
> make install
> 
> 
> what can be the problem ? what do you recommend ?
> 
You are editing the options in debian/rules and then not calling.  You
call ./configure directly.  After editing debian/rules, build with
'fakeroot debian/rules binary' or 'fakeroot dpkg-buildpackage'.  The
binary packages will be placed in the parent directory and you can see
them with 'cd .. ; ls *.deb'.  You can then install whichever of the
packages you need with 'dpkg -i .deb .deb ...'.

Additional information is available here:

https://wiki.debian.org/BuildingTutorial

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: wiki

[Rodary Jacques]

Le vendredi 16 février 2018, 06:42:52 CET rhkra...@gmail.com a écrit :
> On Thursday, February 15, 2018 08:42:14 PM Rodary Jacques wrote:
> > Why can't I access wikis from a Debian box:
> > Forbidden
> > You are not allowed to access this!
> > is the message I get.
> 
> I think we need more information--which wiki are you having trouble with?  
> (What is its URL?)
I first had this message on  https://wiki.debian.org, then on various problems.
> Maybe you have to register and then login on that wiki.
and I was never asked to register before you mention it. 
Jacques 

Re: BIND and iptables config

[rhkramer]

On Thursday, February 15, 2018 10:26:14 PM Rodary Jacques wrote:
> Le jeudi 15 février 2018, 11:44:36 CET Henning Follmann a écrit :
> > On Thu, Feb 15, 2018 at 05:01:52PM +0100, Rodary Jacques wrote:
> > > With NetworkManager, /etc/network/interfaces has only the loopbak
> > > interface, and I can't use wicd which can't deal with two wired
> > > interfaces. And, Henning Follmann, my English is too poor to explain
> > > clearly my setup which is the standard one when your ISP gives you one
> > > routable address and you want your home LAN to have access to
> > > internet.

I don't understand--what are the two wired interfaces that you have connected 
to your computer?

> > Hello,
> > no your english was good enough to describe your setup. And I would say
> > that 90% of "us" have a form of "dialup" with on routable ip address and
> > a NAT setup.
> > First bind is not "standard" in this kind of situation and makes things
> > overly complicated. I would recommend dnsmasq instead. It is much more
> > staight forward for a NAT box to setup. It will also provide you with a
> > dhcp server.
> > And in your situation you also want to disable/avoid the NetworkManager.
> 
> I told before that wiced can't deal with two wired interfaces.
> 
> > It is quite easy because evry device you list in /e/n/i

Based on context, I would say that is a difficult to understand attempt at 
abbreviating /etc/network/interfaces, especially to offer for someone with 
limited English skills.

I hope you are not giving up (I got the idea you might based on your previous 
post)--I'm not sure I can help you, but I think someone will be able to.

Re: wiki

[rhkramer]

On Thursday, February 15, 2018 08:42:14 PM Rodary Jacques wrote:
> Why can't I access wikis from a Debian box:
> Forbidden
> You are not allowed to access this!
> is the message I get.

I think we need more information--which wiki are you having trouble with?  
(What is its URL?)

Maybe you have to register and then login on that wiki.

Re: USB key and lost space

[Thomas Schmitt]

Hi,

Rodary Jacques wrote:
> I did subscribe  in april 2016,

The mail header X-Spam-Status in your mail to the list does not contain
the test "LDOSUBSCRIBER". So currently your address roda...@free.fr is
not subscribed.

Consider to subscribe again and also to Cc: the debian-user list with
your replies.


> Where am I supposed to find firmware.tar.gz. It may be a very stupid
> question, I was used with .iso  image disks only.

Other people on debian-user probably have more experience with that.
I have to google.
For the current Debian release 9 "stretch" it is probably on
  
https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/stretch/current/


I wrote:
> > So use /sbin/fdisk to create partition 3.

> I used fdisk, cfdisk and partitionprobe and it seems my Key is  quite
> useless now

Which ISO image did you put onto the USB stick ?

Let's give current netinst a try:

  $ dd if=debian-9.3.0-amd64-netinst.iso of=/dev/sdc bs=1M
  ...
  $ /sbin/fdisk /dev/sdc
  ...
  Command (m for help): p
  ...
  Device Boot StartEnd Sectors  Size Id Type
  /dev/sdc1  *0 593919  593920  290M  0 Empty
  /dev/sdc23760   4591 832  416K ef EFI (FAT-12/16/32)

  Command (m for help): n
  Partition type
 p   primary (2 primary, 0 extended, 2 free)
 e   extended (container for logical partitions)
  Select (default p): p
  Partition number (3,4, default 3): 3
  First sector (593920-7864318, default 593920): 
  Last sector, +sectors or +size{K,M,G,T,P} (593920-7864318, default 7864318): 

  Created a new partition 3 of type 'Linux' and of size 3.5 GiB.

  Command (m for help): p
  Disk /dev/sdc: 3.8 GiB, 4026531328 bytes, 7864319 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x0347fd41

  Device Boot  Start End Sectors  Size Id Type
  /dev/sdc1  * 0  593919  593920  290M  0 Empty
  /dev/sdc2 37604591 832  416K ef EFI (FAT-12/16/32)
  /dev/sdc3   593920 7864318 7270399  3.5G 83 Linux


  Command (m for help): w
  The partition table has been altered.
  Calling ioctl() to re-read partition table.
  Re-reading the partition table failed.: Permission denied

The final error message comes because i did this as normal user, just
having rw-permission to /dev/sdc.
I unplug and replug the USB stick to let the kernel assess the new
partitioning:

  $ ls /dev/sdc*
  /dev/sdc  /dev/sdc1  /dev/sdc2  /dev/sdc3


> I will try dd, very carefully. to erase this new partition I finally
> created, and perhaps come back to you afterwards.

I would just copy the ISO again onto the USB stick base device 
and then run fdisk.


Have a nice day :)

Thomas

Re: how to config usb wireless card?

[Long Wind]

Thank Deloptes!
i've tried "rfkill list", it says no to both hard and soft blocked 
my energy  is limited and i'll try other methods later on.
 

On Friday, February 16, 2018 3:21 PM, deloptes  wrote:
 

 Long Wind wrote:

> Thank bw!i've installed wicd-gtkit shows only wired interface, no wireless
> interface. i've not explored other methodsthey're likely more hard

Try
        rfkill list

and see if something is blocked. Use rfkill to unblock it

Try
        iwconfig

to see if interface is available and use iwconfig to power up.

regards



   

serpent cipher kernel module broken in sid

[Tiarnán Ó Corráin]

Hi--

the serpent cipher is unusable at the moment in sid.

Linux pharoah 4.14.0-3-amd64 #1 SMP Debian 4.14.13-1 (2018-01-14) x86_64
GNU/Linux

# modprobe serpent
modprobe: ERROR: could not insert 'serpent_sse2_x86_64': Unknown symbol in
module, or unknown parameter (see dmesg)
modprobe: ERROR: could not insert 'serpent_avx_x86_64': Unknown symbol in
module, or unknown parameter (see dmesg)
modprobe: ERROR: could not insert 'serpent_avx2': Unknown symbol in module,
or unknown parameter (see dmesg)

syslog has:

Feb 16 10:18:44 pharoah kernel: [16131.500226] ablk_helper: Unknown symbol
__x86_indirect_thunk_rax (err 0)
Feb 16 10:18:44 pharoah kernel: [16131.520670] ablk_helper: Unknown symbol
__x86_indirect_thunk_rax (err 0)
Feb 16 10:18:44 pharoah kernel: [16131.548529] ablk_helper: Unknown symbol
__x86_indirect_thunk_rax (err 0)

regards

Tiarnan

-- 
Imaginary evil is romantic and varied; real evil is gloomy, monotonous,
barren, boring.  Imaginary good is boring; real good is always new,
marvelous, intoxicating. - Simone Weil