Re: bash, dash and sh

[Bob Proulx]

Glenn English wrote:
> May I suggest just changing the pointer from Dash back to Bash. You
> sound like somebody that stays with a release for a while, and this
> is would be a lot less work than editing all those scripts. 

But trivial to change those scripts.  Test it this way:

   find . -type f -exec grep -lZ '^#!/bin/sh' {} + | xargs -0 sed 's@^#! 
*/bin/sh$@#!/bin/bash@' | less

If you like it then fire it for effect with sed's --in-place option.

   find . -type f -exec grep -lZ '^#!/bin/sh' {} + | xargs -0 sed --in-place 
's@^#! */bin/sh$@#!/bin/bash@'

Bob


signature.asc
Description: Digital signature

Re: bash, dash and sh

[Glenn English]

On Apr 22, 2015, at 9:22 PM, Bob Proulx  wrote:

> jeremy bentham wrote:
>> I am finally abandonning my fifteen-year-old computer and Lenny
>> for a six (?) year old used Gateway 2802 (as a Bad Consumer
>> (tm) I never buy anything new if I can avoid it) and, right now,
>> it has a start at Wheezy on it.

As a consumer running an elderly server with Lenny on it, I too congratulate 
you -- Wheezy is more fun than Lenny. They fixed a lot of stuff that gave me 
trouble with Lenny.

>> I have a bunch of scripts 
>> 
>> (ls -1 ~/bin | wc
>>   138   139   1302)
>> 
>> with the first line #!/bin/sh that use bashisms, and the above
>> would be a lot easier than editing each one (of course, maybe
>> just editing each one would be easier than doing this ;-) ).

May I suggest just changing the pointer from Dash back to Bash. You sound like 
somebody that stays with a release for a while, and this is would be a lot less 
work than editing all those scripts. 

Or maybe editing the top line of them from #!/bin/sh to #!/bin/bash, for the 
time being. 

You'll likely have to do significant editing and debugging eventually. But this 
way, you could do that at your pleasure and at your own speed.

-- 
Glenn English




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/bc105d19-4551-4df3-93ba-0d51e2ab4...@slsware.net

wheezy multiarch: binutils:amd64 conflicts with binutils:i386?

[Tom Roche]

summary: 3 questions:

1. Can one install both `binutils:amd64` and `binutils:i386` on the same device?
2. If one can: how? or, what am I doing wrong?
3. If one cannot: why not?

details:

I need to setup a 32-bit app (don't ask!) on a 64-bit linode with

> $ lsb_release -ds
> Debian GNU/Linux 7.8 (wheezy)
> $ cat /etc/debian_version
> 7.8
> $ uname -rv
> 3.19.1-x86_64-linode53 #1 SMP Tue Mar 10 15:30:28 EDT 2015

> $ dpkg --print-architecture
> amd64
> $ dpkg --print-foreign-architectures
> i386
> $ sudo aptitude update
> ...
> $ sudo aptitude full-upgrade
> ...

> $ aptitude --version
> Thu Apr 23 00:08:02 EDT 2015
> aptitude 0.6.8.2 compiled at Nov  7 2012 07:08:03
> Compiler: g++ 4.7.2
> Compiled against:
>   apt version 4.12.0
>   NCurses version 5.9
>   libsigc++ version: 2.2.10
>   Ept support enabled.
>   Gtk+ support disabled.
>   Qt support disabled.
>
> Current library versions:
>   NCurses version: ncurses 5.9.20110404
>   cwidget version: 0.5.16
>   Apt version: 4.12.0

> $ apt-get --version
> Thu Apr 23 00:08:39 EDT 2015
> apt 0.9.7.9 for amd64 compiled on Oct 17 2014 09:15:56
> Supported modules:
> *Ver: Standard .deb
> *Pkg:  Debian dpkg interface (Priority 30)
>  Pkg:  Debian APT solver interface (Priority -1000)
>  S.L: 'deb' Standard Debian binary tree
>  S.L: 'deb-src' Standard Debian source tree
>  Idx: Debian Source Index
>  Idx: Debian Package Index
>  Idx: Debian Translation Index
>  Idx: Debian dpkg status file
>  Idx: EDSP scenario file

Among other packages, I need to install `binutils:i386`. However, I can't seem 
to install that and keep the native/64-bit `binutils`:

> $ date ; sudo apt-get install binutils:i386
> Thu Apr 23 00:08:50 EDT 2015
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> The following extra packages will be installed:
>   libstdc++6:i386 zlib1g:i386
> Suggested packages:
>   binutils-doc:i386
> The following packages will be REMOVED:
>   binutils
> The following NEW packages will be installed:
>   binutils:i386 libstdc++6:i386 zlib1g:i386
> 0 upgraded, 3 newly installed, 1 to remove and 0 not upgraded.
> Need to get 4,993 kB of archives.
> After this operation, 325 kB disk space will be freed.
> Do you want to continue [Y/n]? ^C

> $ date ; sudo aptitude -s install binutils:i386
> Thu Apr 23 00:08:21 EDT 2015
> The following NEW packages will be installed:
>   binutils:i386{b} libstdc++6:i386{a} zlib1g:i386{a} 
> 0 packages upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
> Need to get 4,993 kB of archives. After unpacking 14.7 MB will be used.
> The following packages have unmet dependencies:
>  binutils : Conflicts: binutils:i386 but 2.22-8+deb7u2 is to be installed.
>  binutils:i386 : Conflicts: binutils but 2.22-8+deb7u2 is installed.
> The following actions will resolve these dependencies:
>
>  Remove the following packages:
> 1) binutils

> Accept this solution? [Y/n/q/?] q

So I have 3 questions:

1. Can one install both `binutils:amd64` and `binutils:i386` on the same device?

2. If one can: how? or, what am I doing wrong?

3. If one cannot: why not?

Apologies if this is a FAQ, but

* I saw no answers relating to this (though several similar questions) when 
DuckDuckGo-ing

* I see nothing @ https://wiki.debian.org/Multiarch/HOWTO indicating that I 
should not be able to do this.

TIA, Tom Roche 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87d22vigvc@pobox.com

