kernel replacement in installation media
Hi,
I bought a QNAP ts-509.
I'ld like to set up a gate, with a RAID ; I'm still waiting for the disks,
5*2T - Samsung, ecogreen, 5400rpm - to be delivered.
I've seen managing a RAID may be quite difficult. That's my first one. I
don't want to loose everything 'cause of a mistake.
I've read zfs, and RAID-Z, may be helpfull, since there's no risk to loose
data on read, and since zfs handle variable blob (is that the correct word?)
size
The thing is, it only have a 128M flash disk (seen as /dev/da0)
GENERIC needs almost 250M.
I though about using mfsBSD. But I'm not sure my drivers would be there
(since at least the RAID one is quite new in FB-8).
I tried to build nanoBSD in a 128M disk, without configuring that much
(hoping it would be nano out-of-the-box), and it failed saying no more
space on device
Moreover, every small BSD with zfs I found was a custom FreeBSD. So I
decided to make mine.
First, from a USB stick, I installed FreeBSD on an other USB stick.
Then, I looked at what I would have to get in the kernel (mainly: da, usb,
ehci, kbd, vga, bge, ...)
So I build a custom kernel, deleting some lines from the GENERIC
configuration file.
As my USB stick doesn't seem to handle write access that well, I had to
compile the kernel on a VM, and the to send/extract the tarball on the NAS.
But once installed, I still have a lot of .ko in boot/kernel. I'm not sure I
actually removed something, except symbols.
Whatever, it worked I haven't that much time. Once I'll get some, I'll also
try to reduce the /usr size.
Then, I replaced the kernel from the installation stick with mine, updated
the .mtree and checksums files, ...
But, I didn't understood, what's the generic.inf file? How can I update it?
In doubt, I deleted it. And maybe I shouldn't have. (or is it because my
kernel is not called GENERIC any more, but QNAP?!)
The thing is, the install failed, I finished it with the Fixit shell, untar
my kernel, ... it's now working
So, first question, how can I be sure I removed modules from my kernel? is
there something to add to the config file? how can I have so much if_*.ko,
while I deleted almost all device lines?
Second one, how to generate .inf files for distribs? (I may have to do it at
least for base too)
And even if it's a dirty way to do it, is it ok to update a .img file (or
the created stick)? or should I rebuild everything? (on my VM...)
Regards,
Samuel Martín Moro
{EPITECH.} tek4
CamTrace S.A.S
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: kernel replacement in installation media
On 09/10/2010 07:57 PM, Samuel Martín Moro wrote: Hi, ... The thing is, it only have a 128M flash disk (seen as /dev/da0) GENERIC needs almost 250M. I have run into something similar, while building a ZFS install to run on an Intel SS4200EHW NAS device. Utilizing a series of scripts I have developed[1], I was able to compact an entire functional FreeBSD system into 4.6MB /boot and 84MB root with mkisofs and mkuzip, without permanently tying up a bunch of the machine's limited RAM with an MFS, and with acceptable performance despite the IDE channel's speed limit of 1.6MB/sec. Plus, boot and root are read-only, so the CompactFlash card won't wear out prematurely. You can make use of src.conf(5) while building world and kernel to eliminate a lot of unnecessary userland components, and MODULES_OVERRIDE and WITHOUT_MODULES to control what modules get built, as the kernel build process will build all modules regardless of what might be in your kernel config. Be prepared to perform lots of testing, though, as a missed critical dependency can appear to succeed, but leave something else broken. [1] http://git.cyberleo.net/Mosi.git -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: kernel replacement in installation media
On 09/10/10 20:01, CyberLeo Kitsana wrote: On 09/10/2010 07:57 PM, Samuel Martín Moro wrote: Hi, ... The thing is, it only have a 128M flash disk (seen as /dev/da0) GENERIC needs almost 250M. I have run into something similar, while building a ZFS install to run on an Intel SS4200EHW NAS device. Utilizing a series of scripts I have developed[1], I was able to compact an entire functional FreeBSD system into 4.6MB /boot and 84MB root with mkisofs and mkuzip, without permanently tying up a bunch of the machine's limited RAM with an MFS, and with acceptable performance despite the IDE channel's speed limit of 1.6MB/sec. Plus, boot and root are read-only, so the CompactFlash card won't wear out prematurely. You can make use of src.conf(5) while building world and kernel to eliminate a lot of unnecessary userland components, and MODULES_OVERRIDE and WITHOUT_MODULES to control what modules get built, as the kernel build process will build all modules regardless of what might be in your kernel config. Be prepared to perform lots of testing, though, as a missed critical dependency can appear to succeed, but leave something else broken. I do believe you can omit the *.symbols files. I plan to try it myself. Would someone please confirm this? And you might look at resurrecting the picobsd method of crunching binaries into one single statically linked binary with hard links of differing file names if you want to get really small. I used to do this when compactflash was only 128MiB. Thanks, Jason C. Wells ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: kernel replacement in installation media
On Fri, Sep 10, 2010 at 10:56 PM, Jason C. Wells j...@speakeasy.net wrote I do believe you can omit the *.symbols files. I plan to try it myself. Would someone please confirm this? Yes you can remove them safely. And you might look at resurrecting the picobsd method of crunching binaries into one single statically linked binary with hard links of differing file names if you want to get really small. I used to do this when compactflash was only 128MiB. /usr/src/tools/tools/nanobsd/ /usr/src/tools/tools/tinybsd/ -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
