from:"Stephen"

I have a need to pad a binary file with some character
(probably a null character) so that its total length
is a multiple of some number.  For example, I have a file
called kernel.debian, whose size is 6319616 bytes.  I need
to pad it with nulls until its length is a multiple of 80.
The next higher multiple of 80 is 6319680, which can be
obtained by padding the file with 64 null characters.
In CMS, the FBLOCK CMS Pipelines stage will do the trick.
For example,

   PIPE < KERNEL DEBIAN A1 | FBLOCK 80 00 | > KERNEL1 DEBIAN A1 F

This will create an output file with fixed-length 80-byte
records, padded as necessary at the end with null characters,
so that all records are exactly 80 bytes long.

I am looking for a way to do this padding in Linux.
A search of the internet using the keywords "pad file Linux"
did not seem to produce any useful results.  Does anyone know
how to accomplish this? 

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


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/173555076.1944854.1372523652842.javamail.r...@md01.wow.synacor.com

Re: How do I pad files in Linux? (SOLVED)

On Sat, 29 Jun 2013 13:19:22 -0400 (EDT), Tixy wrote:
> 
> On Sat, 2013-06-29 at 12:34 -0400, Stephen Powell wrote:
>> 
>> I have a need to pad a binary file with some character
>> (probably a null character) so that its total length
>> is a multiple of some number.  For example, I have a file
>> called kernel.debian, whose size is 6319616 bytes.  I need
>> to pad it with nulls until its length is a multiple of 80.
>> The next higher multiple of 80 is 6319680, which can be
>> obtained by padding the file with 64 null characters.
>> In CMS, the FBLOCK CMS Pipelines stage will do the trick.
>> For example,
>> 
>>PIPE < KERNEL DEBIAN A1 | FBLOCK 80 00 | > KERNEL1 DEBIAN A1 F
>> 
>> This will create an output file with fixed-length 80-byte
>> records, padded as necessary at the end with null characters,
>> so that all records are exactly 80 bytes long.
>> 
>> I am looking for a way to do this padding in Linux.
>> A search of the internet using the keywords "pad file Linux"
>> did not seem to produce any useful results.  Does anyone know
>> how to accomplish this? 
> 
> truncate -s %80 FILENAME
> 
> Will pad with zero's to round size up to a multiple of 80.

Thank you, Tixy, that's exactly what I wanted to know!
I knew that there must be a way to do this, but I couldn't
figure out how.  By the way, I also tried the command

   apropos pad

But it didn't yield any useful results either.

   truncate

Who would have thought?  That would appear to be the opposite
of what I want to do.  I want to pad, not truncate.  But
truncate can also pad.  How about that!  Thanks again!

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


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1952171005.1945999.1372529697239.javamail.r...@md01.wow.synacor.com

Re: How do I pad files in Linux?

On Sat, 29 Jun 2013 14:23:51 -0400 (EDT), Stan Hoeppner wrote:
> On 6/29/2013 12:19 PM, Tixy wrote:
>> 
>> truncate -s %80 FILENAME
>> 
>> Will pad with zero's to round size up to a multiple of 80.
> 
> That'll teach me to read all posts before replying.  Question:
> 
> Does this append ASCII zeros to the end of the file, or nulls?  Stephen
> asked for nulls, and you state "zero's" above.

It appends hex zeros (0x00), or nulls.  Also known as ^@ characters.
The ASCII zero is 0x30.

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


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/75239159.1946418.1372533440767.javamail.r...@md01.wow.synacor.com

"Operation not permitted" error when using su

I have discovered a problem recently when using su to switch to a user
other than root on a Gnome Terminal session.  Let's say I login to the
graphical desktop using a userid of "fred".  When I launch a Gnome
Terminal session, I'm automatically logged in as "fred".  Now, let's
suppose I switch to user "barney" by using

   su barney

After entering the password for user "barney", my userid changes to
"barney" in that session.  (whoami reports "barney".)  I then change
to barney's home directory with "cd", issued with no operands.  Now,
certain commands will cause error messages to the terminal.  For example,
if I issue

   vi stuff

Then exit vi with :q, I am back to another shell prompt, but there is an
error message on the screen which looks like this:

   Error: messages not turned on: /dev/pts/0: Operation not permitted

(vi is actually nvi on my system.)
This problem does not occur in a virtual terminal (vt1-vt6).  It also
does not occur if I switch to root, instead of a non-root user.

A search of the internet seemed to suggest that the problem was the
presence of "biff y" in a bash profile.  However, I have looked, and
I cannot find "biff y" specified in any bash-related file.  (I am running
jessie.)  In fact, the biff package is not even installed.  Ideas anyone?

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


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/402356644.1946777.1372536041381.javamail.r...@md01.wow.synacor.com

Re: "Operation not permitted" error when using su

On Sat, 29 Jun 2013 16:07:54 -0400 (EDT), David Guntner wrote:
> 
> Stephen Powell grabbed a keyboard and wrote:
>> 
>>Error: messages not turned on: /dev/pts/0: Operation not permitted
>> 
>> (vi is actually nvi on my system.)
>> This problem does not occur in a virtual terminal (vt1-vt6).  It also
>> does not occur if I switch to root, instead of a non-root user.
>> 
>> A search of the internet seemed to suggest that the problem was the
>> presence of "biff y" in a bash profile.  However, I have looked, and
>> I cannot find "biff y" specified in any bash-related file.  (I am running
>> jessie.)  In fact, the biff package is not even installed.  Ideas anyone?
> 
> Since it's complaining about messages not being turned on, try "mesg y"
> and see if that helps.

I just tried that.  "mesg y" produced no output and no error messages, but
a subsequent execution of vi produced the same error on exit as before.

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


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/644172295.1946934.1372537018465.javamail.r...@md01.wow.synacor.com

Re: "Operation not permitted" error when using su

On Sat, 29 Jun 2013 16:26:56 -0400 (EDT), David Guntner wrote:
> 
> No, it won't output a message when you set it y or n.  Not sure I
> understand why vi is doing something that needs a messages channel
> turned on.  And it's kind of hard to guess without seeing actual output. :-)
> 
> You said you had done some su commands before invoking vi, if I recall
> correctly.  Did you try doing the "mesg y" command at the initial login
> point, before su'ing to the user where you're trying to run vi?

Yes, I tried that too.  No difference.

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


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/7449658.1947240.1372538833179.javamail.r...@md01.wow.synacor.com

Re: the continuing disappointment of Debian 7

On Sat, 29 Jun 2013 18:07:14 -0400 (EDT), Jeff Shearer wrote:
> 
> Iceweasel crashes all the time and cannot play flash

