Hello,
I did not seem to find this topic in this list - I hope it is the right
place to discuss that.
The problem is - mounting UFS under Linux and to provide
both - R and W options.
So far I have found that R is easily implemented but Write option is
quite dangerous -
it harms the filesyste
Hi,
What processor is in ? If prior 486 try woody.
New debian kernels don't support less 486 processors.
regards
Eugen Paiuc
On Sat, 2006-11-04 at 00:24 -0500, Name Withheld wrote:
> Can anyone tell me, or point me towards something that will explain what is
> the minimum I need to put into
Can anyone tell me, or point me towards something that will explain what is
the minimum I need to put into an initrd image to satisfy init and complete
the boot process?
I have a kernel that I can load into an old i386, that fails at the point
where it tries to open /dev/console, and fails to
Processing commands for [EMAIL PROTECTED]:
> reassign 396879 linux-2.6
Bug#396879: linux-source-2.6.18-3 problem
Warning: Unknown package 'linux'
Warning: Unknown package 'source'
Bug reassigned from package `linux source' to `linux-2.6'.
> --
Stopping processing here.
Please contact me if you n
On Thu, 02 Nov 2006, Roland Stigge wrote:
> Hi,
>
> you can either do this:
>
> ===
> diff -ruN initrd-tools-0.1.84.1.orig/mkinitrd initrd-tools-0.1.84.1/mkinitrd
> --- initrd-tools-0.1.84.1.orig/mkinitrd 2006-04-24 01:08:14.000
On Fri, Nov 03, 2006 at 09:17:23PM +0100, maximilian attems wrote:
>
> cryptsetup has it's own set of initramfs hooks that enable crypto root
> based on the in kernel lvm-crypto support aka via luks.
> you want to read man initramfs-tools.
>
Thanks for the hint. I was reading that skript when
hello,
On Fri, 03 Nov 2006, Hadmut Danisch wrote:
> Hi,
>
> I just saw in /usr/sbin/mkinitramfs that the code pieces for mdadm and
> lvm are intended to be removed after release of Etch.
yes.
> How is LVM booting intended to work after removal of these code
> pieces?
hooks. hope that the lv
Your message dated Fri, 3 Nov 2006 21:18:07 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#396924: voluntary preemption in 686 package
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Hi,
I just saw in /usr/sbin/mkinitramfs that the code pieces for mdadm and
lvm are intended to be removed after release of Etch.
How is LVM booting intended to work after removal of these code
pieces?
( I am just updating a initrd script for booting from encrypted LVM
volumes and would like to
Package: kernel
Severity: wishlist
*-686 package could use voluntary preemption to reduce latency
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: linux source
Version: 2.6.18-3
I have compiled the kernel and when the computer boots, after grub has
loaded, I get the following error:
CPU: 1
EIP: 0060:[] Not tainted VLI
EFLAGS: 00010246 (2.6.18 #1)
EIP is at 0xc00f0488
eax: b100 ebx: ecx: 2504 edx: 25808086
esi: 0
Accepted:
initramfs-tools_0.85a.dsc
to pool/main/i/initramfs-tools/initramfs-tools_0.85a.dsc
initramfs-tools_0.85a.tar.gz
to pool/main/i/initramfs-tools/initramfs-tools_0.85a.tar.gz
initramfs-tools_0.85a_all.deb
to pool/main/i/initramfs-tools/initramfs-tools_0.85a_all.deb
Override entries
initramfs-tools_0.85a_amd64.changes uploaded successfully to localhost
along with the files:
initramfs-tools_0.85a.dsc
initramfs-tools_0.85a.tar.gz
initramfs-tools_0.85a_all.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "u
Hey betsy messina,
0 closing costs. We have the best quotes.
www.ibespr.com/16r
Great for re finance or new purchase
Respects,
Erik Peel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
14 matches
Mail list logo
