So i got my partition back, and succesfully mounted it. All
the old data was there. Now i just need my old slice on that
partition back.
Here's what happend in chronological order of what i did:
- I boot 4.4 installdisk to fix mbr
- I set ad0s1 as bootable, and write changes
- Then i boot to HD ins
I'm so ashamd for sending the answer right after the question:
So i found T(Toggle Newfs) option in sysinstall's label editor,
and made that one partition i had in it. Then the label editor
used fsck_ffs to recover it. I JUST LOVE FREEBSD!!
Just when i thought all my data was lost!
Well, atleast so
Hello hackers,
I am a board member of the Dutch Unix Users Group, and we would like to
make a DVD with several free/open UNIX releases together with the Dutch
Hobby Computer Club/UNIX.
The DVD boots a program that lets the user select the OS (s)he wants to
install, and then pseudo-boots the boot
Clifton Royston <[EMAIL PROTECTED]> writes:
> For a large temporary file system which must hold short-lived files,
> mostly small but occasionally several very large ones (e.g. 100MB+), is
> it better for performance and stability if this file system:
>
> 1) resides on a swap-backed MFS and tru
Walter Belgers wrote:
Hello hackers,
I am a board member of the Dutch Unix Users Group, and we would like to
make a DVD with several free/open UNIX releases together with the Dutch
Hobby Computer Club/UNIX.
The DVD boots a program that lets the user select the OS (s)he wants to
install, and then ps
On Saturday 23 October 2004 03:14 am, you wrote:
> Anish Mistry wrote:
> >On Friday 22 October 2004 02:55 pm, Erik Udo wrote:
> >>My boot loader wansn't working properly and i didn't find my 5.2.1
> >>install cd, so i grabbed 4.4(or is that 4.6) install cd, and chose fdisk,
> >>marked the freebsd p
> If you have done any testing, that should be sufficent.
I've done a little testing under various loads. The driver switches
chip to store and forward mode soon during initial use after attaching
(I also get few messages about watchdog timeouts together with
"increasing TX threshold"). But it s
On Fri, Oct 22, 2004 at 12:32:40PM -1000, Clifton Royston wrote:
> I have seen some conflicting information posted about this in the
> past, and I figure this is the best place to get an authoritative
> answer.
>
> For a large temporary file system which must hold short-lived files,
> mostly s
On Sat, Oct 23, 2004 at 01:12:46PM -0500, Ryan Sommers wrote:
> >
> >You can also use md(4). In my case I use it for /tmp.
> >
> MFS is the same thing as md(4). mfs = Memory File System, md = Memory
> Disk. Difference is only in the name.
I thought mfs is allocated from virtual memory, while md -
Hello all,
I've added a -h flag to pstat(8)/swapinfo(8) that works much like the -h
flag of du(1), ls(1) and other tools. Does anyone see something that is
obviously wrong with this, or have a better idea about implementing it?
The diff is against pstat in 6.0-CURRENT.
--- pstat-humanize.patch
On 2004-10-23 21:29, Giorgos Keramidas <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I've added a -h flag to pstat(8)/swapinfo(8) that works much like the -h
> flag of du(1), ls(1) and other tools.
I only have ony swap device and failed to notice that a total is printed
for ndevs > 1. This second t
On Sat, 23 Oct 2004, Igor Pokrovsky wrote:
> On Sat, Oct 23, 2004 at 01:12:46PM -0500, Ryan Sommers wrote:
> > >
> > >You can also use md(4). In my case I use it for /tmp.
> > >
> > MFS is the same thing as md(4). mfs = Memory File System, md = Memory
> > Disk. Difference is only in the name.
>
[EMAIL PROTECTED] wrote:
I've done a little testing under various loads. The driver switches
chip to store and forward mode soon during initial use after attaching
(I also get few messages about watchdog timeouts together with
"increasing TX threshold"). But it seems to work OK.
I haven't done any
13 matches
Mail list logo