I'm sorry things aren't working well for you, but that has not
been my experience.  I'm running jessie now, but I was running
wheezy for a long time, and your experience does not match my
experience.  For me, iceweasel never crashed (except for a
power failure, which is hardly Debian's fault), and flash
played just fine.  (Of course, I was using flash-plugin-nonfree,
not the default free player.)

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

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1918330956.1947914.1372544285762.javamail.r...@md01.wow.synacor.com

Re: "Operation not permitted" error when using su

On Sat, 29 Jun 2013 18:39:32 -0400 (EDT), Chris Bannister wrote:
> 
> Is there a difference if you " su - barney" ?

No, there is no difference.  I still get the same error.

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


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1462006945.1948292.1372547161473.javamail.r...@md01.wow.synacor.com

Re: Gnome3 HS after update

2013-07-02 Thread Stephen Allen

On Sun, Jun 30, 2013 at 12:59:51PM +0200, Jean-Marc wrote:
> Hi everybody,
> 
> I updated my jessie and Gnome3 does not start anymore.
> Actually, it starts but I never got any menu.
> 
> Do other people got the same ?
> 
> -- 
> Jean-Marc 


---end quoted text---

Yup same here, installed Cinnamon until things are sorted. Actually
enjoying the improvements to Cinnamon since last used.

-- 
Cheers,
Stephen, Toronto
My Google+ Profile | http://goo.gl/JbQsq


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130702115501.ga8...@thunkpad.gateway.2wire.net

Re: [SOLVED] Gnome3 HS after update

2013-07-02 Thread Stephen Allen

On Tue, Jul 02, 2013 at 01:15:48PM +0800, Stephane Duchesne wrote:
> Noticed the same Gnome3 behaviour in Jessie.  Gnome started but without 
> statusbar and
> without window decorations.
> Gnome Classic works fine.
> 
> "Expect Jessie to be a bumpy ride," #gnome-next on oftc suggests. 
> Especially if you are running Gnome, and at least until all 3.8.x components 
> have percolated into Jessie, I reckon.  
> 
> Gnome-shell in Sid is now 3.4.2-10 and working absolutely fine, indeed.  I 
> might
> stick with Sid for a while.  
> 
> There's still quite a few crucial components to go: 
> http://www.0d.be/debian/debian-gnome-3.8-status.html
> 
> Seems it is all coming together nicely, though.  

---end quoted text---

Thanks for the update -- Using Cinnamon until 3.8 percolates to Jessie.

-- 
Cheers,
Stephen, Toronto
My Google+ Profile | http://goo.gl/JbQsq


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130702115707.gb8...@thunkpad.gateway.2wire.net

Re: Help - Gnome Died After Update/Upgrade

2013-07-03 Thread Stephen Allen

On Tue, Jul 02, 2013 at 05:10:33PM +0200, Steven Post wrote:
> On Tue, 2013-07-02 at 07:59 -0700, Mark Phillips wrote:
> > I have been running Debian testing on my laptop for several years. I
> > performed a "routine" update/upgrade on Sunday, and I seem to have
> > lost gnome. At first, I could not log in, but I got that fixed.
> > However, when I log in, all I get is my wallpaper. No favorites on the
> > left, no window docks (not sure of the terminology here) on the right,
> > no taskbar at the top, etc. Just a wall paper. I also get an error
> > message "No system tray detected, unable to start". However, I traced
> > that back to an hp printer service, so I don't think it is relevant.
> > 
> > I have tried uninstalling/installing gnome, but no change. I tried
> > creating an new user and logging in with that user, and I get the same
> > situation - but the default wall paper and not my personal one. I have
> > run several update/upgrade and update/dist-upgrades since Sunday, and
> > no change. I have looked through the 'net to find solutions, and I am
> > not getting anywhere.
> > 
> [...]
> 
> Multiple people seem to have this issue, including me. The problem is
> solved in gnome-shell from unstable, you can either wait until it
> migrates to testing (in 1 or 2 days I guess, judging from the QA page
> [1]) or you can install from unstable with "aptitude install -t unstable
> gnome-shell" (no quotes). Make sure you have unstable in your
> sources.list file. Just be careful not to upgrade your whole system to
> unstable, but only that package.
> 
> Regards,
> Steven


---end quoted text---

FYI

Updated my Testing/Jessie laptop this morning. It appears Gnome-Shell is
now launching correctly with menus etc.



-- 
Cheers,
Stephen, Toronto
My Google+ Profile | http://goo.gl/JbQsq


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130703234936.ga12...@thunkpad.gateway.2wire.net

Re: "Operation not permitted" error when using su

2013-07-04 Thread Stephen Powell

Sun, 30 Jun 2013 02:09:35 -0400 (EDT), Bob Proulx wrote:
> 
> Stephen Powell wrote:
>> ...logged in as root...
>>su barney
>>vi stuff
>>Error: messages not turned on: /dev/pts/0: Operation not permitted
> 
> The above is basically a normal result of the current environment.  At
> another level it is a bug in nvi.  I suggest that you understand it
> and then ignore it.  Or jump into the nvi code and fix it.
> 
> There are two issues.  First is that root needs to protect itself
> against attacks against its smart terminal.  Therefore "messages"?
> will be off by default for root.  What does that mean?  It means the
> ability of processes to send text to the terminal.  Processes may be a
> "biff" mail notification program saying "you have mail".  Or it may be
> a user trying to "write(1)" (old Unix IM program) to your terminal.
> Or it may be a local user (think student on a multiuser university
> system) trying to crack into your terminal by sending smart terminal
> escape sequences.  (Most terminals have those disabled these days for
> security surrounding this issue too.  Because even for non-root smart
> terminal attacks is still an issue.)
> 
> Non-Root User:
>   $ ls -l /dev/pts/23
>   crw--w 1 rwp tty 136, 23 Jun 29 19:02 /dev/pts/23
> 
> Root User:
>   $ ls -l /dev/pts/11
>   crw--- 1 root tty 136, 0 Jun 29 19:00 /dev/pts/11
> 
> Or in the old days on other systems I recall it being world writable
> by other too.  But that may be an incorrect memory.
> 
> For root the standard is that no one else can write(1) to the
> terminal.  (And probably "talk" and others too.)  See the man page for
> mesg(1) for a small amount of additional information.  It was common
> in the old days to see "mesg n" in root's dot profile file.
> 
>   man mesg
> 
> So back to your problem...  You are starting from a /dev/pts/X that is
> owned by root and is not otherwise writable.  That is good.  Safe from
> various attacks.  That is what you want.
> 
> But then the second issue comes into play.  You are using su to switch
> user to a non-root user.  After you have switched to that user the pty
> hasn't changed.  That is intentional due to the security risk nature
> of root.  But it means that the non-root user processes can't make
> changes to the tty device.
> 
> Now is where the nvi bug/misfeature comes into play.  There really
> isn't any reason for nvi to need to touch the pty.  In my opinion it
> should do nothing to it by default.  Emacs doesn't touch the pty.  If
> you try your test case with emacs there will be no error printed.  Nor
> with vim.  This is only a problem in the nvi program.  Why?  Because
> it is trying to do too much.
> 
> What the nvi program is trying to do is to turn off messages to the
> terminal while it is running.  It is trying to prevent other local
> users from using write(1) to you while you are editing.
> 
>   man nvi
> 
>mesg [on]
>   Permit messages from other users.
> 
> In order to prevent messages from other users it tries to run chmod on
> your pty device.  This can be seen with strace.
> 
>   $ strace -v -e chmod -o /tmp/nvi.strace.out nvi .bashrc
>   $ cat /tmp/nvi.strace.out
>   chmod("/dev/pts/0", 020620) = -1 EPERM (Operation not permitted)
>   chmod("/var/tmp/vi.recover/vi.ryTzPt", 0700) = 0
>   chmod("/dev/pts/0", 020600) = -1 EPERM (Operation not% 
> permitted)
> 
> And those chmod's are the source of the messages that you are seeing.
> The only way to fix this is to patch the nvi source code to avoid the
> chmod calls.
> 
> Basically I ignore the errors.  The file is edited successfully
> anyway.  It is just noise.  Annoying.  But since I know what is
> happening and I only do that a very few times I just ignore it.
> 
> This would be a reasonable issue to submit as a bug against nvi.
> However there are worse problems with nvi.  See Bug#497342 which has
> been around for years which is much more annoying.  Filing bugs is
> easy but if no one is around to fix them then it doesn't do much
> good.  But this is a valid bug in my opinion.  Though much less of a
> problem than Bug#497342 which is very annoying.  Especially since the
> previous version 1.79 of nvi didn't have it.  But that is a different
> story.
> 
> Hope this explanation helps!
> Bob

Thank you, Bob, for that detailed explanation.  I'm not starting out
as root though.  I'm starting out as "fred" (Applications -> Utilities ->
Terminal, in the latest version of Gnome under Jessie, while logged
in to the

Re: How do I pad files in Linux?

2013-07-04 Thread Stephen Powell

On Mon, 01 Jul 2013 02:59:40 -0400 (EDT), Urs Thuermann wrote:
> 
> dd if=/dev/zero bs=1 count=64 >> file

Thanks, Urs.  I haven't tried this, but it looks like this should work too.

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


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/548375498.2015945.1372936609846.javamail.r...@md01.wow.synacor.com

Re: Starting Google Chrome - resend

2013-07-06 Thread Stephen Allen

On Sat, Jul 06, 2013 at 07:53:15AM +0100, Lisi Reisz wrote:
> On Saturday 06 July 2013 01:23:54 green wrote:
> > chromium does not include flash, which is non-free and available via
> > the flashplugin-nonfree package.
> 
> Yes, but I couldn't get it to work with Chromium.
> 
> Lisi
> 
---end quoted text---

What do you mean exactly? It just does, if you have it installed. You
must go to Adobe's website and install it first of course.

I have it working here fine on Debian's Chromium.

-- 
Cheers,
Stephen, Toronto
My Google+ Profile | http://goo.gl/JbQsq


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130706212434.ga4...@thunkpad.gateway.2wire.net

Re: Starting Google Chrome - resend

2013-07-06 Thread Stephen Allen

On Sat, Jul 06, 2013 at 10:36:59PM +0100, Lisi Reisz wrote:
> On Saturday 06 July 2013 22:24:34 Stephen Allen wrote:
> > I have it working here fine on Debian's Chromium.
> 
> Does it matter?
> 
> Lisi
> 
---end quoted text---

Well, apparently it does, you posted asking.

-- 
Cheers,
Stephen, Toronto
My Google+ Profile | http://goo.gl/JbQsq


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130706235915.ga4...@thunkpad.gateway.2wire.net

Re: Starting Google Chrome - resend

2013-07-07 Thread Stephen Allen

On Sun, Jul 07, 2013 at 01:13:07AM +0100, Lisi Reisz wrote:
> On Sunday 07 July 2013 00:31:41 Charlie wrote:
> >  On Sat, 6 Jul 2013 22:36:59 +0100 "Lisi Reisz lisi.re...@gmail.com"
> >  sent this:
> >
> >     >On Saturday 06 July 2013 22:24:34 Stephen Allen wrote:
> > >> I have it working here fine on Debian's Chromium.
> > >
> > >Does it matter?
> > >
> > >Lisi
> >
> > I think it must Lisi, because someone posted about a problem with Chrome
> > and the discussion was taken from that to Chromium not being "nearly"
> > the same and then about things not working in Chromium or Chrome and so
> > it continued.
> >
> > So I imagine it does matter.
> 
> Yes, Charlie.  I agree.  I had been involved in the discussion and agree that 
> that discussion matters.  And most people were saying that they found 
> flash-plugin-nonfree adequate, with which I did not disagree.  It was not 
> adequate for me, it was for them.  Worth establishing.  And it may well have 
> been my fault that I did not find it satisfactory.
> 
> 
> What do you mean exactly? It just does, if you have it installed. You
> must go to Adobe's website and install it first of course.
> 
> I have it working here fine on Debian's Chromium.
> 
> 
> But Stephen appeared to me to want confrontation for confrontation's sake, 
> and 
> it was that with which I was disagreeing.  Of course I know about having to 
> get it and install it before it would work!  It appeared to me as if he was 
> being deliberately insulting.  So I repeat:  Does it matter that Stephen, 
> clever Stephen, has it working to his satisfaction, so assumes that I am too 
> thick to know that something is not going to work unless I first download and 
> install it?  I still say not!
> 
> Lisi
> 
---end quoted text---

Sorry, no confrontation and wasn't trolling. Flash is on it's last legs,
and I'm just left wondering what you expect.  No worries.

-- 
Cheers,
Stephen, Toronto
My Google+ Profile | http://goo.gl/JbQsq


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130707112722.ga5...@thunkpad.gateway.2wire.net

What's with the blue overlining in text consoles?

2013-07-13 Thread Stephen Powell

Something strange has started happening recently. For a long time I have
used ISO-8859-1 as my character mapping in text consoles.

dpkg-reconfigure console-setup

and I have had no difficulty, except when using the ssh client to connect
to a remote system which uses UTF-8. The box-drawing characters sent by
the remote system did not look right under these conditions. To solve this
problem, I switched my local system to use UTF-8. Now the box-drawing
characters sent by the remote system look right when displayed by my
local ssh client. However, I recently began noticing that all blue fields
are now overlined. For example, the lynx web browser, when used in a
text console (vt1-vt6), displays emphasized fields (the ... html
tag) as blue overlined, when it used to display them simply as blue.

I can live with that, I suppose. But what really bothers me is when I
use the c3270 text-mode 3270 terminal emulator to logon to a mainframe.
All blue fields are now overlined! This is driving me batty! I tried
searching the world wide web using search words of

blue overlining "UTF-8"

but did not obtain any useful results. Does anyone know the cause of this?
Does anyone know the cure? Is this a bug? If so, in what package is the
bug? The problem does not seem to occur in a Gnome Terminal window, only
on a text console. My system locale is en_US.UTF-8. I am running an
up-to-date Jessie system on i386 architecture.

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

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/1182082504.2151649.1373745348517.javamail.r...@md01.wow.synacor.com

What's with the blue overlining in text consoles? [SOLVED]

2013-07-15 Thread Stephen Powell

On Sun, 14 Jul 2013 11:10:18 -0400 (EDT), commandl...@telenet.be wrote:
> 
> On 13/07/13 21:55, Stephen Powell wrote:
>> 
>> Something strange has started happening recently.  For a long time I have
>> used ISO-8859-1 as my character mapping in text consoles.
>>
>> dpkg-reconfigure console-setup
>>
>> and I have had no difficulty, except when using the ssh client to connect
>> to a remote system which uses UTF-8.  The box-drawing characters sent by
>> the remote system did not look right under these conditions.  To solve this
>> problem, I switched my local system to use UTF-8.  Now the box-drawing
>> characters sent by the remote system look right when displayed by my
>> local ssh client.  However, I recently began noticing that all blue fields
>> are now overlined.  For example, the lynx web browser, when used in a
>> text console (vt1-vt6), displays emphasized fields (the ... html
>> tag) as blue overlined, when it used to display them simply as blue.
>>
>> I can live with that, I suppose.  But what really bothers me is when I
>> use the c3270 text-mode 3270 terminal emulator to logon to a mainframe.
>> All blue fields are now overlined!  This is driving me batty!  I tried
>> searching the world wide web using search words of
>>
>> blue overlining "UTF-8"
>>
>> but did not obtain any useful results.  Does anyone know the cause of this?
>> Does anyone know the cure?  Is this a bug?  If so, in what package is the
>> bug?  The problem does not seem to occur in a Gnome Terminal window, only
>> on a text console.  My system locale is en_US.UTF-8.  I am running an
>> up-to-date Jessie system on i386 architecture.
> 
> Never heard of something similar to start with.  Few guesses.
> 
> * Terminal Emulation?
>   Check what happens if you switch from say xterm to linux to vt100 to ...
> 
> * Character map error?
>   Might be for some reason the charmap is damaged?  Did you edit them at 
> one point?  Of would someone else have access to them?
> 
> I'd suggest you make a backup of the current files, then proceed with 
> tests.  If it still fails proceed to reinstall the packages. Then check 
> again...
> 
> Do you mix the repo with Wheezy or unstable?  This might at times cause 
> quite unique weirdness.

Thank you for your reply, but please don't top post.  I took the liberty of
reformatting this post in the bottom posting / interleaving style.

Well, after a lot of trial-and-error experimentation, I have found the culprit.
It's the video BIOS.  This video BIOS supports eleven hardware text modes,
as documented below:

hex mode id screen size   character cell
(vga=ask)   (text columns x   size (horiz pixels
text rows)x vert pixels)

F00 80x25 9x16
F01 80x50 9x8
F02 80x43 8x8
F03 80x28 9x14
F05 80x30 9x16
F06 80x34 9x14
F07 80x60 9x8
121 100x259x16
122 100x309x16
123 132x258x16
133 132x448x8

Of these eleven hardware text video modes, ten of them work fine.  That is, blue
fields appear without overlining.  One of them is defective.  Mode id 0x122,
for 100 text columns by 30 text rows, displays blue fields with overlining.
And that's the one I was using.  Coincidentally, I switched from 80x34 to
100x30 shortly after I switched from ISO-8859-1 character mapping to UTF-8
character mapping.  The overlining of blue fields had nothing to do with the
switch to UTF-8.  It just appeared to be related because the video mode switch
occurred at about the same time.  The video BIOS apparently does not set up
the VGA registers correctly for video mode id 0x122.  But it does for all the
other text video modes.  The solution (actually a circumvention) is to choose
a different video mode.  Problem solved.  For those of you who are interested,
here is the information I have been able to obtain about my video chipset
and BIOS:

The video chipset is listed by "lspci -nn" as follows:

05:03.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Rage XL PCI [1002:4752] (rev 27)

The video chip is built-in to the motherboard; so it's video BIOS is built-in 
to the
motherboard too.

/var/log/Xorg.0.log shows the following information about the video BIOS:

MACH64(0): Primary V_BIOS segment is: 0xc000
...
MACH64(0): VESA BIOS detected
MACH64(0): VESA VBE Version 2.0
MACH64(0): VESA VBE Total Mem: 8128 kB
MACH64(0): VESA VBE OEM: ATI MACH64
MACH64(0): VESA VBE OEM Software Rev: 1.0
MACH64

Re: Deleting chromium DNS cache entry doesn't seem to help.

2013-07-19 Thread Stephen Allen

On Thu, Jul 18, 2013 at 04:43:07PM +, Hendrik Boom wrote:
> On Sun, 14 Jul 2013 14:57:14 +, Hendrik Boom wrote:
> 
> > On Sat, 13 Jul 2013 16:53:01 -0400, staticsafe wrote:
> > 
> >> On Sat, Jul 13, 2013 at 08:39:10PM +, Hendrik Boom wrote:
> >>> For some reason, chromium seems to have got it stuck in its head that
> >>> slashdot,org is at 69.165.131.134.  At least, when I try to browse to
> >>> slashdot.org using chromium, the displayed contents are identical to
> >>> the contents at 16.165.131.134, which contains my personal web site.
> >>> 
> >>> Firefox and chrome have no trouble reaching the real site.
> >>> 
> >>> And I can read slashdot just fine on chromium if I enter the IP number
> >>> 216.34.181.45 instead of the domain name.
> >>> 
> >>> So I'm guessing that chromium has got that IP number stuck in some
> >>> internal DNS cache.
> > 
> > It now looks as if chromium's DNS cache may not be the problem. 
> > Chromium must be getting slashdot's IP address from somewhere else --
> > somewhere that firefox and ping don't access.
> > 
> > 
> >>> How can I get it to forget it?
> >>> 
> >>> -- hendrik
> >> 
> >> Navigate to chrome://net-internals/#dns and press the "Clear host
> >> cache"
> >> button.
> > 
> > After navigating there from chromium and pressing the button,
> > slashdot.org doesn't appear in the listing of the cache entries on that
> > page.
> > 
> > But the misbehaviour still persists, even after a reboot.
> > 
> > And firefox and chrome and ping still reach the right site.
> > 
> > And when I go to chrome://net-internals/#dns on chrome itself, it tells
> > mem it *does* have slashdot.org in its cache, with the right IP number.
> > 
> > The cache chromium reveals with chrome://net-internals/#dns clearly has
> > different contents from the one that chrome reveals -- which confirms
> > that they have different caches.
> > 
> > And even after browsing to slashdot.org in chromium and getting to the
> > wrong place, going to chrome://net-internals/#dns with chromium still
> > indicates that slashdot.org is not in the cache.
> > 
> > So I'm suspecting that chrome://net-internals/#dns may not reeveal the
> > real cache in chromium.
> > 
> > So where *is* chromium getting this misinformation?
> > 
> > Just for reference, here's my /etc/resolv.conf file:
> > 
> > # Generated by NetworkManager domain topoi.pooq.com search
> > topoi.pooq.com nameserver 8.8.8.8 nameserver 8.8.4.4
> > 
> > 
> > -- hendrik
> > 
> > 
> >> Source -
> >> http://superuser.com/a/203702
> 
> It's been most of a week now, and the problem persists.
> Chromium still insists on going to the website normally known as 
> topoi.pooq.com when I request slashdot.org.
> 
> Neither iceweasel nor chrome do this; both find the proper slashdot.org.
> 
> Even ping finds the proper site.
> 
> The problem presumably started a week ago when there was a temporary 
> networking problem, but only chromium seems to have fixated on the wrong 
> IP address.
> 
> I have followed the procedure for clearing chromium's dns cache.  When I 
> look at the cache contents, slashdot isn't in it.  Does chromium have 
> another, secret cache?
> 
> And it appears that I do not have nscd running, or even installed.
>  
> I'm starting to think of shuttering chromium forever, assuming I can copy 
> its bookmarks elsewhere, say, to chrome.
> 
> 
---end quoted text---

Why would you need to copy your bookmarks? Presumably you used bookmark
sync with Chromium, thus they will be available to Google-Chrome when
you login into your Google account the 1st time in Chrome.

Have you tried using a different DNS server? Try the Google DNS servers,
Google will give you their address -- I don't have them handy at the
moment.

-- 
Cheers,
Stephen, Toronto
My Google+ Profile | http://goo.gl/JbQsq


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130719104526.ga4...@thunkpad.gateway.2wire.net

Re: root.root and netdev group for /dev/net/tun ?

2013-07-27 Thread Stephen Powell

On Sat, 27 Jul 2013 21:28:09 -0400 (EDT), Zenaan Harkness wrote:
> 
> Is there a reason why the default ownership of /dev/net/tun is root.root?
> I'm on sid. Don't know if it's anything I did, pretty sure not.
> 
> As in, is there a reason that /dev/net/tun is not owned root.netdev?

The attributes of /dev/net/tun are controlled by the file

   /lib/udev/rules.d/91-permissions.rules

which is part of the udev package.  Search for the character string "tun"
in this file.  You will find a line which looks like this:

   KERNEL=="tun",  MODE="0666",
OPTIONS+="static_node=net/tun"

If you want to change the group to netdev, change the above to

   KERNEL=="tun", GROUP="netdev"   MODE="0666",
OPTIONS+="static_node=net/tun"

You might also want to change the mode settings, so that only root and members
of the netdev group can access the /dev/net/tun device.  For example,

   KERNEL=="tun", GROUP="netdev"   MODE="0660",
OPTIONS+="static_node=net/tun"

As for why it is the way it is, you might want to ask the package maintainer for
the udev package that question.  Of course, if the udev package is ever 
serviced,
you may need to re-make your changes.  The change does not take effect until the
next reboot, of course.

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

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/548182802.2367641.1374977982693.javamail.r...@md01.wow.synacor.com

Re: root.root and netdev group for /dev/net/tun ?

2013-07-28 Thread Stephen Powell

On Sun, 28 Jul 2013 04:28:01 -0400 (EDT), Erwan David wrote:
> 
> I think that what is found in /etc/udev/rules predates /lib/udev/rules,
> thus just putting the modified line in a file in this directory should
> be sufficient and shoud survive an udev update.

I think you meant to say /etc/udev/rules.d and /lib/udev/rules.d,
respectively.  Yes, you can copy the file from /lib/udev/rules.d
to /etc/udev/rules.d and then modify the copy in /etc/udev/rules.d.
But if the file 91-permissions.rules changes in a subsequent update
of the udev package, chances are that there were changes made to
it that you *want* to take effect.  It is still necessary to coordinate
the changes made by package maintenance with the changes which you
yourself have made.

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

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/744543456.2369828.1375018300585.javamail.r...@md01.wow.synacor.com

Re: root.root and netdev group for /dev/net/tun ?

2013-07-28 Thread Stephen Powell

On Sun, 28 Jul 2013 07:42:29 -0400 (EDT), Brian  wrote:
> 
> On Sat 27 Jul 2013 at 22:19:42 -0400, Stephen Powell wrote:
>> 
>> ...
>> The change does not take effect until the next reboot, of course.
> 
> Wouldn't 'udevadm trigger' avoid a reboot?

If you wish to avoid a reboot, the simplest solution is to manually alter
(as root) the attributes of the /dev/net/tun pseudo-file.  For example,

# chgrp netdev /dev/net/tun
# chmod 0660 /dev/net/tun

But of course, the attributes will revert to what they were before upon
the next reboot unless changes have been made to the 91-permissions.rules
file.

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

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/384154941.2369874.1375018772241.javamail.r...@md01.wow.synacor.com

Re: root.root and netdev group for /dev/net/tun ?

2013-08-01 Thread Stephen Powell

On Sat, 27 Jul 2013 22:19:42 -0400 (EDT), Stephen Powell wrote:
> 
> The attributes of /dev/net/tun are controlled by the file
> 
>/lib/udev/rules.d/91-permissions.rules
> 
> which is part of the udev package.  Search for the character string "tun"
> in this file.  You will find a line which looks like this:
> 
>KERNEL=="tun",  MODE="0666",
> OPTIONS+="static_node=net/tun"
> 
> If you want to change the group to netdev, change the above to
> 
>KERNEL=="tun", GROUP="netdev"   MODE="0666",
> OPTIONS+="static_node=net/tun"
> 
> You might also want to change the mode settings, so that only root and members
> of the netdev group can access the /dev/net/tun device.  For example,
> 
>KERNEL=="tun", GROUP="netdev"   MODE="0660",
> OPTIONS+="static_node=net/tun"
> 

One other thing -- 91-permissions.rules is in the initial RAM file system;
so if you change 91-permissions.rules, you will need to rebuild the initial
RAM file system image file.

   update-initramfs -uk $(uname -r)

will rebuild the initial RAM file system image file for the running kernel.
If you have alternate kernels installed, you will need to rebuild the initial
RAM file system image files for the alternate kernels too.

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


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1625680288.2446703.1375410066034.javamail.r...@md01.wow.synacor.com

Re: Partitions

2013-08-11 Thread Stephen Powell

On Fri, 09 Aug 2013 09:58:19 -0400 (EDT), Klaus Jantzen wrote:
> 
> by "some magic" the partitions on a HDD receive a block-id
> or UUID (for fstab).
> 
> Does the ID of a partition change when the partition is moved
> or when a new partition is created in the unallocated space
> between two partitions?
> 
> Thanks for any info.

The UUID is assigned when the partition is formatted, not when
it is allocated.  Commands such as mke2fs or mkswap do the
formatting.  Moving or resizing a partition will not change its
UUID, nor will allocating or deallocating another partition
in any location.  However, reformatting the partition will
normally change its UUID unless the old UUID is explicitly
specified as an option during formatting.  For example, I've heard,
though I have not personally verified it, that the Ubuntu installer
has a habit of reformatting swap partitions during installation
that were originally created by the Debian installer, thus messing
up the Debian system's use of the swap partitions.

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

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1782814833.2585471.1376231789082.javamail.r...@md01.wow.synacor.com

Re: post-install questions

2013-08-11 Thread Stephen Powell

On Sun, 11 Aug 2013 12:49:36 -0400 (EDT), François Patte wrote:
> 
> I have just finished my debian installation and I have a few questions:
> 
> 1- For some reason the root account was not activated (I, maybe, missed
> some step); so I activated it following the docs, but there are two
> problems:
> a) root can login through lightdm and access a graphical session! How to
> disable this?

