On 24/07/15 12:24 PM, Nathaniel Nelson wrote:
Hello! I hope this is the proper way to seek Debian support, and that
I'm not making a mistake/emailing the wrong list/whatever.
I've never used Debian before, and I'm trying to install it on an old
Mac Mini with a PowerPC G4 processor. I downloade
Should have re-read before I posted.
On Sat, Jul 25, 2015 at 1:36 PM, Joel Rees wrote:
> [...] but I've generally had the best success using the
> Mac OS 10 partitioning tool to set up the three Mac OS style
> partitions I use for debian, one for yaboot, one for the root
> partition, and one for
2015/07/25 1:42 "Nathaniel Nelson" :
>
> Hello! I hope this is the proper way to seek Debian support, and that I'm not
> making a mistake/emailing the wrong list/whatever.
>
There is a better list. I've cross-posted, but I haven't set the reply header.
> I've never used Debian before, and I'm tr
On Sat, Aug 25, 2007 at 12:09:34PM -0400, Frank McCormick wrote:
> Took your advice here and re-installed Hal...at least the error
> message goes away. I have no idea which package was still referring
> to Haldaemonhow would I track that down ?
>
I suppose the brute-force method would be a
On Sat, 25 Aug 2007 15:42:45 +0200
Florian Kulzer <[EMAIL PROTECTED]> wrote:
> On Sat, Aug 25, 2007 at 08:46:01 -0400, Frank McCormick wrote:
> > On Sat, 25 Aug 2007 10:23:54 +0200
> > Florian Kulzer wrote:
>
> [...]
>
> > > > > On Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote:
> >
On Sat, 25 Aug 2007 15:42:45 +0200
Florian Kulzer <[EMAIL PROTECTED]> wrote:
> On Sat, Aug 25, 2007 at 08:46:01 -0400, Frank McCormick wrote:
> > On Sat, 25 Aug 2007 10:23:54 +0200
> > Florian Kulzer wrote:
>
> [...]
>
> > > > > On Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote:
> >
On Sat, Aug 25, 2007 at 08:46:01 -0400, Frank McCormick wrote:
> On Sat, 25 Aug 2007 10:23:54 +0200
> Florian Kulzer wrote:
[...]
> > > > On Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote:
> > > > > For the past few weeks I've been seeing an error message fly by
> > > > > (doesn't see
On Sat, 25 Aug 2007 10:23:54 +0200
Florian Kulzer <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 24, 2007 at 20:46:22 -0400, Frank McCormick wrote:
> > On Fri, 24 Aug 2007 15:07:49 +0200 Florian Kulzer wrote:
> > > n Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote:
> > > > For the past few we
On Fri, Aug 24, 2007 at 20:46:22 -0400, Frank McCormick wrote:
> On Fri, 24 Aug 2007 15:07:49 +0200 Florian Kulzer wrote:
> > n Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote:
> > > For the past few weeks I've been seeing an error message fly by
> > > (doesn't seem to affect anything) a
On Fri, 24 Aug 2007 15:07:49 +0200
Florian Kulzer <[EMAIL PROTECTED]> wrote:
> n Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote:
> > For the past few weeks I've been seeing an error message fly by
> > (doesn't seem to affect anything) and I curious what's going on.
> >
> > the message
On Thu, Aug 23, 2007 at 21:25:29 -0400, Frank McCormick wrote:
> For the past few weeks I've been seeing an error message fly by (doesn't
> seem to affect anything) and I curious what's going on.
>
> the message is:
>
> dbus unknown username "haldemon" in message bus configuration file.
It shoul
David Fuchs wrote:
thanks for the help.
as I mentioned, the modules.dep file is there - but not in the initrd
image that's created.
I've addressed that same issue:
http://lists.debian.org/debian-user/2007/03/msg00772.html
and never got an answer.
modules.dep is not in the initrd of kernels t
thanks for the help.
as I mentioned, the modules.dep file is there - but not in the initrd
image that's created.
however, I've solved it by recompiling the kernel with the parallel
port driver as a module rather than into the kernel. it seems it was
this driver that tried to load some additional
On Mon, 2007-05-21 at 22:33 +0200, David Fuchs wrote:
> hi all,
>
> I want to have a grsecurity enabled kernel and thus compiled my own.
> while doing so, I also removed tons of modules from the kernel config
> (drivers I know I'll never need), and chose to compile some into the
> kernel instead o
Marco Calviani wrote:
>i've got an error (maybe a warning) during the boot up process, as
> written in /var/log/boot:
> Cleaning /tmpfind: warning: you have specified the -maxdepth option
> after a non-option argument -perm, but options are not positi
> onal (-maxdepth affects tests spe
Oops... sends message in sucky outlook... sorry. See below
for the rest of my message...
-Original Message-
From: Michael Kahle
Sent: Wednesday, March 03, 2004 11:27 AM
To: Debian User List
Subject: boot error -> cdrom: open failed.?
Hello. I recently built a 2.6.3 custom kernel for
Try
#> dmesg
to read boot messages at your leisure.
The remaining pcmcia messages probably come from scripts in etc/rc*.d/
directories. Try
#> ls -l /etc/rc*.d/ | grep pcmcia
to see which such scripts are softlinked there. I should be 'OK' to
remove those links as well as the corresponding script
dpkg --purge pcmcia-cs
Eileen Orbell wrote:
>
> Thank you that removed most of the errors. When I ran that command I did
> receive the following errors though:
> directory not empty so it could not remove all reference..
> can I delete these directories???
> I still get some reference to pcmcia o
Thank you that removed most of the errors. When I ran that command I did
receive the following errors though:
directory not empty so it could not remove all reference..
can I delete these directories???
I still get some reference to pcmcia on boot...
Thanks
At 01:41 AM 12/5/2000 +0100, you wr
On Mon, Dec 04, 2000 at 07:21:38PM -0500, Eileen Orbell wrote:
> I reconfig my kernel and now on boot I get about 5 -6 lines of error re
> PCMICIA modules. Because it boots fast I cannot read them all but I am
> assuming I am missing the modules. I do not have any PCMCIA hardware
> anyway so c
On Tue, Jun 20, 2000 at 10:32:31AM +0100, Moore, Paul wrote:
> But the message comes at bootup. AFAIK, the root FS is always mounted
> read-only in the first instance, and is then remounted read-write later in
> the boot sequence.
I think this is so.
> So this looks like a problem in the base De
AFAIK, the root filesystem is mounted read-write and remounted read-only
on errors...
Ron
On Tue, 20 Jun 2000, Moore, Paul wrote:
> From: Ron Rademaker [mailto:[EMAIL PROTECTED]
> > On Mon, 19 Jun 2000, Sven Burgener wrote:
> >
> > > Anyone know why do I get the following error upon bootup:
> >
From: Ron Rademaker [mailto:[EMAIL PROTECTED]
> On Mon, 19 Jun 2000, Sven Burgener wrote:
>
> > Anyone know why do I get the following error upon bootup:
> >
> > insmod: /lib/modules/2.2.15/misc/unix.o cannot create
> > /var/log/ksymoops/2619212757.ksyms Read Only Filesystem
> >
> Looks like
Looks like your root file system is mounted read only, try to do (as
root): touch /a (if no error occurs, don't forget to do rm /a). If it's
mounted read only, you can remount it read-write, but you better check out
your /etc/fstab.
Ron Rademaker
On Mon, 19 Jun 2000, Sven Burgener wrote:
> Hi al
On Sat, 12 Jun 1999, Kevin A. Foss wrote:
> On Thu, Jun 10, 1999 at 07:55:58AM -0700, Lazar Fleysher wrote:
> > Hi everyone,
> >
> > I have noticed that sometimes I get this boot error:
> > mktime() failed unexpectedly (rc -1). Aborting.
> > Could someone tell what and how dengerous it is?
>
> T
On Thu, Jun 10, 1999 at 07:55:58AM -0700, Lazar Fleysher wrote:
> Hi everyone,
>
> I have noticed that sometimes I get this boot error:
>
> mktime() failed unexpectedly (rc -1). Aborting.
>
> Could someone tell what and how dengerous it is?
This is probably from hwclock, it will say this if you
26 matches
Mail list logo