Re: FWIW: script vs. configurtion file

[saint]

Zenaan Harkness writes:
 > Scripting has its place, but from my extensive reading
 > of systemd docs and some of the old sysv startup scripts
 > (for postfix and various others over the years), give me
 > systemd unit files any day! Preference. Mine.

"De gustibus non disputandum est" (you can't argue about personal taste)

In the list of things I don't like of crapsystemd, the format
of the configuration files comes last and least :).

 > For games customization,

Games only? Whenever a user has to do repetitive tasks, giving a scripting
capability improves the user experience. And since you have this scripting
capability, handling configuration through that is a wise move.

Scripting makes a program extensible when you can't achieve extensibility
by composition with other programs.

And depending on which service a daemon does, extensibility may be
crucial or useless :).

-- 
 /\   ___Ubuntu: ancient
/___/\_|_|\_|__|___Gian Uberto Lauri_   African word
  //--\| | \|  |   Integralista GNUslamicomeaning "I can
\/ coltivatore diretto di software   not install
 già sistemista a tempo (altrui) perso...Debian"

Warning: gnome-config-daemon considered more dangerous than GOTO


--
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/21456.46228.200173.967...@mail.eng.it

Re: systemd log messages during boot (Re: I'm not a huge fan of systemd)

[Tom H]

On Wed, Jul 23, 2014 at 2:02 AM, Erwan David  wrote:
> On Wed, Jul 23, 2014 at 12:06:51AM CEST, Michael Biebl  
> said:
>> Am 22.07.2014 19:22, schrieb Erwan David:
>>> Le 22/07/2014 18:59, Michael Biebl a écrit :
 Am 22.07.2014 18:24, schrieb The Wanderer:

> As far as I can see, there is no way to get init-system log messages
> without also getting kernel log messages
 Of course there is.

 Might help if you actually tried it before commenting on it?

 The systemd.* specific flags override the global quiet flag. The

 So you can very well keep the quiet kernel command line argument and use

 systemd.show_status=true|false
 systemd.sysv_console=true|false
 systemd.log_level=...
 systemd.log_target=...

 etc. to control in a very fine grained manner, how the data is logged.
>>>
>>> It would be interesting if the default was not changed, ie. same
>>> behaviour when using the default configuration.
>>
>> The default wasn't changed, really.
>> It's simply that SysV init scripts are so horribly inconsistent and
>> interpret the "quiet" parameter differently. So we don't have a
>> consistent behaviour wrt to logging and output.
>
> The defauklt was changed in that nomessage at all, no sign of any
> progression is NOT the former behaviour.
>>
>> The example skeleton SysV init script /etc/init.d/skeleton, which is
>> supposed to be a base for newly written init scripts uses
>> /lib/init/init-d-script. If you take a look at that script, you'll see
>> that prefixes its log message with [ "$VERBOSE" != no ] && log_*_msg
>>
>> And surprise, VERBOSE is set to "no" by /lib/init/vars.sh if the kernel
>> command line contains "quiet".
>>
>> Thankfully, this is all fixed now with systemd, where you have a
>> consistent and central place to configure that.
>
> NO it ids NOT fixed,k because what imports is NOT the theory but the
> actual behaviour. The actual behaviour is changed, and the new one is
> more than disturbing.

The behavior of the boot messages hasn't changed for me and according
to the systemd man pages it shouldn't. So your setup must be
different.


--
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/CAOdo=sx-so_i4nat1k2vo8hjtntjqwka72eueakuhys1-vm...@mail.gmail.com

Re: /var partition seems locked or read only

[berenger . morel]

Le 24.07.2014 00:04, Pascal Hambourg a écrit :

Vincent Zweije a écrit :

On Wed, Jul 23, 2014 at 09:59:26AM -0700, der.hans wrote:

Do you have large open files that have been removed? The filesystem 
will
show those as free space, but until the proceses holding the files 
open

have been stopped the disk space has not been freed.


du (which uses the directory tree) would not show the space allocated 
to

deleted-but-not-yet-closed files as used, but df would.


Thanks to all who replied, but it was not a process problem, since I 
tried rebooting it (you like to play, or not, right?).



This looks most probable to me. Try this:


Inode exhaustion (df -i) looks more probable to me.


Nice, you point the problem, it seem:

# df -i
Sys. de fichiers Inœuds IUtil. ILibre IUti% Monté sur
/dev/sda3610800  46946 5638548% /
udev 506659376 5062831% /dev
tmpfs507294339 5069551% /run
tmpfs507294  2 5072921% /run/lock
tmpfs507294  2 5072921% /run/shm
/dev/sda2  1152286866   25% /boot
/dev/sda5  9568   1246   8322   14% /home
/dev/sda7243840 15 2438251% /tmp
/dev/sda6 13952  13952  0  100% /var

I guess that I need to delete files to have a temporary resolution of 
the problem, but how can I avoid it to come back?



--
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/e4e5f4c31fd195e6d1e7b61421f90...@neutralite.org

Re: /var partition seems locked or read only

[berenger . morel]

Le 23.07.2014 19:06, Eduardo M KALINOWSKI a écrit :

On Qua, 23 Jul 2014, berenger.morel wrote:
On a distant Debian testing/unstable, it seems that the /var  
partition can no longer be written: even "# touch /var/test" returns  
a message saying that there is no space on the drive, which is  
something that "# df -h" deny:


Check df -i also.


Thanks, that's the problem, my inode spool has exhausted.

Now, I have no idea about how can I fix this issue. May it be 
aptcacheng which is too greedy about inodes?



--
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/88e7c19cd0560749387ec59df6f7a...@neutralite.org

New 64bit Installation. Root partition too small--what to do?

[David Baron]

Yes, indeed. I previously complained about its partitioning with little 
capability to revise it! (I did not use LVM because it put everything in one 
big physical partition which I also did not like.)

So, want to install a more recent kernel? No room.

While I was able to bind /opt and /usr/local to folders on my /home partition 
(which is most all of the disk!), root obviously cannot be so bound. Must be 
available to boot. (No huge loss with no /opt or local available to start.)

So now, what can I do, short of moving everything to another disk (this is the 
one which had unwritable block which necessitated the new install!)??
Could I move /var like I did /opt, etc (probably a good idea) and move rootfs 
to there? Would know how to set it up in lilo but in grub?

Must have at least one fully working kernel around before trying any other and 
cannot fulfill this at present! :-(


-- 
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/2369404.rv3k4nAKTr@dovidhalevi

Re: testing-dedicated ML? ( was Re: End of hypocrisy ? )

[Bret Busby]

On 24/07/2014, Zenaan Harkness  wrote:
> On 7/24/14, Bret Busby  wrote:
>> On 24/07/2014, Zenaan Harkness  wrote:
>>> On 7/24/14, Bret Busby  wrote:
 On 21/07/2014, berenger.mo...@neutralite.org
  wrote:
> Le 21.07.2014 15:31, Slavko a écrit :
>> Ahoj,
>>
>> it seems, that there can good idea to provide separate ML for testing
>> users.
>
> I agree, since testing is not for normal users (well... theoretically
> at least), so we could imagine that different MLs for (beta-)testing
> and
> productive usage (questions about "how to do..." and stable related
> bugs
> would go there, I guess).
> Now, I have no idea about the complexity of maintaining a new ML.
> Maybe
> there are also problems because some issues can not clearly affect
> only
> one of both testing and stable?

 I would like to see a list for each of:
 experimental
 unstable
 testing
 stable (by version number, eg, at present, 7)
 oldstable (by version number, eg, at present, 6)
 obsolete (versions previous to oldstable)
 hybrid - combinations of the above, eg, where people mix stable and
 testing,
 etc

 I believe that it would be helpful, and, would provide for most
 scenario's, and, when a new release occurs (eg, for Debian 8), the
 archives get each moved into the lower level archive, so the oldstable
 archive goes into the obsolete, the stable archive goes into the
 oldstable, and the testing archive goes into the stabl;e achive.

 Or, the top three;
 experimental
 unstable
 testing
 then by version number;
 7
 6
 5
 4
 3.1
 3
>>>
>>> No no, that's really impractical - the applications man,
>>> the applications!
>>>
>>> We need a list for each package! You can't ruly home in
>>> on your questions of interest until you have dedicated
>>> lists for each package.
>>>
>>> Sometimes, those lists should have a repeater which
>>> copies each message to a corresponding upstream list
>>> (I'm thinking mutt for example, but I'm sure there's
>>> others).
>>>
>>> so mutt-debian-users@.., postgresql-debian-users@... etc.
>>
>> Well,   there are application lists.
>>
>> PostgreSQL has its own lists, MySQL has its own lists, Fetchmail has
>> its own list, Posfix has its own list, Procmail has its own list,
>> alpine has its own list, GRAMPS has its own list, GnuCash has its own
>> list, as mentioned in another thread (the one about iceape), Seamonkey
>> has its own list, and, as the King (as played by Yul Brynner) said,
>> "etcetera, etcetera, etcetera".
>
> There's a slashdot saying appropriate just here ...
> not quite sure what that is, it's ...
> going over my head right now.
>
> ;)
>
>

I do not understand the last posting above.


-- 
Bret Busby
Armadale
West Australia
..

"So once you do know what the question actually is,
 you'll know what the answer means."
- Deep Thought,
 Chapter 28 of Book 1 of
 "The Hitchhiker's Guide to the Galaxy:
 A Trilogy In Four Parts",
 written by Douglas Adams,
 published by Pan Books, 1992




--
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/CACX6j8NpeRX0=v7mcmt-vbfwiyl7e0hxduohn8gso-vq8eq...@mail.gmail.com

Re: New 64bit Installation. Root partition too small--what to do?

[Darac Marjal]

On Thu, Jul 24, 2014 at 12:16:32PM +0300, David Baron wrote:
> Yes, indeed. I previously complained about its partitioning with little 
> capability to revise it! (I did not use LVM because it put everything in one 
> big physical partition which I also did not like.)
> 
> So, want to install a more recent kernel? No room.
> 
> While I was able to bind /opt and /usr/local to folders on my /home partition 
> (which is most all of the disk!), root obviously cannot be so bound. Must be 
> available to boot. (No huge loss with no /opt or local available to start.)
> 
> So now, what can I do, short of moving everything to another disk (this is 
> the 
> one which had unwritable block which necessitated the new install!)??
> Could I move /var like I did /opt, etc (probably a good idea) and move rootfs 
> to there? Would know how to set it up in lilo but in grub?
> 
> Must have at least one fully working kernel around before trying any other 
> and 
> cannot fulfill this at present! :-(

Download, burn and boot a copy of GParted-Live[1], which is a live-cd for 
GParted,
the partition manager. Use that to shrink your, say, home partition and
grow your root partition.

Another alternative, if you need minimal downtime and you can unmount
hour home partition is to shrink that, create a second root partition
and copy everything onto that, adjust grub to boot the new root
partition and then delete the old one and grow your home back into the
recovered space. In other words:

 [--- root ---] [- home ---]
 [--- root ---] [- home ]
 [--- root ---] [- home ] [--- new root ---]
 *** Reboot ***
[- home ] [--- new root ---]
 [- home ---] [--- new root ---]


[1]: http://sourceforge.net/projects/gparted/files/gparted-live-stable/

> 
> 
> -- 
> 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/2369404.rv3k4nAKTr@dovidhalevi
> 


signature.asc
Description: Digital signature

Re: Special hotkeys for Openbox and LXDE users

[Curt]

On 2014-07-24, Zenaan Harkness  wrote:
>
> Sometimes I use right hand, but mostly left hand. It did take a week
> or two to get really comfortable both sides.
>

Yes the OP assumes right-handedness, doesn't he? My wife is both
gauchiste and gauchère; sharing a mouse was l'enfer (because of the
cable and my right-handedness), until we got a wireless one for her
laptop.

I suppose someone will pipe up to say that more people are right-handed
than left-handed, and we must seek to satisfy the majority in all
things. Of course, in the past (that murky sea), it was often the case
here and there for the authorities to enforce right-handedness in
left-handed people.  As a school girl my wife sat at a desk with the ink
well on the right; she'd dip her plume and strew cryptic hieroglyphs
over her copy as she brought the writing instrument over to her good
side. As she spent a few years interned with the nuns, I think those
sour biddies would whack her with a ruler from time to time.  Praise the Lord
and full speed ahead.

By the way, that's ambidextrous with an x, like the one in dexterity.


-- 
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/slrnlt1l4h.22f.cu...@einstein.electron.org

Re: systemd log messages during boot (Re: I'm not a huge fan of systemd)

[Erwan David]

On Thu, Jul 24, 2014 at 09:42:52AM CEST, Tom H  said:
> On Wed, Jul 23, 2014 at 2:02 AM, Erwan David  wrote:
> > On Wed, Jul 23, 2014 at 12:06:51AM CEST, Michael Biebl  
> > said:
> >> Am 22.07.2014 19:22, schrieb Erwan David:
> >>> Le 22/07/2014 18:59, Michael Biebl a écrit :
>  Am 22.07.2014 18:24, schrieb The Wanderer:
> 
> > As far as I can see, there is no way to get init-system log messages
> > without also getting kernel log messages
>  Of course there is.
> 
>  Might help if you actually tried it before commenting on it?
> 
>  The systemd.* specific flags override the global quiet flag. The
> 
>  So you can very well keep the quiet kernel command line argument and use
> 
>  systemd.show_status=true|false
>  systemd.sysv_console=true|false
>  systemd.log_level=...
>  systemd.log_target=...
> 
>  etc. to control in a very fine grained manner, how the data is logged.
> >>>
> >>> It would be interesting if the default was not changed, ie. same
> >>> behaviour when using the default configuration.
> >>
> >> The default wasn't changed, really.
> >> It's simply that SysV init scripts are so horribly inconsistent and
> >> interpret the "quiet" parameter differently. So we don't have a
> >> consistent behaviour wrt to logging and output.
> >
> > The defauklt was changed in that nomessage at all, no sign of any
> > progression is NOT the former behaviour.
> >>
> >> The example skeleton SysV init script /etc/init.d/skeleton, which is
> >> supposed to be a base for newly written init scripts uses
> >> /lib/init/init-d-script. If you take a look at that script, you'll see
> >> that prefixes its log message with [ "$VERBOSE" != no ] && log_*_msg
> >>
> >> And surprise, VERBOSE is set to "no" by /lib/init/vars.sh if the kernel
> >> command line contains "quiet".
> >>
> >> Thankfully, this is all fixed now with systemd, where you have a
> >> consistent and central place to configure that.
> >
> > NO it ids NOT fixed,k because what imports is NOT the theory but the
> > actual behaviour. The actual behaviour is changed, and the new one is
> > more than disturbing.
> 
> The behavior of the boot messages hasn't changed for me and according
> to the systemd man pages it shouldn't. So your setup must be
> different.

I did not change anything, I had messages from all starting daemons, I
have no more if I do not add systelmd.show_status=true in an unrelated
configuration file (/etc/default/grub)

That's all that I see.


-- 
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/20140724094128.ga7...@rail.eu.org

this is a test mail, please ignore.

[Dc G]

hey, just for testing.

-- 


Never Give Up!

Re: /var partition seems locked or read only

[berenger . morel]

Le 23.07.2014 18:38, berenger.mo...@neutralite.org a écrit :

Hello.

On a distant Debian testing/unstable, it seems that the /var
partition can no longer be written: even "# touch /var/test" returns 
a
message saying that there is no space on the drive, which is 
something

that "# df -h" deny:

# df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
/dev/sda3  9,1G954M  7,7G  11% /
udev10M   0   10M   0% /dev
tmpfs  397M384K  396M   1% /run
tmpfs  5,0M   0  5,0M   0% /run/lock
tmpfs  2,7G   0  2,7G   0% /run/shm
/dev/sda2  4,4G 27M  4,4G   1% /boot
/dev/sda5   38G 22G   16G  58% /home
/dev/sda7  447M 17K  423M   1% /tmp
/dev/sda6   14G2,7G  8,7G  24% /var

So, I am guessing that something is locking the partition, but I have
no idea about *what* could do that. I tried disabling as many daemons
that I can, so that "# service --status-all |grep '+'" returns this:

# service --status-all |grep '+'
 [ ? ]  bootmisc.sh
 [ ? ]  checkfs.sh
 [ ? ]  checkroot-bootclean.sh
 [ ? ]  hwclock.sh
 [ ? ]  ircd-irc2
 [ ? ]  killprocs
 [ ? ]  kmod
 [ ? ]  mountall-bootclean.sh
 [ ? ]  mountall.sh
 [ ? ]  mountdevsubfs.sh
 [ ? ]  mountkernfs.sh
 [ ? ]  mountnfs-bootclean.sh
 [ ? ]  mountnfs.sh
 [ ? ]  networking
 [ ? ]  rc.local
 [ + ]  rsyslog
 [ ? ]  sendsigs
 [ + ]  ssh
 [ + ]  udev
 [ ? ]  udev-finish
 [ ? ]  umountfs
 [ ? ]  umountnfs.sh
 [ ? ]  umountroot

but it changes nothing. Any idea/supposition/whatever?

Some other informations which might help:
The problem started with a network failure, which avoided aptitude to
download, and so update, some packages, and now some packages are
broken (but dpkg was not concerned by the update). If I can still
trust /var/lib/dpkg/status, it seems that the most important breakage
may come from libasan0 (Status: install reinstreq half-configured)
which is needed by libgcc-4.8-dev, itself needed by linux-headers, so
I do not think it is the source of the problem, but... maybe?

According to /etc/mtab, the var partition is mounted as rw:
"/dev/sda6 /var ext4 rw,nodev,noatime,data=ordered 0 0".


Thanks to people which have replied, it appears that the problem is the 
inode's exhaustion.
I have identified with lot of "find  -name '*'" that 
the problem comes from the cache, and especially from apt-cacher-ng, but 
I think I also made an error when I made the partitions: it was probably 
a wrong choice to choose "big files" inode repartition, that I used 
because I fought that it would preserve some disk space (the 
installation of this machine was on a 80GB only hard disk, so I tried to 
optimize --early optimization caught me anew, it seems-- the space, 
because lot of things to run on it).


So, I wonder if there is a way to fix this inode's size repartition? In 
a more general way, if people have some advices about that kind of 
issues (choosing the right cluster and partitions size, the right 
partition format, etc depending on the planned usage)?
I know, those questions (and the error I supposed I made) may seem 
trivial for real administrators, but... I'm a simple programmer, not an 
admin.



--
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/e89cf914024690bae94b4fdd1e816...@neutralite.org

Re: missing LSB tags and overrides

[Tony van der Hoff]

On 23/07/14 15:24, Darac Marjal wrote:
> On Wed, Jul 23, 2014 at 09:41:08AM +0200, Tony van der Hoff wrote:
>> Any suggestions on how to fix this please?
>>
>>
>> insserv: warning: script 'K01kerneld' missing LSB tags and overrides
>> insserv: warning: script 'K01apache' missing LSB tags and overrides
>> insserv: warning: script 'S15modutils' missing LSB tags and overrides
>> insserv: warning: script 'S15libdevmapper1.02' missing LSB tags and
>> overrides
>> insserv: warning: script 'S15xfree86-common' missing LSB tags and overrides
>> insserv: warning: script 'xfree86-common' missing LSB tags and overrides
>> insserv: warning: script 'libdevmapper1.02' missing LSB tags and overrides
>> insserv: warning: script 'modutils' missing LSB tags and overrides
>> insserv: warning: script 'iptables' missing LSB tags and overrides
>> insserv: warning: script 'kerneld' missing LSB tags and overrides
>> insserv: warning: script 'apache' missing LSB tags and overrides
> 
> Step 1. Purge unconfigured packages providing init scripts. That is,
> init scripts are considers conffiles so removing the package doesn't
> remove the file. Because the package is removed, it doesn't get updates
> to fix problems such as above.
> 
> Step 2. If you have any init scripts that you developed yourself, add
> proper headers[1] to the script.
> 
> Step 3. If you have any init scripts that are provided by a third party,
> add the proper headers to a file in /etc/insserv/overrides. The filename
> must match that of the init script (not the symlinks thereto).
> 

Thanks for all the replies, of which this one seems the most comprehensive.

I have no 3rd party scripts, nor do I have any home-brew scripts.

>From the warning messages, I'll assume that the packages to purge would
be xfree86-common, libdevmapper1.02, iptables, kerneld, and apache. Of
those only iptables appears in the current wheezy list.

So:
root@shell2:/etc# apt-get -s purge xfree86-common, libdevmapper1.02,
iptables, kerneld, apache
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package 'apache' is not installed, so not removed
E: Unable to locate package xfree86-common,
E: Unable to locate package libdevmapper1.02,
E: Couldn't find any package by regex 'libdevmapper1.02,'
E: Unable to locate package iptables,
E: Unable to locate package kerneld,


I presume I could just delete those scripts.

Is that correct?


-- 
Tony van der Hoff  | mailto:t...@vanderhoff.org
Ariège, France |


-- 
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/53d0e106.4040...@vanderhoff.org

inserting kernel modules on startup

[Gary Dale]

After the latest round of upgrades in Jessie, I rebooted. That's when 
the problems started. I'm having problems getting the 3.14 kernel to 
boot, so I'm booting from 3.13. However, that's not the big issue.


The really annoying problem is that I have to boot to the command 
prompt, insmod radeon, then exit back to a regular boot in order to get 
the radeon module loaded.


Radeon is listed in /etc/modules.conf - has been for years. However the 
module isn't being loaded anymore. The Debian wiki, admin docs and other 
documentation on kernel modules in Debian all refer to the 
update-modules program which no longer seems to be around.


How do I get kernel modules to automatically load on startup in Jessie?


--
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/53d0e2fb.30...@torfree.net

no display manager for 3 days

[Alan Simpson-Vlach]

Ever since a dist-upgrade that installed systemd and removed sysvinit-core, I 
have been unable to get a display manager.
I have tried slim, lightdm, and even installed gdm3.  Nothing works.

# /etc/init.d/slim/start

gives no error messages, but

# systemctl status slim.service

tells me that slim exited with status=1

The pertinent line appears to be

/usr/bin/X11/X: symbol lookup error: 
/usr/lib/xorg/modules/extensions/libglx.so: undefined symbol: LoadExtension

which is similar to what happens if I try xinit directly.

Trying lightdm I get 

lightdm.service start request repeated too quickly, refusing to start.

I think this is a systemd problem, but maybe it's a video driver problem?
I'm using the proprietary nvidia driver, which has been recompiled multiple 
times now.
Help, please.  I'd kinda like to have a working X11 again.

Thanks.


--
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/ec84b2ef--41e0-b681-9a93e2b5e...@laurelschool.org

Re: missing LSB tags and overrides

[Darac Marjal]

On Thu, Jul 24, 2014 at 12:33:42PM +0200, Tony van der Hoff wrote:
> On 23/07/14 15:24, Darac Marjal wrote:
> > On Wed, Jul 23, 2014 at 09:41:08AM +0200, Tony van der Hoff wrote:
> >> Any suggestions on how to fix this please?
> >>
> >>
> >> insserv: warning: script 'K01kerneld' missing LSB tags and overrides
> >> insserv: warning: script 'K01apache' missing LSB tags and overrides
> >> insserv: warning: script 'S15modutils' missing LSB tags and overrides
> >> insserv: warning: script 'S15libdevmapper1.02' missing LSB tags and
> >> overrides
> >> insserv: warning: script 'S15xfree86-common' missing LSB tags and overrides
> >> insserv: warning: script 'xfree86-common' missing LSB tags and overrides
> >> insserv: warning: script 'libdevmapper1.02' missing LSB tags and overrides
> >> insserv: warning: script 'modutils' missing LSB tags and overrides
> >> insserv: warning: script 'iptables' missing LSB tags and overrides
> >> insserv: warning: script 'kerneld' missing LSB tags and overrides
> >> insserv: warning: script 'apache' missing LSB tags and overrides
> > 
> > Step 1. Purge unconfigured packages providing init scripts. That is,
> > init scripts are considers conffiles so removing the package doesn't
> > remove the file. Because the package is removed, it doesn't get updates
> > to fix problems such as above.
> > 
> > Step 2. If you have any init scripts that you developed yourself, add
> > proper headers[1] to the script.
> > 
> > Step 3. If you have any init scripts that are provided by a third party,
> > add the proper headers to a file in /etc/insserv/overrides. The filename
> > must match that of the init script (not the symlinks thereto).
> > 
> 
> Thanks for all the replies, of which this one seems the most comprehensive.
> 
> I have no 3rd party scripts, nor do I have any home-brew scripts.
> 
> >From the warning messages, I'll assume that the packages to purge would
> be xfree86-common, libdevmapper1.02, iptables, kerneld, and apache. Of
> those only iptables appears in the current wheezy list.
> 
> So:
> root@shell2:/etc# apt-get -s purge xfree86-common, libdevmapper1.02,
> iptables, kerneld, apache
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Package 'apache' is not installed, so not removed
> E: Unable to locate package xfree86-common,
> E: Unable to locate package libdevmapper1.02,
> E: Couldn't find any package by regex 'libdevmapper1.02,'
> E: Unable to locate package iptables,
> E: Unable to locate package kerneld,

Try "dpkg -l | grep '^rc'" to list the packages that you have which are
removed, but not purged. If that doesn't help, then yes, you should be
fine to just delete them.

> 
> 
> I presume I could just delete those scripts.
> 
> Is that correct?
> 
> 
> -- 
> Tony van der Hoff  | mailto:t...@vanderhoff.org
> Ariège, France |
> 
> 
> -- 
> 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/53d0e106.4040...@vanderhoff.org
> 


signature.asc
Description: Digital signature

systemd waisted 5 hours of my work time today

[Johann Spies]

This morning my work laptop would not boot.  I could not even get to single
user mode initially and when I got  as far as that I could not type
anything on the terminal.  I suspect some upgrade yesterday caused it.

In the end I had to search for a windows user who could write me a
debian-live cd.

Using this, I could, after using some hints shown in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746358 get my system to
boot (taking about 10 minutes do do so) and just as I started to work it
rebooted spontaneously.

In the end after several experiments, I removed systemd and as a result a
lot of other packages, reinstalled sysvinit and it booted normally again
and now I can work.

I know systemd is not an option any more, but if this is the way it is
going to waste my time, I will have to look at a reinstallation of my
system  and then use something that is less buggy than Debian Testing/Sid.

I have heard from a colleague of mine that on Mandriva and other systems he
has used systemd without such problems.

Regards
Johann

-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)

Re: systemd waisted 5 hours of my work time today

[Tom Furie]

On Thu, Jul 24, 2014 at 01:12:32PM +0200, Johann Spies wrote:

> I know systemd is not an option any more, but if this is the way it is
> going to waste my time, I will have to look at a reinstallation of my
> system  and then use something that is less buggy than Debian Testing/Sid.

You are, of course, aware that testing and unstable are test platforms
where breakage is to be expected? They shouldn't be used for anything
"mission critical", that's what stable is for.

Cheers,
Tom

-- 
:-) your own self.
-- Larry Wall in <199709261754.kaa23...@wall.org>