I don't use lightdm, so I don't know.  Someone else will have to answer
this question.

> 
> b) root umask is set to 077, which is problematic if you don't pay
> attention to this setting.

That's strange.  That is not the Debian default.  The Debian default
for umask is 022.  (See /etc/login.defs.)  Perhaps pam_umask is overriding
this?  FTP servers have their own method for specifying the umask value.
For example, vsftpd sets the local_umask value in /etc/vsftpd.conf for
ftp client sessions.

> 
> 2- Is there a gnome-network-manager like program under xfce?
> 
> I try to have an installation with a minimum number of gnome packages.
> I tried to install  gnome-network-manager, but I got a full installation
> of gnome desktop which made a "coup d'état" and took power over xfce.  I
> purged my system from gnome packages.

I don't use xfce, so I don't know.

> 3- Is it possible to install a package without its dependencies  with
> apt-get?  I wanted to install auctex but apt-get wants to install a lot
> of TeX packages which I don't want.
> 
> I know, auctex is made for TeX, but I install texlive directly from CTAN
> and don't want to have 2 TeX installations.

Maybe, but in general, you shouldn't.  There are three levels of "dependency".
A package can DEPEND on another package, RECOMMEND another package, or
SUGGEST another package.  By default, aptitude, and I think apt-get as well,
installs all packages that are dependencies or recommendations.  You can
suppress the installation of recommended packages with

   aptitude -R install 

