> but what is your point? that people should just be able to guess at
> commands and the system should do whatever the user is thinking it will
> do?
>
f...@trout:~> lame
If 'lame' is not a typo you can use command-not-found to lookup the
package that contains it, like this:
cnf lame
f...@t
Song Li wrote:
On Fri, Jan 22, 2010 at 9:20 AM, Marc Espie wrote:
On Fri, Jan 22, 2010 at 07:43:31AM +0100, Song Li wrote:
What seems a little counter intuitive to me is: I would see sd0 as a
shortcut of /dev/sd0 for fdisk, but "fdisk /dev/sd0" does not work.
It's not, as miod pointed out.
I
Am 22.01.10 09:31, schrieb Song Li:
On the other hand, IMHO, a system should allow its user's reasonable
assumption. It would be a headache for everyone if we have to memorize
the exact syntax for every single command.
For me, OpenBSD is perfectly reasonable and easy to use. Even as I
started
On Fri, 22 Jan 2010, Otto Moerbeek wrote:
On Thu, Jan 21, 2010 at 11:34:48PM -0800, Johan Beisser wrote:
You could makefs on /dev/sd0c instead. Nothing really forces you to
create other slices (or partitions) on the device.
Bad advice. disklabel does not record some redundant information for
On Fri, Jan 22, 2010 at 09:31:31AM +0100, Song Li wrote:
> The man page for fdisk matches the actual OS. There is no typo.
>
> On the other hand, IMHO, a system should allow its user's reasonable
> assumption. It would be a headache for everyone if we have to memorize
> the exact syntax for every
On Fri, Jan 22, 2010 at 09:31:31AM +0100, Song Li wrote:
> On Fri, Jan 22, 2010 at 9:20 AM, Marc Espie wrote:
> > On Fri, Jan 22, 2010 at 07:43:31AM +0100, Song Li wrote:
> >> What seems a little counter intuitive to me is: I would see sd0 as a
> >> shortcut of /dev/sd0 for fdisk, but "fdisk /dev/
Song Li wrote:
On the other hand, IMHO, a system should allow its user's reasonable
assumption. It would be a headache for everyone if we have to memorize
the exact syntax for every single command.
You don't need to. You can look in manpages whenever you need, as I do.
Maybe it's more so for
On Fri, Jan 22, 2010 at 9:20 AM, Marc Espie wrote:
> On Fri, Jan 22, 2010 at 07:43:31AM +0100, Song Li wrote:
>> What seems a little counter intuitive to me is: I would see sd0 as a
>> shortcut of /dev/sd0 for fdisk, but "fdisk /dev/sd0" does not work.
>
> It's not, as miod pointed out.
>
> Is it
On Fri, Jan 22, 2010 at 07:43:31AM +0100, Song Li wrote:
> What seems a little counter intuitive to me is: I would see sd0 as a
> shortcut of /dev/sd0 for fdisk, but "fdisk /dev/sd0" does not work.
It's not, as miod pointed out.
Is it something you tried to "deduce" on your own ? or some misinfor
On Thu, Jan 21, 2010 at 11:54 PM, Otto Moerbeek wrote:
>> You could makefs on /dev/sd0c instead. Nothing really forces you to
>> create other slices (or partitions) on the device.
>
> Bad advice. disklabel does not record some redundant information for
> the c partitiion. Which may bite you in ca
On Thu, Jan 21, 2010 at 11:34:48PM -0800, Johan Beisser wrote:
> On Thu, Jan 21, 2010 at 10:43 PM, Song Li wrote:
> > On Fri, Jan 22, 2010 at 6:44 AM, Bret S. Lambert
> > wrote:
> >> On Fri, Jan 22, 2010 at 05:42:25AM +0100, Song Li wrote:
>
> > "fdisk sd0" is not a problem to me now either aft
On Thu, Jan 21, 2010 at 10:43 PM, Song Li wrote:
> On Fri, Jan 22, 2010 at 6:44 AM, Bret S. Lambert
> wrote:
>> On Fri, Jan 22, 2010 at 05:42:25AM +0100, Song Li wrote:
> "fdisk sd0" is not a problem to me now either after I've seen Aaron's
> comments on fdisk. The problem on mount still exists
On Fri, Jan 22, 2010 at 1:43 AM, Song Li wrote:
> I happen to have FreeBSD 6.4 in hand. The following commands work as
> expected:
>
> fdisk ad4
> fdisk /dev/ad4
> fdisk da0
> fdisk /dev/da0
> mount /dev/ad4s4 /mnt/openbsd
> mount -t msdosfs /dev/da0s1 /mnt/usb
>
> and the following commands do no
> What seems a little counter intuitive to me is: I would see sd0 as a
> shortcut of /dev/sd0 for fdisk, but "fdisk /dev/sd0" does not work.
It isn't. `sd0' is actually a shortcut for `/dev/rsd0c'; there is no
/dev/sd0 at all. (If you want to know more about this particular name
expansion, look at
On Fri, Jan 22, 2010 at 6:44 AM, Bret S. Lambert
wrote:
> On Fri, Jan 22, 2010 at 05:42:25AM +0100, Song Li wrote:
>> Hi,
>>
>> Here comes a question again: what's the naming convention of the
>> device on OpenBSD?
>>
>> I am still using the newly installed OpenBSD release 4.6.
>>
>> It did take m
On Fri, Jan 22, 2010 at 05:42:25AM +0100, Song Li wrote:
> Hi,
>
> Here comes a question again: what's the naming convention of the
> device on OpenBSD?
>
> I am still using the newly installed OpenBSD release 4.6.
>
> It did take me some effort to find out the name of device for me to
> use wit
Hi Johan,
Thank you for the info. They are quite helpful. It seems like I have
to read quite some documents on the same things I have been used to
work with on Linux and FreeBSD ...
On Fri, Jan 22, 2010 at 6:04 AM, Johan Beisser wrote:
> On Thu, Jan 21, 2010 at 8:42 PM, Song Li wrote:
>
>> For
On Thu, Jan 21, 2010 at 8:42 PM, Song Li wrote:
> For the mount device: what's the device naming convention and the
> rationale behind it? I do not think it's a good idea to search through
> all the device and find out the device name. Linux and FreeBSD use
> slightly different convention but the
Hi,
Here comes a question again: what's the naming convention of the
device on OpenBSD?
I am still using the newly installed OpenBSD release 4.6.
It did take me some effort to find out the name of device for me to
use with fdisk and mount:
fdisk /dev/rwd0c
and
mount /dev/sd0i
The first one is
19 matches
Mail list logo