signature.asc
Description: Digital signature

Re: New 64bit Installation. Root partition too small--what to do?

[David Baron]

On Thursday 24 July 2014 11:16:47 debian-user-digest-requ...@lists.debian.org 
wrote:
> > Yes, indeed. I previously complained about its partitioning with little
> > capability to revise it! (I did not use LVM because it put everything in 
one
> > big physical partition which I also did not like.)
> >
> > So, want to install a more recent kernel? No room.
> >
> > While I was able to bind /opt and /usr/local to folders on my /home  
partition
> > (which is most all of the disk!), root obviously cannot be so bound. Must
>be available to boot. (No huge loss with no /opt or local available to start
> >
> > So now, what can I do, short of moving everything to another disk (this is 
the
> > one which had unwritable block which necessitated the new install!)??
> > Could I move /var like I did /opt, etc (probably a good idea) and move  
rootfs
> > to there? Would know how to set it up in lilo but in grub?
> >
> > Must have at least one fully working kernel around before trying any other 
and cannot fulfill this at present!
>>
> Download, burn and boot a copy of GParted-Live[1], which is a live-cd for G=
> Parted,
> the partition manager. Use that to shrink your, say, home partition and
> grow your root partition.
> 
> Another alternative, if you need minimal downtime and you can unmount
> hour home partition is to shrink that, create a second root partition
> and copy everything onto that, adjust grub to boot the new root
> partition and then delete the old one and grow your home back into the
> recovered space. In other words:
> 
>  [--- root ---] [- home ---]
>  [--- root ---] [- home ]
>  [--- root ---] [- home ] [--- new root ---]
>  *** Reboot ***
> [- home ] [--- new root ---]
>  [- home ---] [--- new root ---]

Had forgotten about that. Used "partition-magic" in windows for years.

Have the kde partition manager and gparted. Using to repartition and format 
the old disks for use as backups. One should backup first--how safe are these 
utilities (which would be run from the DVD or G-parted-live -- never had any 
problems with the old paid partition-magic, no backups back then either).

Anyway, could not format any primary partitions but have logicals available 
for backups.

I would shrink, move start of  home, then move and expand everything else in 
current order, keeping old root, just bigger. This would be OK, safe?


-- 
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/2517135.78KgTiRGBY@dovidhalevi

Re: systemd waisted 5 hours of my work time today

[Johann Spies]

On 24 July 2014 14:00, Tom Furie  wrote:

> On Thu, Jul 24, 2014 at 01:12:32PM +0200, Johann Spies wrote:
>
> > I know systemd is not an option any more, but if this is the way it is
> > going to waste my time, I will have to look at a reinstallation of my
> > system  and then use something that is less buggy than Debian
> Testing/Sid.
>
> You are, of course, aware that testing and unstable are test platforms
> where breakage is to be expected? They shouldn't be used for anything
> "mission critical", that's what stable is for.
>

I am aware of that and has been using testing/sid for about 13 years now.
I have never experienced anything like this.

Regards
Johann

-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)

Re: missing LSB tags and overrides

[Tony van der Hoff]

On 24/07/14 13:16, Darac Marjal wrote:

> Try "dpkg -l | grep '^rc'" to list the packages that you have which are
> removed, but not purged. If that doesn't help, then yes, you should be
> fine to just delete them.
> 
OK, Thanks very much. Lots of hits:

root@vanderhoff:~# dpkg -l | grep '^rc'
rc  apache1.3.34-4.1+etch1
i386 versatile, high-performance HTTP server
rc  apache-common 1.3.34-4.1+etch1
i386 support files for all Apache webservers
rc  cyrus-admin-2.2   2.2.13-14+lenny3
all  Cyrus mail system (administration tools)
rc  cyrus-common-2.2  2.2.13-14+lenny3
i386 Cyrus mail system (common files)
rc  cyrus-imapd-2.2   2.2.13-14+lenny3
i386 Cyrus mail system (IMAP support)
rc  cyrus-pop3d-2.2   2.2.13-14+lenny3
i386 Cyrus mail system (POP3 support)
rc  defoma0.11.11
all  Debian Font Manager -- automatic font configuration framework
rc  dovecot-common1:1.0.15-2.3+lenny1
i386 secure mail server that supports mbox and maildir mailboxes
rc  dovecot-imapd 1:1.0.15-2.3+lenny1
i386 secure IMAP server that supports mbox and maildir mailboxes


and many more.

How do I join this output into the purge command to save typing in each
package name?

-- 
Tony van der Hoff  | mailto:t...@vanderhoff.org
Ariège, France |


-- 
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/53d0ff5a.6030...@vanderhoff.org

Re: no display manager for 3 days

[Steve Litt]

On Thu, 24 Jul 2014 10:37:34 +
Alan Simpson-Vlach  wrote:

> Ever since a dist-upgrade that installed systemd and removed
> sysvinit-core, I have been unable to get a display manager. I have
> tried slim, lightdm, and even installed gdm3.  Nothing works.
> 
> # /etc/init.d/slim/start
> 
> gives no error messages, but
> 
> # systemctl status slim.service
> 
> tells me that slim exited with status=1
> 
> The pertinent line appears to be
> 
> /usr/bin/X11/X: symbol lookup
> error: /usr/lib/xorg/modules/extensions/libglx.so: undefined symbol:
> LoadExtension
> 
> which is similar to what happens if I try xinit directly.
> 
> Trying lightdm I get 
> 
> lightdm.service start request repeated too quickly, refusing to start.
> 
> I think this is a systemd problem, but maybe it's a video driver
> problem? I'm using the proprietary nvidia driver, which has been
> recompiled multiple times now. Help, please.  I'd kinda like to have
> a working X11 again.

Hi Alan,

I can't help you with the root cause, because I know less about
systemd than I know of the plant life at the North Pole, but if it
were me, for the time being, I'd just do the workaround and use
startx. You put your window manager in .xinitrc, and then from the
command prompt, as a normal user, type "startx".

Here's my .xinitrc for Openbox:

 
exec /usr/bin/openbox-session


Here's a little humor to make you feel a little better: One of the
reasons I transitioned my daily driver desktop from Ubuntu to Debian is
so I would never have to use lightdm (or any of the other *dm's)
again. :-)

I'd imagine pretty soon your problem will fix itself on an update, and
you can go back to lightdm. But in the meantime, you can still do X.

HTH,

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


-- 
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/20140724085049.22735...@mydesq2.domain.cxm

Re: inserting kernel modules on startup

[Michael Biebl]

Am 24.07.2014 12:42, schrieb Gary Dale:
> After the latest round of upgrades in Jessie, I rebooted. That's when
> the problems started. I'm having problems getting the 3.14 kernel to
> boot, so I'm booting from 3.13. However, that's not the big issue.
> 
> The really annoying problem is that I have to boot to the command
> prompt, insmod radeon, then exit back to a regular boot in order to get
> the radeon module loaded.
> 
> Radeon is listed in /etc/modules.conf - has been for years. However the

Can you post your modules.conf, please


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

Re: no display manager for 3 days

[Brian]

On Thu 24 Jul 2014 at 10:37:34 +, Alan Simpson-Vlach wrote:

> Ever since a dist-upgrade that installed systemd and removed
> sysvinit-core, I have been unable to get a display manager.

The dist-upgrade would have more than this. You are using testing?

> I have tried slim, lightdm, and even installed gdm3.  Nothing works.
> 
> # /etc/init.d/slim/start
> 
> gives no error messages, but
> 
> # systemctl status slim.service
> 
> tells me that slim exited with status=1
> 
> The pertinent line appears to be
> 
> /usr/bin/X11/X: symbol lookup error: 
> /usr/lib/xorg/modules/extensions/libglx.so: undefined symbol: LoadExtension
> 
> which is similar to what happens if I try xinit directly.
> 
> Trying lightdm I get 
> 
> lightdm.service start request repeated too quickly, refusing to start.
> 
> I think this is a systemd problem, but maybe it's a video driver problem?
> I'm using the proprietary nvidia driver, which has been recompiled multiple 
> times now.
> Help, please.  I'd kinda like to have a working X11 again.

If xinit or startx will not bring up X it seems more like a video
problem to me. How do feel about using the nouveau driver if you cannot
fix the proprietry one?


-- 
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/24072014133859.de42aeeef...@desktop.copernicus.demon.co.uk

Re: systemd waisted 5 hours of my work time today

[Tony van der Hoff]

On 24/07/14 14:24, Johann Spies wrote:
> On 24 July 2014 14:00, Tom Furie  > wrote:
> 
> On Thu, Jul 24, 2014 at 01:12:32PM +0200, Johann Spies wrote:
> 
> > I know systemd is not an option any more, but if this is the way it is
> > going to waste my time, I will have to look at a reinstallation of my
> > system  and then use something that is less buggy than Debian
> Testing/Sid.
> 
> You are, of course, aware that testing and unstable are test platforms
> where breakage is to be expected? They shouldn't be used for anything
> "mission critical", that's what stable is for.
> 
> 
> I am aware of that and has been using testing/sid for about 13 years
> now.  I have never experienced anything like this.
> 

Well, neither have I :)
But then I use stable in order to avoid such occurrences.
Your luck had to run out sometime...

-- 
Tony van der Hoff  | mailto:t...@vanderhoff.org
Ariège, France |


-- 
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/53d10060.5070...@vanderhoff.org

Re: no display manager for 3 days

[Michael Biebl]

Am 24.07.2014 12:37, schrieb Alan Simpson-Vlach:
> Ever since a dist-upgrade that installed systemd and removed sysvinit-core, I 
> have been unable to get a display manager.
> I have tried slim, lightdm, and even installed gdm3.  Nothing works.
> 
> # /etc/init.d/slim/start
> 
> gives no error messages, but
> 
> # systemctl status slim.service
> 
> tells me that slim exited with status=1
> 
> The pertinent line appears to be
> 
> /usr/bin/X11/X: symbol lookup error: 
> /usr/lib/xorg/modules/extensions/libglx.so: undefined symbol: LoadExtension
> 
> which is similar to what happens if I try xinit directly.
> 
> Trying lightdm I get 
> 
> lightdm.service start request repeated too quickly, refusing to start.
> 
> I think this is a systemd problem, but maybe it's a video driver problem?

No, that doesn't look like a systemd problem.

It looks like your GLX installation is broken, so X fails to start.

Are you using a binary driver like NVIDIA?


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

Re: no display manager for 3 days

[Brian]

On Thu 24 Jul 2014 at 08:50:49 -0400, Steve Litt wrote:

> I can't help you with the root cause, because I know less about
> systemd than I know of the plant life at the North Pole, but if it
> were me, for the time being, I'd just do the workaround and use
> startx. You put your window manager in .xinitrc, and then from the
> command prompt, as a normal user, type "startx".

It is much wiser to use ~/.xsession on Debian.


-- 
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/24072014140330.c3fc49562...@desktop.copernicus.demon.co.uk

Re: New 64bit Installation. Root partition too small--what to do?

[Brian]

On Thu 24 Jul 2014 at 10:26:30 +0100, Darac Marjal wrote:

> Download, burn and boot a copy of GParted-Live[1], which is a live-cd for 
> GParted,
> the partition manager. Use that to shrink your, say, home partition and
> grow your root partition.

A small point, which may be useful for those without blank CDs or who
wish tp save them for something else: the GParted-Live image is an
isohybrid so can be put on a USB stick with dd or cat.


-- 
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/24072014141209.6e33a424d...@desktop.copernicus.demon.co.uk

Re: systemd waisted 5 hours of my work time today

[Slavko]

Ahoj,

Dňa Thu, 24 Jul 2014 13:00:24 +0100 Tom Furie 
napísal:

> On Thu, Jul 24, 2014 at 01:12:32PM +0200, Johann Spies wrote:
> 
> > I know systemd is not an option any more, but if this is the way it
> > is going to waste my time, I will have to look at a reinstallation
> > of my system  and then use something that is less buggy than Debian
> > Testing/Sid.
> 
> You are, of course, aware that testing and unstable are test platforms
> where breakage is to be expected? They shouldn't be used for anything
> "mission critical", that's what stable is for.

No, i will not comply with this.

The testing must be in state, where it must to boot (except some boot
options tweaks) by default. I think, that nobody here will complain if
some of software/services on testing doesn't work, but computer must to
boot!

If it will not boot, then it is not appropriate to "mission critical"
only, but then it is not appropriate to nothing. And because the NFS is
installed by default, then it can be considered as "is used" by
default too, then system doesn't boot for default and IMO this is a
problem.

BTW, i am curious - if systemd maintainers will allow to set the higher
severity for some bug and if then it will be removed from testing
after time threshold) :P

regards

-- 
Slavko
http://slavino.sk


signature.asc
Description: PGP signature

Re: /var partition seems locked or read only

[Eduardo M KALINOWSKI]

On Qui, 24 Jul 2014, berenger.morel wrote:
So, I wonder if there is a way to fix this inode's size repartition?  
In a more general way, if people have some advices about that kind  
of issues (choosing the right cluster and partitions size, the right  
partition format, etc depending on the planned usage)?
I know, those questions (and the error I supposed I made) may seem  
trivial for real administrators, but... I'm a simple programmer, not  
an admin.


It's not possible to change the number of inodes after the filesystem  
has been created. You'll have to backup and create a new filesystem.


As far as I remember, I've always accepted the defaults for number of  
inodes, and I've never got even close to exhausting inodes.


--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br



--
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/20140724131925.horde.fxvjmuwuj9vnvfs6s3h5...@mail.kalinowski.com.br

Re: systemd waisted 5 hours of my work time today

[Brian]

On Thu 24 Jul 2014 at 14:24:36 +0200, Johann Spies wrote:

> On 24 July 2014 14:00, Tom Furie  wrote:
> 
> I am aware of that and has been using testing/sid for about 13 years now.
> I have never experienced anything like this.

You are now. :)

Look on the bright side; the BTS came to the rescue.


-- 
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/24072014140959.36861967e...@desktop.copernicus.demon.co.uk

Re: Lost high res desktop settings on vbox upgrade to 4.3.14

[Klaus]