or

   apt-get --no-install-recommends install 

This may help.  But if the extra packages are truly dependencies of the
package you want to install, it probably won't work without the dependent
packages, even if you can get it installed.
> 
> 4- I installed emacs24, and it returns a warning when it is launched
> from an xfce terminal:
> 
> Gtk-WARNING **: gtk window parse geometry() called on a window with no
> visible children; the window should be set up before gtk window parse
> geometry() is called.
> 
> What does this mean?

I don't use emacs and I know nothing about gtk.  I hope others can help
you with the questions I couldn't answer.

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

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1723425972.2588008.1376245293270.javamail.r...@md01.wow.synacor.com

Re: Building initrd for install Wheezy on pc without PAE

2013-08-26 Thread Stephen Powell

On Mon, 26 Aug 2013 05:32:36 -0400 (EDT), antispammbox-debian wrote:
> 
> Kernel 486 is very old 1999?,  for my laptop,  :-), I would like to install 
> a kernel 686, as with Squeeze.

Unfortunately, Debian does not offer a 686 non-PAE kernel in wheezy as
a stock kernel image package, as it did for squeeze.  If you want a kernel
which is optimized for your processor you will need to build a custom
kernel.  I just finished doing that yesterday, as a matter of fact, for
my laptop, which has a Pentium M processor.  It does not support PAE.
(I only have 1G of memory installed anyway, so PAE features would not
benefit me.)

   cat /proc/cpuinfo

