public inbox for kernelnewbies@kernelnewbies.org
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Manuel Quintero F <manuel@uas.edu.mx>
Cc: james young <pronoiac+kn@gmail.com>,
	kernelnewbies@kernelnewbies.org, Ezra Buehler <ezra@easyb.ch>,
	Greg KH <greg@kroah.com>
Subject: Re: Testing 6.11.0 - No audio
Date: Fri, 27 Sep 2024 21:10:43 -0400	[thread overview]
Message-ID: <543507.1727485843@turing-police> (raw)
In-Reply-To: <CAPegGh8a+T9s0bDTOKcMG=psay8Xd2r9KMqh6aWz53qQ_tcj4w@mail.gmail.com>

On Fri, 27 Sep 2024 17:22:41 -0700, Manuel Quintero F said:
> I already have audio with the compiled kernel. I copied the
> configuration /boot/config-6.10.9-amd64
>
> I had to do it by hand, copy it and rename it to .config because the
> command shown in https://kernelnewbies.org/KernelBuild, does not work:
>
> cp /boot/config-`uname -r`* .config
>
> it shows me the error that the ".config" directory does not exist.

I'm willing to bet that you have a /boot/config-6.10.9-amd64 and also a
/boot/config-6.10.9-i686  or similar, so when you did the cp command, the *
expanded to 2 filenames.  And if there's 3 or more filenames total, the last one needs
to be the target directory to copy the 2+ preceding files into.

Moral of the story - beware of shell metacharacter expansions.
If you're unsure of what's going on, try sticking an 'echo' in front
of the command:

$ echo cp /boot/config-`uname -r`* .config

Having said that, I'm not sure what changes to make to the webpage to
avoid this issue....
\0\0\0\0\0\0\0\0

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2024-09-28  1:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25 22:33 Testing 6.11.0 - No audio Manuel Quintero F
2024-09-26  8:37 ` Greg KH
2024-09-26 21:09   ` Manuel Quintero F
2024-09-26 23:58     ` Manuel Quintero F
2024-09-27  6:12       ` Greg KH
2024-09-27  9:16         ` james young
2024-09-27 20:47           ` Manuel Quintero F
2024-09-27 21:47             ` Ezra Buehler
2024-09-27 21:55               ` james young
2024-09-28  0:22                 ` Manuel Quintero F
2024-09-28  1:10                   ` Valdis Klētnieks [this message]
2024-09-28  5:29             ` Greg KH
2024-09-28 16:34 ` Aruna Hewapathirane
2024-09-28 23:32   ` Manuel Quintero F
2024-09-29 16:24     ` Aruna Hewapathirane

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=543507.1727485843@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=ezra@easyb.ch \
    --cc=greg@kroah.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=manuel@uas.edu.mx \
    --cc=pronoiac+kn@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox