On Sat, 7 Jun 2003, P Oscar Boykin wrote:
> On Sat, Jun 07, 2003 at 02:06:20PM +0200, Thomas Winischhofer wrote:
> > /etc/mtab is no configuration file. This file is used by the mount
> > command to store the currently mounted devices. It is written to
> > everytime you mount/unmount a device.
>
On Sat, Jun 07, 2003 at 02:06:20PM +0200, Thomas Winischhofer wrote:
> /etc/mtab is no configuration file. This file is used by the mount
> command to store the currently mounted devices. It is written to
> everytime you mount/unmount a device.
Just out of curiosity, why isn't /etc/mtab in the v
Gaudenz Steinlin wrote:
I had the same problem. i noticed, that when booting with init=/bin/sh
mount reports /proc already mounted, which seems very strange to me.
I then deleted /etc/mtab (don't forget to sync!) and now everything
works fine. So there must have been somthing wrong with /etc/mta
Am Don, 2003-06-05 um 11.17 schrieb Thomas Winischhofer:
> I solved the problem that /proc was not mounted.
>
> The reason is the file "keymap.sh" (part of console-common, version
> 0.7.22), which in the subroutine reset_kernel() in a loop
>
> - mounts -n /proc
> - executes sysctl
> - and then u
The ALSA problem is solved,too. It didn't like to be compiled with gcc 3.3.
Thomas
Michel Dänzer wrote:
On Wed, 2003-06-04 at 17:09, Thomas Winischhofer wrote:
Michel Dänzer wrote:
In fstab, I have (like on all my x86 machines)
proc /procproc defaults 00
What the heck...
I solved the problem that /proc was not mounted.
The reason is the file "keymap.sh" (part of console-common, version
0.7.22), which in the subroutine reset_kernel() in a loop
- mounts -n /proc
- executes sysctl
- and then umounts -n /proc
with the result, that
- the first mount outputs "/pr
On Wed, 2003-06-04 at 17:09, Thomas Winischhofer wrote:
> Michel Dänzer wrote:
> >>In fstab, I have (like on all my x86 machines)
> >>
> >>proc /procproc defaults 00
> >>
> >>What the heck...?
> >
> >
> > I have
> >
> > none/proc procdefaults0 0
> > ^^
Michel Dänzer wrote:
In fstab, I have (like on all my x86 machines)
proc /procproc defaults 00
What the heck...?
I have
none/proc procdefaults0 0
but I don't expect that to make a difference? You may have to boot with
init=/bin/sh and start each
On Wed, 2003-06-04 at 12:31, Thomas Winischhofer wrote:
>
> Although I didn't touch any init script or /etc/fstab, during the init
> phase for runlevel 2 many scripts complain about an empty /proc
> directory. Indeed, after "Mounting local filesystems" it prints "/proc
> is already mounted" - b
On Wed, Jun 04, 2003 at 12:31:44PM +0200, Thomas Winischhofer wrote:
> 3) Power management
>
> This one might be related to ALSA, but since I put an "exit 0" in
> init.d/alsa, perhaps not... However: snooze, which worked perfectly
> previously, now also freezes the machine. The display goes dar
OoO Pendant le temps de midi du mercredi 04 juin 2003, vers 12:31,
Thomas Winischhofer <[EMAIL PROTECTED]> disait:
> ALSA worked fine with 0.9.0beta10. Now I updated to 0.9.3 (or whatever
> is current in sid), and it does not work at all. In fact, it modprobes
> some i2c modules and presumably snd
Jeroen Roovers wrote:
4) XFree strangeness
In my B/W Power Mac G3 there's room for 64 PCI interrupts, and an X
tool such as xosview reports about 48 of them. In my dual Pentium
133MHz Hewlett-Packard desktop from 1995 (when PCI 1.x was only just
starting to get integrated in high-end mainst
Jeroen Roovers wrote:
> On 4 Jun 2003 at 12:31, Thomas Winischhofer wrote:
>
>
>
>> 4) XFree strangeness
>>
>> Altough I use the same XF86Config-4 like before with Woody, X failed
>> to come up with sid. lspci revealed that the VGA adapter has PCI ID
>> 0:10.0, while my old XF86Config-4, which -
After moving from woody to sid (using the very same kernel, some
2.4.18-benX, which has worked flowlessly for more than 1 year, including
power management, sound, etc), I face the following problems on an ibook
1 (it's one of these dual-colored almost round plastic boxes, this one
is orange).
14 matches
Mail list logo