will tell you all the details about your processor.  If you don't see
"pae" under "flags", then your processor does not support PAE.  Building
a custom kernel is not a trivial process.  But if you want to tackle this
task, I recommend

   http://users.wowway.com/~zlinuxman/Kernel.htm

as your guide.  Select your processor type during "make menuconfig".
Use a -486 kernel config file as your starting point for customization.
Good luck.

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

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/8377690.2832355.1377529627608.javamail.r...@md01.wow.synacor.com

Re: minicom and/or setserial

2013-08-31 Thread Stephen Powell

On Fri, 30 Aug 2013 10:08:36 -0400 (EDT), co...@esid.gecgr.co.cu wrote:
> 
> I have problem with my serial port
> 
> With dmseg | grep tty
> 
> [0.004000] console [tty0] enabled
> [1.769854] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> [1.770070] serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> [1.770721] 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> [1.771023] 00:0a: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> [1.772842] :02:02.0: ttyS2 at I/O 0x9400 (irq = 9) is a 16550A
> [1.773360] :02:02.1: ttyS3 at I/O 0x9800 (irq = 9) is a 16550A
> 
> How do change
> 
> [1.770721] 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> [1.771023] 00:0a: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> 
> to
> 
> [1.770721] 00:09: ttyS4 at I/O 0x3f8 (irq = 4) is a 16550A
> [1.771023] 00:0a: ttyS5 at I/O 0x2f8 (irq = 3) is a 16550A
> 
> It posible resolve with setserial or minicom ???
> 
> Sorry my english is not good

What's the problem?  This is the standard way for Linux to name serial
ports.  3F8 gets /dev/ttyS0 and 2F8 gets /dev/ttyS1.  That is working
as designed.  I would be more concerned about /dev/ttyS2 and /dev/ttyS3
sharing IRQ 9.  IRQ sharing usually doesn't work with serial ports.
Also, IRQ 9 is normally used by the ACPI controller.

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


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1175097672.2922167.1377952145307.javamail.r...@md01.wow.synacor.com

Re: strange bash behavior

2013-09-02 Thread Stephen Powell