Gnumeric's DAYS function

[David Wright]

Seeing some spreadsheet discussion reminded me that I had noticed a
change in the behaviour of gnumeric between wheezy and jessie, which
affected some of my spreadsheets.

The order of the arguments to DAYS() has been reversed. DAYS() returns
the number of days between two dates. I've used it in monitoring my
household utility consumption, for example.

I have checked that jessie's ordering agrees with jessie's libreoffice,
and I think there is some sort of newish standard for spreadsheets that
mandates this order. But I've seen no warnings about the change.

It poked me right in the eye, but there may be more subtle effects
in other people's spreadsheets that use it. I also wonder if other
functions may have been modified too.

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150423044918.GD4457@alum

Re: reading an empty directory after reboot is very slow

[David Wright]

Quoting Vincent Lefevre (vinc...@vinc17.net):
> On 2015-04-21 10:35:12 -0600, Bob Proulx wrote:
> > Vincent Lefevre wrote:
> > > So, there's still something I don't understand: after dropping the
> > > caches, why is Mutt fast to read the mailbox (about 1 minute), but
> > > not my tool (about 30 minutes)?
> > 
> > Are you using mutt's header_cache feature?  It keeps a cache of mail
> > files off to the side.  It really improves Maildir performance.  I
> > personally also have maildir_header_cache_verify=no set too.
> 
> No, I don't use it. This variable doesn't even exist with my compiled
> version.

OK, I'll ask. What *is* your version?

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150423043049.GC4457@alum

Re: reading an empty directory after reboot is very slow

[David Wright]

Quoting Vincent Lefevre (vinc...@vinc17.net):
> On 2015-04-21 12:47:14 -0500, David Wright wrote:
> > Quoting Vincent Lefevre (vinc...@vinc17.net):
> > > This mailbox is constantly open in a Mutt running in screen (in
> > > read-only mode). I often read it, and I modify it from time to time,
> > > either by adding new messages in the usual way, or by modifying some
> > > header of existing messages with some tool of mine (in which case, I
> > > restart Mutt to take the changes into account).
> > 
> > I guess I find it hard (not knowing what all these emails are) to get
> > my head around needing an email-style random access to 145k emails in
> > one folder.
> 
> I can then do any filtering I like to search for an old e-mail
> instead of having to look at several folders individually.

You have more of these folders with thousands of emails in them?

> > > When I wrote my tool, I thought that such a cached mapping would be
> > > useless because the mailbox would have to be read by Mutt anyway.
> > > So, there's still something I don't understand: after dropping the
> > > caches, why is Mutt fast to read the mailbox (about 1 minute), but
> > > not my tool (about 30 minutes)?
> > 
> > Because mutt caches, and its caches are persistent.
> > The default location (not in the man page, I think) is
> > ~/.mutt-cache/header-cache/
> > for the headers, and its parent for the emails themselves.
> 
> No, I don't use caches (the header cache is not enabled and the
> ~/.mutt-cache directory doesn't exist).

My fault; I had forgotten that I myself added these settings to .muttrc.
After all, that was probably in 1998.

In which case, if you want to know how come mutt is so fast, take a
look at the source. Just to mention one optimisation I would consider:
slurp the directory and sort the entries by inode. Open the files in
inode order.
And another: it's probably faster to slurp bigger chunks of each file
(with an intelligent guess of the best buffer size) and use a fast
search for \nMessage-ID rather than reading and checking line by line.

> > > > Have you considered running a local IMAP server to handle this (and
> > > > any other) maildir?
> > > 
> > > There would be other problems. All the tools would have to talk
> > > with this server... and for instance, mairix doesn't support IMAP.
> > 
> > Is this correct?
> > http://www.gnu.org/software/emacs/manual/html_node/gnus/Setting-up-mairix.html
> 
> This seems to be something different (nnmairix), which is not in Debian.
> For mairix:
> 
>  mairix is a program for indexing and searching locally stored email messages.
>  mairix supports Maildir, MH folders, and mbox formats.

nnmairix is a backend to mairix. It's here in wheezy and jessie.
usr/share/emacs/23.4/lisp/gnus/nnmairix.el.gz editors/emacs23-el
usr/share/emacs/23.4/lisp/gnus/nnmairix.elc editors/emacs23-common
usr/share/emacs/24.4/lisp/gnus/nnmairix.el.gz editors/emacs24-el
usr/share/emacs/24.4/lisp/gnus/nnmairix.elc editors/emacs24-common

> > But I don't understand why, if you're running mairix, you need to scan the
> > emails yourself. Hasn't mairix done this already? (As well as mutt.)
> 
> Only once for indexing. This is persistent after reboots and not
> used by Mutt at all.

No, I wasn't expecting mutt to use mairix. But I thought you might be
using it. Otherwise, why do you index them?

I also wondered what the problem would be with putting the thousands
of emails in a general purpose database. Don't they search and
retrieve faster than perl scripts?

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150423042845.GB4457@alum

Re: reading an empty directory after reboot is very slow

[David Wright]

Quoting Vincent Lefevre (vinc...@vinc17.net):
> On 2015-04-21 11:05:58 -0500, David Wright wrote:
> > Quoting Vincent Lefevre (vinc...@vinc17.net):
> > > On 2015-04-20 13:04:41 -0500, David Wright wrote:
> > > > Quoting Vincent Lefevre (vinc...@vinc17.net):
> > > > > But with the current solution (no automatic moving of an entry), you
> > > > > can't miss an entry that hasn't been removed.
> > [...]
> > > > ...so if you happen to be reading the entry for file5 at the
> > > > time I typed mv, you'll get the entry for file4 twice, under
> > > > two different names. (Or the opposite.)
> > > 
> > > OK, so, if the rename(2) system call can reorder the entries (this is
> > > not quite clear because one doesn't see the empty entries here),
> > 
> > No, and you wouldn't *normally* see them with readdir, I'd suppose.
> 
> But this matters for the implementation in the kernel.

What's "this". And what does it matter? You make some system calls,
and you get replies. They come out of a black box.

> > > then
> > > there is already a problem with the file system. Getting an entry
> > > twice under different names is not much a problem, IMHO, because one
> > > can look at the inode number; there's a race condition, but at worst,
> > > one can just miss a *new* inode (whose number has been reassigned).
> > > Missing an existing entry is a problem.
> > 
> > ...easily demonstrated with

[old demonstration snipped]
> > 
> > where file3 goes AWOL.
> 
> You haven't demonstrated anything. If you have before the mv:
> 
> 0: file1
> 1: file4
> 2: file5
> 3: file6
> 4: file2
> 5: file3
> 
> and after the mv:
> 
> 0: file1
> 1: file4
> 2: file5
> 3: [empty]
> 4: [empty]
> 5: file3file3file3file3file3file3file3file3file3file3file3file3file3
> 6: file6
> 7: file2
> 
> there's no problem.

So you don't believe the problem when it's demonstrated, but you do
believe some hypotheticals you just made up. Ask yourself why an
efficient filesystem would move a load of directory entries just
because someone renamed a file.

> What actually needs to be done is a real test
> using readdir.

OK. Here's a demonstration of a file going AWOL by moving *up* the
directory listing. Because of read-ahead, readdir still sees the old
name and the stat() fails. Again, because of read-ahead, I can't
demonstrate the opposite effect in the same program because
you'd have to have a directory bigger than the read-ahead buffer
in order to see any effect. But, as was said already, it's occurrence
can be discovered by checking the inode numbers for duplicate returns.

I scan the directory with readdir, then stat the file to obtain its
inode number. E is stat's return code, I is inode number.
When the latter matches 497051, I sleep for 5 seconds so that
another process can rename a file.

~ $ for j in 1 2 3 4 5 6 ; do mkdir /tmp/testdir/file$j ; done

~ $ /tmp/a.out /tmp/testdir/ ← before doing anything
1 E: 0 I: 496992 file1
2 E: 0 I: 497007 file4
3 E: 0 I: 497039 file5
4 E: 0 I: 488682 .
5 E: 0 I: 497051 file6
sleeping ← I give myself 5 seconds to do something
6 E: 0 I: 488641 ..
7 E: 0 I: 497003 file2
8 E: 0 I: 497006 file3

~ $ /tmp/a.out /tmp/testdir/ ← during the alteration
1 E: 0 I: 496992 file1
2 E: 0 I: 497007 file4
3 E: 0 I: 497039 file5
4 E: 0 I: 488682 .
5 E: 0 I: 497051 file6
sleeping← here I renamed file2 (in another xterm)
6 E: 0 I: 488641 ..
7 E: -1 I: 488641 file2 ← oops, file2 stat() fails (so the inode number is 
untouched from the previous call)
8 E: 0 I: 497006 file3

~ $ /tmp/a.out /tmp/testdir/ ← after the alteration
1 E: 0 I: 496992 file1
2 E: 0 I: 497007 file4
3 E: 0 I: 497039 file5
4 E: 0 I: 488682 .
5 E: 0 I: 497003 
file2file2file2file2file2file2file2file2file2file2file2file2file2file2 ← here 
it is
6 E: 0 I: 497051 file6
sleeping
7 E: 0 I: 488641 ..
8 E: 0 I: 497006 file3
~ $ 

> Any idea of the algorithm to choose the directory entries? The fact
> that the files are not ordered initially is unintuitive.

A hashing function, so I guess one reads that as "random".
Oh, oh, I better be careful what I say. "Pseudorandom", as it's
deterministic. I get the same sequence every time I make those
files.

> > > What do the backup systems do?
> > 
> > I don't know. Lock the directory and slurp it (if it's not too big),
> > otherwise check the modification time before and after reading it,
> > and reread it if necessary, maybe...
> 
> The modification time mustn't be used since it can be changed by some
> tools, e.g. during unarchiving or decompressing. The ctime could be
> OK, but re-reads can introduce endless loops for directories that are
> constantly modified.

What's going on here? Is "What do the backup systems do?" an Aunt Sally,
so you can take pot shots at any suggestion? If you want to know what
backup systems do, how filesystems "choose the directory entries",
then you've got the same access to the source as I have. Take a look.
But don't expect me to come up with a bullet-proof scheme.

This subthread started at 
http

Re: LibreOffice 64 bit suddenly wont save.

[Marc Shapiro]

Changes made to a spreadsheet and saved were reloaded correctly after 
exiting and restarting LibreOffice. A new text document saved from 
Writer also loaded just fine.  No problems here.


Marc


On 04/20/2015 12:54 AM, lina wrote:

I do not have problem with LibreOffice Impress in "Save File".
However, once I closed the LibreOffice Impress,
restart and re-open the former saved file, it loses 100% fidelity.
Some "Connector" have gone; Some lines changed its place or orientation.

Thanks,

On Mon, Apr 20, 2015 at 8:34 AM, Gary Roach  wrote:

Has anyone else had the problem that LibreOffice 64 suddenly refuses to save
files. If I pull up an old file and change it and save everything seems to
be OK. But when I try to open the file again the restore corrupted file
screen  pops up. When I go through that routine the file opens with none of
the new changes show. If I create a new file and use save as, LibreOffice
closes and the file is not saved. I reinstalled the office suit, the base
and the core programs. This didn't help. I think this is more a Debian
problem than an LO problem so am posting here.
 Debian wheezy amd64 up to date.

Gary R.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject
of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5534497b.1090...@verizon.net






--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/55386a1b.5020...@gmail.com

Re: bash, dash and sh

[David Christensen]

On 04/22/2015 08:02 PM, jeremy bentham wrote:

I have a bunch of scripts ...
with the first line #!/bin/sh that use bashisms, ...


How about changing the shebang line of the scripts with Perl?


http://debian-administration.org/article/298/Search_and_replace_across_many_files_with_a_perl_one-liner


Note that you can leave off the -i switch to Perl while developing your 
code snippet and/or regular expression, and Perl will print the munged 
results to STDOUT rather than clobbering your file(s):


