From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harry Kalogirou Subject: Re: Swap support Date: 23 Apr 2002 22:36:23 +0300 Sender: linux-8086-owner@vger.kernel.org Message-ID: <1019590559.479.178.camel@cool> References: <20020422160057.O88916-100000@agora.rdrop.com> <1019544987.479.168.camel@cool> <3CC5BDF6.66FC@havn.com> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <3CC5BDF6.66FC@havn.com> List-Id: Content-Type: text/plain; charset="iso-8859-7" To: blaz.antonic@havn.com Cc: Linux-8086 =D4=E7=ED =D4=F1=E9, 23-04-2002 =F3=F4=E9=F2 23:03, =EF/=E7 Blaz Antoni= c =DD=E3=F1=E1=F8=E5: > > I just said that the ramdisk driver doesn't report it's size, other= s > > report it just fine. There is a little structure that contains the = size > > ,among other things, of the device but ramdisk doesn't seem to upda= te > > it. >=20 > My bad, this should be easy to add. I was peeking at doshod.c when i = was > writing ramdisk driver, i must have missed the relevant part abot > updating this thing. If doshd.c does it it should be no biggie (a cou= ple > of lines of code, namely in function that creates and destroys > ramdisks). >=20 > Blaz Antonic >=20 You are right, basicaly it just needs a=20 blk_size[MAJOR][MINOR] =3D no_of_1024_byte_blocks; Harry - To unsubscribe from this list: send the line "unsubscribe linux-8086" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html