On Mon, 02 Sep 2013 05:27:55 -0400 (EDT), Matej Kosik wrote:
> 
> This morning I have been puzzled by bash.
> After typing the following command:
> 
>   for i in `seq 1 5`;do echo $i; test $i = 3 && break; done
> 
> I see:
> 
>   1
>   2
>   3
> 
> Which is OK.
> 
> However, if the "break" command appears in a subshell:
> 
>   for i in `seq 1 5`;do echo $i; test $i = 3 && (break); done
> 
> then the "break" command does not seem to have any effect
> 
>   1
>   2
>   3
>   4
>   5
> 
> I am curious, is this something to be expected?

Interesting.  If "break" appears out of context, you should get
an error message something like:

   bash: break: only meaningful in a 'for', 'while', or 'until' loop

You didn't get an error message, so part of bash thinks it is in context.
Yet it did not exit the loop.  It seems to me that you should get one
behavior or the other.  Either you should get an error message or it
should exit the loop.

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


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1155847423.2945873.1378139177503.javamail.r...@md01.wow.synacor.com

Re: strange bash behavior

2013-09-04 Thread Stephen Powell

On Mon, 02 Sep 2013 12:26:17 -0400 (EDT), Stephen Powell wrote:
> 
> Interesting.  If "break" appears out of context, you should get
> an error message something like:
> 
>bash: break: only meaningful in a 'for', 'while', or 'until' loop
> 
> You didn't get an error message, so part of bash thinks it is in context.
> Yet it did not exit the loop.  It seems to me that you should get one
> behavior or the other.  Either you should get an error message or it
> should exit the loop.

I just tried this in both ash and dash.  Neither one of them produce an
error message when break is issued out of context.  It simply executes
as a no-op.  (break is a shell built-in command, of course, not an
external command.)  So despite the fact that break is not producing an error
message when one might expect it to, it is apparently exhibiting
"expected behavior" in the sense that output is identical to what would
occur with ash and dash.  (Issue "busybox ash" to get ash.  exit to exit,
of course.)

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

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/84639284.2989400.1378334667562.javamail.r...@md01.wow.synacor.com

Re: rename ttyS*

2013-09-06 Thread Stephen Powell

On Fri, 06 Sep 2013 09:20:08 -0400 (EDT), Josh Stephens wrote:
> 
> You could look at using a udev rule to do the mapping for you.

(Sigh).  Replying to Cosme's posts are a waste of time.  He is from
Cuba.  And his government blocks in-coming e-mails from
outside Cuba.  And either the Debian mailing list archives are a blocked
web site or he doesn't know how to access them.  The only way he's going
to get a reply, if at all, is if someone inside Cuba sends him a private
e-mail.  And that's not likely, because chances are no-one inside Cuba
saw his post.  Cosme posted essentially the same question last month,
and got some on-list replies, one from me, but he evidently did not see them.
It is very frustrating.  It's probably frustrating for him, too.

As for the "problem" itself, I don't see the problem.  Linux is working
as designed.  That's what it is supposed to do.

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

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1173885961.3028466.1378507772181.javamail.r...@md01.wow.synacor.com

Re: DEVTMPFS, DEVTMPFS_MOUNT, custom no initrd kernel, udev 175-7.2 and 204-4

On Thu, 26 Sep 2013 07:25:33 -0400 (EDT), Regid Ichira wrote:
> 
>   In view of http://bugs.debian.org/722580 and
> http://bugs.debian.org/722604:
> 
>   A machine with:
> - a custom, non initrd, linux image
> - udev 175-7.2
> - no DEVTMPFS in the kernel configuration
> is able to boot.
> 
> 1. Will the machine boot with 
>CONFIG_DEVTMPFS=y
># CONFIG_DEVTMPFS_MOUNT is not set
>?  Again, custom, non initrd, linux image.  udev 175-7.2.
> 2. What about
>CONFIG_DEVTMPFS=y
>CONFIG_DEVTMPFS_MOUNT=y
>?  custom, non initrd, linux image.  udev 175-7.2.
> 3. Will it boot when /etc/init.d/udev from udev 175-7.2 is edtited
>by hand?  If so, what modifications, by hand, are required to
>/etc/init.d/udev?  Are there more files to edit?  Again, custom,
>non initrd, linux image.
> 4. When udev 204-4 is installed, what should be the settings of
>CONFIG_DEVTMPFS and CONFIG_DEVTMPFS_MOUNT for a custom, non
>initrd, linux image?
> 
>   Isn't there an upgrade path problem for people with a custom, non
> initrd, linux image that have DEVTMPFS unset?  I mean, newer udev
> can't be installed without CONFIG_DEVTMPFS=y.  So one has to boot
> into a CONFIG_DEVTMPFS=y kernel before upgrading udev.  But will a
> custom, non initrd, linux image with CONFIG_DEVTMPFS=y boot with udev
> 175-7.2?

I don't know the answer to any of your specific questions, but I will
say in general that, in my humble opinion, I would avoid creating kernels
with no initial RAM file system.  Back in the day when the only purpose
for an initial RAM file system was to load kernel modules that were needed
before the permanent root file system could be mounted, an alternative to
doing this was to build the needed support directly into the kernel, thus
eliminating the need to load these kernel modules and thus eliminating the
need for an initial RAM file system.

But modern Linux systems need the
initial RAM file system for other things now besides loading kernel modules,
such as launching early user space processes such as udev.  Some work by
udev may need to be done before the permanent root file system can be
mounted, such as creating symbolic links in the /dev/disk directory and
its subdirectories.  In general, it is not safe to use root file system
specifications such as /dev/sda1 anymore, since the device name mapping
can change from boot to boot.  Specifying the root file system by means
of a UUID or LABEL gets around this problem, but that requires that udev
and friends have already done their disk identification work by then.  And
without an initial RAM file system, udev cannot be launched until after
the permanent root file system has been mounted.  It's a "catch 22"
situation.  My advice, for what it's worth, is to stop swimming upstream
and use an initial RAM file system.

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

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/633734621.3380613.1380198178265.javamail.r...@md01.wow.synacor.com

Re: HDD repair help please

On Thu, 26 Sep 2013 12:08:54 -0400 (EDT), Gábor Hársfalvi wrote:
> 
> Hi,
> 
> How could I repair my HDD with disk manager or similar?
> 
> Because, it has got a lots of bad sector.
> 
> Before I could do that with fsck in recovery mode after umount /home. But
> now it can't work - it says device in use.

fsck cannot repair a file system which is mounted read/write.  It can only
repair a file system which is not mounted or which is mounted read/only.

However, if the sectors are bad because the hard disk is going bad, fsck
cannot fix that.  You need to determine why the sectors went bad in the
first place.  If your hard disk is going bad, it's time to replace the
hard disk.

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

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/740343458.3392139.1380233277438.javamail.r...@md01.wow.synacor.com

Re: should an end user stick to a kernel with an initrd?

On Thu, 26 Sep 2013 17:33:40 -0400 (EDT), Lisi Reisz wrote:
> 
> You know more than Stephen Powell, but you do not know about 
> threading?!

Regid,

What Lisi is saying is that changing the subject line of a post does not
start a new thread.  You have to remove the "In-reply-to:" tag from your
e-mail header before you send it.  If your e-mail client does not allow
you to edit the header, then you need to do a copy and paste of the old
message into a brand new e-mail with a new subject line to start a new
thread.  If you look on the Debian mailing list archives, you will see
that your second e-mail is still part of the original thread.  I learned
this the same way I learned most things: by making mistakes and learning
from them.

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

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/292348606.3392457.1380234628455.javamail.r...@md01.wow.synacor.com

Re: should an end user stick to a kernel with an initrd?

On Thu, 26 Sep 2013 11:57:34 -0400 (EDT), Regid Ichira wrote:
> 
>   I deliberately changed the subject of this message because I hope
> people will also pay attention to my previous message in the thread. 
>   At http://lists.debian.org/debian-user/2013/09/msg01150.html, which,
> I hope, this message will be a follow-up to, Stephen Powell wrote
> that, in general, initrd are desirable.  He gave a few example where,
> he believes, one can not get without it.  I am no expert.  I do 
> believe that, other then corner cases, most, if not all, the examples
> are wrong.  They can be done without an initrd.  I think the basic 
> reason is that one can have udev rules that will map specific devices
> to specific names.
>   Now, considering that an initrd requires a lot more software, I
> think that an initrd should be avoided unless absolutely necessary.  