On 23/07/14 22:04, Harry Putnam wrote:
> Andreas Rönnquist  writes:
> 
>>> I upgraded vbox from 4.3.10 to 4.3 14.  Now the best screen res I can
>>> get in 1024 x 768.   When it was something like 1500 x .  Not sure
>>> of exact setting but desktop was much larger when I logged in before
>>> this upgrade.
>>>
>>
>> An ISO with guest additions is linked in the final post here:
>>
>> https://forums.virtualbox.org/viewtopic.php?f=3&t=62629
>>
>> That solved the problem(s) for me.
> 
> Thanks for the clear input.
> 
> Downloaded and mounted and installed from that iso.
> 
> However, after a restart I still have no res choices other than
> 1024x768.
> 
> Maybe this is the reason:
> 
> When I do the install, I get a warning that the header files for my
> running kernel were not found.
> 
> ASIDE showing installed kernel and installed header pkgs:
>   NOTE: uname -r 
> 3.14-1-486
> 
> aptitude search headers |grep ^i
> 
>   i   linux-headers-3.14-1-486- Header files for Linux 3.14-1-486 
> 
>   i A linux-headers-3.14-1-686-pae- Header files for Linux 3.14-1-686-pae 
> 
>   i   linux-headers-3.14-1-all-i386   - All header files for Linux 3.14 
> (meta-pack
>   i A linux-headers-3.14-1-amd64  - Header files for Linux 3.14-1-amd64   
> 
>   i A linux-headers-3.14-1-common - Common header files for Linux 3.14-1  
> 
>   i A linux-headers-3.14-1-common-rt  - Common header files for Linux 
> 3.14-1-rt   
>   i A linux-headers-3.14-1-rt-686-pae - Header files for Linux 
> 3.14-1-rt-686-pae  
> 
> (surely one of those installed pkgs has to be the right headers..You'd
> think the very first one is itso why are they not found...)
> 
> The next steps are building the modules and near as I can tell it
> succeeds:
> 
> here is the action: 
> 
> --- --- ---=--- --- --- 
>  NOTE:
>   Since I have already installed the iso you'll notice it remove that
>   pkg and then re-installs it.
> 
>   There is some commentary about xorg driver not being installed that
>   might also be why I'm not getting the result you did.
> 
>   There seems to be nothing mentioned to indicate any modules failed
>   to build so perhaps the bit about the X.org drivers not being
>   installed is the main culprit?
> ---   ---   ---=---   ---   --- 
> 
>   (I've marked out the pertinent parts with asterisks).
> 
> root # sh  VBoxLinuxAdditions.run 
> 
> Verifying archive integrity... All good.
> Uncompressing VirtualBox 4.3.15 Guest Additions for Linux
> VirtualBox Guest Additions installer
> Removing installed version 4.3.15 of VirtualBox Guest Additions...
> Copying additional installer modules ...
> Installing additional modules ...
> Removing existing VirtualBox non-DKMS kernel modules ...done.
> Building the VirtualBox Guest Additions kernel modules
> 
> *
> The headers for the current running kernel were not found. If the
> following module compilation fails then this could be the reason.
> *
> 
> Building the main Guest Additions module ...done.
> Building the shared folder support module ...done.
> Building the OpenGL support module ...done.
> Doing non-kernel setup of the Guest Additions ...done.
> 
> You should restart your guest to make sure the new modules are
> actually used
> 
> Installing the Window System drivers
> 
> ***
> Warning: unsupported pre-release version of X.Org Server installed.  Not
> installing the X.Org drivers.
>  ...done.
> ***
> 
> Installing graphics libraries and desktop services components ...done.
> 
> 
Could it be that you don't have dkms installed on the virtual machine?
What response do you get for:

$ apt-cache policy dkms


-- 
Klaus


-- 
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/53d10b19.5060...@gmail.com

Re: exact name of headers for 3.14-1-486

[Curt]

On 2014-07-23, Harry Putnam  wrote:
>
> Any ideas why vbox continues to report not finding header files for my
> running kernel?

I don't know. Have you installed "virtualbox-guest-dkms"?

Yes, I'm answering a question with a question.


-- 
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/slrnlt22so.22f.cu...@einstein.electron.org

Re: Special hotkeys for Openbox and LXDE users

[Steve Litt]

On Thu, 24 Jul 2014 09:40:33 + (UTC)
Curt  wrote:

> On 2014-07-24, Zenaan Harkness  wrote:
> >
> > Sometimes I use right hand, but mostly left hand. It did take a week
> > or two to get really comfortable both sides.
> >
> 
> Yes the OP assumes right-handedness, doesn't he? 

Yes, I did, and I forgot to mention that as one of my assumptions. If
one mouses with his/her left hand, most of those one-hand hotkeys would
need to be moved to the right side.

It's odd I forgot to mention this as an assumption, because both my
mother and my daughter are left handed.

> My wife is both
> gauchiste and gauchère; sharing a mouse was l'enfer (because of the
> cable and my right-handedness), until we got a wireless one for her
> laptop.
> 
> I suppose someone will pipe up to say that more people are
> right-handed than left-handed, and we must seek to satisfy the
> majority in all things. 

We needn't go that far. The functionalities I identified are a great
set for a person using a computer; the exact hotkeys to trigger them
can be adjusted by each individual to his/her exact maximum efficiency.

> Of course, in the past (that murky sea), it
> was often the case here and there for the authorities to enforce
> right-handedness in left-handed people.  

They tried to do that with my mother as a child, and she was very bitter
about it. From a very early age (6) I remember her frustration at living
in a right handed world. Every time she used a scissors, she got royally
pissed.

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


--
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/20140724093634.6fbc0...@mydesq2.domain.cxm

Re: missing LSB tags and overrides

[Brian]

On Thu 24 Jul 2014 at 14:43:06 +0200, Tony van der Hoff wrote:

> How do I join this output into the purge command to save typing in each
> package name?

A=$(dpkg -l | sed  '1,5d' | grep ^rc | awk -F" " '{print $2}')

dpkg -P $A


-- 
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/24072014143730.707b2c894...@desktop.copernicus.demon.co.uk

Re: exact name of headers for 3.14-1-486

[Klaus]

On 23/07/14 21:36, Harry Putnam wrote:
> uname -r:
>
>   3.14-1-486

$ apt-cache show linux-headers-3.14-1-486


Depends: linux-headers-3.14-1-common (= 3.14.12-1), linux-kbuild-3.14,
linux-compiler-gcc-4.8-x86
Description-en: Header files for Linux 3.14-1-486
 This package provides the architecture-specific kernel header files for
 Linux kernel 3.14-1-486, generally used for building out-of-tree kernel
 modules.




-- 
Klaus


-- 
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/53d10cc8.5090...@gmail.com

tune2fs: last write time is weeks or even months ago, moreover before last reboot

[David Guyot]

Hello, there.

I recently noticed that one of our servers was horribly slow when
aptitude upgrading, at the point that installing a simple mysql update
took a minute or so, when this server is in no way overloaded : twenty
or so mail accounts, not heavily used, an intranet with its MySQL daemon
and a front web page and under 1 Mbps on network interface. I forcefully
checked mdadm clusters: they're all clean. I checked RAID attributes: I
got a full scale reading on the read error rate on one of the two disks
— in fact a 2^16 value, so I assumed this was a positive integer
counter which reached its full scale reading — but this value disappeared
when I tried to investigate and dropped back to zero. Already a problem
because, as far as I know, this value just can't decrease, only increase;
am I right to suspect a faulty hard disk ?

Besides that, I listed the filesystems — all of them being ext3 —
parameters with tune2fs, and the I saw strange values at last
mount/write dates : every filesystems say that these dates are a few
weeks ago, at a moment I restarted the server — cleanly, I mean. Worse
than that, the / filesystem says that it hasn't been written since the
7th of December, 2013. That's more than seven months ago ! I would make
clear that this server's clock is NTP-synchronised; I just checked it
and it has corrects date and time; in addition, inodes counts are OK,
there are plenty of them free, and filesystems are not even used at 10%.
In fact, I see nothing else wrong with these filesystems. Apart from the
strange change in RAID attributes values, virtually nothing is wrong with
these disks besides the inconsistent last write dates in the filesystems.
I noticed that our other servers also show a last write date some weeks
ago, so I assume these values are consistent, but seven months ago, with
at least one reboot and a server always running since December ? I can't
imagine a logical reason for such a period. Do you know if this long
period is consistent ? If so, why is it consistent ? If not, does that
mean that a hard disk is to be changed ? The one whose RAID attributes
values are so erratic ? By the way, how can such a value decrease from
full scale reading to zero in a matter of minutes — during an extended
self-test, I should add ?

I was considering running the sync command to forcibly flush disks
caches, but, as the filesystems are all that slow that a single file
remove with rm took around a minute and slowed I/O at the point that
half the CPU cores where used for I/O wait, I'm not sure this is a good
idea to launch a sync. In fact, would a sync be effective ? fask,
maybe ? What else could be effective ?

Thank you in advance for your answers.

Regards.

PS: I will of course provide any needed additional information, as long
as it isn't a critical information for our server's security.
-- 
David Guyot
Administrateur système, réseau et télécommunications / Sysadmin
Europe Camions Interactive / Stockway
Moulin Collot
F-88500 Ambacourt
Tel: +33 (0)3 29 30 47 85
Fax : +33 (0)3 29 31 31 31


signature.asc
Description: Digital signature

Re: missing LSB tags and overrides

[Steve Kemp]

On Thu Jul 24, 2014 at 14:40:14 +0100, Brian wrote:

> > How do I join this output into the purge command to save typing in each
> > package name?
> 
> A=$(dpkg -l | sed  '1,5d' | grep ^rc | awk -F" " '{print $2}')

  That seems needlessly complex, using both sed and awk.

  Removing sed you could use this:

 dpkg --list | grep ^rc | awk '{print $2}'

  And given that awk can be used to match you could drop the grep too:

dpkg --list | awk '/^rc/ {print $2}' 

Steve
--
# git-based dns hosting.
https://dns-api.com/


-- 
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/20140724140737.ga10...@steve.org.uk

Logwatch output in the "Kernel" section

[Sharon Kimble]

I have two problems that have been bothering me for some time, the first
for about several days, and the second for a week or two.

 - This has begun appearing in my daily Logwatch output, and now using
   these file managers is virtually impossible as they are so
   untrustworthy. But what can I do about them, they only just crash out
   stating that there is a seg fault? Sometimes it crashes after several
   minutes, and sometimes after several hours, nothing seems to be a
   trigger, it just crashes. Even "thunar" crashes too!
 --8<---cut here---start->8---
 WARNING:  Segmentation Faults in these executables
caja :  4 Time(s)
gmain :  1 Time(s)
nautilus :  1 Time(s)
nemo :  2 Time(s) 
--8<---cut here---end--->8---

 - The second one shows every day. sde1 is an external usb drive
   formatted ext4 which is rather important as it is my backup
   drive. How should I resolve it please?
 --8<---cut here---start->8---
 WARNING:  Kernel Errors Present
EXT4-fs (sde1): error count: 1 ...:  1 Time(s)
EXT4-fs (sde1): initial error at 1397381477: _ ...:  1 Time(s)
EXT4-fs (sde1): last error at 1397381477: _ ...:  1 Time(s) 
--8<---cut here---end--->8---

Both of these errors show up in Logwatch output in the "Kernel" section.

Thanks
Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, fluxbox 1.3.5, emacs 24.3.92.1


signature.asc
Description: PGP signature

Re: missing LSB tags and overrides

[Darac Marjal]

On Thu, Jul 24, 2014 at 03:07:37PM +0100, Steve Kemp wrote:
> On Thu Jul 24, 2014 at 14:40:14 +0100, Brian wrote:
> 
> > > How do I join this output into the purge command to save typing in each
> > > package name?
> > 
> > A=$(dpkg -l | sed  '1,5d' | grep ^rc | awk -F" " '{print $2}')
> 
>   That seems needlessly complex, using both sed and awk.
> 
>   Removing sed you could use this:
> 
>  dpkg --list | grep ^rc | awk '{print $2}'
> 
>   And given that awk can be used to match you could drop the grep too:
> 
> dpkg --list | awk '/^rc/ {print $2}' 

All this, of course, assumes the OP doesn't want to use the previously
mentioned suggestion of "aptitude purge '~c'". And that's fair enough;
aptitude is not to everyone's taste.



signature.asc
Description: Digital signature

Re: systemd waisted 5 hours of my work time today

[Sharon Kimble]

Johann Spies  writes:

> This morning my work laptop would not boot.  I could not even get to single 
> user mode initially and when I got  as far as that I could not
> type anything on the terminal.  I suspect some upgrade yesterday caused it.
>
> In the end I had to search for a windows user who could write me a 
> debian-live cd.
>
> Using this, I could, after using some hints shown in 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746358 get my system to 
> boot (taking
> about 10 minutes do do so) and just as I started to work it rebooted 
> spontaneously.
>
> In the end after several experiments, I removed systemd and as a result a lot 
> of other packages, reinstalled sysvinit and it booted normally
> again and now I can work.
>
> I know systemd is not an option any more, but if this is the way it is going 
> to waste my time, I will have to look at a reinstallation of my
> system  and then use something that is less buggy than Debian Testing/Sid. 
>
> I have heard from a colleague of mine that on Mandriva and other systems he 
> has used systemd without such problems.
>
Yesterday I had the same problem when I rebooted, it left me at a tty
screen, where I was prompted to input my login and password, it then
lead on to my lightdm screen, as expected.

Whilst booting it showed an error message, which I've since been unable
to find, that systemd had broken error/start messages.

It was a bit of a shock to find that I was now using systemd, as I was
intending to not use it until forced to, but since then I haven't found
any problems, but then I haven't rebooted since then either.

Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, fluxbox 1.3.5, emacs 24.3.92.1


signature.asc
Description: PGP signature

Re: systemd waisted 5 hours of my work time today

[Sven Joachim]

On 2014-07-24 16:18 +0200, Sharon Kimble wrote:

> Johann Spies  writes:
>
>> This morning my work laptop would not boot.  I could not even get to
>> single user mode initially and when I got  as far as that I could
>> not
>> type anything on the terminal.  I suspect some upgrade yesterday caused it.

There should be at least some message on the terminal, although other
people have not been able to log in in that situation either[1].

> Yesterday I had the same problem when I rebooted, it left me at a tty
> screen, where I was prompted to input my login and password, it then
> lead on to my lightdm screen, as expected.

That's not the same problem.  In fact, it is not even a problem but
merely the fact that getty starts up much faster than X.

> Whilst booting it showed an error message, which I've since been unable
> to find, that systemd had broken error/start messages.

You should be able to find them in the journal, see journalctl(1).
Note that that systemd clears the boot messages by default when it
starts getty, see [2] on how to change that.

Cheers,
   Sven


1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755581
2. https://wiki.archlinux.org/index.php/Disable_Clearing_of_Boot_Messages


--
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/87k372n69i@turtle.gmx.de

Desktop sharing question

[Nelson Green]

Good morning all,

I have a new, novice Debian user running the XFCE desktop on his PC. I
would like to be able to share his desktop to me so that I can see
what he is seeing and offer instruction and advice. I have used VNC to
connect to a different X screens, but I'm not sure how to arrange
things so that we can both see the same screen a the same time. I'm
not necessarily interested in being able to control his session, just
to see what he sees. Would someone mind pointing me towards some
learning material regarding how to do this?

Thanks,
Nelson


-- 
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/cago-kzmh8tmgmofefazkwvsf6520zbilaf5mj0c_fbe7zlw...@mail.gmail.com

Re: Desktop sharing question

[Bzzzz]

On Thu, 24 Jul 2014 10:36:47 -0500
Nelson Green  wrote:

> Good morning all,

Good afternoon alone,

> PC. I would like to be able to share his desktop to me so that I
> can see what he is seeing and offer instruction and advice. I have

Use X2GO (x2go.org), it includes a 'desktop sharing' function
and just need an access to the SSH port. Furthermore, is uses
NX libraries, greatly accelerating graphic transfers (compared
yo VNC).
You can also access it without a password (you'll need the 
other side 'id_rsa' private key, though).

If you don't wanna open a forwarding in the box|modem at the
young padaWAN's home, use teamviewer (but it is non-free and
non-open-source, so… take your chances against nsa, fbi, homeland
security, cia, cfr, nwo, tsa, etc:).

