Hello,
I'm not sure wheter this is a bug or a feature... However, I just noticed
that cp(1) fails to copy /proc/cpuinfo to the file system (tested on i686 and
x86_64 lenny systems):
$ wc -l /proc/cpuinfo 200 /proc/cpuinfo
$ cp /proc/cpuinfo /tmp
$ echo $?
0
$ wc -l /tmp/cpuinfo
125 /tmp/cpuinfo
Sven Joachim --> debian-user (2009-04-01 18:07:34 +0200):
> On 2009-04-01 17:23 +0200, Jukka Salmi wrote:
>
> > Hello,
> >
> > is it possible to install a daemon from a Debian package without having
> > it automatically started afterwards?
>
> Temporaril
Hello,
is it possible to install a daemon from a Debian package without having
it automatically started afterwards?
What I want to do is to install samba, but neither smbd nor nbmd
should be started until I had a chance to edit smb.conf(5) manually...
TIA, Jukka
--
bashian roulette:
$ ((RANDO
Sven Joachim --> debian-user (2008-12-11 13:02:54 +0100):
> Have you rebuilt your initramfs? Udev and the whole /etc/udev directory
> are copied into it, so you need to run "update-initramfs -u" to have
> these rules available at boot time.
Thanks a lot, that was exactly what I was missing (hmm,
Boyd Stephen Smith Jr. --> debian-user (2008-12-08 16:46:46 -0600):
> http://reactivated.net/writing_udev_rules.html
Thanks, udev(7) is probably what I was looking for.
I tried two approaches:
1) Using built-in persistent symlinks (/dev/disk/...).
2) Writing custom rules to create symlinks t
Daniel Burrows --> debian-user (2008-12-09 06:57:48 -0800):
> On Tue, Dec 09, 2008 at 03:29:09PM +0100, Jukka Salmi <[EMAIL PROTECTED]> was
> heard to say:
[...]
> > Aptitude::UI::Default-Grouping
> > { "task,status,section(subdir,passthrough),section(to
Hi,
on a recent 4.0r5 system I tried setting the aptitude theme but failed.
I added
Aptitude::Theme "Dselect";
to ~/.aptitude/config, but aptitude simply didn't show _any_ package
anymore. Same for the "Vertical-Split" theme. Both themes _are_
defined in /usr/share/aptitude/aptitude-defaul
Hello,
I'd like the packages to be displayed sorted by status and then by
priority. Hitting `G' and then changing the given
task,status,section(subdir,passthrough),section(topdir)
to
task,status,priority,section(subdir,passthrough),section(topdir)
seems to do what I want. But I'd lik
Chris Davies --> debian-user (2008-12-05 18:15:12 +):
> I've also come across this, and it seems only to affect DELL 2950s.
> I've not logged a bug because I couldn't work out /where/ (i.e. which
> package) I should log it against.
>
> You need to boot a Rescue CD [*] and change all occurrence
Jukka Salmi --> debian-user (2008-12-07 16:27:57 +0100):
> Hello,
>
> Sven Joachim --> debian-user (2008-12-05 17:54:56 +0100):
> > On 2008-12-05 17:27 +0100, Jukka Salmi wrote:
> >
> > > I just installed Debian 4.0r5 on a i386 systems (Dell PowerEdge 2950).
Hello,
Sven Joachim --> debian-user (2008-12-05 17:54:56 +0100):
> On 2008-12-05 17:27 +0100, Jukka Salmi wrote:
>
> > I just installed Debian 4.0r5 on a i386 systems (Dell PowerEdge 2950).
> > While the installer seemed to have succeeded without problems, the
> > fres
Hello,
I just installed Debian 4.0r5 on a i386 systems (Dell PowerEdge 2950).
While the installer seemed to have succeeded without problems, the
freshly installed system didn't boot because its root file systems could
not be found:
Begin: Waiting for root file system... ...
[...]
Clive Menzies --> debian-user (2005-08-24 16:27:38 +0100):
> On (24/08/05 16:31), Jukka Salmi wrote:
> > Clive Menzies --> debian-user (2005-08-24 15:08:11 +0100):
> > > Have you tried something like:
> > >
> > > $ mdadm /dev/md2 -a /dev/hdb3
> >
Clive Menzies --> debian-user (2005-08-24 15:08:11 +0100):
> On (24/08/05 15:53), Jukka Salmi wrote:
> > Clive Menzies --> debian-user (2005-08-24 14:22:39 +0100):
> > > On (24/08/05 14:45), Jukka Salmi wrote:
> > > > a Debian 3.1 system which uses md
Clive Menzies --> debian-user (2005-08-24 14:22:39 +0100):
> On (24/08/05 14:45), Jukka Salmi wrote:
> > a Debian 3.1 system which uses md devices for all its file systems and
> > swap was reset by a power failure. On startup, the root file systems
> > md device faile
Hi,
a Debian 3.1 system which uses md devices for all its file systems and
swap was reset by a power failure. On startup, the root file systems
md device failed to configure and is in degraded mode now. I think the
failed device is probably fine, but md configuration failed due to
parity errors or
Hi Pete,
> I have a script that performs batch zipping of files. Trouble is that it
> only does one file at a time (kind of going against the "batch" idea).
> Could someone point out the silly mistake I am obviously making?
[...]
> #!/bin/sh
> #
> # batch zip
> # invoke with batchzip
> #
> # th
Roberto Sanchez --> debian-user (2004-04-08 11:20:33 -0400):
> Jukka Salmi wrote:
> >Hi,
> >
> >I just installed Debian testing on two DELL PowerEdge systems (PE 1750
> >and PE 2650). On the 1750, Debian runs fine. But on the 2650, some programs
> >segfault
Hi,
I just installed Debian testing on two DELL PowerEdge systems (PE 1750
and PE 2650). On the 1750, Debian runs fine. But on the 2650, some programs
segfault sometimes. I saw sshd, nvi, apt-get, less and dselect segfault.
However, they don't always segfault, e.g. sometimes they run, sometimes
th
Colin Watson --> debian-user (2004-01-07 14:44:43 +):
> Are you using the most current version of debootstrap from unstable? You
> always want to do this. Specifically your problem looks like:
>
> debootstrap (0.2.21) unstable; urgency=high
>
> * [sarge] Added coreutils' new predependencies
Hi,
I'm trying to install sarge on a i386 system. debootstrap fails as
follows:
# debootstrap --arch i386 sarge /troot http://
I: Retrieving debootstrap.invalid_dists_sarge_Release
I: Validating debootstrap.invalid_dists_sarge_Release
I: Retrieving debootstrap.invalid_dists_sarge_main_binary-i386
Hi,
where have the official jigdo files for sarge gone? They used to be on
http://gluck.debian.org/cdimage/testing/jigdo-area/ (they are linked
from http://www.debian.org/CD/jigdo-cd/ ("Available images")), but I get
HTTP 404...
Jukka
--
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~
--
To UNS
Colin Watson --> debian-user (2003-12-11 12:24:07 +):
> Sounds like your cron job doesn't have an appropriate path. Try setting
> PATH=/usr/bin:/bin explicitly at the top, adding any other directories
> you need.
That's it! There was a typo in cron's $PATH. Thanks a lot!
Jukka
--
bashian ro
Hello,
I still couldn't solve my problem. I stripped down the script to the
following:
$ cat ~/bin/tapetest
#!/bin/sh
cd /
/bin/tar -czf /dev/nst0 dir
echo "tar returned $?"
Running it manually gives:
$ ~/bin/tapetest
tar returned 0
...but when run from cron I get:
tar (grandchild): gzip: Can
Hi,
I wrote a script which uses tar to backup a filesystem to a Seagate DAT.
If I run the script from the shell it works fine, but when started by cron
(as root) I get this:
tar (grandchild): gzip: Cannot exec: No such file or directory
tar (grandchild): Error is not recoverable: exiting now
/dev
Hello,
every now and then I install Debian on new ix86 machines (Dell PowerEdge).
They often have hardware which is not yet supported by the kernels of the
official stable Debian release 3.0r1. So far I was using an unofficial
"stable" netinst boot CD to install the OS.
I also tried a few testing
Colin Watson --> debian-user (2003-08-20 16:50:50 +0100):
> Oh, um, sorry, let's test this time.
>
> Either use -D_FILE_OFFSET_BITS=64, in which case I believe you can
> simply drop the O_LARGEFILE option as open() will support opening large
> files by default; or else use -D_LARGEFILE64_SOURCE.
Damien Solley --> debian-user (2003-08-20 21:09:16 +1000):
> Check out:
> http://www.suse.de/~aj/linux_lfs.html
I read this article and followed the instructions, without success.
Neither compiling with '-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE'
nor adding O_LARGEFILE to the flags for open(2) wo
Damien Solley --> debian-user (2003-08-20 21:09:16 +1000):
> Also, what file system are you using? Smbfs, fat and nfs all
> have issues with lfs that ext doesn't.
I'm using ext3 and ReiserFS (3.6.x), they both have full LFS support.
But I'm having problems during compile time, so the file system s
Hi,
Colin Watson --> debian-user (2003-08-20 11:55:14 +0100):
> Try building with the -D_FILE_OFFSET_BITS=64 option. See 'info libc'
> under "Feature Test Macros" for more details.
Does not help, same result as before...
Thanks anyway,
Jukka
--
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~
-
Hello,
I'm having problems with opening large (>2 GB) files on a Debian testing
system:
---
#include
#include
#include
[...]
int fd;
fd = open(argv[1], O_RDONLY | O_LARGEFILE);
[...]
---
gcc complains that O_LARGEFILE is undeclared. However, if I
#define O_LARGEFILE 010
the program works.
Damien Solley --> debian-user (2003-08-20 19:37:28 +1000):
> Old kernel version? AFAIK, you need a recent (ish) kernel to create
> files greater than 2GB.
$ uname -sr
Linux 2.4.21-3-686-smp
It's the latest kernel from the kernel-image-2.4-686-smp package.
Greetings, Jukka
--
bashian roulette:
Hello,
I'm having problems with opening large (>2 GB) files on a Debian testing
System:
---
#include
#include
#include
[...]
int fd;
fd = open(argv[1], O_RDONLY | O_LARGEFILE);
[...]
---
gcc complains that O_LARGEFILE is undeclared. However, if I
#define O_LARGEFILE 010
the program works.
33 matches
Mail list logo