You don't seem to understand.  First of all, even if you have written
udev rules to map specific devices to specific names, this mapping
cannot take place until udev starts.  udev is not kernel code.  It is
not a kernel module, nor can it be built in to the kernel.  It is a
user-space process.  That means that it must be read from a file system
and executed as a command.  And that means that a file system must be
mounted.  If you don't use an initial RAM file system, there is no file
system from which to read udev until the permanent root file system is
mounted (usually read-only initially).  And if the permanent root file
system is already mounted, it is too late to assign a name to it.
You must know the name before udev gets launched.

Second, this is contrary to the direction and thinking of the kernel
people these days.  Traditional device names, such as /dev/sda, /dev/sdb,
(and therefore the partitions on those devices, such as /dev/sda1, /dev/sdb1,
etc.) are not assigned in a predictable manner anymore.  This device name
assignment can change from one boot to the next.  In order to specify
which partition is to be mounted as the permanent root file system in a manner
which is independent of the now-unpredictable device name assignment, you must
rely on something like the uuid or label of the partition, which is presumed
to be unique.  For example, if your boot loader is LILO, something like

   root="UUID=3860da3c-b206-44d9-920c-5ed4beac34e9"

can be specified in /etc/lilo.conf.  This results in the following being
added to the kernel command line by the LILO boot loader:

   root=UUID=3860da3c-b206-44d9-920c-5ed4beac34e9

But in order for the kernel to figure out which partition on which disk
this is, it looks for a symbolic link called

   /dev/disk/by-uuid/3860da3c-b206-44d9-920c-5ed4beac34e9

If it finds it, it can determine what partition to mount as the permanent
root file system.  But if it can't find it, it can't mount the permanent
root file system.  How did that symbolic link get created?  udev created it.
udev, launched from the initial RAM file system, has already created this
symbolic link.  It might point to /dev/sda1 on this boot.  But on the next
boot, it might point to /dev/sdb1.  In either case, it will be the
correct partition to mount as the permanent root file system.  But if you
don't use an initial RAM file system, udev has not been launched yet, and
therefore, the symbolic link does not exist yet, and therefore, the kernel
can't find the permanent root file system if you refer to it by means of
a uuid.  The same principle applies for referring to a partition by means
of a disk label.

Although it is still possible to create a kernel that does not use an
initial RAM file system, the design of modern Linux systems pretty much
assumes that one is used.  I predict that as time goes on you will continue
to encounter more and more problems as the result of not using one.

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

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1287490021.3392877.1380236855592.javamail.r...@md01.wow.synacor.com

Re: Building computer

2013-09-27 Thread Stephen Powell

On Thu, 26 Sep 2013 22:57:43 -0400 (EDT), Beco  wrote:
> 
> Questions for people who compile kernel and their machines:
> 
> How long a "considered fast" kernel compilation would last? I'd like to
> have a clue. And in what kind of computer (processor / RAM / anything else
> relevant)?
> 
> Thanks!
> Beco.

I haven't been following this thread, but I happened to notice this
particular post.

That depends on many factors, such as the speed of your processor, the
speed of your hard disk drive, how you have your kernel configured, the
architecture you use and how many drivers are available for it, etc.
For my 32-bit Xeon processor (2.40 GHz) compiling for the i386 architecture,
using a kernel configuration that is not too much different from a stock
Debian kernel, it takes hours.  The machine has 4G of RAM.

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

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1714746847.3410869.1380322377088.javamail.r...@md01.wow.synacor.com

Re: should an end user stick to a kernel with an initrd?

2013-09-27 Thread Stephen Powell

On Thu, 26 Sep 2013 23:00:14 -0400 (EDT), Tom H  wrote:
> 
> "A lot more software"?! Installing initramfs-tools will just pull in
> klibc-utils, libklibc, and busybox!

Also, one can limit the size of the initial RAM file system itself by using

   modules=dep

in /etc/initramfs-tools/conf.d/driver-policy.  This attempts to include only
items required for booting in the initial RAM file system.

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


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/558304455.3410915.1380322665423.javamail.r...@md01.wow.synacor.com

Re: should an end user stick to a kernel with an initrd?

2013-09-27 Thread Stephen Powell

On Fri, 27 Sep 2013 14:41:54 -0400 (EDT), Tom H  wrote:
> 
> I couldn't care less how many disks you have.
> 
> Defaulting to the use of UUIDs isn't some wacky whim but a
> well-reasoned technical decision, unless you want to claim to know
> more than the developers putting together distributions.
> 
> This isn't a question of "/dev/sdX works for me, yay!" The issue is
> that device names aren't NECESSARILY stable (some would say that
> they've never been so) so, distributions are using UUIDs in order to
> avoid having any Linux user anywhere be unable to boot because sda is
> now sdc, sdb is now sda, and sdc is now sdb...

+1

Well said.  By the way, even if you only have one hard disk, you can
still get into trouble.  For example, I have a one-hard-disk system
where my hard disk normally shows up as /dev/sda and my CD-ROM drive
normally shows up as /dev/sr0.  But if I boot from the CD-ROM drive
using a Debian installer CD in rescue mode, my CD-ROM drive shows up
as /dev/sda and my hard disk shows up as /dev/sdb!

Specifying the device name for the permanent root file system is not
the only problem.  Suspend/resume is another example.  The suspend
partition is identified by the Debian installer in
/etc/initramfs-tools/conf.d/resume by means of a UUID.  The Debian init
scripts try to process a resume image *before* they attempt to mount
the permanent root file system.  (By the way, this tells you that
/etc/initramfs-tools/conf.d/resume is one of the files that gets built
in to the initial RAM file system; so if you change it you must rebuild
your initial RAM file system.)  If you don't use an initial RAM file
system, you may have trouble with getting suspend/resume to work, or
to work properly.  Early loading of CPU microcode upgrades is another
example.

The point is that the architects of the Debian init scripts pretty much
assume that an initial RAM file system is used, and they take advantage
of that assumption when they write their init scripts.  Although it is
still possible to create a kernel that does not use an initial RAM file
system, that doesn't mean that it is a good idea.  As time goes on, one
is likely to encounter more and more problems as the result of swimming
upstream against the way the system is designed to work these days.

On s390x hardware, I have a Debian Linux system that has four disks.
These disks are assigned the device names /dev/dasda, /dev/dasdb,
/dev/dasdc, and /dev/dasdd by the kernel.  But the correspondence between
these Linux device names and the hardware device numbers varies widely
from boot to boot.  I can assure you of that from personal experience.

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

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/133244.3411509.1380325292433.javamail.r...@md01.wow.synacor.com

Re: should an end user stick to a kernel with an initrd?

2013-09-28 Thread Stephen Powell

On Fri, 27 Sep 2013 23:17:40 -0400 (EDT), Ralf Mardorf wrote:
> On Fri, 2013-09-27 at 19:41 -0400, Stephen Powell wrote:
>> But the correspondence between these Linux device names and the
>> hardware device numbers varies widely from boot to boot.  I can assure
>> you of that from personal experience.
> 
> So my question, if somebody experienced it already is answered.

The s390x hardware platform is more susceptible to device name variations
because of the extra "online/offline" layer.  The kernel does not assign a major
or minor device number to a DASD, nor does it assign it a user-space device
name (/dev/dasda, /dev/dasdb, etc.) until the device is brought "online".
Under Debian, a DASD device is brought online by the sysconfig-hardware
package, which in turn is invoked by udev.  IDE and SCSI drives on the i386
or amd64 hardware platform do not have this extra layer of processing.
But device name changes can happen on i386 and amd64 too.  It's just less
likely.

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

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1370315749.3415771.1380373177940.javamail.r...@md01.wow.synacor.com

Re: just released Grml 2013.09

2013-09-29 Thread Stephen Allen

On Sun, Sep 29, 2013 at 10:38:49PM +0200, sp113438 wrote:
> Hi All,
> 
> To have a new boot-entry with grml:
> 
> put grml64-full_2013.09.iso (or another one, see below) in
> the /boot/grml directory
> 
> sudo apt-get install grml-rescueboot
> 
> sudo update-grub
> 
> get the iso at: http://grml.org/download/
> 