-- 
 I'm living in a magnificent world of plenty
 my mom is pushing my friends and me to drink
 (so my father won't finish the beers)


signature.asc
Description: PGP signature

Re: systemd waisted 5 hours of my work time today

[Sharon Kimble]

Sven Joachim  writes:

> On 2014-07-24 16:18 +0200, Sharon Kimble wrote:
>
>> Johann Spies  writes:
>>
>>> This morning my work laptop would not boot.  I could not even get to
>>> single user mode initially and when I got  as far as that I could
>>> not
>>> type anything on the terminal.  I suspect some upgrade yesterday caused it.
>
> There should be at least some message on the terminal, although other
> people have not been able to log in in that situation either[1].
>
>> Yesterday I had the same problem when I rebooted, it left me at a tty
>> screen, where I was prompted to input my login and password, it then
>> lead on to my lightdm screen, as expected.
>
> That's not the same problem.  In fact, it is not even a problem but
> merely the fact that getty starts up much faster than X.
>
>> Whilst booting it showed an error message, which I've since been unable
>> to find, that systemd had broken error/start messages.
>
> You should be able to find them in the journal, see journalctl(1).
> Note that that systemd clears the boot messages by default when it
> starts getty, see [2] on how to change that.
>
> Cheers,
>Sven
>
>
> 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755581
> 2. https://wiki.archlinux.org/index.php/Disable_Clearing_of_Boot_Messages
>
Thanks for this, this is the error message that I saw
--8<---cut here---start->8---
Jul 23 06:34:47 london systemd[1]: Breaking ordering cycle by deleting job 
downtimed.service/start
Jul 23 06:34:47 london systemd[1]: Job downtimed.service/start deleted to break 
ordering cycle starting with basic.target/start
--8<---cut here---end--->8---

Hope it helps
Sharon.
-- 
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, fluxbox 1.3.5, emacs 24.3.92.1


signature.asc
Description: PGP signature

gnome 3: ways to set to play an audio file when battery power is very low?

[Kejia柯嘉]

Hi,

In gnome 3, is there a way to set to play sound for warning low battery power?

Thanks a lot.

Cheers,
Daniel

☵☯☲


--
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/cale-ffok4mf8mw-pqrsemdoqcfaehzb3seerkagol_zsju7...@mail.gmail.com

Re: systemd waisted 5 hours of my work time today

[Paul E Condon]

On 20140724_1411+0100, Brian wrote:
> On Thu 24 Jul 2014 at 14:24:36 +0200, Johann Spies wrote:
> 
> > On 24 July 2014 14:00, Tom Furie  wrote:
> > 
> > I am aware of that and has been using testing/sid for about 13 years now.
> > I have never experienced anything like this.
> 
> You are now. :)
> 
> Look on the bright side; the BTS came to the rescue.

I've been using Debian since the time of Y2K. From the beginning I
believed that running testing was a path to advancement as a
programmer or sysadmin. I thought I might study Debian by using the
testing distribution, but I never made much progress on this path.

Over the years I have developed little tricks to smooth over the
inevitable rough times in the transition to a new release. This time
is different. Before, when I sensed that a pre-release freeze was
immanent I would dist-upgrade to testing so that I would already be
using the new packages at the moment of official release. Now I have
little confidence in this strategy, and instead I am hoping to survive
the chaos by sticking with Wheezy until that happy future time when
everyone using Jessie is happily singing its praise. But when the time
comes for me to leave Wheezy behind, Jessie may very well be old and
nearing replacement. In which case, dist-upgrade to the testing
release of that future time may not be possible without intermediate
steps, and the transition will be by way of a full backup to external
HD followed by a clean install of whatever makes the most sense at
that future time. To that end, I am doing practice installs using a
second computer as an Approx proxy repository. I'm getting pretty good
at it. Well, maybe not by other people's standards, but much better
than the first time. 

I suggest that people who complain about testing/Jessie being unusable
for days on end, figure out how to modify their behavior to better
conform to the current reality. Everybody running testing should have
an interest in some day becoming a Debian developer, whatever their
current skill level is today. And maybe even some who do have such a
goal should step aside for a while to lessen the burden on the
developers to hand-hold them. These are tough times.

Best regards to all,

-- 
Paul E Condon   
pecon...@mesanetworks.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/20140724155936.ga3...@big.lan.gnu

Re: systemd waisted 5 hours of my work time today

[Joe]

On Thu, 24 Jul 2014 15:00:05 +0200
Slavko  wrote:

> Ahoj,
> 
> Dňa Thu, 24 Jul 2014 13:00:24 +0100 Tom Furie 
> napísal:
> 
> > On Thu, Jul 24, 2014 at 01:12:32PM +0200, Johann Spies wrote:
> > 
> > > I know systemd is not an option any more, but if this is the way
> > > it is going to waste my time, I will have to look at a
> > > reinstallation of my system  and then use something that is less
> > > buggy than Debian Testing/Sid.
> > 
> > You are, of course, aware that testing and unstable are test
> > platforms where breakage is to be expected? They shouldn't be used
> > for anything "mission critical", that's what stable is for.
> 
> No, i will not comply with this.
> 
> The testing must be in state, where it must to boot (except some boot
> options tweaks) by default. I think, that nobody here will complain if
> some of software/services on testing doesn't work, but computer must
> to boot!
> 
> If it will not boot, then it is not appropriate to "mission critical"
> only, but then it is not appropriate to nothing. And because the NFS
> is installed by default, then it can be considered as "is used" by
> default too, then system doesn't boot for default and IMO this is a
> problem.
> 

I don't think this is intentional. It's not the first non-booting issue
I've had with sid, and each time it seems that not many other people
have the problem.

I'm sure a lot of testing has been done, but unfortunately the switch
to systemd from a mature sysvinit installation ('drop-in replacement')
seems to be quite stressful, and a few systems have broken badly,
including one of mine. (I still have two unmigrated sids...)

A new systemd installation is likely to be much more stable, and while
my main workstation is mostly working, there are far too many error
messages for my liking, as well as crashes during most shutdowns. It
may be worth rebuilding to get a more reliable system, when I get the
time, as I have the feeling it will be a less frustrating experience
than trying to fix the existing system.

-- 
Joe


--
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/20140724170508.1b30e...@jretrading.com

Re: inserting kernel modules on startup

[Gary Dale]

On 24/07/14 08:56 AM, Michael Biebl wrote:

Am 24.07.2014 12:42, schrieb Gary Dale:

After the latest round of upgrades in Jessie, I rebooted. That's when
the problems started. I'm having problems getting the 3.14 kernel to
boot, so I'm booting from 3.13. However, that's not the big issue.

The really annoying problem is that I have to boot to the command
prompt, insmod radeon, then exit back to a regular boot in order to get
the radeon module loaded.

Radeon is listed in /etc/modules.conf - has been for years. However the

Can you post your modules.conf, please


This is basically how it's looked for a long time. Up until my recent 
reboot, the kernel module seems to have been loading properly. Now I 
have to insert it manually when rebooting.



# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.

firewire-sbp2
loop
radeon
# usblp


--
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/53d136af.9020...@torfree.net

Re: HTML5 => png or HTML5 => jpg.

[peter]

From: Jerry Stuckle 
Date: Wed, 09 Jul 2014 12:20:37 -0400
> How is the document revised? 

Text editor.

> is the HTML5 document always served by a web server, or 
> can it be loaded from a file?

It is self-contained and can come from a file or from a server.

> ... put a couple of comment lines in the file - one
> before the images and one after the images.  Then have your script
> search for those comment lines and replace everything between them with
> the contents of the new file.

For the text manipulations, can you recommend AWK, Perl, sed or another?

Thanks,   ... Peter E.
 
-- 
123456789 123456789 123456789 123456789 123456789 123456789 123456789 12
Tel +1 360 639 0202  http://carnot.yi.org/  Bcc: peter at easthope. ca


-- 
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/E1XALuO-00084b-UG@dalton.invalid

Re: inserting kernel modules on startup

[Michael Biebl]

Am 24.07.2014 18:39, schrieb Gary Dale:
> On 24/07/14 08:56 AM, Michael Biebl wrote:
>> Am 24.07.2014 12:42, schrieb Gary Dale:
>>> After the latest round of upgrades in Jessie, I rebooted. That's when
>>> the problems started. I'm having problems getting the 3.14 kernel to
>>> boot, so I'm booting from 3.13. However, that's not the big issue.
>>>
>>> The really annoying problem is that I have to boot to the command
>>> prompt, insmod radeon, then exit back to a regular boot in order to get
>>> the radeon module loaded.
>>>
>>> Radeon is listed in /etc/modules.conf - has been for years. However the
>> Can you post your modules.conf, please
>>
>>
> This is basically how it's looked for a long time. Up until my recent
> reboot, the kernel module seems to have been loading properly. Now I
> have to insert it manually when rebooting.
> 
> 
> # /etc/modules: kernel modules to load at boot time.
> #
> # This file contains the names of kernel modules that should be loaded
> # at boot time, one per line. Lines beginning with "#" are ignored.
> # Parameters can be specified after the module name.
> 
> firewire-sbp2
> loop
> radeon
> # usblp

That looks fine.

What's the status of
systemctl status systemd-modules-load.service

After a reboot, is the radeon kernel module not loaded at all? Or is it
loaded but not functional?
What about the firewire-sbp2 and loop module?

Fwiw, I'm suprised you need to manually load the radeon kernel module.
It should be auto-loaded afair.





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

Re: inserting kernel modules on startup

[Gary Dale]

On 24/07/14 12:57 PM, Michael Biebl wrote:

Am 24.07.2014 18:39, schrieb Gary Dale:

On 24/07/14 08:56 AM, Michael Biebl wrote:

Am 24.07.2014 12:42, schrieb Gary Dale:

After the latest round of upgrades in Jessie, I rebooted. That's when
the problems started. I'm having problems getting the 3.14 kernel to
boot, so I'm booting from 3.13. However, that's not the big issue.

The really annoying problem is that I have to boot to the command
prompt, insmod radeon, then exit back to a regular boot in order to get
the radeon module loaded.

Radeon is listed in /etc/modules.conf - has been for years. However the

Can you post your modules.conf, please



This is basically how it's looked for a long time. Up until my recent
reboot, the kernel module seems to have been loading properly. Now I
have to insert it manually when rebooting.


# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.

firewire-sbp2
loop
radeon
# usblp

That looks fine.

What's the status of
systemctl status systemd-modules-load.service

After a reboot, is the radeon kernel module not loaded at all? Or is it
loaded but not functional?
What about the firewire-sbp2 and loop module?

Fwiw, I'm suprised you need to manually load the radeon kernel module.
It should be auto-loaded afair.

root@transponder:/home/garydale# systemctl status 
systemd-modules-load.service

systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; 
static)

   Active: active (exited) since Thu 2014-07-24 06:17:41 EDT; 6h ago
 Docs: man:systemd-modules-load.service(8)
   man:modules-load.d(5)
 Main PID: 342 (code=exited, status=0/SUCCESS)

Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 'lp'
Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'ppdev'
Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'parport_pc'
Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'fuse'
Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'firewire_sbp2'
Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'loop'

Jul 24 06:17:41 transponder systemd[1]: Started Load Kernel Modules.
Warning: Journal has been rotated since unit was started. Log output is 
incomplete or unavailable



The radeon kernel module is not being loaded. insmod readeon works.

I added the radeon line back in 2012 when the drm was new. Having it in 
/etc/modules was never a problem. I was wondering if it might have been 
blacklisted so I checked /etc/modprobe.d and it doesn't seem to be. 
However I note the fglrx driver is listed. It blacklists radeon. I 
haven't used the fglrx driver in some time because it's a real pain in 
the butt when running Jessie.


root@transponder:/home/garydale# ls -l /etc/modprobe.d/
total 40
-rw-r--r-- 1 root root 1222 Aug 15  2013 alsa-base.conf.dpkg-bak
-rw-r--r-- 1 root root  157 Feb  3  2012 blacklist-cups-usblp.conf.dpkg-bak
-rw-r--r-- 1 root root  127 Oct  5  2012 dkms.conf
-rw-r--r-- 1 root root  410 Jun 28 07:28 fbdev-blacklist.conf
-rw-r--r-- 1 root root   65 Sep 25  2010 fglrx-driver.conf
-rw-r--r-- 1 root root   23 May 14  2010 i915-kms.conf
-rw-r--r-- 1 root root   16 Nov 15  2011 libpisock9.conf
-rw-r--r-- 1 root root   51 May 10 19:22 modesetting.conf
-rw-r--r-- 1 root root  119 Sep  1  2013 oss-compat.conf
-rw-r--r-- 1 root root   26 Jul 15  2010 radeon-kms.conf


--
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/53d1408e.4080...@torfree.net

Re: Latest Jessie doesn't respond to /etc/default/tmpfs "RAMTMP=yes"

[Andrei POPESCU]

On Mi, 23 iul 14, 00:12:25, Rick Thomas wrote:
> 
> I’m trying to get /tmp on tmpfs, so I put “RAMTMP=yes” in /dev/default/tmpfs .
> 
> But I don’t get /tmp/mounted on tmpfs.

What's wrong with fstab?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

[SOLVED] Re: inserting kernel modules on startup

[Gary Dale]

On 24/07/14 01:21 PM, Gary Dale wrote:

On 24/07/14 12:57 PM, Michael Biebl wrote:

Am 24.07.2014 18:39, schrieb Gary Dale:

On 24/07/14 08:56 AM, Michael Biebl wrote:

Am 24.07.2014 12:42, schrieb Gary Dale:

After the latest round of upgrades in Jessie, I rebooted. That's when
the problems started. I'm having problems getting the 3.14 kernel to
boot, so I'm booting from 3.13. However, that's not the big issue.

The really annoying problem is that I have to boot to the command
prompt, insmod radeon, then exit back to a regular boot in order 
to get

the radeon module loaded.

Radeon is listed in /etc/modules.conf - has been for years. 
However the

Can you post your modules.conf, please



This is basically how it's looked for a long time. Up until my recent
reboot, the kernel module seems to have been loading properly. Now I
have to insert it manually when rebooting.


# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.

firewire-sbp2
loop
radeon
# usblp

That looks fine.

What's the status of
systemctl status systemd-modules-load.service

After a reboot, is the radeon kernel module not loaded at all? Or is it
loaded but not functional?
What about the firewire-sbp2 and loop module?

Fwiw, I'm suprised you need to manually load the radeon kernel module.
It should be auto-loaded afair.

root@transponder:/home/garydale# systemctl status 
systemd-modules-load.service

systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; 
static)

   Active: active (exited) since Thu 2014-07-24 06:17:41 EDT; 6h ago
 Docs: man:systemd-modules-load.service(8)
   man:modules-load.d(5)
 Main PID: 342 (code=exited, status=0/SUCCESS)

Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'lp'
Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'ppdev'
Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'parport_pc'
Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'fuse'
Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'firewire_sbp2'
Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'loop'

Jul 24 06:17:41 transponder systemd[1]: Started Load Kernel Modules.
Warning: Journal has been rotated since unit was started. Log output 
is incomplete or unavailable



The radeon kernel module is not being loaded. insmod readeon works.

I added the radeon line back in 2012 when the drm was new. Having it 
in /etc/modules was never a problem. I was wondering if it might have 
been blacklisted so I checked /etc/modprobe.d and it doesn't seem to 
be. However I note the fglrx driver is listed. It blacklists radeon. I 
haven't used the fglrx driver in some time because it's a real pain in 
the butt when running Jessie.


root@transponder:/home/garydale# ls -l /etc/modprobe.d/
total 40
-rw-r--r-- 1 root root 1222 Aug 15  2013 alsa-base.conf.dpkg-bak
-rw-r--r-- 1 root root  157 Feb  3  2012 
blacklist-cups-usblp.conf.dpkg-bak

