69595 – ramdisk behavior for svcdir no longer needed ?

Bug 69595 - ramdisk behavior for svcdir no longer needed ?

Summary: ramdisk behavior for svcdir no longer needed ?

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] baselayout (show other bugs)
Hardware:	All All

Importance:	High normal (vote)
Assignee:	Gentoo Cluster Team

URL:
Whiteboard:
Keywords:

Duplicates (1):	70347 (view as bug list)
Depends on:
Blocks:

Reported:	2004-10-31 03:18 UTC by SpanKY
Modified:	2010-09-10 19:00 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description SpanKY gentoo-dev

2004-10-31 03:18:38 UTC

currently the ramdisk for svcdir behaves like this:
mount ramdisk on /mnt/.init.d
run critical services (checkroot/checkfs/localmount/etc...)
mount bind /mnt/.init.d to /var/lib/init.d

since the critical services step doesnt require the dependency system (and thus the svcdir), is there any reason for keeping this behavior ?

ideally we'd move the entire svcdir setup after critical services and get rid of /mnt/.init.d all together ...

we're asking you because we wanted to make sure we didnt go around breaking specialized systems

Comment 1 Donnie Berkholz (RETIRED) gentoo-dev

2004-11-03 23:05:37 UTC

The main potentially relevant specialized systems that come to mind are:
(1) diskless nodes, and
(2) systems mounting /var (or anything else) from elsewhere, perhaps via NFS.

If you can figure out what would happen in both of those cases, you're safe as far as what I can think of.

Comment 2 SpanKY gentoo-dev

2004-11-07 22:23:36 UTC

*** Bug 70347 has been marked as a duplicate of this bug. ***

Comment 3 SpanKY gentoo-dev

2004-11-13 15:04:52 UTC

now in cvs