Thanks!


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130930025730.ga31...@debian.gateway.3wire.net

Re: google-chrome-unstable apparently removes its executable

2013-10-08 Thread Stephen Allen

On Sun, Oct 06, 2013 at 11:42:15AM -0400, Patrick Wiseman wrote:
> Updating two testing systems this morning, I found that my Chrome
> suddenly became unable to find any web pages. Attempting to relaunch,
> it wasn't there!
> 
> 'which google-chrome' returned nothing. I tried 'sudo apt-get install
> google-chrome-unstable', but it was already installed. Finally, on
> both systems, I did 'sudo apt-get install google-chrome-stable' and
> now have a working Chrome again.
> 
> I guess that's what I get for being willing to live with unstable!
> 
> Patrick
> 
> 

You could have reinstalled it: 'aptitude reinstall google-chrome-unstable'.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131009004326.GA8799@jessie.gatewire

Re: apt-get vs. aptitude

2013-10-08 Thread Stephen Allen

On Tue, Oct 08, 2013 at 01:33:41PM +0200, Florian Lindner wrote:
> Hello,
> 
> Since I'm about to setup a new server using current stable wheezy, I want to 
> recheck some of debian knowledge.
> 
> What is the prefered tool for installing on the CLI? apt-get or aptitude? 
> Last 
> time I read about it, it was aptitude, due to better dependency checking. 
> What 
> is the current state? apt-get or aptitude? Does it matter? What about using 
> both?
> 
> Thanks!
> 
> Florian
> 
> 
>
My understanding is that apt-get is better at resolving dependencies when a 
large amount of packages are to be installed,  'dist-upgrade'. 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131009004635.GB8799@jessie.gatewire

Re: apt-get vs. aptitude

2013-10-08 Thread Stephen Allen

On Tue, Oct 08, 2013 at 11:35:57AM -0400, david...@ling.ohio-state.edu wrote:
> On Tue, 8 Oct 2013, Florian Lindner wrote:
> >Since I'm about to setup a new server using current stable wheezy, I want to
> >recheck some of debian knowledge.
> >
> >What is the prefered tool for installing on the CLI? apt-get or aptitude? 
> >Last
> >time I read about it, it was aptitude, due to better dependency checking. 
> >What
> >is the current state? apt-get or aptitude? Does it matter? What about using
> >both?
> 
> you might find this worth a look:
> 
>  
> http://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_basic_package_management_operations
> 
>
Excellent! Thanks for the resource, Wes. 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131009005150.GC8799@jessie.gatewire

Re: Set widescreen resolution in console

2013-10-12 Thread Stephen Powell

On Wed, 09 Oct 2013 21:16:11 -0400 (EDT), Antonio Paiva wrote:
> 
> I have recently acquired an old Sony Vaio PCG-C1VN (aka, a "PictureBook")
> and installed Debian wheezy. The problem is that I can only get the
> *console* to run at 640x480 resolution.
> 
> The C1VN has a (very wide) native resolution of 1024x480, but using only
> 640x480 is a serious waste of screen real estate. It works fine in X but,
> the for uses I have in mind (playing some music and reading/writing text),
> all I need works on the console. Moreover, using X slows down the machine
> enough to have a noticeable drag (not unbearable, not very annoying). (Bear
> in mind all this has is a Transmeta Crusoe @600MHz ~= Pentium II @400Mhz,
> and 112MB of RAM.) I'm using kernel modesetting (KMS) with the radeon
> kernel module (graphics card is an ATI Rage Mobility / Mach64). I tried
> setting the mode in GRUB via the GRUB_GFXPAYLOAD_LINUX option, creating my
> own framebuffer mode, but either made no difference or I ended up with an
> even smaller resolution?!
> 
> If you have any ideas or pointers to potential solutions, I would greatly
> appreciate the help. Thank you.
> 
> Best regards,
> Antonio

What driver is used in X?  The MACH64 driver in X is a non-KMS-based driver.
(/var/log/Xorg.0.log should tell you what driver is being used.)  There will
be a whole bunch of lines which start with that driver name.  For example:

MACH64(0): VESA BIOS DETECTED

If you are using a non-KMS-based X driver, then your console should be
running in a hardware text mode, the default for which is 80 columns by
25 rows.  (That's 640 pixels by 400 pixels with a character cell of 16 pixels
high by 8 pixels wide.)  This can be changed by the VGA option.  See my LILO
web page for more information about the VGA option

   http://users.wowway.com/~zlinuxman/lilo.htm

When using the VGA option with grub2, you have to use the linux16 and initrd16
commands instead of linux and initrd, as described in this web page:

   https://wiki.debian.org/GrubTransition

At least, that's what I've been told.  I myself don't use grub2, I use lilo.

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

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/930339389.3648261.1381582664487.javamail.r...@md01.wow.synacor.com

RE: Set widescreen resolution in console

2013-10-13 Thread Stephen Powell

On Sat, 12 Oct 2013 16:14:14 -0400, Antonio Paiva wrote:
> On Fri, 11 Oct 2013 00:25:06 +0400, Dmitrii Kashin wrote:
>> 
>> First of all, have you tried to boot your kernel with vga=ask option?
> 
> Thank you Dmitrii.
> 
> I did try "vga=ask" but that option is no longer supported by the
> debian kernel. On the grub console, I also tried vbeinfo and couldn't
> find the 1024x480 mode. And vbetest only worked with 640x480.

Strictly speaking, "vga" is not a kernel option.  That is, it cannot be
passed on the kernel command line.  It has to be specified by the boot
loader by zapping the kernel boot sector before transferring control to
the kernel.  There has to be special support in the boot loader for the
vga option.  As I said in a previous post, "vga" does not work with the
"linux" and "initrd" statements in grub2.  You have to use "linux16" and
"initrd16" instead.  See my previous post for more information.

I use the lilo boot loader, and the vga option works just fine with it,
even on current jessie kernels.

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

-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/564578903.3659969.1381689768389.javamail.r...@md01.wow.synacor.com

Ubuntuone Package

Good morning;

Any chance that this package will be included in the Debian archive?

Tried to install it but ran into dependency hell and in the end realized
that I wasn't going to be able to install it.

I had found an e-mail from one of the Ubuntu packagers from some time back
indicating that he was going to try to get this included in Debian, due to the
problems of installing the Ubuntu package on a Debian installation.

Comments?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/201812.ga3...@thinkpad.gateway.2wire.net

Re: xfce weather plugin broken?

On Mon, Nov 14, 2011 at 06:06:55PM -0500, Pete Orrall wrote:
> On Sun, 2011-11-13 at 16:31 +, Brian wrote:
> > On Sun 13 Nov 2011 at 10:18:52 -0500, Pete Orrall wrote:
> > 
> > > What's going on and how do I fix this?
> > 
> > https://mail.xfce.org/mailman/listinfo/xfce
> > 
> > November 2011.
> 
> Thanks Brian and Joey for the help.  I dug a little deeper with the
> links provided and found this:
> 
> http://mail.xfce.org/pipermail/goodies-dev/2011-October/003139.html
> 
> Apparently this affects more than just Xfce users

The Gnome weather applet still works, wonder why the XFce plugin doesn't use 
the 
same service?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/2018172915.ga2...@thinkpad.gateway.2wire.net

Re: Is for this community XFCE the most common DE to replace GNOME 3?

On Mon, Nov 14, 2011 at 08:39:06PM +0100, Ralf Mardorf wrote:
> Hi :)
> 
> do most of you replace GNOME 3 by XFCE?
> 
> I'm undecided what to do, but I guess it would be wise to install
> parallel to GNOME 3 the most used alternative installed by users who are
> subscribed to this list.
> 
> Excepted of KDE users, XFCE seems to be the most used replacement for
> GNOME 3. Am I mistaken?
> 
> Cheers!
> 
> Ralf
> 
---end quoted text---

You might try using Openbox. I run it without a desktop environment and it just
works. Even better without the overhead of LXDE.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/2019004408.ga4...@thinkpad.gateway.2wire.net

Re: Ubuntuone Package