-rw-r--r-- 1 root root  127 Oct  5  2012 dkms.conf
-rw-r--r-- 1 root root  410 Jun 28 07:28 fbdev-blacklist.conf
-rw-r--r-- 1 root root   65 Sep 25  2010 fglrx-driver.conf
-rw-r--r-- 1 root root   23 May 14  2010 i915-kms.conf
-rw-r--r-- 1 root root   16 Nov 15  2011 libpisock9.conf
-rw-r--r-- 1 root root   51 May 10 19:22 modesetting.conf
-rw-r--r-- 1 root root  119 Sep  1  2013 oss-compat.conf
-rw-r--r-- 1 root root   26 Jul 15  2010 radeon-kms.conf

OK, that did it. Removing /etc/modprobe.d/fglrx.conf allowed the radeon 
kernel module to load. I have no idea why this just started happening. I 
would have thought that a blacklist in a module that wasn't being used 
would be ignored, as seems to have been the case up to very recently.



--
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/53d1471f.6000...@torfree.net

Re: no display manager for 3 days

[Andrei POPESCU]

On Jo, 24 iul 14, 14:08:55, Brian wrote:
> On Thu 24 Jul 2014 at 08:50:49 -0400, Steve Litt wrote:
> 
> > I can't help you with the root cause, because I know less about
> > systemd than I know of the plant life at the North Pole, but if it
> > were me, for the time being, I'd just do the workaround and use
> > startx. You put your window manager in .xinitrc, and then from the
> > command prompt, as a normal user, type "startx".
> 
> It is much wiser to use ~/.xsession on Debian.

Or 'update-alternatives --config x-session-manager', which provides a 
nice menu with all installed x-session-managers and makes the setting 
system-wide.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

[SOLVED] Re: inserting kernel modules on startup

[Gary Dale]

On 24/07/14 01:21 PM, Gary Dale wrote:

On 24/07/14 12:57 PM, Michael Biebl wrote:

Am 24.07.2014 18:39, schrieb Gary Dale:

On 24/07/14 08:56 AM, Michael Biebl wrote:

Am 24.07.2014 12:42, schrieb Gary Dale:

After the latest round of upgrades in Jessie, I rebooted. That's when
the problems started. I'm having problems getting the 3.14 kernel to
boot, so I'm booting from 3.13. However, that's not the big issue.

The really annoying problem is that I have to boot to the command
prompt, insmod radeon, then exit back to a regular boot in order 
to get

the radeon module loaded.

Radeon is listed in /etc/modules.conf - has been for years. 
However the

Can you post your modules.conf, please



This is basically how it's looked for a long time. Up until my recent
reboot, the kernel module seems to have been loading properly. Now I
have to insert it manually when rebooting.


# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.

firewire-sbp2
loop
radeon
# usblp

That looks fine.

What's the status of
systemctl status systemd-modules-load.service

After a reboot, is the radeon kernel module not loaded at all? Or is it
loaded but not functional?
What about the firewire-sbp2 and loop module?

Fwiw, I'm suprised you need to manually load the radeon kernel module.
It should be auto-loaded afair.

root@transponder:/home/garydale# systemctl status 
systemd-modules-load.service

systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; 
static)

   Active: active (exited) since Thu 2014-07-24 06:17:41 EDT; 6h ago
 Docs: man:systemd-modules-load.service(8)
   man:modules-load.d(5)
 Main PID: 342 (code=exited, status=0/SUCCESS)

Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'lp'
Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'ppdev'
Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'parport_pc'
Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'fuse'
Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'firewire_sbp2'
Jul 24 06:17:41 transponder systemd-modules-load[342]: Inserted module 
'loop'

Jul 24 06:17:41 transponder systemd[1]: Started Load Kernel Modules.
Warning: Journal has been rotated since unit was started. Log output 
is incomplete or unavailable



The radeon kernel module is not being loaded. insmod readeon works.

I added the radeon line back in 2012 when the drm was new. Having it 
in /etc/modules was never a problem. I was wondering if it might have 
been blacklisted so I checked /etc/modprobe.d and it doesn't seem to 
be. However I note the fglrx driver is listed. It blacklists radeon. I 
haven't used the fglrx driver in some time because it's a real pain in 
the butt when running Jessie.


root@transponder:/home/garydale# ls -l /etc/modprobe.d/
total 40
-rw-r--r-- 1 root root 1222 Aug 15  2013 alsa-base.conf.dpkg-bak
-rw-r--r-- 1 root root  157 Feb  3  2012 
blacklist-cups-usblp.conf.dpkg-bak

-rw-r--r-- 1 root root  127 Oct  5  2012 dkms.conf
-rw-r--r-- 1 root root  410 Jun 28 07:28 fbdev-blacklist.conf
-rw-r--r-- 1 root root   65 Sep 25  2010 fglrx-driver.conf
-rw-r--r-- 1 root root   23 May 14  2010 i915-kms.conf
-rw-r--r-- 1 root root   16 Nov 15  2011 libpisock9.conf
-rw-r--r-- 1 root root   51 May 10 19:22 modesetting.conf
-rw-r--r-- 1 root root  119 Sep  1  2013 oss-compat.conf
-rw-r--r-- 1 root root   26 Jul 15  2010 radeon-kms.conf

OK, that did it. Removing /etc/modprobe.d/fglrx.conf allowed the radeon 
kernel module to load. I have no idea why this just started happening. I 
would have thought that a blacklist in a module that wasn't being used 
would be ignored, as seems to have been the case up to very recently.



--
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/53d14386.4020...@torfree.net

Re: [SOLVED] Re: inserting kernel modules on startup

[Sven Joachim]

On 2014-07-24 19:49 +0200, Gary Dale wrote:

> OK, that did it. Removing /etc/modprobe.d/fglrx.conf allowed the
> radeon kernel module to load.

You don't need to list it in /etc/modules anymore then, since udev will
load it automatically for you.

> I have no idea why this just started
> happening. I would have thought that a blacklist in a module that
> wasn't being used would be ignored, as seems to have been the case up
> to very recently.

I'm not sure if I can parse that sentence correctly, but the difference
to a sysvinit setup is that the kmod initscript runs modprobe without
the "-b" parameter (thus ignoring the blacklist), while
systemd-modules-load will not load blacklisted modules.

Blacklisting a module that would be autoloaded by udev, only to load it
via /etc/modules anyway, seems rather illogical.  So the systemd
behavior at least forced you to fix your setup. ;-)

Cheers,
   Sven


-- 
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/874my6mxcn@turtle.gmx.de

Re: [SOLVED] Re: inserting kernel modules on startup

[Gary Dale]

On 24/07/14 02:21 PM, Sven Joachim wrote:

On 2014-07-24 19:49 +0200, Gary Dale wrote:


OK, that did it. Removing /etc/modprobe.d/fglrx.conf allowed the
radeon kernel module to load.

You don't need to list it in /etc/modules anymore then, since udev will
load it automatically for you.

The joys of an evolving system. At one time it was necessary.




I have no idea why this just started
happening. I would have thought that a blacklist in a module that
wasn't being used would be ignored, as seems to have been the case up
to very recently.

I'm not sure if I can parse that sentence correctly, but the difference
to a sysvinit setup is that the kmod initscript runs modprobe without
the "-b" parameter (thus ignoring the blacklist), while
systemd-modules-load will not load blacklisted modules.

Blacklisting a module that would be autoloaded by udev, only to load it
via /etc/modules anyway, seems rather illogical.  So the systemd
behavior at least forced you to fix your setup. ;-)

Cheers,
Sven

I think you missed the point. The blacklist was in fglrx.conf where it 
makes sense to not load the radeon module if I'm loading the fglrx 
proprietary one. Again, this was necessary back when I was playing 
around with the fglrx driver. I would have expected the system to only 
parse the .conf files of modules it was loading.



--
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/53d15381.7080...@torfree.net

[Wheezy] [networking] post-up NOT executed

[Mickael MONSIEUR]

Hi,
I have a fresh installation of Debian Wheezy 7.6.0 amd64.
The post-up line does not execute when eth0 is mounted!
(by against my eth0 interface is mounted!)

I have to mount routes, and are not:

post-up /sbin/route add 1.2.3.4 dev eth0

simple test:

post-up touch /tmp/test
reboot (...)

cat /tmp/test
cat: /tmp/1: No such file or directory

Have you ever had this problem?
I find nothing in dmesg and syslog!

With Kind Regards,
Mickael Monsieur

Re: [SOLVED] Re: inserting kernel modules on startup

[Sven Joachim]

On 2014-07-24 20:42 +0200, Gary Dale wrote:

> I think you missed the point. The blacklist was in fglrx.conf where it
> makes sense to not load the radeon module if I'm loading the fglrx
> proprietary one. Again, this was necessary back when I was playing
> around with the fglrx driver. I would have expected the system to only
> parse the .conf files of modules it was loading.

Files under /etc/modprobe.d do not necessarily "belong" to any modules,
so this is not possible.  Any file there whose name ends in ".conf" will
be parsed.

Cheers,
   Sven


-- 
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/87fvhqlgqe@turtle.gmx.de

Re: no display manager for 3 days

[Alan Simpson-Vlach]

> On Thu 24 Jul 2014 at 10:37:34 +, Alan Simpson-Vlach wrote:
> 
> > Ever since a dist-upgrade that installed systemd and removed
> > sysvinit-core, I have been unable to get a display manager.
> 
> The dist-upgrade would have more than this. You are using testing?
> 
> > I have tried slim, lightdm, and even installed gdm3.  Nothing works.
> > 
> > # /etc/init.d/slim/start
> > 
> > gives no error messages, but
> > 
> > # systemctl status slim.service
> > 
> > tells me that slim exited with status=1
> > 
> > The pertinent line appears to be
> > 
> > /usr/bin/X11/X: symbol lookup error: 
> > /usr/lib/xorg/modules/extensions/libglx.so: undefined symbol: LoadExtension
> > 
> > which is similar to what happens if I try xinit directly.
> > 
> > Trying lightdm I get 
> > 
> > lightdm.service start request repeated too quickly, refusing to start.
> > 
> > I think this is a systemd problem, but maybe it's a video driver problem?
> > I'm using the proprietary nvidia driver, which has been recompiled multiple 
> > times now.
> > Help, please.  I'd kinda like to have a working X11 again.
> 
> If xinit or startx will not bring up X it seems more like a video
> problem to me. How do feel about using the nouveau driver if you cannot
> fix the proprietary one?

I had problems with nouveau about a year ago, so I switched back to the 
proprietary driver.
The NVIDIA driver has always been reliable, even if non-open-source and a pain 
in the neck to have to recompile with every new kernel.
But at this point, I'd be happy with _anything_ that gives me X back. Here goes:

sudo install xserver-xorg-video-nouveau