2015-04-22 20:30:58 dpchrist@t2250 ~/sandbox/sh
$ ll hello.sh
-rwxr-xr-x 1 dpchrist dpchrist 31 2015/04/22 20:30:51 hello.sh*

2015-04-22 20:31:02 dpchrist@t2250 ~/sandbox/sh
$ cat hello.sh
#!/bin/sh
echo "hello, world!"

2015-04-22 20:31:04 dpchrist@t2250 ~/sandbox/sh
$ ./hello.sh
hello, world!

2015-04-22 20:31:08 dpchrist@t2250 ~/sandbox/sh
$ perl -p -e 's(#!/bin/sh)(#!/bin/bash)' hello.sh
#!/bin/bash
echo "hello, world!"

2015-04-22 20:31:14 dpchrist@t2250 ~/sandbox/sh
$ cat hello.sh
#!/bin/sh
echo "hello, world!"

2015-04-22 20:31:19 dpchrist@t2250 ~/sandbox/sh
$ perl -pi -e 's(#!/bin/sh)(#!/bin/bash)' hello.sh

2015-04-22 20:31:26 dpchrist@t2250 ~/sandbox/sh
$ cat hello.sh
#!/bin/bash
echo "hello, world!"

2015-04-22 20:31:29 dpchrist@t2250 ~/sandbox/sh
$ ./hello.sh
hello, world!


David


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/553867fc.5090...@holgerdanske.com

Re: bash, dash and sh

[Bob Proulx]

jeremy bentham wrote:
> I am finally abandonning my fifteen-year-old computer and Lenny
> for a six (?) year old used Gateway 2802 (as a Bad Consumer
> (tm) I never buy anything new if I can avoid it) and, right now,
> it has a start at Wheezy on it.

Congratulations on your recent upgrade.  I am sure you will enjoy it.

> I happened to read on another list, and then verified for myself,
> that /bin/sh is now a link to dash, instead of bash.

Yes.

> If I
> 
> cd /bin
> sudo rm sh; ln -s bash sh
> 
> will I break a bunch of stuff?

You have an error in the above.  You have sudo for the first command,
the rm, but not for the second command, the ln.

Do it in one command instead.

  sudo ln -sfn bash /bin/sh

Note that I didn't test the above but I believe it will work.

> I have a bunch of scripts 
> 
> (ls -1 ~/bin | wc
>138   139   1302)
> 
> with the first line #!/bin/sh that use bashisms, and the above
> would be a lot easier than editing each one (of course, maybe
> just editing each one would be easier than doing this ;-) ).

I suggest editing each one of those.  Changing /bin/sh just treats a
symptom.  Changing the #! line is the Right Thing to do.

Do every single one of those contain bashisms?  That seems unlikely.

Bob


signature.asc
Description: Digital signature

bash, dash and sh

[jeremy bentham]

I am finally abandonning my fifteen-year-old computer and Lenny
for a six (?) year old used Gateway 2802 (as a Bad Consumer
(tm) I never buy anything new if I can avoid it) and, right now,
it has a start at Wheezy on it.

I happened to read on another list, and then verified for myself,
that /bin/sh is now a link to dash, instead of bash.

If I

cd /bin
sudo rm sh; ln -s bash sh

will I break a bunch of stuff?

I have a bunch of scripts 

(ls -1 ~/bin | wc
   138   139   1302)

with the first line #!/bin/sh that use bashisms, and the above
would be a lot easier than editing each one (of course, maybe
just editing each one would be easier than doing this ;-) ).

--
Dave WilliamsIn order to save you from the terrorists, we
d...@eskimo.com   need to find out about your sex life.  And we've
 got the technology to do it!


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150423030228.GS14392@benny

Re: empty directories need disk space

[Bob Proulx]

basti wrote:
> on different servers I have cache folders with a lot of small files. Now
> all the files are delete but the folder "need" 151 MB.
> Whats gonig on here? What is the problem? How can I fix? Delete and
> create would be impracticable.

With ext2, ext3 and ext4 directories can only grow.  They never
shrink.  If you take the file system offline and run 'e2fsck -D -f' on
them then the fsck will shrink them.  But it is an offline operation.

> --- /home/somedir/cache/baseall/basecache
>   151.0MiB [##]

In this day and age 151M of data seems too small to try to recover.

Bob


signature.asc
Description: Digital signature

Re: can't automatically launch lxde

[James]

On 04/21/2015 11:46 PM, Gary Dale wrote:

On 21/04/15 08:21 PM, James wrote:
I installed lxde as a gui desktop but I can't get it to run 
automatically.

I need to login as me and then do sudo kdm (sudo lxdm doesn't work).


It sounds like kdm isn't starting automatically, so you probably don't 
have any gui starting (is this correct?).

Correct.


You probably have kdm or lxdm installed but not both, which is why 
only one starts. Lxdm is not a Debian package so if you are running 
Debian, that would explain it.

I am running Debian Jessie and I have lxde 8.
I think I just installed the lxde package.
https://wiki.debian.org/LXDE#LXDE_in_Debian



The easiest way to fix the problem may be to:

sudo apt-get purge kdm
sudo apt-get install kdm

This should fix any corruption that may have occurred and should set 
up kdm to run on startup. If you prefer lxdm, simply change the 
install line to lxdm (assuming that you are running Ubuntu).

sudo apt-get install lxde
Reading package lists... Done
Building dependency tree
Reading state information... Done
lxde is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/55385bfa.8000...@lockie.ca

Re: boot logo in Jessie?

[deloptes]

German wrote:

> Is that possible to set up boot logo in Jessie? Black screen during boot
> is not nice. Thanks
> 

install plymouth




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/mh94lc$bfl$1...@ger.gmane.org

Re: Installing open-vm-tools in Debian Wheezy

[Sven Hartge]

Eric Gamess  wrote:

>> If you install this for a VM running on ESX then you can ignore this
>> error, since HGFS (Host-Guest-Filsystem) does not work with ESX and
>> vmsync is for the experimental VSS-like snapshot feature for Linux which
>> I never saw used in any production environment.

> I am using VMware Workstation. Even with the problem mentioned, the
> compilation finishes. However, "Edit Copy" and "Edit Paste" does not
> work. And dragging files between the host OS (Windows 7) to the guest
> OS(Debian) does not work.

I am not sure if the first one even works with the native VMware Tools.
The last one uses the HGFS, so if the module is not available it will of
course not work.

S°

-- 
Sigmentation fault. Core dumped.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/mbib7rcdh...@mids.svenhartge.de

Re: Installing open-vm-tools in Debian Wheezy

[Eric Gamess]

> If you install this for a VM running on ESX then you can ignore this
> error, since HGFS (Host-Guest-Filsystem) does not work with ESX and
> vmsync is for the experimental VSS-like snapshot feature for Linux which
> I never saw used in any production environment.

Sven,

I am using VMware Workstation. Even with the problem mentioned, the
compilation finishes. However, "Edit Copy" and "Edit Paste" does not
work. And dragging files between the host OS (Windows 7) to the guest
OS(Debian) does not work.

Thank you.

Eric.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/eedb85c4-c96a-4e72-8859-ab04bf813...@googlegroups.com

Re: Installing open-vm-tools in Debian Wheezy

[Eric Gamess]

Dear Darac,

> Sounds like Bug #779081, which suggests an upgrade to version
> 2:8.8.0+2012.05.21-724730-1+nmu2+deb7u1.

Yes, you are right!!! This is the bug. I found information
on it in the Internet. So now, can someone point me to how
to move to version 2:8.8.0+2012.05.21-724730-1+nmu2+deb7u1 ???

Thank you.

Eric.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/f1545619-69fa-4814-b7cb-805bce9e4...@googlegroups.com

Re: can't automatically launch lxde

[Patrick Bartek]

On Tue, 21 Apr 2015, James wrote:

> I installed lxde as a gui desktop but I can't get it to run
> automatically. I need to login as me and then do sudo kdm (sudo lxdm
> doesn't work).

Exactly how did you install LXDE?  What other desktop environments do
you have installed?  Does that desktop run instead of LXDE?  I'm
assuming so.  Try this:

At login, at the bottom of the screen -- maybe at the top (I haven't
run a desktop in years, just a WM), there should be a gadget to select
which desktop, window manager, etc. to run.  Pick one of the LXDE
options.

B


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150422092143.1ca17...@debian7.boseck208.net

Re: Installing open-vm-tools in Debian Wheezy

[Sven Hartge]

Eric Gamess  wrote:

> And I got an error message:
> Error!  Build of vmhgfs.ko failed for: 3.2.0-4-686-pae (i686)
> Consult the make.log in the build directory
> /var/lib/dkms/open-vm-tools/2012.05.21/build/ for more information.
> Setting up open-vm-tools (2:8.8.0+2012.05.21-724730-1+nmu2) ...
> FATAL: Module vmhgfs not found.
> FATAL: Module vmsync not found.

If you install this for a VM running on ESX then you can ignore this
error, since HGFS (Host-Guest-Filsystem) does not work with ESX and
vmsync is for the experimental VSS-like snapshot feature for Linux which
I never saw used in any production environment.

All other modules, for example vmxnet3 or vmware-balloon are already
inside the default Debian kernel.

And if you can live without the Shared Folder feauture of VMware
Workstation you don't need to bother fixing vmhgfs either.

Grüße,
S°

-- 
Sigmentation fault. Core dumped.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/lbib417dh...@mids.svenhartge.de

Re: Need help fixing an unhandled irq

[Kynn Jones]

On Tue, Apr 21, 2015 at 9:49 PM, Kynn Jones  wrote:

> OK, I found a way to turn off one of the two snd_hda_intel,
> but it turned out to be the one on IRQ 45.  (In any case,
> doing this did not solve the problem.)  The method I used was

> 1. find the prefix of the audio device(s) in the output of lspci
> 2. search for a path under /sys/devices with this prefix in the basename
> 3. add a line of the form

> echo 1 > /path/found/in/previous/step/remove

> When did step (1) I found two candidate prefixes 00:03.0 and 00.1b.0,
from the lines

> 00:03.0 Audio device: Intel Corporation Haswell HD Audio Controller
(rev 06)
> 00:1b.0 Audio device: Intel Corporation Lynx Point High Definition
Audio Controller (rev 04)

> but in step (2) I was able to find only one matching path, namely

> /sys/devices/pci:00/:00:1b.0

Correction: when I looked again I did find a file for 00.03.0:

   /sys/devices/pci:00/:00:03.0

I'm not sure why I missed it the first time.

> I went ahead and added the line

> echo 1 > /sys/devices/pci:00/:00:1b.0/remove

> to /etc/rc.local, and rebooted.

I repeated the same thing once more with this line instead:

echo 1 > /sys/devices/pci:00/:00:03.0/remove

...and now after rebooting the IRQ 16 line of /proc/interrupts
shows only one driver:

# grep '^ 16:' /proc/interrupts
 16:   1211  0  0  0  IR-IO-APIC-fasteoi
ehci_hcd:usb1

But, unfortunately, this turned out to be a red herring: the
unhandled IRQ 16 error continues to happen, and along with it the
mouse that, as it were, "wakes drunk from sleep".  (At least the
system's sound continues to work fine, AFAICT.)

Now it looks like the problem is with the ehci_hcd driver.

In this case, I don't think that disabling the driver is an
option, so I decided to send a full bug report to the
debian-kernel list, here:

https://lists.debian.org/debian-kernel/2015/04/msg00348.html

Putting aside the main issue (the problem with the mouse) I now
have the additional (but far less pressing) question of which of
the two instances of snd_hda_intel I should keep around?

kj

Re: Installing open-vm-tools in Debian Wheezy

[Darac Marjal]

On Wed, Apr 22, 2015 at 08:04:14AM -0700, Eric Gamess wrote:
> Thank you Liam,
> 
> > The open-vm-tools package recomends open-vm-dkms. The package
> > description for the latter is 'Source for VMware guest systems driver
> > (DKMS)'. It seems that that will give you the source, packaged to work
> > with DKMS.  Therefore the module(s) will automaticaly be recompiled on
> > kernel upgrade.
> 
> Yes, by the way, when you install open-vm-tools, it will
> also install open-vm-dkms, since it is a dependency. It seems
> that the source code is now in this new package, and not in
> open-vm-source anymore.
> 
> 
> Yes, open-vm-tools starts to compile, and will stop compiling
> because there is a syntax error in file:
> /var/lib/dkms/open-vm-tools/2012.05.21/build/vmhgfs/inode.c

Sounds like Bug #779081, which suggests an upgrade to version
2:8.8.0+2012.05.21-724730-1+nmu2+deb7u1.

> 
> Compilation will also show this message:
> > FATAL: Module vmhgfs not found.
> > FATAL: Module vmsync not found. 
> 
> Any other idea
> Thank you.
> 
> Eric.
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> https://lists.debian.org/6db8fcee-6bc2-4d31-a4b3-1be4d93cb...@googlegroups.com
> 


signature.asc
Description: Digital signature

Re: Installing open-vm-tools in Debian Wheezy

[Eric Gamess]

Thank you Liam,

> The open-vm-tools package recomends open-vm-dkms. The package
> description for the latter is 'Source for VMware guest systems driver
> (DKMS)'. It seems that that will give you the source, packaged to work
> with DKMS.  Therefore the module(s) will automaticaly be recompiled on
> kernel upgrade.

Yes, by the way, when you install open-vm-tools, it will
also install open-vm-dkms, since it is a dependency. It seems
that the source code is now in this new package, and not in
open-vm-source anymore.


Yes, open-vm-tools starts to compile, and will stop compiling
because there is a syntax error in file:
/var/lib/dkms/open-vm-tools/2012.05.21/build/vmhgfs/inode.c

Compilation will also show this message:
> FATAL: Module vmhgfs not found.
> FATAL: Module vmsync not found. 

Any other idea
Thank you.

Eric.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/6db8fcee-6bc2-4d31-a4b3-1be4d93cb...@googlegroups.com

Re: Installing open-vm-tools in Debian Wheezy

[David Wright]

Quoting Liam O'Toole (liam.p.oto...@gmail.com):
> The open-vm-tools package recomends open-vm-dkms. The package
> description for the latter is 'Source for VMware guest systems driver
> (DKMS)'. It seems that that will give you the source, packaged to work
> with DKMS.  Therefore the module(s) will automaticaly be recompiled on
> kernel upgrade.

Alternatively, purge and reinstall open-vm-dkms which should trigger
a recompilation. (That's a complete guess, based on the behaviour of
ndiswrapper under similar conditions.)

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150422152019.GA25251@alum

Re: Proxy authentication on gnome

[Liam O'Toole]

On 2015-04-22, Iuri Guilherme  wrote:
> --=_09865548c132c4c9e7ee8a86ad210a78
> Content-Transfer-Encoding: 7bit
> Content-Type: text/plain; charset="UTF-8"
>
> I couldn't search the list archives for this, but I am having trouble
> trying to authenticate on proxies servers.
>
> In the system network configuration on Wheezy, there are the fields to
> configure a proxy. However, it just allow one to put the server and
> port, and there is no place in the GUI to configure user and password.
>
> Upon trying to force Iceweasel to use specific configuration, or even
> WPAD, the same problem occurs because the popup window that shows up
> on most systems asking for a moz-proxy:// password never shows up.
> Also there seems to be no other (easy) way to put the user and
> password on Iceweasel because the sqlite file on the mozilla folder
> seems to have some source of protection.
>
> So this Debian machine is sitting here because authentication is
> needed on a corporate proxy.

Do you know what authentication protocol is used by the proxy? If it is
NTLM, then the ntlmaps package might help you.

-- 

Liam



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnmjfden.hf9.liam.p.otoole@dipsy.tubbynet

squid and apt

[Pol Hallen]

Hi all

I've squid with transparent proxy, why linux clients has problems with 
apt? (apt-get update)


Err http://mirrordirector.raspbian.org wheezy/non-free armhf Packages
  400  Bad Request

on every clients I've:

iptables -t nat -A OUTPUT -p tcp --dport 80 -j DNAT --to-destination ip:port

Do I need set to /etc/apt/... the proxy to solve the issue?

thanks

Pol


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/5537ad80.5080...@fuckaround.org

Debian Testing: Upgrade XFCE from v-4.10 to v-4.12

[Stephen P. Molnar]

Has anyone upgraded XFCE v-4.10 to v-4.12 in Debian Testing without 
having to compile the tarballs?


I am currently running RC3 in a VM and willing to experiment if there 
might be some guidance available.


Thanks in advance.

--
Stephen P. Molnar, Ph.D.Life is a fuzzy set
www.FoundationForChemistry.com  Stochastic and multivarate
(614)312-7528 (c)
Skype: smolnar1


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/5537a848.2060...@sbcglobal.net

Re: /etc/network/interfaces in jessie and systemd?

[Michael Biebl]

Am 22.04.2015 um 10:21 schrieb Vincent Lefevre:
> On 2015-04-21 17:27:46 +0200, Michael Biebl wrote:
>> The ifup@.service is triggered by a udev rule and responsible to handle
>> allow-hotplug interfaces.
> 
> I hope that this will remain always optional. For a laptop at least,
> that's not the correct way to do.

Are you advocating the use of auto over allow-hotplug or the use of
something enirely else, more dynamic, like network-manager?

I'm not quite sure what you mean with "remain always optional" though.

Care to elaborate?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

(Solved)Re: define a new keyboard shortcuts in "settings/keyboard/shortcuts"

[mudongliang]

Thank you very much! 
The problem is solved.
On Wed, 2015-04-22 at 11:04 +, Liam O'Toole wrote: 
> On 2015-04-22, mudongliang  wrote:
> > I want to define a new  keyboard shortcuts in the graphic
> > "settings/keyboard/shortcuts" to start-up the gitlab!
> > Name: Gitlab Panel
> > Commands: su -c "/opt/gitlab-7.9.3-0/manager-linux-x64.run"
> > The attribute of this file is following :
> > /opt/gitlab-7.9.3-0/manager-linux-x64.run: ELF 64-bit LSB executable,
> > x86-64, version 1 (GNU/Linux), statically linked, stripped
> > But when I press the keyboard , there is no response to me! 
> >
> > mudongliang
> >
> >
> 
> Try using /usr/bin/gksu (from the package of the same name) instead of
> su. (See the man page for the appropriate syntax.) Then you will be
> prompted for the root password.
> 
> -- 
> 
> Liam
> 
> 
> 



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/blu436-smtp169c0ebb8233a90410649b5bc...@phx.gbl

Re: define a new keyboard shortcuts in "settings/keyboard/shortcuts"

[Liam O'Toole]

On 2015-04-22, mudongliang  wrote:
> I want to define a new  keyboard shortcuts in the graphic
> "settings/keyboard/shortcuts" to start-up the gitlab!
> Name: Gitlab Panel
> Commands: su -c "/opt/gitlab-7.9.3-0/manager-linux-x64.run"
> The attribute of this file is following :
> /opt/gitlab-7.9.3-0/manager-linux-x64.run: ELF 64-bit LSB executable,
> x86-64, version 1 (GNU/Linux), statically linked, stripped
> But when I press the keyboard , there is no response to me! 
>
> mudongliang
>
>

Try using /usr/bin/gksu (from the package of the same name) instead of
su. (See the man page for the appropriate syntax.) Then you will be
prompted for the root password.

-- 

Liam



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnmjf022.fg9.liam.p.otoole@dipsy.tubbynet

define a new keyboard shortcuts in "settings/keyboard/shortcuts"

[mudongliang]

I want to define a new  keyboard shortcuts in the graphic
"settings/keyboard/shortcuts" to start-up the gitlab!
Name: Gitlab Panel
Commands: su -c "/opt/gitlab-7.9.3-0/manager-linux-x64.run"
The attribute of this file is following :
/opt/gitlab-7.9.3-0/manager-linux-x64.run: ELF 64-bit LSB executable,
x86-64, version 1 (GNU/Linux), statically linked, stripped
But when I press the keyboard , there is no response to me! 

mudongliang


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/blu436-smtp1723a675d603583790113dbc...@phx.gbl

Re: Grub is not showing after install debian on windows 8.1 laptop

[Darac Marjal]

On Wed, Apr 22, 2015 at 01:29:24PM +0800, 丁海江 wrote:
>I tried to install debian whizzey into my laptop which runs windows 8.1
>now, and the last step i have chosen to install grub with mbr.
>Then it asked me to reboot, after reboot, there is no grub and directly
>launching the windows as normal.
>Can anyone help?
>How can i get the grub to be shown before windows is showing?

Likely your laptop is set to use "Secure Boot". Debian Wheezy (and even
Jessie) does not support this. The easiest option is to disable "Secure
Boot" in your firmware menu. If you cannot or do not wish to then,
depending on your requirements, running Debian in a Virtual Machine may
be acceptable.



signature.asc
Description: Digital signature

Re: Need help fixing an unhandled irq

[Kynn Jones]

On Tue, Apr 21, 2015 at 10:03 PM, James  wrote:

> What kind of connection for the mouse?
> Does unplugging it and plugging it back in help?



Sorry, I should have covered those questions in my original post!

It's a USB2 mouse, and no, unplugging/re-plugging it back in does not help.

kj

Re: reading an empty directory after reboot is very slow

[Vincent Lefevre]

On 2015-04-21 12:47:14 -0500, David Wright wrote:
> Quoting Vincent Lefevre (vinc...@vinc17.net):
> > This mailbox is constantly open in a Mutt running in screen (in
> > read-only mode). I often read it, and I modify it from time to time,
> > either by adding new messages in the usual way, or by modifying some
> > header of existing messages with some tool of mine (in which case, I
> > restart Mutt to take the changes into account).
> 
> I guess I find it hard (not knowing what all these emails are) to get
> my head around needing an email-style random access to 145k emails in
> one folder.

I can then do any filtering I like to search for an old e-mail
instead of having to look at several folders individually.

> > When I wrote my tool, I thought that such a cached mapping would be
> > useless because the mailbox would have to be read by Mutt anyway.
> > So, there's still something I don't understand: after dropping the
> > caches, why is Mutt fast to read the mailbox (about 1 minute), but
> > not my tool (about 30 minutes)?
> 
> Because mutt caches, and its caches are persistent.
> The default location (not in the man page, I think) is
> ~/.mutt-cache/header-cache/
> for the headers, and its parent for the emails themselves.

No, I don't use caches (the header cache is not enabled and the
~/.mutt-cache directory doesn't exist).

> > > Have you considered running a local IMAP server to handle this (and
> > > any other) maildir?
> > 
> > There would be other problems. All the tools would have to talk
> > with this server... and for instance, mairix doesn't support IMAP.
> 
> Is this correct?
> http://www.gnu.org/software/emacs/manual/html_node/gnus/Setting-up-mairix.html

This seems to be something different (nnmairix), which is not in Debian.
For mairix:

 mairix is a program for indexing and searching locally stored email messages.
 mairix supports Maildir, MH folders, and mbox formats.

> But I don't understand why, if you're running mairix, you need to scan the
> emails yourself. Hasn't mairix done this already? (As well as mutt.)

Only once for indexing. This is persistent after reboots and not
used by Mutt at all.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150422090326.gd20...@xvii.vinc17.org

Re: reading an empty directory after reboot is very slow

[Vincent Lefevre]

On 2015-04-21 10:35:12 -0600, Bob Proulx wrote:
> Vincent Lefevre wrote:
> > So, there's still something I don't understand: after dropping the
> > caches, why is Mutt fast to read the mailbox (about 1 minute), but
> > not my tool (about 30 minutes)?
> 
> Are you using mutt's header_cache feature?  It keeps a cache of mail
> files off to the side.  It really improves Maildir performance.  I
> personally also have maildir_header_cache_verify=no set too.

No, I don't use it. This variable doesn't even exist with my compiled
version.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150422084059.gc20...@xvii.vinc17.org

Re: /etc/network/interfaces in jessie and systemd?

[Vincent Lefevre]

On 2015-04-21 17:27:46 +0200, Michael Biebl wrote:
> The ifup@.service is triggered by a udev rule and responsible to handle
> allow-hotplug interfaces.

I hope that this will remain always optional. For a laptop at least,
that's not the correct way to do.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150422082135.ga20...@xvii.vinc17.org

Re: reading an empty directory after reboot is very slow

[Vincent Lefevre]

On 2015-04-21 11:05:58 -0500, David Wright wrote:
> Quoting Vincent Lefevre (vinc...@vinc17.net):
> > On 2015-04-20 13:04:41 -0500, David Wright wrote:
> > > Quoting Vincent Lefevre (vinc...@vinc17.net):
> > > > But with the current solution (no automatic moving of an entry), you
> > > > can't miss an entry that hasn't been removed.
> [...]
> > > ...so if you happen to be reading the entry for file5 at the
> > > time I typed mv, you'll get the entry for file4 twice, under
> > > two different names. (Or the opposite.)
> > 
> > OK, so, if the rename(2) system call can reorder the entries (this is
> > not quite clear because one doesn't see the empty entries here),
> 
> No, and you wouldn't *normally* see them with readdir, I'd suppose.

But this matters for the implementation in the kernel.

> > then
> > there is already a problem with the file system. Getting an entry
> > twice under different names is not much a problem, IMHO, because one
> > can look at the inode number; there's a race condition, but at worst,
> > one can just miss a *new* inode (whose number has been reassigned).
> > Missing an existing entry is a problem.
> 
> ...easily demonstrated with
> 
> ~ $ for j in 1 2 3 4 5 6 ; do mkdir /tmp/testdir/file$j ; done
> ~ $ ls -lU /tmp/testdir
> total 24
> drwxr-x--- 2 david david 4096 Apr 21 10:58 file1
> drwxr-x--- 2 david david 4096 Apr 21 10:58 file4
> drwxr-x--- 2 david david 4096 Apr 21 10:58 file5
> drwxr-x--- 2 david david 4096 Apr 21 10:58 file6
> drwxr-x--- 2 david david 4096 Apr 21 10:58 file2
> drwxr-x--- 2 david david 4096 Apr 21 10:58 file3
> ~ $ mv -i /tmp/testdir/file3 
> /tmp/testdir/file3file3file3file3file3file3file3file3file3file3file3file3file3
> ~ $ ls -lU /tmp/testdir
> total 24
> drwxr-x--- 2 david david 4096 Apr 21 10:58 file1
> drwxr-x--- 2 david david 4096 Apr 21 10:58 file4
> drwxr-x--- 2 david david 4096 Apr 21 10:58 file5
> drwxr-x--- 2 david david 4096 Apr 21 10:58 
> file3file3file3file3file3file3file3file3file3file3file3file3file3
> drwxr-x--- 2 david david 4096 Apr 21 10:58 file6
> drwxr-x--- 2 david david 4096 Apr 21 10:58 file2
> ~ $ 
> 
> where file3 goes AWOL.

You haven't demonstrated anything. If you have before the mv:

0: file1
1: file4
2: file5
3: file6
4: file2
5: file3

and after the mv:

0: file1
1: file4
2: file5
3: [empty]
4: [empty]
5: file3file3file3file3file3file3file3file3file3file3file3file3file3
6: file6
7: file2

there's no problem. What actually needs to be done is a real test
using readdir.

Any idea of the algorithm to choose the directory entries? The fact
that the files are not ordered initially is unintuitive.

> > What do the backup systems do?
> 
> I don't know. Lock the directory and slurp it (if it's not too big),
> otherwise check the modification time before and after reading it,
> and reread it if necessary, maybe...

The modification time mustn't be used since it can be changed by some
tools, e.g. during unarchiving or decompressing. The ctime could be
OK, but re-reads can introduce endless loops for directories that are
constantly modified.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150422083747.gb20...@xvii.vinc17.org

Re: Installing open-vm-tools in Debian Wheezy

[Liam O'Toole]

On 2015-04-22, Eric Gamess  wrote:
> Hello all,
>
> I am trying to install open-vm-tools in Debian 7.8 i386.
> I tried:
>apt-get install open-vm-tools
>
>
> And I got an error message:
> Error!  Build of vmhgfs.ko failed for: 3.2.0-4-686-pae (i686)
> Consult the make.log in the build directory
> /var/lib/dkms/open-vm-tools/2012.05.21/build/ for more information.
> Setting up open-vm-tools (2:8.8.0+2012.05.21-724730-1+nmu2) ...
> FATAL: Module vmhgfs not found.
> FATAL: Module vmsync not found.
>
>
> Some web pages recommend to install "open-vm-source". But there is
> no such packet in Debian Wheezy.
>
> By the way, it seems that the problem is during the compilation
> of file:
> /var/lib/dkms/open-vm-tools/2012.05.21/build/vmhgfs/inode.c
>
> What should I do
> Thank you.
>
> Eric.
>
>

The open-vm-tools package recomends open-vm-dkms. The package
description for the latter is 'Source for VMware guest systems driver
(DKMS)'. It seems that that will give you the source, packaged to work
with DKMS.  Therefore the module(s) will automaticaly be recompiled on
kernel upgrade.

-- 

Liam



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnmjekuv.e0e.liam.p.otoole@dipsy.tubbynet

Re: How to bypass login screen in Jessie?

[Frédéric Marchal]

On Tuesday 21 April 2015 16:35:18, German wrote :
> hi. I'd like to bypass the login screen and boot straight to LXDE desktop.
> How do I accomplish this? I am the only user on this system. Thanks

It depends on the Display Manager started during boot. Some of the biggest 
players support autologin (kdm or gdm). Others don't (xdm).

The simplest display manager I know of with autologin is nodm.

I never tried to start LXDE but I use it to start OpenBox without login 
prompt. The user to autologin is defined in /etc/default/nodm (not sure about 
the exact file name as the system running it is currently powered off).

Frederic


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/201504220932.51623.frederic.marc...@wowtechnology.com