From: David Combs on
In article <g29ilk$2bb$1(a)bluegill.adi.com>,
Thomas Schulz <schulz(a)adi.com> wrote:
>In article <g2739f$mb5$1(a)reader2.panix.com>,
>David Combs <dkcombs(a)panix.com> wrote:
>>In article <bYednZuySIkfsdjVnZ2dnUVZ_tfinZ2d(a)comcast.com>,
>>Richard B. Gilbert <rgilbert88(a)comcast.net> wrote:
>>...
>>>
>>>I believe, that we would call a skip a "dumpster"! Ultra 5s make high
>>>tech doorstops! I have one that I haven't powered up in several years!
>>>It was the first Sun box I ever owned but I have replaced it with an
>>>Ultra 10; same MOBO but bigger power supply and more physical space to
>>>install RAM (the 256 MB DIMMs won't fit in the Ultra 5), two hard drive
>>>bays instead of one, etc.
>>
>>OOPS! Ultra TWENTY-5. the one they came out with just last year
>>or so.
>>
>>What do I know about these things? Three names, so far: sun 3/160 (1986)
>>("rack" went up to the ceiling), then the wonderful sparstation 5,
>>and now the blade100, which just went past end of life (no sunservice
>>available any more). And each time, only one of them.
>>
>>Thanks so much for explaining that skip term, guys. Would be a bit
>>embarrassing trying to order the "super-fast" ultra 5!
>>
>>
>>Back to the main question: This symlink-scheme outta work, right?
>
>
>It may not work correctly. If some patch runs a package check then
>the fact that a directory was replaced by a symlink will show up and
>cause problems. Better might be a loopback mount.


Looks interesting. Looks VERY intersting! If only I understood it? :-(


I could sure use some education on this -- and I bet there are others
here just like me!



Thanks!

David


From: Reginald Beardsley on
David Combs wrote:

[snip]

>
> Looks interesting. Looks VERY intersting! If only I understood it? :-(
>
>
> I could sure use some education on this -- and I bet there are others
> here just like me!
>
>
>
> Thanks!
>
> David
>
>

David,

Surprisingly easy. This is a commented console log from doing it on my
system. RTFM of course ;-)

1) create a large file somwhere

# dd if=/dev/zero of=zero.dat bs=1024k count=1024
1024+0 records in
1024+0 records out

2) associate a block device w/ the file

# lofiadm -a /scr/tmp/zero.dat

/dev/lofi/2

3) create a filesystem on the block device

# newfs /dev/lofi/2
/dev/rlofi/2: Unable to find Media type. Proceeding with
system determined parameters.
newfs: construct a new file system /dev/rlofi/2: (y/n)? y

/dev/rlofi/2: 2097000 sectors in 3495 cylinders of 1 tracks, 600
sectors
1023.9MB in 219 cyl groups (16 c/g, 4.69MB/g, 2240 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 9632, 19232, 28832, 38432, 48032, 57632, 67232, 76832, 86432,
2006432, 2016032, 2025632, 2035232, 2044832, 2054432, 2064032, 2073632,
2083232, 2092832

4) mount the file system in the desired place

# mount -F ufs /dev/lofi/2 /mnt

5) verify it's there

# df -h
Filesystem size used avail capacity Mounted on

[snip]

/usr/lib/libc/libc_hwcap2.so.1
32G 16G 15G 52% /lib/libc.so.1
/dev/lofi/2 961M 1.0M 902M 1% /mnt


Pretty cool, huh?

Have Fun!
Reg
From: David Combs on
In article <48605e19$0$4086$bbae4d71(a)news.suddenlink.net>,
Reginald Beardsley <user(a)example.net> wrote:
>David Combs wrote:
>
>[snip]
>
>>
>> Looks interesting. Looks VERY intersting! If only I understood it? :-(
>>
>>
>> I could sure use some education on this -- and I bet there are others
>> here just like me!
>>
>>
>>
>> Thanks!
>>
>> David
>>
>>
>
>David,
>
>Surprisingly easy. This is a commented console log from doing it on my
>system. RTFM of course ;-)
>
>1) create a large file somwhere
>
> # dd if=/dev/zero of=zero.dat bs=1024k count=1024
> 1024+0 records in
> 1024+0 records out
>
>2) associate a block device w/ the file
>
> # lofiadm -a /scr/tmp/zero.dat
>
> /dev/lofi/2
>
>3) create a filesystem on the block device
>
> # newfs /dev/lofi/2
> /dev/rlofi/2: Unable to find Media type. Proceeding with
> system determined parameters.
> newfs: construct a new file system /dev/rlofi/2: (y/n)? y
>
> /dev/rlofi/2: 2097000 sectors in 3495 cylinders of 1 tracks, 600
> sectors
> 1023.9MB in 219 cyl groups (16 c/g, 4.69MB/g, 2240 i/g)
>super-block backups (for fsck -F ufs -o b=#) at:
> 32, 9632, 19232, 28832, 38432, 48032, 57632, 67232, 76832, 86432,
> 2006432, 2016032, 2025632, 2035232, 2044832, 2054432, 2064032, 2073632,
> 2083232, 2092832
>
>4) mount the file system in the desired place
>
> # mount -F ufs /dev/lofi/2 /mnt
>
>5) verify it's there
>
> # df -h
> Filesystem size used avail capacity Mounted on
>
> [snip]
>
> /usr/lib/libc/libc_hwcap2.so.1
> 32G 16G 15G 52% /lib/libc.so.1
> /dev/lofi/2 961M 1.0M 902M 1% /mnt
>
>
>Pretty cool, huh?
>
>Have Fun!
>Reg

Thanks!

Now I go study it!


David