(My memory tells me this used to ask if I wanted my proprietary nvidia setup 
disabled. That didn't happen this time.)

No change whatsoever.  Invoking startx/xinit still doesn't work.
I still get the complaint about libglx.so

One respondent said maybe my GLX installation is broken.  How do I fix that? 

Thanks much,
--Alan


--
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/45855514-ccee-4204-aa90-ed1a55b99...@laurelschool.org

Re: no display manager for 3 days

[Steve Litt]

On Thu, 24 Jul 2014 19:18:47 +
Alan Simpson-Vlach  wrote:


> No change whatsoever.  Invoking startx/xinit still doesn't work.
> I still get the complaint about libglx.so
> 
> One respondent said maybe my GLX installation is broken.  How do I
> fix that? 

I don't know, but just for fun why don't you run startx as root, and
see whether the symptom stays the same or changes.

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


-- 
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/20140724153141.518e1...@mydesq2.domain.cxm

Re: no display manager for 3 days

[Erwan David]

DId you remove also the nividia specific glx libs ?


-- 
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/53d1600b.90...@rail.eu.org

ip6tables: unexpected behaviour ?

[Jerome BENOIT]

Hello List,

I am building an IPv6 firewall: I get the message

ip6tables v1.4.14: host/network `172.20.0.1' not found


Is it expected ?

Thanks in advance,
Jerome


-- 
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/53d161f9.1020...@rezozer.net

Re: [SOLVED] Re: inserting kernel modules on startup

[Gary Dale]

On 24/07/14 03:05 PM, Sven Joachim wrote:

On 2014-07-24 20:42 +0200, Gary Dale wrote:


I think you missed the point. The blacklist was in fglrx.conf where it
makes sense to not load the radeon module if I'm loading the fglrx
proprietary one. Again, this was necessary back when I was playing
around with the fglrx driver. I would have expected the system to only
parse the .conf files of modules it was loading.

Files under /etc/modprobe.d do not necessarily "belong" to any modules,
so this is not possible.  Any file there whose name ends in ".conf" will
be parsed.

Cheers,
Sven
Sorry but that doesn't make much sense to me. The files I have in 
/etc/modprobe.d all look like they belong to kernel modules. Moreover, 
the directory is related to modules.



--
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/53d16264.5030...@torfree.net

Re: ip6tables: unexpected behaviour ?

[Erwan David]

Le 24/07/2014 21:43, Jerome BENOIT a écrit :
> Hello List,
>
> I am building an IPv6 firewall: I get the message
>
> ip6tables v1.4.14: host/network `172.20.0.1' not found
>
>
> Is it expected ?
>
> Thanks in advance,
> Jerome
>
>
It seems quite natural to me that ip6tables does not knows how to treat
an IPv4 address.


-- 
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/53d16310.6090...@rail.eu.org

Re: ip6tables: unexpected behaviour ?

[Jerome BENOIT]

On 24/07/14 21:48, Erwan David wrote:
> Le 24/07/2014 21:43, Jerome BENOIT a écrit :
>> Hello List,
>>
>> I am building an IPv6 firewall: I get the message
>>
>> ip6tables v1.4.14: host/network `172.20.0.1' not found
>>
>>
>> Is it expected ?
>>
>> Thanks in advance,
>> Jerome
>>
>>
> It seems quite natural to me that ip6tables does not knows how to treat
> an IPv4 address.

Not to me, because I assume that IPv6 encapsulates somehow IPv4:
do I miss something ?

Jerome

> 
> 



-- 
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/53d16970.3060...@rezozer.net

Re: ip6tables: unexpected behaviour ?

[Jochen Spieker]

Jerome BENOIT:
> 
> On 24/07/14 21:48, Erwan David wrote:
>> Le 24/07/2014 21:43, Jerome BENOIT a écrit :
>>> Hello List,
>>> 
>>> I am building an IPv6 firewall: I get the message
>>> 
>>> ip6tables v1.4.14: host/network `172.20.0.1' not found
>>> 
>>> 
>>> Is it expected ?
>>> 
>>> 
>> It seems quite natural to me that ip6tables does not knows how to treat
>> an IPv4 address.
> 
> Not to me, because I assume that IPv6 encapsulates somehow IPv4:
> do I miss something ?

http://en.wikipedia.org/wiki/IPv6#IPv4-mapped_IPv6_addresses

J.
-- 
If you do not move for long enough, you might see a rat.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Howtos and Faqs

[Mike McClain]

Howdy,
When I started to setup my Linux computer to forward IP packets
to my Windows computer I realized my copies for the HOWTOs are dated
so tried to update them with 'apt-get install doc-linux-text' which
failed. After fumbling a bit I went searching at debian.org only to
find there is no such package in english only french, japanese and a
couple of other languages. Nor is it to be found in the orphaned
packages list.
Where did it go or what is the package now called that holds the
LDP HOWTOs and FAQs?

Thanks,
Mike
--
Goodness will be rewarded with goodness.
- Chinese proverb


-- 
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/20140724000114.GA31234@playground

Re: Howtos and Faqs

[Bzzzz]

On Wed, 23 Jul 2014 17:01:14 -0700
John McClain  wrote:

> doc-linux-text' which failed. After fumbling a bit I went
> searching at debian.org only to find there is no such package in
> english only french, japanese and a couple of other languages. Nor

So, let's learn japanese ;)

> Where did it go or what is the package now called that holds
> the LDP HOWTOs and FAQs?

Check tldp.org

-- 
titix: seriously, I still don't understand.
titix: you want to be a physician, right
titix: but a coroner… I'm out of words.
titix: this is a disgusting occupation, and you're going to
   autopsy poor guys that had terrible accidents reduced
   to slop… So why?
momo: patients won't piss me off
titix: …you scored a goal.


signature.asc
Description: PGP signature

Re: ip6tables: unexpected behaviour ?

[Jerome BENOIT]

Hello Again,

On 24/07/14 22:17, Jochen Spieker wrote:
> Jerome BENOIT:
>>
>> On 24/07/14 21:48, Erwan David wrote:
>>> Le 24/07/2014 21:43, Jerome BENOIT a écrit :
 Hello List,

 I am building an IPv6 firewall: I get the message

 ip6tables v1.4.14: host/network `172.20.0.1' not found


 Is it expected ?


>>> It seems quite natural to me that ip6tables does not knows how to treat
>>> an IPv4 address.
>>
>> Not to me, because I assume that IPv6 encapsulates somehow IPv4:
>> do I miss something ?
> 
> http://en.wikipedia.org/wiki/IPv6#IPv4-mapped_IPv6_addresses

Thanks a lot for the link.

Jerome

> 
> J.
> 


-- 
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/53d16f95.6040...@rezozer.net

Re: [SOLVED] Re: inserting kernel modules on startup

[Michael Biebl]

Am 24.07.2014 21:45, schrieb Gary Dale:
> On 24/07/14 03:05 PM, Sven Joachim wrote:
>> On 2014-07-24 20:42 +0200, Gary Dale wrote:
>>
>>> I think you missed the point. The blacklist was in fglrx.conf where it
>>> makes sense to not load the radeon module if I'm loading the fglrx
>>> proprietary one. Again, this was necessary back when I was playing
>>> around with the fglrx driver. I would have expected the system to only
>>> parse the .conf files of modules it was loading.
>> Files under /etc/modprobe.d do not necessarily "belong" to any modules,
>> so this is not possible.  Any file there whose name ends in ".conf" will
>> be parsed.
>>
>> Cheers,
>> Sven
> Sorry but that doesn't make much sense to me. The files I have in
> /etc/modprobe.d all look like they belong to kernel modules. Moreover,
> the directory is related to modules.

It is like Sven says.
When you run modprobe, it will parse /etc/modprobe.conf and all files in
/etc/modprobe.d/ ending with .conf
It doesn't really matter how they are named.

So you could have named fglrx.conf foo.conf, that wouldn't have made a
difference.

So, after dropping the blacklist, you can also drop "radeon" from
/etc/modules. As already mentioned it will be autoloaded by udev.

Cheers,
Michael


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

Re: no display manager for 3 days

[Brian]

On Thu 24 Jul 2014 at 21:00:44 +0300, Andrei POPESCU wrote:

> On Jo, 24 iul 14, 14:08:55, Brian wrote:
> > On Thu 24 Jul 2014 at 08:50:49 -0400, Steve Litt wrote:
> > 
> > > I can't help you with the root cause, because I know less about
> > > systemd than I know of the plant life at the North Pole, but if it
> > > were me, for the time being, I'd just do the workaround and use
> > > startx. You put your window manager in .xinitrc, and then from the
> > > command prompt, as a normal user, type "startx".
> > 
> > It is much wiser to use ~/.xsession on Debian.
> 
> Or 'update-alternatives --config x-session-manager', which provides a 
> nice menu with all installed x-session-managers and makes the setting 
> system-wide.

Indeed. What I mentioned though is minor in the context of the OP's
issue. If xinit won't work, neither will startx. Declaring the "root
cause" to lie outside X probably isn't helpful either.


-- 
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/20140724210819.gc27...@copernicus.demon.co.uk

Re: systemd waisted 5 hours of my work time today

[Brian]

On Thu 24 Jul 2014 at 16:45:42 +0100, Sharon Kimble wrote:

> Sven Joachim  writes:
> 
> > You should be able to find them in the journal, see journalctl(1).
> > Note that that systemd clears the boot messages by default when it
> > starts getty, see [2] on how to change that.
> >
> > Cheers,
> >Sven
> >
> >
> > 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755581
> > 2. https://wiki.archlinux.org/index.php/Disable_Clearing_of_Boot_Messages
> >
> Thanks for this, this is the error message that I saw
> --8<---cut here---start->8---
> Jul 23 06:34:47 london systemd[1]: Breaking ordering cycle by deleting job 
> downtimed.service/start
> Jul 23 06:34:47 london systemd[1]: Job downtimed.service/start deleted to 
> break ordering cycle starting with basic.target/start
> --8<---cut here---end--->8---

My original thought was to point you at

  http://lists.freedesktop.org/archives/systemd-devel/2013-March/009994.html

and comment 7 in

  https://bugzilla.redhat.com/show_bug.cgi?id=689861

Then #755930 and #755931 popped up.

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755930

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755931

Seems that things are well in hand.
  


-- 
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/24072014215253.17ce0b518...@desktop.copernicus.demon.co.uk

Re: Howtos and Faqs

[Brian]

On Wed 23 Jul 2014 at 17:01:14 -0700, Mike McClain wrote:

> When I started to setup my Linux computer to forward IP packets
> to my Windows computer I realized my copies for the HOWTOs are dated
> so tried to update them with 'apt-get install doc-linux-text' which
> failed. After fumbling a bit I went searching at debian.org only to
> find there is no such package in english only french, japanese and a
> couple of other languages. Nor is it to be found in the orphaned
> packages list.
> Where did it go or what is the package now called that holds the
> LDP HOWTOs and FAQs?

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614131

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668078


-- 
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/24072014221922.b995f016f...@desktop.copernicus.demon.co.uk

Re: exact name of headers for 3.14-1-486

[Harry Putnam]

Curt  writes:

> On 2014-07-23, Harry Putnam  wrote:
>>
>> Any ideas why vbox continues to report not finding header files for my
>> running kernel?
>
> I don't know. Have you installed "virtualbox-guest-dkms"?
>
> Yes, I'm answering a question with a question.

Are talking about a debian pkg?  If so then an aptitude search turns
up nothing with that name.

Even using a search like: `aptitude search virtual' turns up nothing
with the string virutalbox in 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/87ha26sazi@reader.local.lan

Re: exact name of headers for 3.14-1-486

[Harry Putnam]

Klaus  writes:

> On 23/07/14 21:36, Harry Putnam wrote:
>> uname -r:
>>
>>   3.14-1-486
>
> $ apt-cache show linux-headers-3.14-1-486
>
> 
> Depends: linux-headers-3.14-1-common (= 3.14.12-1), linux-kbuild-3.14,
> linux-compiler-gcc-4.8-x86
> Description-en: Header files for Linux 3.14-1-486
>  This package provides the architecture-specific kernel header files for
>  Linux kernel 3.14-1-486, generally used for building out-of-tree kernel
>  modules.

Thanks, but as my earlier post shows ... I do have that installed

,
|   aptitude search headers |grep ^i
| 
| i   linux-headers-3.14-1-486- Header files for Linux 3.14-1-486   
  
| i A linux-headers-3.14-1-686-pae- Header files for Linux 3.14-1-686-pae   
  
| i   linux-headers-3.14-1-all-i386   - All header files for Linux 3.14 
(meta-pack
| i A linux-headers-3.14-1-amd64  - Header files for Linux 3.14-1-amd64 
  
| i A linux-headers-3.14-1-common - Common header files for Linux 3.14-1
  
| i A linux-headers-3.14-1-common-rt  - Common header files for Linux 3.14-1-rt 
  
| i A linux-headers-3.14-1-rt-686-pae - Header files for Linux 
3.14-1-rt-686-pae  
`


-- 
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/87a97ysaks@reader.local.lan

Re: exact name of headers for 3.14-1-486

[Harry Putnam]

Curt  writes:

> On 2014-07-23, Harry Putnam  wrote:
>>
>> Any ideas why vbox continues to report not finding header files for my
>> running kernel?
>
> I don't know. Have you installed "virtualbox-guest-dkms"?
>
> Yes, I'm answering a question with a question.

I'll take my turn at it too:

Do you mean a debian pkg...?

I can't find anything under that name.  Or even just searching on
virtualbox


-- 
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/8761imsagz@reader.local.lan

Re: tune2fs: last write time is weeks or even months ago, moreover before last reboot

[Linux-Fan]

On 07/24/2014 03:44 PM, David Guyot wrote:
> Hello, there.

[...]

> I checked RAID attributes: I
> got a full scale reading on the read error rate on one of the two disks
> — in fact a 2^16 value, so I assumed this was a positive integer
> counter which reached its full scale reading — but this value disappeared
> when I tried to investigate and dropped back to zero. Already a problem
> because, as far as I know, this value just can't decrease, only increase;
> am I right to suspect a faulty hard disk ?

If it is a Hitachi, the raw read error rate can switch between 0, 1, and
the 2^16 without the disk being faulty. My only Hitachi disk also does
this and works quite well. I also remember seeing some blog/article on
the Internet explaining this behaviour but I do not currently find it.

Considering the rest of your issues, I do not know, but the slowness is
definitely a bad sign. Is a simple reboot an option?

HTH
Linux-Fan



signature.asc
Description: OpenPGP digital signature

Re: New 64bit Installation. Root partition too small--what to do?

[David Christensen]

On 07/24/2014 02:16 AM, David Baron wrote:

Going by the subject, I'd say "wipe your system drive and do another 
install, using what you have learned to do it better."



A better option is to install onto a spare drive, so that you can boot 
the old drive in case you forgot something.  The old drive then becomes 
your spare for the next go-around.




Yes, indeed. I previously complained about its partitioning with little
capability to revise it!  (I did not use LVM because it put everything in one
big physical partition which I also did not like.)


I use the "manual" partitioning option in the Debian installer.


I have a SOHO with several Wheezy Xfce machines.  I don't use LVM, ZFS, 
RAID, etc., because my needs don't require them, and because I've found 
that the administrative complexities outweigh the operational benefits.




So, want to install a more recent kernel? No room.


That means the partition containing /boot is full, or nearly so.  You 
need to allocate more space to /boot and/or / (root) when you re-install.



My system drives are partitioned as follows.  I don't need to save core 
dumps in swap, so it is smaller than RAM.  I tried running without swap, 
but my machines crashed under heavy RAM loads:


primary #1 - 0.5 GB bootable ext4 /boot
primary #2 - 0.5 GB random encrypted swap
primary #3 - 8.0 GB encrypted ext4 /


My bulk data fits on one encrypted ext4 drive, which is in one machine 
and is shared via Samba.  The same drive and machine also provides 
Approx and CVS services.  My backups, archives, and system images are on 
various encrypted ext4 drives that I can plug into any machine (via 
mobile docks/ caddies and/or external drives).  I keep my desktop very 
light and install Xfce on all the machines, so I can move my desktop to 
another machine easily.



HTH,

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/53d18b9c.2080...@holgerdanske.com

Re: /var partition seems locked or read only

[Linux-Fan]

On 07/24/2014 10:56 AM, berenger.mo...@neutralite.org wrote:
[...]
> # df -i
> Sys. de fichiers Inœuds IUtil. ILibre IUti% Monté sur
> /dev/sda3610800  46946 5638548% /
> udev 506659376 5062831% /dev
> tmpfs507294339 5069551% /run
> tmpfs507294  2 5072921% /run/lock
> tmpfs507294  2 5072921% /run/shm
> /dev/sda2  1152286866   25% /boot
> /dev/sda5  9568   1246   8322   14% /home
> /dev/sda7243840 15 2438251% /tmp
> /dev/sda6 13952  13952  0  100% /var
> 
> I guess that I need to delete files to have a temporary resolution of
> the problem, but how can I avoid it to come back?

You could either recreate the filesystem with more inodes (as already
suggested) or give xfs (aptitude install xfsprogs) a try. IIRC, xfs
performs very well in situations where other filesystems' inode counts
are exceeded. Note however, that I have not ever used xfs myself -- I am
merely reciting what I have read.

HTH
Linux-Fan




signature.asc
Description: OpenPGP digital signature

Re: [SOLVED] Re: inserting kernel modules on startup

[Gary Dale]

On 24/07/14 04:48 PM, Michael Biebl wrote:

Am 24.07.2014 21:45, schrieb Gary Dale:

On 24/07/14 03:05 PM, Sven Joachim wrote:

On 2014-07-24 20:42 +0200, Gary Dale wrote:


I think you missed the point. The blacklist was in fglrx.conf where it
makes sense to not load the radeon module if I'm loading the fglrx
proprietary one. Again, this was necessary back when I was playing
around with the fglrx driver. I would have expected the system to only
parse the .conf files of modules it was loading.

Files under /etc/modprobe.d do not necessarily "belong" to any modules,
so this is not possible.  Any file there whose name ends in ".conf" will
be parsed.

Cheers,
 Sven

Sorry but that doesn't make much sense to me. The files I have in
/etc/modprobe.d all look like they belong to kernel modules. Moreover,
the directory is related to modules.

It is like Sven says.
When you run modprobe, it will parse /etc/modprobe.conf and all files in
/etc/modprobe.d/ ending with .conf
It doesn't really matter how they are named.

So you could have named fglrx.conf foo.conf, that wouldn't have made a
difference.

So, after dropping the blacklist, you can also drop "radeon" from
/etc/modules. As already mentioned it will be autoloaded by udev.

Cheers,
Michael


I'm not disputing that it happens. I'm just looking for a reasonable 
explanation for what appears to be an unreasonable behaviour. Shouldn't 
the .confs be checked just once to build an internal representation of 
the modules rules, so that if fglrx is needed, it would block radeon and 
vice-versa?


As it stands, instead of the .conf files telling you how to configure 
the system for that module, you have to look at all the .confs to figure 
out what will happen. This kind of defeats the purpose of breaking the 
configuration into separate files for each module.


I grant that doing it differently is probably a bit more complex to 
program, but it would make life easier for system administrators. Why 
should someone have to look at the configuration for a module that isn't 
being used to debug a problem with a module that is?


In keeping with the configuration method of systemd, why shouldn't the 
computer do the sorting out?



--
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/53d195a8.1070...@torfree.net

Re: [SOLVED] Re: inserting kernel modules on startup

[Michael Biebl]

Am 25.07.2014 01:24, schrieb Gary Dale:
> As it stands, instead of the .conf files telling you how to configure
> the system for that module, you have to look at all the .confs to figure
> out what will happen. This kind of defeats the purpose of breaking the
> configuration into separate files for each module.


Well, yeah. This might be a misunderstanding on your part.
You'll have to look at all the files combined as a whole, and not a
single one.



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

Re: Lost high res desktop settings on vbox upgrade to 4.3.14

[Harry Putnam]

Yusaku OGAWA  writes:

> Harry Putnam  wrote:
>> ***
>> Warning: unsupported pre-release version of X.Org Server installed.  Not
>> installing the X.Org drivers.
>>  ...done.
>> ***
>
> Hi,
>
> Did you upgrade X Server?
>
> It seems that the X.Org Server version 1.*.99 installed on your jessie.
>
> So I think, maybe you should re-execute VBoxLinuxAdditions.run script
> after upgrade "xserver-xorg-core" package to latest version.
>
> You can check your X Server's version.
>
>   $ Xorg -version

I think you hit the jackpot there... I had the version you reference
above so upgraded it.

Then along with Klaus mention of the dkms pkg which was NOT installed.

So those 2 things together has solved my problem... (Along with a step
already taken which was advised by yet another poster (Install an as
yet not released newer version of the guest additions 4.3.15)

No its smooth sailing.  My debian guest picks up the resolution as I
expand it, all the way to my monitors 1900 X 1280... very nice

Thank you sir for the great coaching


-- 
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/87oawee20n@reader.local.lan

Re: Lost high res desktop settings on vbox upgrade to 4.3.14

[Harry Putnam]

Klaus  writes:

[...]

>> 
>> 
> Could it be that you don't have dkms installed on the virtual machine?
> What response do you get for:
>
> $ apt-cache policy dkms

That was certainly 1 large part of the problem.

That command showed that there was no dkms pkg installed.  So I
installed it.

Then fixed the problem that Yusaku O pointed out:

Yusaku wrote:
,
| Did you upgrade X Server?
| 
| It seems that the X.Org Server version 1.*.99 installed on your jessie.
| 
| So I think, maybe you should re-execute VBoxLinuxAdditions.run script
| after upgrade "xserver-xorg-core" package to latest version.
| 
| You can check your X Server's version.
| 
|   $ Xorg -version
`

Upgraded the server as suggested.

Then one more part of the puzzle... This may have been on a thread in
a different group but somewhere in my queries someone recommended me
to install the newest (as yet unreleased guest additions 4.3.15) which
I also did.

Put it all together and away we go now my resolution increased as
I expand the guest window... all the way up to my monitors 1900 x
1280.  Very nice.

Thank you sir for you kind advice.

 


-- 
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/87k372e1o8@reader.local.lan

Re: [SOLVED] Re: inserting kernel modules on startup

[Gary Dale]

On 24/07/14 08:00 PM, Michael Biebl wrote:

Am 25.07.2014 01:24, schrieb Gary Dale:

As it stands, instead of the .conf files telling you how to configure
the system for that module, you have to look at all the .confs to figure
out what will happen. This kind of defeats the purpose of breaking the
configuration into separate files for each module.


Well, yeah. This might be a misunderstanding on your part.
You'll have to look at all the files combined as a whole, and not a
single one.

Isn't that what I said? I'm asking for how this makes sense.

Shouldn't each module be a self-contained configuration? If a module is 
needed, why should the configuration of a non-used module interfere? 
This strikes me as a design flaw, not a feature.



--
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/53d1a1af.1090...@torfree.net

systemd support for init level use case

[Gregory Seidman]

I'm on stable, but I'm reading the threads about systemd and I want to be
prepared for the next stable release. I run a RAID1 with an encryption loop
and LVM on top of that for my home directories and a number of data volumes
(i.e. nothing system-critical like /usr or /var).

I boot into init level 2, which does not bring up the RAID, much less
encryption, LVM, or mounted filesystems. I then log in as root on the
console and run a script to bring up the additional filesystems,
particularly the encryption. This requires interaction to supply the
password. Once the filesystems are mounted, the script runs /sbin/telinit 3
to start additional services which depend on those filesystems (apache2,
exim4, fetchmail, etc.).

I don't always want to bring everything up, and I certainly don't want boot
to hang on user input waiting for the encryption password. Does systemd
have some init level equivalent? Should I be modeling my script as several
custom systemd services (which are not automatically started), including
some virtual service that depends on all the ones I'm currently bringing up
as init level 3?

Note that I am not complaining about the upcoming switch to systemd, just
trying to understand and prepare for the implications for my particular
needs.

--Greg


-- 
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/20140724234317.ga23...@anthropohedron.net

Re: HTML5 => png or HTML5 => jpg.

[Jerry Stuckle]

On 7/24/2014 12:30 PM, pe...@easthope.ca wrote:
> From: Jerry Stuckle 
> Date: Wed, 09 Jul 2014 12:20:37 -0400
>> How is the document revised? 
> 
> Text editor.
> 
>> is the HTML5 document always served by a web server, or 
>> can it be loaded from a file?
> 
> It is self-contained and can come from a file or from a server.
> 
>> ... put a couple of comment lines in the file - one
>> before the images and one after the images.  Then have your script
>> search for those comment lines and replace everything between them with
>> the contents of the new file.
> 
> For the text manipulations, can you recommend AWK, Perl, sed or another?
> 
> Thanks,   ... Peter E.
>  
> 

My recommendation would be whatever you're most familiar with.  Almost
any language (except maybe ALGOL) can do text manipulation.  But I
wouldn't recommend learning an entirely new language just to do one job.

Of course, if you're not a programmer, you might want to enlist the help
of a friend who could help you.  Cheaper than hiring a consultant )

Jerry


-- 
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/53d1a635.8090...@attglobal.net

PARTIALLY SOLVED: no display manager for 3 days

[Alan Simpson-Vlach]

> On Thu 24 Jul 2014 at 10:37:34 +, Alan Simpson-Vlach wrote:
> 
> > Ever since a dist-upgrade that installed systemd and removed
> > sysvinit-core, I have been unable to get a display manager.
> 
> The dist-upgrade would have more than this. You are using testing?
> 
> > I have tried slim, lightdm, and even installed gdm3.  Nothing works.
> > 
> > # /etc/init.d/slim/start
> > 
> > gives no error messages, but
> > 
> > # systemctl status slim.service
> > 
> > tells me that slim exited with status=1
> > 
> > The pertinent line appears to be
> > 
> > /usr/bin/X11/X: symbol lookup error: 
> > /usr/lib/xorg/modules/extensions/libglx.so: undefined symbol: LoadExtension
> > 
> > which is similar to what happens if I try xinit directly.
> > 
> > Trying lightdm I get 
> > 
> > lightdm.service start request repeated too quickly, refusing to start.
> > 
> > I think this is a systemd problem, but maybe it's a video driver problem?
> > I'm using the proprietary nvidia driver, which has been recompiled multiple 
> > times now.
> > Help, please.  I'd kinda like to have a working X11 again.
> 
> If xinit or startx will not bring up X it seems more like a video
> problem to me. How do feel about using the nouveau driver if you cannot
> fix the proprietary one?

Thanks to the list, I now have X working again.
And it was a video issue rather than anything to do with systemd.

As suggested, I did the following:

+ deleted the proprietary nvidia glx libs
+ deleted /etc/X11/xorg.conf
+ installed xserver-xorg-video-nouveau

But now I can only get 1024x768 resolution;
I have for several years been running 1600x1200 using Debian on this monitor 
and video card.

Any suggestions?

Thanks again,
--Alan


--
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/3f9d5ff5-1c3d-4c22-9b56-6a89fc6fe...@laurelschool.org

30 second wait kernel 3.14.12-1

[Hugo Vanwoerkom]

Hi,

Running Sid and sysvinit. With the recent kernel upgrade in Sid from 
3.14.10-1 to 3.14.12-1 there appeared a 30 second wait in the boot 
process. It shows up in kernel.log, like so:


...
Jul 24 21:02:30 hda5 kernel: [   11.363107] input: HDA NVidia Front Mic 
as /devices/pci:00/:00:07.0/sound/card0/input10
Jul 24 21:02:30 hda5 kernel: [   11.363743] input: HDA NVidia Rear Mic 
as /devices/pci:00/:00:07.0/sound/card0/input9
Jul 24 21:02:30 hda5 kernel: [   40.926711] Adding 19535004k swap on 
/dev/sdc8.  Priority:-1 extents:1 across:19535004k
Jul 24 21:02:30 hda5 kernel: [   40.972160] EXT4-fs (sdc5): re-mounted. 
Opts: (null)
Jul 24 21:02:30 hda5 kernel: [   41.496744] EXT4-fs (sdc5): re-mounted. 
Opts: errors=remount-ro

Jul 24 21:02:30 hda5 kernel: [   41.977703] loop: module loaded
...

Anybody venture a guess as to what is happening? I have a 5 second 
rootdelay specified in the kernel parameter list and this happens after 
that. I get no messages during the wait.


Hugo


--
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/lqsg9s$3fo$1...@ger.gmane.org

Re: PARTIALLY SOLVED: no display manager for 3 days

[Ric Moore]

On 07/24/2014 09:00 PM, Alan Simpson-Vlach wrote:

On Thu 24 Jul 2014 at 10:37:34 +, Alan Simpson-Vlach wrote:


Ever since a dist-upgrade that installed systemd and removed
sysvinit-core, I have been unable to get a display manager.


The dist-upgrade would have more than this. You are using testing?


I have tried slim, lightdm, and even installed gdm3.  Nothing works.

# /etc/init.d/slim/start

gives no error messages, but

# systemctl status slim.service

tells me that slim exited with status=1

The pertinent line appears to be

/usr/bin/X11/X: symbol lookup error: 
/usr/lib/xorg/modules/extensions/libglx.so: undefined symbol: LoadExtension

which is similar to what happens if I try xinit directly.

Trying lightdm I get

lightdm.service start request repeated too quickly, refusing to start.

I think this is a systemd problem, but maybe it's a video driver problem?
I'm using the proprietary nvidia driver, which has been recompiled multiple 
times now.
Help, please.  I'd kinda like to have a working X11 again.


If xinit or startx will not bring up X it seems more like a video
problem to me. How do feel about using the nouveau driver if you cannot
fix the proprietary one?


Thanks to the list, I now have X working again.
And it was a video issue rather than anything to do with systemd.

As suggested, I did the following:

+ deleted the proprietary nvidia glx libs
+ deleted /etc/X11/xorg.conf
+ installed xserver-xorg-video-nouveau

But now I can only get 1024x768 resolution;
I have for several years been running 1600x1200 using Debian on this monitor 
and video card.


You might wait until they get the nvidia packages sorted out.
If you run dpkg -l |grep nvidia you'll get the list of installed nvidia 
packages, which have to be removed prior to using the run file, should 
you decide to go that route, ...which I did. I'm usually not one to go 
outside the repos, but with my setup I really needed my nvidia driver 
intact. :) Ric




