How to hide foreground responses?

[CentralWare]

Line added to tc-config:

Code: [Select]

mount /dev/sda1 /mnt/test >/dev/null 2>/dev/nullDuring init, when EXT2 partitions are mounted as listed above, mount throws a warning saying EXT3 is incompatible (though the mount works.)  I need to muffle the response, but the script has to run in the foreground and redirecting output is seemingly ignored as shown.  Am I doing something wrong, missing something, etc?

Thanks!

[gerald_clark]

Where in init do you think this mount takes place?

[CentralWare]

I added it (scanning contents of drive partitions)
This takes place before the command-line is processed.

[curaga]

It's a kernel message, not from mount. You can either up the kernel log level to avoid that, or use a more exact mount command (add -t ext4).

[CentralWare]

{feeling sheepish}

I hadn't realized where the message originated.  Thank you!
Modifying mount isn't really an option as the best (I can think of) to fetch the actual format is shown only as "ext" when doing an FDISK -L and the process being run here has no clue what might or might not be plugged in (ie: FAT, EXT2/3/4, NTFS, etc.)

[gerald_clark]

The output of fdisk only show what was entered as the partition type, not what filesystem is actually on the partition.
For that use blkid.

Why did you add the scan?  Rebuildfstab already scans all drives and updates /etc/fstab and adds mountpoints.  All you need to do is mount the entries already created.

[CentralWare]

Mounts were done prior to fstab being updated by tc-config.  I have many manipulation tactics going on long before tc-config launches from rcS for what you might consider a "dynamic" command line (proc/cmdline)

The concept here is to mute responses (less cluttered boot) where necessary, but there's a few I haven't been able to put a cork in.
EXT3/2 notice: Thank you Curaga for showing me what's right in front of my eyes!!!
acpi/cron...  these two are being stubborn.  They both have init.d scripts, but neither of them like being quiet.
acpid is being launched by start-stop-daemon.  Adding --quiet as well as redirecting has had no effect.
crond is being launched manually through busybox...  busybox likes to chatter.  sudo app [start] >/dev/null 2>&1 or 2>/dev/null don't seem to have a bearing on the outcome.
crond (busybox 1.20.2) started, log level 8
I'm thinking this one's due to the BB alias; which I'll be looking into.  ACPI on the other hand...  not sure of that one yet.

Thanks for taking the time to reply!