Harry Edmon's solution works here too.
FWIW https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512757 reports the same
issue in a previous release but that was fixed. Now that problem has been
reintroduced into debian Jessie.
--
Andy, HNAS Engineering, Hitachi Data Systems
Hi Christian
> > /home/andyc/lost+found
> > /var/chroot/ia32/home/andyc/lost+found
> If those are ext{2,3,4} filesystems, the script is working as expected,
> ie those filesystems are missing the lost+found directory.
They're part of an ext4 filesystem. IE the filesystem itself is:
# ls /u277
Is there some way of configuring NetworkManager to not break it? Or fix it?
--
Andy, BlueArc Engineering
gcc-4.3 is no longer installable:
# apt-get install gcc-4.3
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution tha
> By the way, Andy, could you give a quick reminder of what you are
> using gcc 4.2 and 4.3 to do?
We have some old code that we need to maintain that won't compile with later
versions of the compiler.
--
Andy, BlueArc Engineering
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists
Hi Jonathan
> Andy Chittenden wrote:
>
> >> The toolchain in Debian has been updated to cope with that, and
> most
> >> build systems should be unaffected. If you are using a non-
> Debian
> >> toolchain to build your software and it is not
Hi Jonathan
> The toolchain in Debian has been updated to cope with that, and most
build systems should be unaffected. If you are using a non-Debian
toolchain to build your software and it is not able to cope with
multiarch, you might try to pass the following
Ø On 2011-05-29 09:44, Andreas Beckmann wrote:
Ø > Two new driver versions are available:
Ø > * 270.41.19-1 (release) in unstable
Ø* 275.09.04-1 (beta) in experimental, this fixes some regressions with KDE
Ø > Please try them.
I moved on to different hardware so cannot say whether th
> > I'm using 270.41.06-1 from unstable and the second screen is just not
> > usable. I can post a video if you'd like.
> How does your xorg.conf look like?
My xorg.conf was created/modified by nvidia-xconfig/nvidia-settings. See
attached.
> Have you tried a minimal one as described in
> /usr
I'm using 270.41.06-1 from unstable and the second screen is just not usable. I
can post a video if you'd like.
--
Andy, BlueArc Engineering
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> http://pkg-xorg.alioth.debian.org/howto/use-gdb.html
Program received signal SIGSEGV, Segmentation fault.
0x00427db0 in doListFontsAndAliases (client=0x2a230a0, c=0x2a23610)
at ../../dix/dixfonts.c:614
614 ../../dix/dixfonts.c: No such file or directory.
in ../../dix/dix
> > How do we get that change into the 2.6.32 debian packages for squeeze and
> > sid?
> I've just applied it; it should go into package version 2.6.32-28.
Thanks. I don't see that yet. How long does it normally take to become
available?
--
Andy, BlueArc Engineering
The upstream bug (https://bugzilla.kernel.org/show_bug.cgi?id=16494) has been
fixed in Linux kernel 2.6.36 by this ChangeSet:
commit 669502ff31d7dba1849aec7ee2450a3c61f57d39
Author: Andy Chittenden
Date: Tue Aug 10 10:19:53 2010 -0400
SUNRPC: fix NFS client over TCP hangs due to packet
https://bugzilla.kernel.org/show_bug.cgi?id=16494
--
Andy, BlueArc Engineering
> Or should nis say it provides nis as well as what it currently says
> it provides or instead of?
I think using LDAP as a Network Information Service (see RFC2307) may be
relevant here. I don't know whether that's possible on Linux at the moment but
I would guess that if it is (or ever will be)
having had a look at /etc/init.d/nis, I see it says:
# Provides: ypbind ypserv ypxfrd yppasswdd
So, I thought perhaps autofs shouldn't say nis in Should-Start but should say
ypbind. Having done that and rerun insserv, the start files look ok:
ws-andyc-debian64:~# ls /etc/rc*d/*{nis,
Having applied your patch to autofs and reenabling insserv, I had to reinstall
portmap to get its links in /etc/rc*d so that when nis started, the portmapper
was enabled.
Once I'd done that, autofs is still starting before nis:
ws-andyc-debian64:~# ls /etc/rc*d/*{nis,autofs}
/etc/rc0.d/K01autof
> Is the bug worth investigating, given that it occurs with a setting
> that is not deeply supported?
Well I spoke too soon saying it no longer occurs: over the weekend I
received a number of emails giving the same backtrace that I reported
originally. In syslog, there are a number of backtraces f
After much toing and froing, our domain admin managed to create me an
account and samba's now working. Now for the other 45 machines ... :-)
--
Andy, BlueArc Engineering
> Does the samba log give a more useful backtrace here?
It seems so. Here's the output from smbd in syslog:
Jan 6 08:41:12 boco smbd[27555]: [2006/01/06 08:41:12, 0]
lib/util_sock.c:get_peer_addr(1222)
Jan 6 08:41:12 boco smbd[27555]: getpeername failed. Error was
Transport endpoint is not co
> ... I strongly recommend converting your system to use
> security =
> domain instead (with the cooperation of the domain admin).
In the past that hasn't been forthcoming and that's why we've used
security = server. I'll try and persuade our new incumbants to create me
an account.
--
Andy, Blu
;
; /etc/smb.conf
;
; Sample configuration file for the Samba suite for Debian GNU/Linux
;
; Please see the manual page for smb.conf for detailed description of
; every parameter.
;
[global]
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/
22 matches
Mail list logo