--
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/53d1ca4c.80...@gmail.com

Re: 30 second wait kernel 3.14.12-1

[Michael Biebl]

Am 25.07.2014 04:44, schrieb Hugo Vanwoerkom:

> 
> Anybody venture a guess as to what is happening? I have a 5 second
> rootdelay specified in the kernel parameter list and this happens after
> that. I get no messages during the wait.

If you edit /lib/udev/net.agent and change

do_everything > /dev/null 2> /dev/null &

to

( do_everything ) > /dev/null 2> /dev/null &

is the delay gone?

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

Re: no display manager for 3 days

[Andrei POPESCU]

On Jo, 24 iul 14, 19:18:47, Alan Simpson-Vlach wrote:
> 
> sudo install xserver-xorg-video-nouveau
> 
> (My memory tells me this used to ask if I wanted my proprietary nvidia 
> setup disabled. That didn't happen this time.)
> 
> No change whatsoever.  Invoking startx/xinit still doesn't work.
> I still get the complaint about libglx.so
> 
> One respondent said maybe my GLX installation is broken.  How do I fix that? 

How did you install the nvidia driver (Debian packages?)? Please also 
post the output of 'dpkg --audit' (if any).

I've heard that switching to nouveau should be as simple as

update-alternatives --config glx

but didn't get the chance to test it myself. I'm guessing a reboot might 
also be necessary because nouveau needs KMS. If this doesn't work purge 
anything nvidia related and reboot.

If you still have problems please also attach (yes, attach) your full 
/var/log/Xorg.0.log.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: [SOLVED] Re: inserting kernel modules on startup

[Andrei POPESCU]

On Jo, 24 iul 14, 20:15:43, Gary Dale wrote:
> 
> Shouldn't each module be a self-contained configuration? If a module is
> needed, why should the configuration of a non-used module interfere? This
> strikes me as a design flaw, not a feature.

This is not really about modules, but about packages. As per policy a 
package is not allowed to change the configuration of another package, 
unless that package provides a standard interface of doing so. One of 
the most common interfaces is the .d directory, where *other* packages 
can install their own configuration.

This method allows the fglrx *package* to instruct 
module-init-tools/kmod to *not* load the radeon module, which would 
interfere with fglrx. The name of the file should be named such as to 
give a hint to the admin what package might have installed it.

It seems like you have been experimenting with fglrx in the past. No 
problem here, except that when you decided you don't need it anymore you 
should have purged (not removed) all packages.

Based on the name (and confirmed with apt-file) the file 
/etc/modprobe.d/fglrx-driver.conf the culprit is the fglrx-driver 
*package*, which you should probably purge.

Just as a side note, this package doesn't even contain the kernel 
module, that one is compiled by the fglrx-modules-dkms package.

Hope this explains,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature